Loading content
The Minimum Viable Product (MVP) is a concept for quickly launching products with the minimally necessary features. It allows companies to obtain early feedback from users before investing more comprehensive development resources.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A minimum viable product is the smallest product version with which a team can test a central assumption under real conditions.
The term was coined by Frank Robinson and spread through the Lean Startup movement via Steve Blank and Eric Ries. It arose from the need to learn from real market behavior before making large investments.
An MVP is a measuring probe: it carries just enough function to test a concrete assumption and observe real behavior. The result guides learning, adaptation, or abandonment.
The test needs a clearly stated hypothesis.
Only functionality needed for the test is built.
Behavior and feedback show what to do next.
An MVP helps test uncertain product assumptions early with real signals. It fits high-uncertainty work; minimal scope must preserve test validity and does not mean arbitrary poor quality.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.