01A feature is not a proposition
A product can contain impressive features and still lack a compelling reason for customers to use it. The proposition must explain whose problem is being solved, why it matters and what makes the solution preferable to alternatives.
Treat those elements as assumptions to test. Early work should strengthen or challenge the case for building—not simply add detail to a predetermined concept.
02Give the first release a clear purpose
A minimum viable product should be designed around the most important uncertainty to resolve. It needs enough capability to test the proposition, but not every feature that could eventually be useful.
Define the target user, the core task, the acceptance criteria and the evidence that would justify the next investment. A disciplined first release creates learning as well as functionality.
A disciplined first release creates learning as well as functionality.
03Connect the experience to the economics
The user journey and the business model should develop together. How will customers discover the product? What will they pay for? What does it cost to deliver and support the service?
These questions influence product priorities, pricing, channels and the operating model. They are not work to postpone until development is complete.
04Build a learning system after launch
Launch is the beginning of a new evidence cycle. Use customer feedback, usage patterns and commercial performance to decide what to improve next.
Prioritise changes against the problem the product exists to solve. Growth comes from improving the value delivered to the right users—not from expanding the feature list without a clear reason.
