An MVP is a product with a minimum set of features that solves a definite problem of users. It allows you to spend as little resources as possible to engage your first users and get useful feedback. Used correctly, an MVP can be a great tool to both manage the risk of developing a new product and guide product development as you scale. In this event we took a brief look at some reasons why you might want an MVP, common mistakes you can avoid, and how to turn that MVP into your first marketable product. We also talked about at what point in the build-measure-learn cycle does an MVP become a final product that can grow and scale.

1. How to Turn Minimum Viable Products into
Growth by fmr Amazon PM
www.productschool.com

2. FREE INVITE
Join 23,000+ Product Managers on

3. COURSES
Product Management
Learn the skills you need to land a product manager job

4. COURSES
Coding for Managers
Build a website and gain the technical knowledge to lead software engineers

5. COURSES
Data Analytics for Managers
Learn the skills to understand web analytics, SQL and machine learning concepts

6. COURSES
Blockchain and Cryptocurrencies
Learn how to trade cryptocurrencies and build products using the blockchain

7. TONIGHT’S SPEAKER
Himani Jain

8. Himani Jain
Head of Product - Transactional
How To Design Minimum Viable Products
and Then Grow Them

9. Bio

10. Top 20 Reasons Startups Fail

11. What is an MVP

13. MVP is not a Product launched at a moment in time. It is
a Continuous Process
The Myth of MVP

16. What is a MVP?
A Minimum Viable Product is [a] version of a new
product which allows a team to collect the maximum
amount of validated learning about customers with the
least effort
- Eric Ries

17. Minimum Viable
a product that is cobbled together, feature-poor, and buggy
and one that few customers would ever use except
earlyvangelists

18. Validated Learning
In a trial-and-error world, the one who can find errors the
fastest wins

19. Least Effort
an inelegant product which nevertheless works

20. How To Design an MVP

21. Step 1: Define the Problem
...the riskiest aspect of new products is not technology
(whether it can be built) but market (will people use it and pay
for it)

22. Step 1: Define the Problem
1. Build products that people need
2. Do not get attached to solutions
3. Do not project “your” needs to what the “market” needs

23. Step 2: Find The Simplest Way to Solve the
problem
our MVPs are tests – not great products
Use existing stack and HACK your way through to launch fast

24. Step 3: Prioritize
Use common frameworks such as MoSCoW method to
prioritize feature list

25. Step 4: Don’t be afraid to do things that don’t
scale
you can afford to develop your MVP in an inefficient and un-
scalable way

26. Step 5: Build, Measure and Learn

27. Step 5: Build, Measure and Learn
1. Develop a User Base
2. Collect Usage Data
3. Ask for User Feedback
4. Update Your Product

28. Example: AirBed&Breakfast
Problem 1 - Need help paying rent
Problem 2 - It is hard and expensive to find a hotel room for
conference attendees

29. Example: AirBed&Breakfast
Assumption 1 - People will live in stranger’s houses and pay
for it
Assumption 2 - Others will let strangers stay in their houses

30. Example: AirBed&Breakfast

31. Example: AirBed&Breakfast

32. Example: Convoy

33. Pitfalls to watch out for
1. Analysis Paralysis
2. Perfectionism (your MVP will most likely...suck)
3. Forgetting the core problem you are trying to solve
4. Ignoring customer feedback
5. Being afraid of mistakes

34. MVP Phase: What Skills do you need as a PM?
1. Persevere
2. Be Scrappy
3. Customer Obsession
4. Prioritize..prioritize..prioritize
5. Analyze..analyze..analyze
6. Be curious and Challenge assumptions
7. Experimentation

35. Product Market Fit

36. What is Product Market Fit?
Product/Market Fit is achieved if your product has found a
repeatable and scalable model that drives demand

37. What is Product Market Fit?

38. When do you know you have Product Market Fit?
1. Customer buying behavior changes -> Push to Pull
2. Usage is growing as fast as your technical infrastructure
can scale
3. Net Promoter Score
4. You have good retention

39. What do PMs do?
1. Customer Acquisition and retention
3. Resources and Organizational Processes
4. Experimentation
5. New Product Features
2. Scrappy to Scalable

40. Product Market Fit: What Skills do you need as a
PM?
1. Metrics Obsession
2. Customer Obsession
3. Data Pipeline instrumentation
4. Influence and Authority
5. Process Obsession

41. Growth/Scaling

42. Growth Phase
Pouring gasoline over . Optimize customer acquisition,

43. What do PMs do?
1. Experimentation
2. Unit Economics - Find product-economics fit
3. Pay tech debt and build alarms/monitors
4. Identify new verticals and build competitive moats
5. New Product Features

44. Growth Phase: What Skills do you need as a
PM?
1. Data Oriented - Ask Why
2. Think Independently and Think Big
3. Take Risks
4. Social Capital
5. Stakeholder Management
6. Operational Excellence
7. Experimentation

45. TAKEAWAYS

46. 1. MVP is not a product at a point in time; it’s a continuous process
3. Perfectionism during MVP phase is the biggest mistake you can make
6. Constant experimentation is important - the one who fails more and faster, wins
7. Scaling prematurely can cost you growth
8. Do not lose sight of building competitive moats after product market fit
2. Define a real customer problem and keep validating it
4. Be willing to do things that don’t scale
5. Prioritize brutally

47. THANK YOU!

48. Part-time Product Management Courses in
San Francisco, Silicon Valley, Los Angeles, New
York, Austin, Boston, Seattle, Chicago, Denver,
London, Toronto
www.productschool.com