Design thinking is a human-centered approach to problem-solving that originated at Stanford's d.school and was popularized by IDEO. It gives teams a structured framework to deeply understand user needs and develop creative solutions. The process has five stages, but they are not strictly linear — you will often loop back as you learn more.
Stage 1: Empathize
Empathy is the foundation of design thinking. Before you can solve a problem, you must genuinely understand the people experiencing it. This means setting aside your assumptions and observing real behavior.
Practical empathy techniques:
- Contextual inquiry — Watch users perform tasks in their real environment (their desk, their phone, their kitchen).
- Shadowing — Follow a user through their day to see pain points you would never discover in a meeting room.
- Empathy interviews — Ask open-ended questions like "Walk me through the last time you tried to..." and listen without leading.
The goal is not to collect data points but to build genuine understanding. You want to feel what it is like to be your user dealing with this problem.
Stage 2: Define
After empathizing, you synthesize what you learned into a clear problem statement. A strong problem statement, often called a Point of View (POV) statement, follows this format:
[User] needs [need] because [insight].
For example: "First-time home buyers need a way to compare mortgage options side by side because the current process requires opening multiple tabs and manually copying numbers."
A well-defined problem statement keeps the team aligned and prevents "solution creep" — building features that do not address the core issue.
Stage 3: Ideate
With a clear problem to solve, you now generate as many ideas as possible. The key rule during ideation is to defer judgment. Bad ideas often spark great ones.
Effective ideation methods:
- Brainstorming — Set a timer for 10 minutes and aim for quantity. Write every idea on a sticky note.
- How Might We (HMW) — Reframe your problem as "How might we make comparing mortgage options feel effortless?" This opens up creative angles.
- Crazy Eights — Fold a paper into 8 sections, sketch 8 different ideas in 8 minutes. Forces rapid, visual thinking.
After generating ideas, cluster them by theme and vote on which to prototype. You do not need consensus — pick 2 to 3 promising directions.
Stage 4: Prototype
A prototype is a quick, inexpensive representation of your idea. The goal is to make your concept tangible enough to test, not to build a finished product.
Types of prototypes by fidelity:
- Paper prototypes — Hand-drawn screens on paper. Fast, great for early exploration.
- Clickable wireframes — Tools like Figma or Balsamiq let you link screens together for basic flow testing.
- Coded prototypes — When you need to test interactions that static mockups cannot capture, a simple HTML/CSS prototype works:
<div class="prototype-screen">
<h2>Compare Mortgages</h2>
<div class="comparison-grid">
<div class="option">Option A: 3.5% fixed</div>
<div class="option">Option B: 2.9% variable</div>
</div>
<button class="cta">Select & Continue</button>
</div>Keep prototypes disposable. You should feel comfortable throwing them away after testing.
Stage 5: Test
Testing means putting your prototype in front of real users and observing how they interact with it. You are not testing the user — you are testing your design.
Best practices for usability tests:
- Give users a task, not instructions. Say "Find and compare two mortgage options" instead of "Click the compare button."
- Stay quiet and observe. Resist the urge to help when they struggle — that struggle is your most valuable data.
- Ask follow-up questions: "What did you expect to happen?" and "What would you do next?"
After testing, bring insights back into the process. You may need to re-empathize, redefine the problem, or generate new ideas. This iteration is the core strength of design thinking.