Confirmed Access vs Quick Access

Not rated yet. Be the first who rates this item!

We need large numbers of high quality users
Confirming access reduces the rate of user acquisition
Not confirming access reduces quality of users

D: Allow users quick access to premium data
D': Allow only confirmed users access to premium data
B: Acquire more users
C: Acquire high quality users
A: Build a database containing a large number of high quality users
Click on the icons on the arrows to see assumptions and injections
In order to Build a database containing a large number of high quality users I must Acquire more users and in order to Acquire more users I must Allow users quick access to premium data. But, in order to Build a database containing a large number of high quality users I must also Acquire high quality users and in order to Acquire high quality users I must Allow only confirmed users access to premium data. I can't both Allow users quick access to premium data and Allow only confirmed users access to premium data.
RelationAssumption(s)Injection(s)
D-D'Email is the only way to confirm high qualityUser could send the site an email with a hashcode
User could be imediately signed in with a delayed confirmation, user info is marked unconfirmed until they complete the signup
A/B testing could be used to determine the quality/quantity tradeoff
B-DPeople don't want to wait
Email delivery is unreliable
C-D'People will try to game the systemThe rate of growth in users increases as the time to access decreases
A-BAll users will not game the system
system gamers can be rooted out with a delayed confirmation
Email is not the only way to confirm quality
A-CA low quality user as no value