Reframing the Problem:

From Insight to Clarity

“What’s the problem?” Your team looks up at you expectantly. Maya has just voiced the question that’s on everybody’s mind. People on the team begin throwing out ideas rapid fire.

“Wait!” you find yourself saying. “Let’s step back and reframe the problem before we define it.”

Good move.   But does your team know what you mean? Isn’t the problem obvious by now?

You and your team are building a social enterprise. You’ve identified a need in the community and completed a full empathy cycle. You’ve organized your data and created an Insight Map, which captures the main ideas from the data. Now you need to translate those patterns into a clear, actionable problem statement.

But if you rush this step, you may end up with something too vague to act on, or an impromptu solution disguised as a problem statement.

Where You Are: Insight Map to Problem Statement

You’ve already organized your data and created an Insight Map, as we covered in the last post, From Notes to Insight.

Now reframe the problem. Reframing turns your insights into a focused description of the problem, grounded in the data you’ve collected. Your Insight Map is a guide to transform what you’ve learned into a clear problem statement. For example, in earlier posts, we met Maria and her need to get a good meal on the table quickly after coming home from work. Her Insight Map had idea clusters around “Urban food deserts/few good supermarkets,” “Single working parent time crunch,” “Fast Food Everywhere!” “Healthy Homecooked Meals take time. “

Using their map and the checklist below, the team wrote this problem statement:

“Single working parents like Maria cannot obtain affordable, fresh groceries between 5–7 p.m. near their homes in some urban neighborhoods, forcing them to rely on fast food despite their desire to serve their families healthy meals.”

We’ll explore this this problem statement in more depth below.

During this reframing process, your problem statement will evolve as your understanding deepens. Aim first for clarity, and then for completeness.

What Makes a Strong Problem Statement

A strong problem statement is a clear, specific sentence that is firmly linked to your Insight Map and describes a meaningful challenge without implying a preconceived solution. Above all, it must be actionable.

Use this five-part checklist to test yours:

Five-part checklist
Who	Which specific group or person?
Barrier	What obstacle prevents them from making progress?
Context	When or where does this show up?
Consequence	Why does this matter? What’s the impact?
Evidence	How do you know? Link to insights, quotes, and observations.

A good test is to read your statement aloud and ask, “Could five different solutions fit this problem?” If yes, you’ve defined a problem. If no, you’ve may have described a solution.

Example

Let’s return to Maria’s problem statement and see why it works. Maria wants to feed her hungry family soon after she gets home. Her neighborhood has plenty of fast-food chains but no grocery stores with affordable fresh produce or quality meat. Now, let’s contrast two possible problem statements.

Weak problem statement: “Families need better access to healthy food.”

Why it’s weak: Too vague. Which families? What does “access” mean? What’s preventing it?

Stronger problem statement (from above): “Single working parents like Maria cannot obtain affordable, fresh groceries between 5–7 p.m. near their homes in some urban neighborhoods, forcing them to rely on fast food despite their desire to serve their families healthy meals.”

Why it’s stronger:

• Who: Single working parents, a specific user group
• Barrier: Fresh, affordable groceries are not available during the critical time window
• Context: Between 5–7 p.m., near home
• Consequence: Little choice but to rely on fast food
• Evidence: Links back to your Insight Map clusters on time constraints, store locations, and price points

This statement opens up multiple solution possibilities, such as mobile markets, extended hours, delivery cooperatives, or community buying clubs, without prescribing any single answer.

This is a problem statement you can design for.

Grounding in Community Partners

A problem statement is only as good as how well it reflects the reality of the people you are designing with. If you are co-designing with your community partners, this check is already built in. If not, do a quick check with them before moving forward.

15-Minute Validation:

Read your statement to one or two community partners and ask:

• “Does this describe your experience?”
• “What did I miss or oversimplify?”
• “When does this show up most in your day or week?”

Their answers will tell you if you are on track or if you need to revise.

Common Pitfalls

Watch out for these three common mistakes:

1. Too vague

Example: “Families need better access to healthy food.”

Why it weakens the statement: It does not name a specific group, setting, or barrier clearly enough to guide action.

Fix: Tighten the user group and add context. Ask: Which families? What gets in the way? When and where does this happen?

2. Solution in disguise

Example: “Maria needs an app to locate affordable grocery stores near home.”

Why it weakens the statement: This jumps to one possible answer before the problem is fully defined.

Fix: Replace solution language with barrier language. Focus on the obstacle, not the tool. Ask: What is preventing Maria from getting affordable groceries?

3. Not grounded in evidence

Example: A statement based mostly on assumptions, opinions, or guesses.

Why it weakens the statement: If your statement is not tied to insights, quotes, observations, or partner feedback, you may be defining the wrong problem.

Fix: Go back to your Insight Map and check your wording against what you actually learned. Then test it with one or two community partners: Does this describe your experience? What did I miss?

Try This Now

Take your current problem statement and run it through the five-part checklist:

1. Underline the user group
2. Circle the barrier
3. Box the context, when and where
4. Double-underline the consequence
5. Add a footnote linking to your evidence

Missing any piece? Revise until all five are present and specific.

Why This Matters

A strong problem statement is specific, grounded in evidence, and open to multiple solution paths. Use the five-part checklist, validate with community partners, and avoid the common pitfalls.

Defining the right problem is half the work of finding the right solution. Take the time to reframe well, and you’ll explore better possibilities in the Ideate phase. Rush it, and you may define the wrong problem and fail to help your community partners.

Now you’re ready to ask “How Might We” questions, the next step in the Define phase. That’s where we’re headed in the next post.

*****

For more on Reframing and the Define phase of Design Thinking, see my book Design Thinking: A Guide to Innovation.

Photo by Adrea Piacquandio on Pexels.