Problem Definition Framework
Reference model
A clear problem definition leads to better solutions.
About this model
A structured approach to defining a problem before solving it: state the problem, set out its context and stakeholders, separate visible symptoms from suspected causes, and agree the desired outcome and the constraints.
Originator not stated.
How to read it
- Start with the problem statement, then check the context and who is affected.
- Separate symptoms (what we see) from causes (why it happens), and treat causes as hypotheses to test.
- Agree the desired outcome and the constraints, then turn the result into dated actions.
What this does
Clarifies the nature of a problem so that the right issues are addressed, and sets out the outcome, limits and first actions needed to guide an effective solution.
When to use it
Use it when a team is struggling to agree on what the real problem is, or when solutions are being proposed without a clear understanding of the underlying issues.
Not when: Do not use it when the problem is already well defined and agreed by all stakeholders, or when an emergency needs immediate action before any analysis.
What happens next
Take the leading cause hypotheses into a root cause analysis tool to test them with data, then build a solution plan against the agreed outcome and constraints.
Golden thread
Builds on ←
- Stakeholder analysis
- Situation assessment
- Customer or operational data review
Feeds into →
- Root Cause Analysis
- Solution Development Plan
Use this tool, free
Sign in to open the worksheet. Your work saves as you type, the AI can draft the parts you have not filled in, and you finish with an analysis and a 30/60/90-day action plan.
Drafted with AI and reviewed by Eccellere on 04/11/2026. Guidance, not advice: apply your own judgement.