Mental model
Problem Framing
The foundation of effective problem-solving: clearly defining what you're actually trying to solve before jumping to solutions.
Discover
A team spends three months building a new project management tool, but nobody uses it. They realize they never answered one critical question first.
What should happen FIRST?
Let's explore how to frame problems so solutions actually fit.
Understand
Understand
A problem statement is a clear, specific description of what needs to change and why it matters. It's like writing a prescription before filling it—you need to diagnose the illness before prescribing treatment. For example, instead of saying "we need better meetings," a strong problem statement specifies "weekly team meetings run 30 minutes over with no clear outcomes, causing project delays." Try this: Before your next solution, write down exactly what problem you're solving and who experiences it.
Full explanation
Full explanation
How It Works
Crafting a problem statement means pausing to define the gap between current reality and desired outcomes. First, observe what's actually happening without judgment. Then, describe the impact—who's affected and how much it matters. Finally, clarify what success would look like. This process prevents solving the wrong problem or treating symptoms instead of root causes.
Why It Matters
Well-framed problems are half-solved. The quality of your initial question determines the quality of your final answer.
Practical Examples
In business, a manager might complain about "low employee engagement." A specific problem statement reframes this: "Remote team members report feeling excluded from decisions, leading to missed deadlines and voluntary turnover." In personal life, instead of "I'm bad with money," try "I don't track spending, so I run out of money before payday each month." In education, rather than "students aren't learning," specify "Ninth-graders can't identify main ideas in grade-level texts, causing struggles across all subjects." Notice the pattern: observable behavior, measurable impact, clear stakeholders.
Common Pitfalls
Watch out for solution-laden statements like "we need a new app"—that's a solution, not a problem. Also avoid vague complaints like "this is inefficient" without specifying what's inefficient and compared to what. Good problem statements are specific enough that two different people would understand the same issue and agree on whether a proposed solution actually addresses it.
Research
Research
Research on problem formulation shows that how we define problems dramatically influences solution quality and creativity.
- Duncker (1945): Established the principle of "functional fixedness"—the tendency to perceive objects only in terms of their typical use, which can block creative problem-solving. His experiments showed how problem presentation influences the ability to find alternative uses for objects. [1]
Limitations
Limitations
Problem framing has cultural constraints—research shows people from different backgrounds define identical situations differently. Time pressure reduces framing quality, and complex systems with multiple stakeholders often require multiple, overlapping problem statements rather than a single formulation. Some problems resist clear articulation entirely and require iterative exploration.
Try it
Synthesize
Choose a pattern from the guide, then pick an action to try with it.
Which pattern stands out?
What will you try?
Choose a pattern above to select an action.
Sources
Sources
- [1] On Problem-SolvingKarl Duncker - 1945
Try it
Check your understanding
A product manager says "We need to rebuild our mobile app from scratch." What's the most important follow-up question to craft a proper problem statement?
Show the guide's explanation
Answer: What problem are users actually experiencing that the current app doesn't solve?
The first option is jumping to a solution (rebuild). The correct answer (B) digs into the underlying problem—you can't know if rebuilding is necessary until you understand what's actually broken. The other questions (C, D) are logistics that come after defining the problem itself.
Which of these is the strongest problem statement?
Show the guide's explanation
Answer: Users leave our checkout page before completing purchases at a rate of 67%, costing $50K monthly.
Option B is strongest because it includes observable behavior (users leaving), specific measurement (67%), and clear impact ($50K/month). Options A and D embed solutions (redesign, "too long"). Option C is too vague—what's causing the loss? A good problem statement should let someone independently verify whether a solution actually worked.
After spending two months on a "team communication" initiative, nothing changed. A retrospective reveals the original goal was "improve how we talk to each other." What went wrong?
Show the guide's explanation
Answer: The problem statement was too vague to measure or solve effectively.
"Improve how we talk to each other" has no observable baseline, no specific gap, and no measurable outcome. Without these, you can't identify solutions or evaluate success. The other options blame execution or timing, but those come later—you can't execute well when you haven't defined what success means.
Keep exploring
Find another idea for the decision in front of you.
The complete Reframo library is free to read. Explore another guide whenever you are ready.