Holistic Product Thinking
summary
Argues for a concrete checklist: confirm business goals, understand users and the ecosystem, validate with qualitative and quantitative data, and account for organizational and technical constraints. Gives two concrete failure modes: a rushed conference release that earned applause but zero buyers, and an analytics feature shipped on assumptions without data. Recommends including design and engineering in interviews, measuring value in dollars/person-hours/% CSAT, and keeping a captured backlog of discarded ideas for leadership alignment.
AI-written summary · about
chapters (9)
- 0:00Holistic Product Thinking
- 4:43If you're not solving customer problems, you're not doing your job.
- 4:57Starting a new job? Building a roadmap? Team cohesion? Failed release?
- 9:33GOAL OBJECTIVES STRATEGIES
- 10:46Build something quickly Lack of time Unknown ecosystem Undefined target
- 14:06Who is my target audience? What are their probelms?
- 19:07Does your product idea offer sufficient value or benefit which would outweigh the estimated cost and risk?
- 19:38Does your organization have the capacity to support the proposed product idea?
- 20:17How well does the solution fit into the organization's business, technical and information environemnt?
related talks
43mDesigning the Right Product
32mJustify Your Product Decisions and get Stakeholder Buy in
13mHolistic approach in product design
48mOne weird trick to turn your idea into a successful business: Product Thinking
42mDesign Thinking for teams who want to create their own products
47mThe product confidence trap
44mIt’s Easy To Create A Good-Looking Product, But How About A Useful One?
38mResponsible product design