design-thinking.md

# Design Thinking

**Design thinking** is a human-centered problem-solving methodology developed at Stanford's d.school and popularized by IDEO. It follows five iterative phases — Empathize, Define, Ideate, Prototype, Test — to ensure solutions are desirable (people want it), feasible (technically possible), and viable (economically sustainable). It excels at problems where the user's real need is unclear or where existing solutions miss the mark.

---

Analyze the following problem using the **design thinking** framework. Go through all five phases.

**Problem / Topic:**
$ARGUMENTS

---

## Phase 1: Empathize — Understand the Human

Before solving anything, deeply understand the people affected.

- **Who** are the primary users/stakeholders? Create brief persona sketches:
  - Demographics, context, goals, frustrations
  - What does a day in their life look like relative to this problem?
- **What do they say** they want? (Explicit needs)
- **What do they actually do?** (Observed behavior — often contradicts what they say)
- **What do they think and feel?** (Underlying emotions, fears, aspirations)
- **Pain points**: What frustrates them most about the current situation?
- **Workarounds**: What hacks or improvised solutions are they already using? (These reveal unmet needs.)
- **Empathy map**: Summarize what users Say / Think / Do / Feel.

## Phase 2: Define — Frame the Right Problem

Synthesize empathy findings into a clear problem statement.

- Write a **Point of View (POV) statement**:
  > [User] needs [need] because [surprising insight].
- Reframe the problem from the user's perspective, not the organization's.
- Identify the **core tension** — what makes this problem genuinely hard?
- What **"How Might We" (HMW) questions** emerge?
  - Generate 3-5 HMW questions that are broad enough to inspire creativity but narrow enough to be actionable.
  - Example: "How might we make [frustrating process] feel effortless for [user]?"

## Phase 3: Ideate — Generate Solutions

Diverge wildly, then converge.

**Divergent phase (quantity over quality):**
- Generate at least **10 ideas** — include wild, impractical ones
- Use these prompts to break fixedness:
  - What would a child suggest?
  - What if money/time were unlimited?
  - What if we had to solve this in 24 hours?
  - What if the opposite of the current approach worked?
  - What solution exists in a completely different industry for a similar problem?
  - What if we removed the most "essential" feature?

**Convergent phase (select and refine):**
- Cluster similar ideas into themes
- Evaluate ideas on a **2×2 matrix**: Impact (high/low) × Feasibility (high/low)
- Select **top 3 ideas** to develop further, including at least one high-risk/high-reward option

## Phase 4: Prototype — Make It Tangible

Make ideas concrete enough to test.

- For each top idea, describe a **minimum viable prototype**:
  - What is the simplest version that tests the core assumption?
  - What form does it take? (Sketch, wireframe, role-play, landing page, physical model, storyboard)
  - What does it cost to build? (Time, money, effort — should be minimal)
- Identify the **riskiest assumption** each prototype needs to validate
- A prototype should be:
  - **Quick** to build (hours to days, not weeks)
  - **Disposable** (you should be ready to throw it away)
  - **Focused** (tests one hypothesis, not everything)

## Phase 5: Test — Learn and Iterate

Design the feedback loop.

- **Who** should test the prototype? (Real users, not colleagues)
- **How** will you test?
  - What specific behavior will you observe?
  - What questions will you ask? (Open-ended, not leading)
  - What metrics define success?
- **What signals are you looking for?**
  - Delight / confusion / frustration / workaround behavior
  - Does the user "get it" without explanation?
- **Iteration plan**:
  - What would make you pivot (abandon this direction)?
  - What would make you persevere (refine this direction)?
  - What's the next experiment after this one?

## Synthesis

- Summarize the recommended solution and why it addresses the real user need.
- Map the solution against: **Desirable** (do people want it?) × **Feasible** (can we build it?) × **Viable** (does it sustain itself?)
- Define the immediate next action to move forward.

---

Design thinking is iterative, not linear. If testing reveals a flawed assumption, loop back to an earlier phase. The goal is to **fail fast and learn cheap**.