The Transfer That Broke a Programme
A mid-level civil servant has led a rural water-sanitation programme for four years. Under her leadership, coverage in 60 unions rose from 38% to 71%, and a community monitoring system reduced non-functional tube wells from 24% to 9%. She is now transferred, on standard rotation, to an unrelated ministry post. Her successor arrives with no sector experience and is told by a senior official to 'focus on the new donor-funded scheme' rather than the community monitoring system. Within five months, the monitoring system's field visits stop, 14 unions report broken wells with no repair request logged, and the donor asks why coverage data no longer reconcile with field reports. The transferred officer is told her request to brief her successor was 'not necessary'. A junior officer who knows the system well has been reassigned to clerical duties.
1. Diagnose the institutional failure using concepts of administrative continuity and institutional memory.
Read the worked answer
The failure is not the transfer itself - rotation is a legitimate instrument of administrative policy - but the absence of any mechanism for continuity. Three distinct breakdowns can be identified:
- Loss of institutional memory. The programme's effectiveness depended on tacit knowledge: which unions had fragile wells, how the monitoring system was actually used, which community contacts mattered. None of this was codified or handed over, because the briefing was declared 'not necessary'. Tacit knowledge walked out with the officer.
- Weak institutionalisation. A programme that collapses within five months was person-dependent, not institution-dependent. The monitoring system had no formal place in the successor's terms of reference, no budget line, and no reporting requirement. Institutionalisation means embedding a practice in rules, budgets, and job descriptions - not in one officer's commitment.
- Misaligned incentives. The successor was rewarded for attention to the new donor scheme. Where performance is measured by new initiatives rather than sustained results, maintenance will always lose to novelty.
The junior officer's reassignment compounds the loss: the organisation discarded its remaining carrier of memory.
2. What concrete measures would you recommend to prevent recurrence, and who should own each?
Read the worked answer
Recommendations should be specific and assigned:
- Mandatory handover protocol (owner: ministry HR): every transfer requires a signed briefing note, a joint field visit, and a 30-day overlap or at least a documented handover meeting. 'Not necessary' should not be an available answer.
- Programme continuity register (owner: programme manager): codify the monitoring system - schedule, indicators, contacts, repair workflow - so it survives personnel change.
- Embed in the successor's terms of reference and budget (owner: senior official): the monitoring system must be a named duty with a protected budget line, not a discretionary extra.
- Retain the junior officer (owner: programme manager): reverse the reassignment or formally designate her as the system's custodian.
- Balance performance metrics (owner: ministry): include maintenance and data quality indicators alongside new-scheme delivery.
The general principle: continuity must be designed, not hoped for. Rotation is healthy only when the institution, not the individual, holds the knowledge.