MVP Types

Minimum Viable Product (MVP) is a simple product with only a minimal set of features to enable testing with real users. That can be achieved using various types of MVPs.
Read more
Article

MVP Types

Minimum Viable Product (MVP) is a simple product with only a minimal set of features to enable testing with real users. That can be achieved using various types of MVPs.

MVP Archetype Description Metrics Observation Depth Hypothesis Validation
Concierge Hand-created experience you want a customer try Qualitative observations of the individual steps of the experiment High Low
Wizard of Oz Interface with a human under behind the curtain making things happen Subject interaction with the interface and affinity for experience Medium Medium
Sales Selling something before actually having it General growth metrics: click-through, sign up, opened / responded emails Low High
Explainer video Videos describing how complex product works and what is special about it Track engagement and analyze the demand Low Medium
Landing page Landing page explaining the advantages of the product with an option to buy it Analyze the demand and user behavior Low High
Piecemeal MVP A usable product composed of already available tools instead of building new ones Analyze the demand and validate the hypothesis Medium Medium
Single-feature product Creating a product with only the core functionalities Narrow down a target group, analyze feedback Medium Medium

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.