Article · 7 min read
Planning That Gets Implemented: Lessons from 25 Years with MMDAs
Development plans fail at the same three points. Here is what separates the plans that survive a change of leadership.
Plans do not fail randomly
Across a quarter-century of medium-term development planning with metropolitan, municipal and district assemblies, implementation failure clusters at three predictable points: the plan is not costed against realistic revenue, ownership sits with a consultant rather than a directorate, and no review rhythm survives the first year.
The three failure points
- Costing detached from revenue reality, producing a wish list that cannot be sequenced.
- Consultant ownership, so institutional memory leaves with the contract.
- Absent review rhythm, so slippage is discovered only at end-of-term evaluation.
What the surviving plans have in common
| Practice | Effect |
|---|---|
| Revenue-anchored costing | Projects sequenced into fundable tranches |
| Named internal owners per programme | Accountability persists through staff transfers |
| Quarterly review with published minutes | Slippage surfaces while it is still correctable |
| Community validation before adoption | Reduces mid-term political reversal |
| A short public version of the plan | Citizens can hold delivery to a stated schedule |
Surviving a leadership change
Continuity is designed, not hoped for. Plans that survive transitions carry a documented rationale for each priority, a baseline that a new administration can audit, and at least one visible early-delivery project that creates a constituency for the rest of the programme.
Consultation
Need this applied inside your organisation?
Book a consultation with our team to scope the right engagement for your organisation.