3 ms·
I'm really coming to dislike this type of article. It's vague platitudes rather than a practitioner who has earned scars and thus has the experience to describ
by kareemm 5y ago
I'm really coming to dislike this type of article. It's vague platitudes rather than a practitioner who has earned scars and thus has the experience to describe the nitty gritty why and how beyond the vague recommendations.
For example:
1. Has the Userpilot team failed at building and MVP and succeeded with an MLP? If so what did they learn and why?
2. Lots of people have succeeded with an MVP approach. They describe a handful of things you can do wrong when building an MVP... but what if you DON'T do those things that they claim lead to MVP failure?
3. Digging into one of the recommendations - don't sacrifice delighters. They talk about how they wouldn't include the Asana unicorn in their MLP and end with "balance delighters with effort". Fine. But HOW do you do that? What framework can you provide ME to do that?
This smacks of a writer doing a Google Research Project to offer up hand-wavy advice. 0/10 would not recommend.
- jesseendahl 5y agoI agree. FWIW this is a much better article on the same topic by someone who actually has earned scars. It also contains much more concrete advice: https://review.firstround.com/dont-serve-burnt-pizza-and-other-lessons-in-building-minimum-lovable-products https://review.firstround.com/dont-serve-burnt-pizza-and-oth...
- deleted 5y ago[deleted]