Note 58 | An MVBP Tests the Whole Business, Not Just a Feature
These are Robin Shen’s original reading notes and commentary, written in his own words after reading Bill Aulet’s Disciplined Entrepreneurship: 24 Steps to a Successful Startup. They are not the original book, excerpts from it, or an official publication. Methods and concepts from the book are attributed to Bill Aulet; other sources are identified where stated. For reference only; not investment advice.
English translation of Robin’s Chinese reading notes and commentary. Passages are paraphrased, not verified verbatim quotations from the original English edition.
The Minimum Viable Business Product, or MVBP, combines earlier single-assumption tests into a simple but complete product that can sell. Aulet requires three things: customers get value from use, pay for that value, and generate a feedback-and-iteration cycle. An action testing one hypothesis in lean-startup language is different. Without payment, this is not the business-system test intended here.
Minimal is the difficult word. Ideas accumulate through specifications, customer conversations, and brainstorming. Cutting them hurts. Richard Thaler’s endowment effect helps explain why: people value what they already possess more highly than what they do not. Prepare for hard scope decisions.
Reliability requirements depend on the industry. The software maxim that an unembarrassing first release came too late may fit some products, but not brain surgery or other high-consequence failures. Scope can be narrow without compromising essential reliability.
A growing feature list can postpone payment validation. The first version need not prove complete technology. It must show willingness to use and pay, with feedback useful for iteration. All three conditions matter; industry risk determines the reliability floor.
Three actions: Divide features into required for a paid offer and merely makes it cooler. Remove the latter from version one and explain how the remaining scope satisfies all three conditions. For high-consequence products, define a reliability floor and narrow scope to situations it safely covers. Start with real users, add strangers promptly, and distinguish features useful only during information collection from lasting customer value.
#DisciplinedEntrepreneurship
These are reading notes and reflections based on my personal understanding. I recommend reading them alongside the original book for the full context.
Comments
What do you think? Share your experience or questions.
Sign in to comment, reply or like. Sign in / Sign up
Loading comments…