Difference between revisions of "Minimal viable product"
Jump to navigation
Jump to search
(Bockground++ += Forces) |
m (Accelerated learning) |
||
| Line 2: | Line 2: | ||
|goal=test strategic assumptions and hypotheses in a series of rapid feedback loops | |goal=test strategic assumptions and hypotheses in a series of rapid feedback loops | ||
|theme=Agile, Maneuver, Lean | |theme=Agile, Maneuver, Lean | ||
|background=== | |background===Accelerated learning== | ||
{{mvp}}s generally accelerate: the first {{mvp}} takes three quarters, the second only two, the third just one and then they start to come in every other week or so. Each time you will be able to validate or refute your next hypotheses faster than before. | {{mvp}}s generally accelerate: the first {{mvp}} takes three quarters, the second only two, the third just one and then they start to come in every other week or so. Each time you will be able to validate or refute your next hypotheses faster than before. | ||
Revision as of 14:09, 24 August 2015
…{{{context}}}
✣ ✣ ✣
{{{wish full}}}
Accelerated learning
minimal viable products generally accelerate: the first minimal viable product takes three quarters, the second only two, the third just one and then they start to come in every other week or so. Each time you will be able to validate or refute your next hypotheses faster than before.
Forces
- every minimal viable product that results from a pivot both destroys and creates product infrastructure, platform and features, so this accounts for just a part of the acceleration;
- as the product evolves, it turns into legacy, potentially slowing development down;
- learning critical things about needs, customers, markets, and strategy will accelerate development and pivots.
Therefore:
{{{therefore full}}}
✣ ✣ ✣
✣ ✣ ✣
Sources
- HBR » David Aycan,Paolo Lorenzoni » The Future of Prototyping Is Now Live
- Smashing Magazine » Grace Ng » A Guide To Validating Product Ideas With Quick And Simple Experiments