Design
Thinking
Start with the human, not the idea. Understand first, solve second. Empathize deeply, define precisely, ideate widely, prototype cheaply, test honestly.
The five stages
Each stage has a single discipline
Most teams start in the wrong place. They begin with a solution.
Most problem-solving starts with an idea. Someone has a solution, becomes attached to it, and spends months building it before discovering whether anyone needed it. Design Thinking exists to interrupt that reflex. It insists that you begin not with your idea but with the human you are designing for.
Formalized at the Stanford d.school and popularized commercially by IDEO, Design Thinking is less a rigid procedure than a mindset made operational through five stages. The real engine is the underlying disposition: stay curious about people, resist premature solutions, make ideas tangible early, and let real human response guide the work.
The core insight
Design Thinking makes two moves that most problem-solving skips. First: it separates understanding from solving, spending real effort making sure the team is solving the right problem before rushing to solve any problem. Second: it makes ideas tangible early and cheaply — prototypes that let real people react before teams commit.
- 1Observe and engage with the people you are designing for — firsthand, not through surveys or assumptions.
- 2Frame the problem precisely around a real human need, as a point of view that opens solutions rather than closing them.
- 3Generate many possible solutions before evaluating any of them. Volume before judgment.
- 4Build the minimum rough prototype to answer a specific question — not a draft of the product, but a question made physical.
- 5Test with real people and let their actual response guide the next iteration. Expect to loop back.
Real-world example
A designer asked to improve an MRI scanner spent time in the hospital watching children being scanned. Many were so terrified they had to be sedated. The real problem was not the machine's engineering — it was the child's experience. The team reframed the scanner as an adventure: pirate ship, jungle, a story the child was part of. Sedation rates dropped dramatically. Nothing about the machine changed. Everything about the human experience did.
When to use it
Use it when
- →The problem is human-centered and not yet well understood
- →You are designing a product, service, or experience people will use
- →The team is attached to a solution and has not genuinely examined the problem
- →Past attempts have failed because they solved the wrong thing
Do not use it when
- ×The solution is already known and the work is execution
- ×The problem is purely technical with no meaningful human-experience dimension
- ×You are in a domain that demands a heavily regulated, gated process
Click any stage to see how it works
Select a stage to explore its mindset, activities, and a real-world example. The IDEO three-lens model — Desirability, Feasibility, Viability — is surfaced below each stage panel; click a lens to see what it means.
Five versions, one conviction
Design Thinking is not a single fixed method. It is an idea shaped over decades, from academic roots into commercial practice and enterprise scale. Select a version to see what changed.
Where this connects
Design Thinking answers “are we solving the right human problem, and have we explored solutions widely enough?” These are the frameworks and methods that answer the adjacent questions.
Sources & Further Reading
Change by Design
Tim Brown, 2009
Creative Confidence
Tom Kelley and David Kelley, 2013
The Sciences of the Artificial
Herbert Simon, 1969
IDEO Design Kit — Human-Centered Design Toolkit
IDEO.org