wunder beta🧠 Design Thinking
You sit in a launch meeting while someone sketches a notification for a tool nobody is using. Design thinking is a set of habits for finding the real problem before you build the wrong thing.
What you’ll learn
- The Problem With ProblemsDistinguish tame from wicked problems and treat design thinking as a discipline of aim — habits for identifying the right problem before committing to a solution.Tame problems arrive with clear goals; wicked problems, named by Rittel and Webber in 1973 and brought into design theory by Buchanan in 1992, arrive as a fog. The danger is solving the wrong problem perfectly, usually because a team has fallen in love with a first solution. The d.school’s five modes are a starter map for staying with the problem, not a recipe.
- Watch What People DoExplain the empathize mode: privileging observation of real behaviour over stated preferences to surface the true, often unspoken need.People are poor witnesses to their own behaviour, so this research favours watching what people do in context over what they say they want. The gap between stated and real needs is where wicked problems often hide — commuters may ask for faster trains when the felt problem is uncertainty, and missed appointments may be barriers rather than forgetfulness.
- Write the Right ProblemExplain the define mode: synthesizing observations into a sharp, correctly framed problem statement, and the craft of reframing via 'How might we'.Define compresses empathize’s messy findings into a single statement of the right problem. The handed brief is rarely the one to solve. The d.school’s 'How might we…' format keeps the statement solution-agnostic yet aimed: broad enough to invite many ideas, narrow enough to be a real target.
- Cheap, Wrong, FastExplain ideation and prototyping as one discipline: separate generating ideas from judging them, then learn with the cheapest wrong answer you can build.Brainstorms fail because teams generate and judge at once. Osborn’s 1953 rules — defer judgment, go for quantity, welcome wild ideas, combine and improve — protect the diverge phase. A prototype is a question made physical: cheap enough to throw away, specific enough to teach you something, cashed in by putting it in front of a real person.
- Keep the Tools, Drop the MagicTreat the five modes as an iterative loop, then separate the defensible core habits from the magic claims and the fair criticisms.Testing sends you backward, so the modes are a loop, not a line. Design thinking has been oversold as a repeatable innovation engine. Natasha Jen (2017) and Lee Vinsel (2018) named the theatre, the shallow empathy, and the oversold origin tales. The durable core remains: observe users, reframe, prototype cheaply, diverge before converging, iterate.
Questions this course answers
Why is design thinking aimed at 'wicked' problems rather than 'tame' ones?
Tame problems have clear goals and measurable success, so the work is execution. Wicked problems are fuzzy and contested, so the real risk is aiming at the wrong problem — which is exactly what design thinking’s up-front discipline guards against.
What behaviour does 'fall in love with the problem, not the solution' actually train?
The maxim fights the universal pull toward defending a first idea. It trains you to keep investigating the real problem and hold multiple framings open, so you can abandon a solution quickly when evidence says to.
Why does the empathize mode favour observing behaviour over asking people what they want?
We forget, rationalize, and answer to sound reasonable, so stated wants can mislead. Watching real behaviour in context surfaces the true need — the gap between the two (speed vs. uncertainty; forgetting vs. barriers) is where the real problem hides.
What makes a good 'How might we…' problem statement?
A strong 'How might we' is a Goldilocks statement: too narrow ('add a reminder text') hides one solution inside the question; too broad ('improve healthcare') gives no target. It should aim ideation without deciding the answer.
According to the lesson, why do most brainstorms underperform?
Mixing generation and evaluation teaches the room that ideas get shot down, so only safe ideas surface. The fix is to separate divergence from convergence — defer judgment and chase quantity first, then evaluate hard later.
Why does design thinking favour cheap, rough, early prototypes?
A prototype is a question, not a product. Since wrong answers are inevitable on wicked problems, the goal is to find them cheaply — a flaw on paper costs an afternoon; the same flaw after launch can cost the company.
Grounded in trusted sources
- Horst W. J. Rittel and Melvin M. Webber, "Dilemmas in a General Theory of Planning," Policy Sciences 4 (1973): 155–169
- Richard Buchanan, "Wicked Problems in Design Thinking," Design Issues 8, no. 2 (Spring 1992): 5–21
- Stanford d.school, Design Thinking Bootleg (five modes: Empathize, Define, Ideate, Prototype, Test)
- Carissa Carter / Stanford d.school, "Let's Stop Talking about THE Design Process"
- Alex F. Osborn, Applied Imagination (New York: Scribner, 1953)
- IDEO.org, The Field Guide to Human-Centered Design (2015)
- IDEO, "Reimagining the Shopping Cart" (ABC Nightline, 1999; four-day appearance model)
- Natasha Jen, "Design Thinking is Bullshit," 99U Conference, New York (2017)
Every Wunder lesson is built from real, reputable sources — never invented.
Related History courses
Wunder is a personalized learn-anything platform — tell it any topic and it builds a beautiful, fact-checked course in minutes, with narration, a knowledge check, and a college-style University track.
Browse more History courses · All topics · Home
© 2026 Wunder Learning LLC · Terms & Privacy