This model reflects how we think about donor-funded programs, based on work across energy and climate initiatives in Asia, Latin America, and the Caribbean. It is not exhaustive. It captures patterns that tend to hold in practice across the programs we have been involved in or observed.

Programs tend to deliver results when technical work aligns with political and institutional incentives across the actors involved. This model is a way to identify where that alignment exists and where it is likely to come under pressure.

Donor-funded programs, whether in climate, health, governance, or infrastructure, involve multiple layers of decision-making. Each layer responds to its own incentives. This model describes a pattern that holds across most programs we have worked on or observed: the way funding flows, how narratives are constructed, and under what conditions real-world impact becomes possible.

Donor coalition
Responds to domestic political priorities
Donor governments fund international programs partly because their domestic electorate or political coalition cares about specific issues. Within the donor system, different actors often pull in different directions: ministers want political signals, treasury wants evidence of value, embassies want continuity.
Implementers
Accountable upward for compliance. Dependent downward for access.
Delivery partners sit between donor and recipient. They translate requirements into local action while depending on recipient institutions for cooperation. A large part of the job, in practice, is holding the narrative together across layers that want different things.
Recipient coalition
Responds to domestic institutional and political logic
Recipient governments shape donor programs based on how they fit existing priorities. When a champion inside the system supports the work, things move. When that person moves on, the dynamic often changes regardless of program quality.
Funding, priorities, reporting requirements
Compliance, evidence, narrative
Signals feeding back into donor decisions
The pattern that tends to hold

Programs tend to sustain support when they maintain coherence across all three layers: when the narrative is credible to the donor, the activities are feasible for the implementer, and the outcomes are compatible with the recipient's priorities. Impact often depends on how well it aligns with these incentives, not only on whether the technical work is sound.

What this means in practice is that program design is not only a technical exercise. It is also a political navigation exercise. The programs I have seen deliver the strongest results are the ones where the team understood what each layer needed and designed around those constraints from the start, rather than treating them as obstacles that appeared later.

When does impact become politically useful?
IF
Impact is visible enough for the relevant actors to recognise it
AND
Attributable to the parties that need to show results
AND
Timed to coincide with reporting or political cycles
AND
Compatible with incentives at each layer
THEN
Impact tends to be recognised and, in some cases, expanded or replicated.

OTHERWISE
Impact may not be prioritised, even when it is genuinely valuable, because it does not fit the institutional moment.
Where real outcomes tend to happen

Most experienced practitioners can describe moments when political needs, institutional cooperation, and genuine outcomes briefly pointed in the same direction. These windows are not permanent. Recognising them, and being ready to move when they appear, is often the difference between a program that delivers on paper and one that changes something in practice.

Where programs tend to come under pressure
01
Results arrive at the wrong time. The work was solid, but the funding or reporting cycle had already closed.
02
The narratives stop fitting together. The donor needs one story, the recipient needs another, and the gap becomes too wide to bridge.
03
A key counterpart moves on. Access and momentum often follow individuals, not institutions.
04
Donor priorities shift. Programs that were well-supported find their strategic relevance reduced through no fault of their own.
05
Compliance takes over. Reporting and governance absorb so much capacity that there is limited room left to pursue the outcomes the program was designed for.
Implications for how programs are designed
01
Map what each layer needs early. Before the logframe, understand who needs what from this program and where those needs overlap.
02
Design so results can be clearly attributed to the actors who need them. Outcomes that nobody can point to tend to be undervalued, regardless of how real they are.
03
Know the timing. Funding cycles, elections, ministerial rotations. Align deliverables with the moments they will be used.
04
Programs that struggle to maintain a coherent narrative across stakeholders tend to become harder to sustain over time, even when the underlying work is strong.

Adapted from selectorate theory (Bueno de Mesquita & Smith, 2011) and experience inside donor-funded energy and climate programs.

If you are working on similar programs or thinking through these dynamics, feel free to get in touch.