After building +40 apps over the last decade, I think the most valuable skill is an ability to correctly sequence the things that need to validated for the concept to work.
For example:
1. Users need to share the app X number times for the app to have a basis to grow
2. The shares then need to convert to downloads at X rate
3. Then, X% of users need to pay
While this would obviously improve the velocity of product development, that’s actually not the most important reason why sequencing matters:
Knowing the correct sequencing means you can clearly articulate where the uncertainty with a product concept lies—and what conditions must be true for a subsequent condition to even matter.
Without understanding what’s uncertain, you’re just throwing things at a wall and hoping something sticks.
For example:
1. Users need to share the app X number times for the app to have a basis to grow
2. The shares then need to convert to downloads at X rate
3. Then, X% of users need to pay
While this would obviously improve the velocity of product development, that’s actually not the most important reason why sequencing matters:
Knowing the correct sequencing means you can clearly articulate where the uncertainty with a product concept lies—and what conditions must be true for a subsequent condition to even matter.
Without understanding what’s uncertain, you’re just throwing things at a wall and hoping something sticks.
If someone on the team claims that the entire app needs to be polished and snappy, I would push back unless you’re entering into a very competitive market with existing substitutes.
Even then, there are probably areas of uncertainty that should be eliminated first that don’t require the building a Porsche as V1.
Even then, there are probably areas of uncertainty that should be eliminated first that don’t require the building a Porsche as V1.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
