- Most companies do waterfall not agile;
- IDEAS → BIZ CASE → ROAD MAP → DESIGN → BUILD → TEST → DEPLOY
- Most look at;
- How much money will it make?
- How long will it take?
- Assume 50-75% of ideas won’t work
- Use engineers as product designers
- Best teams:
- Risks upfront:
- Customer value
- Usability
- Feasability
- Business viability
- Product is designed collaboratively, instead of PM → Design → Engineer → Test
- Solving problems, not implementing features
- Risks upfront:
- All team work in person, best teams prototype 15-20 ideas/week
- Hiring a VP product
- If Founder is v strong a product/vision, don’t hire someone in the same mould → causes clashes. Needs to complement founder
- If Founder is not strong at product/vision, don’t hire in the same mould.
- Don’t have roadmaps, have outcome based vision that solves business problems
- EVANGELISM;
- Use a prototype
- Share the pain
- Share the vision
- Share the learnings
- Share credit
- Give great demos
- DISCOVERY FRAMING
- Small ideas = opportunity assessment
- Medium ideas = PR release Amazon style
- Big ideas = startup canvas
- objective; what objective is this to address
- key results; how will you know if you’ve succeeded?
- customer problem; what problem will this solve?
- target market; what type of customer?
- DISCOVERY PLANNING
- Story Map
- Customer Discovery; get a “reference customer”, ideally Six
- Fake door demand test - button that only heals to an ask for a user interview
- In user interviews - 4 ways to tell if customer really wants your path
←The bookcase
One of the books Shaun rated five out of five.