0 to 1- Taking a Concept & Launching an MVP by Wish Product Leader
•
0 likes•292 views
Key Takeaways: -Real data from your own users beats any estimation - how to get that as fast as possible -Getting a sense of scale and reach is very important. -Experimentation & Iterations - trying lots of variations to test the boundaries
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to 0 to 1- Taking a Concept & Launching an MVP by Wish Product Leader
Similar to 0 to 1- Taking a Concept & Launching an MVP by Wish Product Leader (20)
More from Product School
More from Product School (20)
Recently uploaded
Recently uploaded (20)
0 to 1- Taking a Concept & Launching an MVP by Wish Product Leader
- 1. 0 to 1- Taking a Concept & Launching an MVP by Wish Product Leader www.productschool.com
- 2. CERTIFICATES Your Product Management Certificate Path Product Leadership Certificate™ Full Stack Product Management Certificate™ Product Management Certificate™
- 3. Corporate Training Level up your team’s Product Management skills
- 4. Free Product Management Resources BOOKS EVENTS JOB PORTAL COMMUNITIES bit.ly/product_resources COURSES
- 5. From 0 to 1: Taking a concept and launching an MVP Atish Bhattacharjya Product Lead @ WISH
- 6. My Product Management Journey
- 7. A minimum viable product (MVP) is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development What is an MVP
- 8. 2 Real Examples from Wish
- 9. Problem: Human agents giving canned responses → Rising customer support costs MVP: A simple decision tree based automated experience for the top issues #1 Wish Assistant - Customer Support Chatbot
- 10. Elements of an MVP Subset of problems Item not delivered beyond due date Focus on basics No NLP Pre formed responses Minimal resources Built on Web / deployed across all platforms Rapid feedback Click Analytics Thumbs Up / Down score Rapid iteration Adding new issues Automating more flows
- 11. #2 Buy Now Pay Later Problem: Drop out before purchase / Insufficient funds → More affordable payment options MVP: A simple pay within 30 days solution
- 12. Elements of an MVP Subset of problems Only for purchases upto $50 Only 1 payment Focus on basics No Installments Basic eligibility criteria Minimal resources In house solution Rapid feedback Adoption Default Rate Repeat Purchase Rapid iteration Late payment Pay Half / Installments Smarter risk rules
- 13. Key Takeaways
- 14. ● Break down the user problem and see where the biggest opportunities are ● Reduce complexity in ○ Functionality ○ Usability ○ Design Tackle a subset of problems & focus on the basics
- 15. ● “Hacking” a solution could be ok → remember to do it the right way when you scale ● Which one is faster -- Building in house OR Integrating with a 3rd party ● Native App Vs Web development Be frugal with resources
- 16. ● Strive for rapid feedback (within a day) ○ Qualitative ○ Build analytics into the product ● How does it affect user behavior throughout the experience Get rapid feedback from your users
- 17. ● Test the limits before optimizing ● Understand adoption before scaling Quickly iterate based on feedback making progress towards the complete solution
- 18. ● You’re still solving a PROBLEM. You’re still building a PRODUCT ● Pick the most critical job to be done ● Get the job done, even if it’s not very pretty ● Measure & Learn Closing Thoughts Build Measure Learn
- 19. Thank You!
- 20. www.productschool.com Part-time Product Management Training Courses and Corporate Training