Product Thinking · Published October 3, 2026
Drawing the Boundary of an MVP
Minimum viable is not the fewest features; it is one complete business loop running end to end.
MVPs are often read as a rough first version. The result demos well but cannot be used, so no value is validated and the effort is wasted. The mistake is treating an MVP as feature trimming instead of loop design.
What a loop contains
One complete flow from start to finish, even if it covers only a single business type.
Essential support: accounts, permissions and data retention are not extras; without them the product cannot be used.
A measurable outcome: how many people used it, how often, and where they got stuck.
Three trimming rules
Cut scenarios, not steps: support one business type, but every step of that type.
Cut automation, not manual work: reports can be exported by hand, but the numbers must be right.
Cut edges, not the core: support one approval level, make it reliable.
An MVP exists to get real feedback quickly. A version that cannot complete the loop produces fake feedback.
← Previous post
Idempotency: Duplicate Submissions Are Not Just Double Clicks
Next post →
Retrospective: Integrating ERP With MES
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →