Define Stage

The Define stage is step two of Design Thinking. It’s where you take all the messy notes, quotes, and stories from the Empathize stage and distill them into one sharp problem statement. The formula is simple:

[User] needs [need] because [insight].

Do this well, and your team stops chasing random ideas and starts solving the same challenge.

What Is the Define Stage in Design Thinking?

The Define stage is the bridge between Empathize and Ideate. After gathering insights from users, the next step is to make sense of them. Instead of leaving with ten different hunches, you leave with one clear problem statement that guides the rest of your project.

Missed step one? Go back to the [Empathize Stage in Design Thinking].

Why Defining the Problem Matters

I once sat in a workshop where the walls were plastered with neon Post-its. Everyone had “great” ideas. The problem? They were solving five different challenges at once—onboarding, dashboards, button colors.

The energy was high, but the focus was missing. That’s what happens when you skip Define: you get scattered creativity. Fun, but ultimately useless.

When you define the problem, you:

• Get everyone solving the same challenge
• Save weeks of running in the wrong direction
• Turn empathy insights into design opportunities

According to IDEO, teams that invest time defining the problem generate 30% more usable ideas during ideation than those who skip this step.

How to Run the Define Stage (Step by Step)

Step 1: Gather Insights from Empathize

Dump everything on the table: interview notes, quotes, observations, even doodles. You can’t find patterns until you see the whole mess.

Step 2: Spot Patterns

Start clustering with affinity mapping. Maybe three people complained about slow loading, or five hinted at feeling lost at checkout. Group them into themes—chaos starts to turn into clarity.

Step 3: Write a POV Statement

A Point of View (POV) statement frames the problem from the user’s perspective. Use the formula:

[User] needs [need] because [insight].

Examples:

• “Busy parents need a way to book childcare quickly because long forms make them give up halfway.”
• “Remote workers need smoother meeting logins because juggling multiple tools increases frustration.”
• “New students need structured support because self-study leaves them overwhelmed.”

Step 4: Flip It Into HMW Questions

Reframe the POV into “How Might We…” questions.

Examples:

• Broad: How might we simplify the childcare booking process?
• Narrow: How might we reduce the number of fields in the form?

Good HMW questions act like open doors—you don’t know what’s behind them yet, but you’ve narrowed the hallway.

Step 5: Sanity-Check With Your Team

Read the statement aloud. Does everyone agree? Or do some still want to chase another problem? Keep refining until the room feels aligned.

Tools That Help

• Affinity mapping → cluster sticky notes into themes
• POV statements → summarize user needs in one sentence
• How Might We questions → springboard into ideation
• Problem statement templates → keep the structure consistent

If you’re stuck, try using our [Empathy Map Template] to bridge Empathize to Define.

Mistakes to Avoid (and Fixes)

* Jumping straight to solutions → Fix: Always write a POV before ideating

* Writing vague statements (“Users want a better experience”) → Fix: Use the [User] + [Need] + [Insight] formula

* Not aligning as a team → Fix: Read problem statements aloud until everyone agrees

Real-World Examples

Fintech Startup

Original statement: “Users need faster transactions.”

Refined statement: “First-time users need to feel secure entering data because trust issues stop them from completing transactions.”

Impact: Instead of chasing milliseconds, the team designed stronger trust signals—clearer copy, security badges, confirmation screens. Conversions went up.

Healthcare

A hospital reframed “patients need faster check-ins” into “patients need clearer instructions because uncertainty increases stress.” This shifted solutions from adding kiosks to simplifying communication.

E-Commerce

A retailer reframed “customers need discounts” into “shoppers need trust signals because they feel insecure about returns.” Result: adding clear return policies improved conversions more than price cuts.

Wrapping It Up

The Define stage isn’t glamorous. You won’t impress anyone with a spreadsheet of sticky notes. But it’s the step that turns chaos into clarity.

Frame the right problem, and every idea that follows has direction. Skip it, and you’ll build beautiful solutions to problems nobody cares about.

Quick checklist before Ideate:

• Cluster empathy data into themes
• Write 1–2 POV statements
• Reframe them into HMW questions
• Align the whole team

Ready to move forward? Head into the [Ideate Stage of Design Thinking] and start turning sharp problems into bold ideas.