Confirmed Access vs Quick Access
B: Acquire more users
D: Allow users quick access to premium data
A: Build a database containing a large number of high quality users
| A-C: | Assumption(s) | Injection(s) |
| A low quality user as no value |
C: Acquire high quality users
D': Allow only confirmed users access to premium data
In order to Build a database containing a large number of high quality users we must Acquire more users and in order to Acquire more users we must Allow users quick access to premium data. But, in order to Build a database containing a large number of high quality users we must also Acquire high quality users and in order to Acquire high quality users we must Allow only confirmed users access to premium data. we can't both Allow users quick access to premium data and Allow only confirmed users access to premium data.
| Relation | Assumption(s) | Injection(s) |
| D-D' | Email is the only way to confirm high quality | User 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-D | People don't want to wait Email delivery is unreliable | |
| C-D' | People will try to game the system | The rate of growth in users increases as the time to access decreases |
| A-B | All 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-C | A low quality user as no value |