DevProduct
MVP Doesn't Mean Building a Bad Product
The word "minimum" has done a lot of damage. Teams use it to justify shipping something fragile, then wonder why early users never came back.
DevYet TeamJune 30, 20265 min read
An MVP exists to answer a question: will people use this to solve a real problem? A broken product can't answer that question — it only tells you that people won't use broken software.
Cut scope, not craft
Reduce the number of things your product does. Keep the quality of the things it does. One workflow that works completely will teach you more than six that half-work.
- Fewer features, fully finished.
- One user type, deeply served.
- Manual behind the scenes is fine; broken in front of the user is not.
What to measure
Return usage beats signups. Depth of use beats breadth. If people come back without being reminded, you've found something.
