The document discusses defining and shaping an MVP (minimum viable product) by first identifying key assumptions through an assumption tree. It recommends designing small initial experiments to test these assumptions at minimum cost, then using the results to iterate the product. The key is to start with the smallest possible code and design to test hypotheses about customer needs and viability before fully developing the product.

1. Shaping and Defining your MVP

2. 1. No market need
2. Ran out of money
3. Don’t have the right team
4. Don’t build the right product
Source: CB Insights
4 Main Reasons Startups Fail

3. What an MVP isn’t.

5. What an MVP actually is.

7. Your MVP should be the smallest amount of code and design
possible in order to conduct your first experiment.

9. Define
Assumptions
Assumption
Tree
Experiment
Design
Build
Run
Experiment
Measure
Iterate
Review
Experiment
Results

10. 1. Product Hypothesis
2. Customer & Problem Hypothesis
3. Distribution & Pricing Hypothesis
4. Demand Creation Hypothesis
5. Market Type Hypothesis
6. Competitive Hypothesis
Source: Steve Blank
Defining Assumptions

11. 1. Sitters are willing to sit for $12/hr
a. Sitters are okay waiting 3 days for payment
i. Sitters will be okay with Venmo for payments
2. Families are willing to pay $15/hr for a sitter
a. Families are willing to book a sitter through an app
i. Families will book sitters more than once
Assumption Tree

12. 1. Start Date
2. Length
3. Stakeholders
4. Interview Questions
5. Workflow
6. Test Cards
7. The scorecard / metrics
Experiment Design

13. Questions?
Email zach@coplex.com
Follow @zcferres linkedin.com/in/zcferres