The document discusses launching products early with a minimum viable product (MVP). It notes that launching early allows companies to validate assumptions and get feedback from users to iterate the product. Specifically, it recommends releasing an MVP that has the core value proposition and solves a broad problem, rather than spending excessive time and money building without releasing. Examples are given of Twitter and LinkedIn launching MVPs early. The presentation agenda includes discussing why to launch early, the concept of an MVP, and opening the floor for questions.

1. Introduction to the
Company
Live Q&A Session with
Ravijot Chugh
Co-founder and Product Head,
UpGrad

2. Page -2-
Agenda for the session
Why Launch Early
Concept of MVP
1
2
Open Q&A3

3. Page -3-
Why Launch Early
1
2
Sooner the Better - “To Validate Assumptions”
3
Start Learning From You Users
"If you're not embarrassed by the first version of your product, you've launched too late"
— Reid Hoffman, Founder, LinkedIn
Building & Iterating Till No End Without Releasting – “A Trap”
Immense Risk in Spending Time & Money

4. Page -4-
Examples - Twitter

5. Page -5-
Examples - LinkedIn

6. Page -6-
Agenda for the session
Why Launch Early
Concept of MVP
1
2
Open Q&A3

7. Page -7-
Concept of MVP to Launch Early
“Release Often & Iterate Fast”
Product having Core Value Proposition
Build on Broad Problem - Trying to Solve
Prevents Wasting Time & Resources
Launching “Minimum Viable Product” - Not just a Minimum Product
Build, Measure & Learn Loop

8. Page -8-
Release Often and Iterate Fast - Build-Measure-Learn

9. Page -9-
Agenda for the session
Why Launch Early
Concept of MVP
Open Q&A
1
2
3

10. Page -10-
Open Q&A
Write Your Queries in the Chat Window