Key Insights

1. Implementation Stalls at the Points That Strategy Documents Ignore

The gap between a strategy and its implementation is not uniform. It concentrates at specific, predictable points: the transition from design to operationalisation, the first budget cycle in which new activities compete against established ones, the moment when recommended changes create friction for departments with an interest in the status quo, and the period after initial momentum fades and new priorities compete for leadership attention.

Strategy documents typically do not address these points in any operational detail. They describe what should change, not the sequencing, coalition-building, or institutional negotiation required to make change happen in a specific context with specific constraints. That gap is where most recommendations die.

Closing it requires advisory presence at exactly those moments, which means maintaining an engagement structure that extends beyond strategy delivery into the implementation period. The insight is not new. The practice remains uncommon because clients procure strategies and advisory firms price engagements accordingly.

2. The Political Economy of Reform Is Not Captured in a Diagnostic

Every public sector reform has stakeholders who benefit from it and stakeholders who lose by it. Those who lose have a structural advantage: their loss is concentrated and immediate, which gives them strong incentives to resist. Those who gain have a structural disadvantage: their gain is diffuse and delayed, which gives them weaker incentives to advocate.

This political economy is rarely captured in a strategy document with the specificity that implementation requires. Who within the institution has the authority and the interest to drive the recommended changes? Who will resist, and at what point in the implementation sequence will that resistance become active? What sequencing allows early wins that build the coalition needed for harder changes downstream?

Answering these questions requires a different kind of consultant: not only the analyst who can synthesise evidence and write a compelling recommendation, but the advisor who understands institutional dynamics well enough to know which changes are achievable in which order and what the pressure points will be. That capability is built through sustained engagement in government systems, not through periodic diagnostic visits.

3. Embedded Advisory Produces Different Outcomes Than Visiting Advisory

The distinction between advisory delivered from a distance and advisory delivered from within is not a stylistic preference. It produces measurably different outcomes.

Advisors embedded in ministries, agencies, and county governments develop an understanding of institutional culture, informal decision-making patterns, and the specific constraints facing individual civil servants that visiting advisors cannot develop from periodic consultations. They are present when implementation decisions are made, not after those decisions have already been taken in directions the strategy did not anticipate. They build the working relationships with civil servants that allow them to identify bottlenecks early and address them before they compound.

In engagements where implementation support presence has been maintained over 18 to 36 months, the pattern of outcomes is consistent: higher rates of recommendation uptake, faster resolution of implementation bottlenecks, and more durable institutional changes than engagements where the advisory firm withdrew after strategy delivery. These outcomes do not appear in a short-term project completion report. They emerge from sustained presence across the arc of institutional change.

4. Monitoring Frameworks That Track Outputs Miss the Point

The standard advisory engagement produces a monitoring and evaluation framework as part of its deliverables. That framework typically tracks outputs: documents produced, workshops delivered, staff trained, systems procured. Output tracking serves reporting requirements. It does not reveal whether change is happening.

The relevant question for a public sector advisory engagement is not whether the monitoring system was designed. It is whether the institution's behaviour changed. Whether the policy was implemented rather than endorsed. Whether the revenue system was reformed rather than reviewed. Whether the new organisational structure is being used or has been quietly set aside.

Outcome-focused monitoring requires a different framework and, more importantly, a different advisory presence. An advisor who has already left the engagement when implementation begins cannot monitor whether recommendations are being followed. Maintaining the monitoring function requires maintaining the engagement.

5. Short-Term Contracts Produce Short-Term Thinking

Advisory contracts that are structured around a fixed deliverable and a defined endpoint create incentives that work against implementation quality. An advisory firm that will be evaluated on the report it produces will invest in the report. An advisory firm that will be evaluated on whether the recommended changes were made will invest in making the changes.

The procurement structures that govern most public sector advisory in Africa are oriented toward the former. Terms of reference define deliverables, timelines, and reporting requirements, and advisory firms that win on price are frequently those that scope the engagement most narrowly. The result is a market that selects for document production rather than institutional change.

Development partners and governments that want advisory to produce outcomes rather than archives need to design mandates accordingly: longer engagement timelines, outcome-based evaluation criteria, and explicit budget for implementation support presence beyond strategy delivery. The additional cost is recoverable many times over in the value of reforms that actually happen.