u.lab works | Practical playbook
The Problem Definition Playbook
7 Questions to Ask Before Attempting to Solve Any Organisational Problem
u.lab works · 12 min read
Before commissioning a project, purchasing a new system or launching an intervention, take the time to understand the problem you are actually trying to solve.

In this article
Introduction
Organisations are often quick to solve problems. They commission consultants, introduce new technologies, restructure departments, launch programmes and allocate resources in pursuit of better outcomes.
But there is a question that frequently gets overlooked: Are we solving the right problem?
A poorly understood problem can produce an impressive solution that achieves very little. New technology may automate a broken process. Additional funding may reinforce an inefficient institution. A training programme may address a skills gap that was never the real constraint on performance.
The difficulty is not always a lack of solutions. Sometimes, it is a failure to understand what actually needs solving.
Problem definition is therefore not a preliminary administrative exercise. It is one of the most consequential stages of decision-making, innovation and institutional improvement.
This playbook introduces seven questions that organisations should ask before committing resources to an intervention. They are designed to help leaders, teams, consultants and decision-makers move beyond visible symptoms towards a clearer understanding of the challenges they face.
Are we solving the right problem?
The seven questions
What exactly is the problem?
Start by defining the challenge without jumping to a solution.
One of the most common mistakes organisations make is confusing a proposed solution with the problem itself.
For example:
- "We need a new information management system."
- "Our employees need more training."
- "We need to improve communication."
- "We need to introduce artificial intelligence."
These statements describe possible interventions, not necessarily the underlying problems.
A stronger problem definition describes an observable gap between the current situation and the desired outcome.
Consider the difference:
| Solution-oriented statement | Problem-oriented statement |
|---|---|
| We need new software. | Our teams cannot access accurate information when making decisions. |
| We need more training. | Employees lack specific capabilities required to perform critical tasks. |
| We need better communication. | Important decisions are frequently delayed because departments operate with disconnected information. |
| We need AI. | Existing processes require repetitive manual work that creates delays and inconsistencies. |
Questions to ask
- What is happening that should not be happening?
- What should be happening that currently is not?
- Who experiences the problem?
- What specific outcome is being affected?
Practical output: A clear, concise problem statement that describes the challenge without prescribing its solution.
Interactive
Solution-oriented or problem-oriented?
Solution-oriented statements
Problem-oriented statement
Our teams cannot access accurate information when making decisions.
“We need new software.” names an intervention. It says what to do before establishing what is wrong, so it cannot show whether that intervention would close the gap.
A stronger problem definition describes an observable gap between the current situation and the desired outcome.
What evidence tells us this is a problem?
Distinguish between what we know, what we assume and what we believe.
An issue may appear significant because it is frequently discussed, politically visible or strongly felt by leadership. However, the frequency with which a problem is mentioned does not necessarily reflect its actual scale or underlying causes.
Organisations need to establish an evidence base before deciding what intervention is appropriate.
Evidence may include operational data, financial records, customer feedback, employee experiences, performance indicators, research findings and direct observation.
Importantly, the absence of reliable data should not automatically mean that a problem does not exist. It may itself reveal an institutional weakness.
Questions to ask
- What evidence demonstrates that the problem exists?
- How frequently does it occur?
- How significant are its consequences?
- Are we relying on measurable information or assumptions?
- What information are we currently missing?
Practical output: An evidence summary distinguishing verified facts, assumptions and information gaps.
Interactive
Classifying the evidence
What can be supported by operational data or direct observation?
- Approval records show the date each request was submitted and signed off.
- A team lead has observed requests waiting in a shared inbox.
Importantly, the absence of reliable data should not automatically mean that a problem does not exist. It may itself reveal an institutional weakness.
Illustrative only. These are examples written to show the shape of the question, not findings from a real organisation.
Who experiences the problem, and how?
Understand the people and institutions affected before designing an intervention.
Organisational problems rarely affect everyone equally.
A process that works well for senior management may create difficulties for frontline employees. A policy that appears effective at institutional level may impose significant costs on the people expected to implement it.
Understanding the different experiences of stakeholders helps organisations avoid designing interventions around the perspectives of only those who have the authority to make decisions.
Stakeholder engagement is particularly important because the people closest to a problem often possess knowledge that is not captured in institutional reports or performance dashboards.
Questions to ask
- Who is directly affected by this problem?
- Who experiences its consequences indirectly?
- How does the problem affect different departments, customers or stakeholders?
- Whose perspectives are currently missing?
- Who will ultimately be responsible for implementing a solution?
Practical output: A stakeholder map identifying affected groups, their experiences, interests and influence.
Illustrative stakeholder map
Who experiences the problem?
- How they may experience it
- Daily, as workarounds, repeated tasks and delays.
- What they may know
- Where the process actually breaks and why.
- How an intervention may affect them
- Directly changes how their work is done.
- Represented in decisions?
- Often not, unless deliberately included.
The people closest to a problem often hold knowledge that never reaches institutional reports or dashboards.
A hypothetical organisation, not a real case study.
What is causing the problem beneath the surface?
Move beyond symptoms to identify underlying causes.
Visible problems are not always the problems that need to be addressed.
For example, declining organisational performance may be attributed to employee productivity. However, further investigation may reveal that employees are working with outdated systems, unclear responsibilities, inefficient approval structures or conflicting performance incentives.
Treating the visible symptom without addressing its underlying causes often produces temporary improvements rather than lasting change.
One useful approach is the Five Whys technique: repeatedly asking why a problem occurs until the investigation moves beyond the immediate explanation.
However, complex organisational challenges rarely have a single cause. They may emerge from the interaction of people, processes, institutions, technology, incentives and external conditions.
Questions to ask
- What factors contribute to the problem?
- What conditions allow it to persist?
- Are there structural, institutional or behavioural causes?
- How do different parts of the organisation influence one another?
- Are we addressing the cause or simply managing the symptoms?
Practical output: A preliminary root-cause analysis identifying the factors sustaining the problem and how they interact.
Interactive
Beneath the surface
What is easy to see and easy to measure. Treating this layer alone tends to produce temporary improvement.
Illustrative only. These are examples written to show the shape of the question, not findings from a real organisation.
Exercise
Five Whys
Write the problem as you see it, then ask why it happens five times. Your answers stay in this page only. The technique is a starting point: complex organisational challenges often have several interacting causes, so a single chain will rarely capture them all.
What happens if we do nothing?
Establish the consequences and urgency of the problem.
Not every organisational problem requires immediate intervention. Some challenges are manageable, while others become increasingly expensive or difficult to address over time.
Understanding the consequences of inaction helps decision-makers distinguish between urgent priorities and issues that may be less consequential.
It also creates a clearer basis for determining whether an intervention is justified.
Consider an organisation experiencing delays in its procurement process. The immediate consequence may be slower purchasing. But over time, the same problem could contribute to higher operating costs, disrupted service delivery, weakened supplier relationships and reduced institutional credibility.
The consequences may extend far beyond the original operational difficulty.
Questions to ask
- What happens if the problem remains unresolved?
- What are the financial, operational and institutional consequences?
- Who bears the greatest cost?
- Will the problem become more difficult to address over time?
- What opportunities are being lost because of it?
Practical output: A consequence assessment outlining the costs of inaction and the urgency of intervention.
Interactive
The cost of doing nothing
Initial problem
Delays in the procurement process
The immediate effect: requests take longer to become orders.
The pathway follows the procurement example above. No values are attached because none were measured.
What constraints or conditions shape the problem?
Understand the environment in which a solution must work.
A solution that works in one organisation may fail in another.
The effectiveness of an intervention depends not only on the quality of its design but also on the conditions surrounding its implementation.
These may include financial resources, institutional capacity, infrastructure, regulatory requirements, organisational culture, political realities and existing systems.
This is particularly important when organisations consider adopting technologies, business models or development frameworks from other contexts.
A successful intervention elsewhere does not guarantee success locally.
The objective is not to limit ambition but to understand the conditions that determine what is practical, sustainable and appropriate.
Questions to ask
- What resources are available?
- What institutional or regulatory constraints exist?
- What existing systems must the intervention work alongside?
- What organisational capabilities are required?
- Which external conditions could affect implementation?
Practical output: A constraints and enabling conditions assessment that establishes the realities within which an intervention must operate.
Interactive
Conditions that shape the intervention
- As a constraint — limits what can be achieved
- A design that needs sustained funding may stall when budgets tighten.
- As an enabling condition — makes implementation possible
- Committed, predictable funding allows a phased, realistic plan.
An intervention has to be designed for the environment in which it will operate.
What would success actually look like?
Define the desired outcome before selecting the intervention.
Organisations sometimes measure success by whether an activity has been completed rather than whether the underlying problem has been resolved.
A new system is installed. A training programme is delivered. A strategy document is approved. An innovation challenge is concluded.
But these activities do not automatically translate into meaningful improvement.
Success should be defined in terms of the change an organisation wants to achieve.
If the problem is slow decision-making, success should not simply mean implementing new software. It should mean that decisions become faster, more informed and more consistent.
If the problem is poor service delivery, success should be measured through improvements in service quality, accessibility and user experience.
Defining success early creates a reference point against which potential interventions can be evaluated.
Questions to ask
- What specifically needs to change?
- What would a successful outcome look like?
- How will we know that the problem has been addressed?
- Which indicators should be used to measure progress?
- What would constitute a meaningful and sustainable improvement?
Practical output: A set of measurable outcomes and success indicators that can guide the design and evaluation of an intervention.
Interactive
Activity is not outcome
Activities
Desired outcome
Faster, more informed and more consistent decisions
Completing “installing a new system” shows that work was done. Only the outcome shows whether the problem changed.
Success should be defined in terms of the change an organisation wants to achieve.
Putting the Seven Questions into Practice
The seven questions are most useful when treated as a connected process rather than an isolated checklist.
Each question builds on the previous one, gradually moving an organisation from an initial concern towards a defensible understanding of the challenge.
Framework
The Problem Definition Framework
A practical sequence for organisational diagnostics
- 01DefineWhat exactly is the problem?Establish the challenge.
- 02VerifyWhat evidence tells us this is a problem?Establish what is known.
- 03UnderstandWho experiences the problem, and how?Establish the human and institutional context.
- 04InvestigateWhat is causing the problem beneath the surface?Identify underlying causes.
- 05AssessWhat happens if we do nothing?Establish consequences and urgency.
- 06ContextualiseWhat constraints or conditions shape the problem?Understand implementation realities.
- 07Define successWhat would success actually look like?Establish the desired outcomes.
A well-defined problem — a stronger foundation for research, intervention design, resource allocation and implementation.
A One-Page Problem Definition Worksheet
Before commissioning a project, purchasing a new system or launching an organisational intervention, use the following worksheet to capture the findings.
u.lab works | Practical playbook
The One-Page Problem Definition Worksheet
Working template. Complete the seven sections to create an initial problem definition record.
Your answers stay in this browser tab only and are cleared when you close it. Nothing is sent to u.lab. To save a PDF, choose “Save as PDF” in the print window.
Before You Build, Make Sure You Understand
The central lesson is straightforward: organisations should resist the pressure to move directly from identifying a challenge to selecting an intervention.
A well-defined problem creates the foundation for better decisions. It helps organisations allocate resources more intelligently, challenge assumptions, identify opportunities and avoid investing in solutions that address the wrong issues.
This does not mean that every problem requires months of research or an elaborate diagnostic exercise. The depth of investigation should be proportionate to the complexity, significance and consequences of the challenge.
What matters is that decisions are informed by a sufficiently clear understanding of the situation.
At u.lab, we believe that meaningful innovation begins with understanding. Before organisations build new systems, introduce technologies or design interventions, they must first understand the problems they are trying to solve.
The quality of a solution is constrained by the quality of the problem definition that precedes it.
Understand the problem. Challenge the assumptions. Then design the intervention.
About u.lab works
u.lab works is an innovation and experimentation lab helping organisations, governments and entrepreneurs understand complex challenges, test ideas and develop practical solutions.
Our approach begins with research, diagnostics and problem framing before moving towards solution design, experimentation and implementation.
Understand better. Build smarter. Create lasting impact.
ulabworks.xyz
Before You Build the Solution, Understand the Problem.
A better-defined problem creates a stronger foundation for research, decision-making, innovation and implementation.
Working through a complex organisational challenge? u.lab helps organisations investigate problems, understand systems and develop practical approaches to solving them.
Bring us the problem.problems@ulabworks.co.zwWritten by
u.lab works
u.lab is an innovation and experimentation lab based in Harare, Zimbabwe. We help organisations, governments and entrepreneurs understand problems, test ideas and build practical solutions.
Continue exploring.
Innovation & Experimentation
Africa's Hidden Innovation Problem: We Keep Importing Solutions to Problems We Haven't Properly Understood
· 14 min
Business & Economic Development
Why Economic Development Is a Systems Problem: Understanding the Connections Between Infrastructure, Institutions and Enterprise
· 15 min
Innovation & Experimentation
How to Run an Innovation Challenge That Doesn't End With a Trophy
10 November 2026 · 18 min
Have a problem worth testing?
Tell us what is not working. We will tell you how we would investigate it — and what a first experiment could look like.
problems@ulabworks.co.zw

