Problem Design
Why Problem Design Beats Design Thinking
What I learned in surfacing and communicating REAL problems business's face and articulating across complex, multi-layered service environments.
Why This Article Matters
Every organisation wants better solutions, yet too often, teams jump straight into design, development, or delivery without first clarifying the real problem they’re trying to solve. The result? Impact and outcomes fall short, with features nobody uses, services that miss the mark, and communities left frustrated.
I’ve seen it happen countless times. A project sponsor walks into a workshop and declares a “problem” that’s really just their preferred solution in disguise. The room stays quiet — no one wants to challenge it. Then someone finally asks: “But is that actually the problem we’re here to solve?” Suddenly the air changes. What felt like progress was really just fast-tracking to the wrong answer.
This article is about changing that pattern. You’ll learn:
Let's be honest, complex services rarely fail in obvious places. The journeys we deliver fail in the build, handoffs, invalidated assumptions, outdated policies, and the invisible gaps no one sees, until something goes wrong.
- Why effective problem design is the foundation of impactful products, services, and programs.
- How to spot the difference between weak problem statements and strong ones.
- Practical methods (like the Five Whys) for uncovering root causes instead of chasing symptoms.
- Ways to frame problems that connect business ambition with real human needs.
By the end, you’ll see how designing problems more effectively leads to solutions that truly matter — for your organisation, your customers, and the communities you serve.
1
Effective problem design
Effective problem design is the foundation of impactful digital products, services, and community programs. It asks us to pause, dig deeper, and connect business ambition with human reality. I sometimes think the industry mis-named itself. We talk so much about design thinking, yet what truly drives value is problem design, because better problem design naturally leads to better solution design. It’s a clearer, more marketable way to describe the real work: uncovering root causes and framing challenges that are genuinely worth solving.
2
Why bad problem statements fail
These kinds of observable statements waste resources and create features nobody asked for.A weak problem statement is often:
Principles of effective problem design
The journey needs to be broken up and illustrated differently in different areas of the business.
1
Anchor in human experience
Bad example: “Customers aren’t signing up fast enough.”Good example: “Single parents report that our sign-up process is too long to complete on a mobile during childcare duties. 60% abandon halfway.” A strong problem statement reflects how real people struggle in specific contexts. Instead of focusing only on business metrics, zoom into the lived experience. The good statement is humanised, contextual, and backed by evidence.
2
Define measurable outcomes
A measurable frame keeps teams accountable and aligned.Problems must be linked to outcomes you can track otherwise, you won’t know if you’ve solved them.
3
Expose root causes, not just symptoms
A common method is the Five Whys: If you only solved the “return rate” symptom, you might launch a better returns policy, but the real fix is upstream in data quality. And this is the most critical element of effective problem design: when you eliminate the root cause, you eliminate the problem itself. Every solution built on symptoms is just a patch; solutions built on root causes create lasting impact.4. Balance human pain and business impact Not every pain point is worth solving first. Prioritise problems where human frustration and business value overlap. Framework: Severity × Frequency × Business Impact This creates a heat-map of where to focus. For example: fixing a severe but rare edge case may be less valuable than solving a moderate but frequent friction in onboarding.Many teams chase symptoms, like low sales or bad reviews, without asking why. To design a meaningful problem statement, you must peel back the layers.
4
Framework: Severity × Frequency × Business Impact
Severity: How painful is it for the individual?
Frequency: How often does it happen?
Impact: How does it affect revenue, cost, or trust?
This creates a heat-map of where to focus. For example: fixing a severe but rare edge case may be less valuable than solving a moderate but frequent friction in onboarding.
5
Frame inclusively
The second framing recognises systemic inequity and sets up a more impactful solution.Communities are diverse. If your problem design excludes certain voices, your solutions will too. Include perspectives from people with accessibility needs, cultural differences, or systemic barriers.
Let's be honest, complex services rarely fail in obvious places. The journeys we deliver fail in the build, handoffs, invalidated assumptions, outdated policies, and the invisible gaps no one sees, until something goes wrong.
Methods to get to the root of meaningful problems
- Listen directly — interviews, usability tests, field research. Look for where people struggle, workaround, or disengage.
- Map the journey — chart the end-to-end experience, including emotional highs and lows. Root causes often lie outside the obvious touchpoint.
- Use mixed data — combine qualitative stories with quantitative metrics. (E.g., “7 of 10 interviewees struggled” + “40% abandonment in analytics”).
- Cross-check with stakeholders — validate whether the pain connects to organisational priorities, compliance, or long-term strategy.
- Synthesise and test — draft your problem statements, then test them with real users and teams. Ask: Does this resonate? Does it feel true?
Putting it all together: A community-focused example
Weak framing: “Residents aren’t using the council’s recycling app.”
Root cause discovery:
- Interviews show residents don’t know collection times.
- Analytics show 65% drop-off at postcode entry.
- Journey mapping reveals confusion between three overlapping council services.
Strong framing: “65% of residents abandon the recycling app when asked to enter their postcode. Many don’t know which council area they belong to, leading to confusion and missed collections. This causes frustration for residents and costs the council ~$200K annually in missed compliance.”
Why problem design matters
Better problem design doesn’t just produce better products, it creates more just, inclusive, and impactful outcomes. It ensures solutions actually change people’s lives, strengthen communities, and deliver measurable business value.
In short: if you don’t design the problem, you’ll never design the right solution.
Conclusion: Design the Problem, Not Just the Solution
Strong solutions don’t come from brainstorming sessions or chasing the latest trend. They come from the discipline of problem design, slowing down to frame challenges clearly, uncovering the root causes, and ensuring the outcomes matter to both people and business.
When we design problems well, we do more than fix symptoms. We eliminate issues at their core, reduce wasted effort, and create products, services, and community programs that make a genuine difference.
In many ways, problem design is the missing half of what’s often called design thinking. It’s the step that ensures our ideas aren’t just clever but actually meaningful.
So the next time your team rushes to build, pause and ask: Have we designed the problem well enough? Because the quality of your solutions will never exceed the quality of your problem framing.