-
When Programs Don’t Address the Underlying Issue
Many programs work hard—and still fall short.
Training is delivered.
Resources are provided.
Systems are improved.And yet, outcomes remain partial.
Participants understand more—but don’t change behaviour.
Interventions are taken up—but not sustained.
Looking Beyond Delivery
When this happens, the instinct is to improve implementation:
- better training
- more support
- closer monitoring
But this assumes the program is addressing the right issue.
Often, it isn’t.
What Sits Beneath
What appears as a problem on the surface can be driven by something else.
A lack of adoption might reflect:
- risk and uncertainty
- labour constraints
- social obligations
- weak or unreliable markets
From one perspective, the issue is knowledge.
From another, the issue is entirely different.
Why It Matters
Programs are built on assumptions about what the problem is.
If those assumptions are only partially right, the response will be too.
This is why well-designed and well-delivered programs can still struggle to achieve meaningful change.
Working Differently
A growing part of my work focuses on making these underlying assumptions visible.
Not to find a single “correct” framing—but to:
- surface different perspectives
- understand what each implies
- design responses grounded in how the problem is actually experienced
A Simple Question
Before asking what should we do?
Ask:
what is driving the issue—and how has it been understood?
Further Reading
I’ve been exploring this idea in more detail in a longer article on problem representation in program design and evaluation—particularly how different ways of defining a problem shape the interventions that follow.
