Building a New Product vs. Iterating on the Old
•Télécharger en tant que PPTX, PDF•
2 j'aime•559 vues
An important skill for a Product Manager is the ability to parachute into an existing product and land on your feet. In this workshop Paul Yokota, the Director of Product for Animoto, talked about how to immerse yourself in your new company and learn as much as you can as quickly as you can. The important thing is understanding your product's problem domain, knowing how to collect good qualitative data, learning how to set expectations with an new team and learning how to become the product diplomat.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Building a New Product vs. Iterating on the Old
Similaire à Building a New Product vs. Iterating on the Old (20)
Plus de Product School
Plus de Product School (20)
Dernier
Dernier (20)
Building a New Product vs. Iterating on the Old
- 1. Building a New Product vs. Iterating on the Old
- 2. Launching Products Paul Yokota Director of Product Management, Animoto Product School, 2017-06-07 @paul_yokota
- 5. v1 Products
- 14. What to Build
- 16. Get out in the world
- 20. Validation
- 21. Validation MVP!=
- 22. How to Build
- 30. Scope down and ship
- 32. Agile Sprint #1 Sprint #2 Sprint #3
- 36. Does it add value on its own? Can we learn from it?
- 38. Think Beyond Launch July August September October Launch
- 46. Part-time Product Management Courses in New York
Notes de l'éditeur
- Thanks for coming!
- If you treat a v1 product launch like regular feature work on an existing product, you’re going to have a bad time.
- Missed important deadlines Morale was in the toilet Android developer put in notice
- Lean methodology
- Build
- Discovery: figuring out what to build Delivery: building it Teresa Torres
- Opportunities
- Discovery: figuring out what to build Delivery: building it Teresa Torres
- Opportunities
- Test riskiest assumptions cheaply Talk about value prop Paper prototype
- Not MVP Clearly define what you want to learn Existing, real users, in context
- Opportunities
- Iron triangle (resource triangle) Two-way relationships
- Scope
- Everything is in flight at once Scope and risk is almost an order of magnitude greater
- Schedule
- At Mosaic we were under a clock Time is (Not) on Your Side
- Shipped is better than perfect
- Resources
- Hold one or two constant Best time to cut scope is at the beginning
- Opportunities
- Don’t build half a bridge Is a product, you can learn from Cutting analytics setup can be tempting. Don’t.
- Shipped doesn’t necessarily mean launched A/B test wider for existing products
- Think beyond launch, look at longer timeline What we ship for launch - just a fraction of where the builder will be in 6mo, 1yr Birth a healthy baby first, Then teach it to walk and talk and do long division
- Statistical Research Group
- Thanks for coming!