Design Thinking for teams who want to create their own products
summary
CB Insights finds ~98% of new initiatives fail for lack of market need, so the process focuses on de‑risking: define outcome and define KPIs before code, run empathy interviews and expert chats, cluster transcripts, pick opportunity, generate many options (use buy-a-feature or card sorting), prototype on paper and test with real users, iterate or kill hypotheses, then write specs. Mentoring experience includes ~200 bootcamp alumni and ~60 startups and an ambulance volunteer app as examples of applied results.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:28Why Im here
- 1:18About me
- 1:43My work
- 2:40Types of projects
- 2:56Design first
- 4:20Output driven
- 6:42Statistics
- 7:49CB Insights
- 10:32The Big Problem
- 12:22The Romanian Schools
- 14:15sunk cost fallacy
- 16:18business challenge
- 21:55Ideation
- 24:33iterative process
- 25:17value creation
- 25:57research
- 27:49why
- 30:15meaningful work
- 31:41quantitative methods
- 34:09business problem
- 37:47quantitative relevant data
- 38:13social demographic profile
- 38:56conclusion
- 39:55recap
related talks
40mIs Design Thinking the Magic Wand for your product success?
43mDesigning the Right Product
48mOne weird trick to turn your idea into a successful business: Product Thinking
41mLeadership By Design: How Design Thinking Can Help You Lead With Impact
16mHow to Create Products & Services that Customer Love?
30mDesign Thinking for Rubyists
51mThe missing link between business need and software development: product design
39mDesign your thinking