Minimum is about scope
Make the promise smaller. Keep the user journey complete enough that someone can try it for real.
Minimum viable does not mean half-built. Slice the product vertically or horizontally, ship each release, and see which one gives customers value and gives the team feedback.
Make the promise smaller. Keep the user journey complete enough that someone can try it for real.
A slice is viable when it can teach you something about demand, usability, or behaviour.
Shipping only wheels, APIs, or dashboards can feel productive while the riskiest assumption remains untouched.
Before calling something an MVP, name the user, the job they can complete, and the assumption you will learn from.
If the release cannot be used by a real customer, it may be necessary construction work, but it is not yet a product experiment.