Adaptive management, learning and reporting: leading with evidence

1Adaptive management

Humanitarian contexts change faster than logframes. Adaptive management consists of deliberately and transparently adjusting activities, methods or targets according to data and context, while keeping the objective. It is not improvisation: it rests on explicit assumptions, monitoring that tests them, and planned decision points.

Its components:

• Working assumptions clearly stated in the theory of change ("women will be able to get to the cash-out points").
• Context and early warning indicators that test them (reported travel time, security incidents on the roads).
• Decision rules written in advance: "if more than 20% of transfers are not collected within 10 days, mobile cash-out points are opened".
• Regular reviews (quarterly, or monthly in an acute crisis) with the authority to decide.
• An agreement with the donor on what can change without a formal request (activities, methods) and what requires an amendment (objectives, overall budget, areas).

Donors are often more open than people think to well-argued adaptation. What they refuse are unannounced changes discovered in the final report.

A project that has changed nothing in 18 months in a volatile context has probably not looked at its data, or has not dared to talk about it.

2Programme reviews and after action reviews

The quarterly review of a programme brings together the programme team, MEAL, logistics, finance and, where possible, representatives of partners and communities. The standard agenda:

• Progress on key indicators against targets and trends.
• Budget execution and burn rate.
• Feedback from people and partners: main themes, responses provided.
• Context and assumptions: what has changed.
• Decisions: what, who, when. And follow-up of decisions from the previous review.

The after action review, which originated in the military and was then widely adopted, is a short tool (one to two hours) to be used after a significant event: a distribution, an evacuation, a first wave of response. Four questions: what did we plan? what actually happened? why is there a gap? what will we do differently next time? It works if people talk about facts, without looking for culprits, and if the last question produces actions with a person responsible.

Lessons must be specific and actionable: "communication needs to be improved" is not a lesson; "announce distribution dates by radio and by voice message at least 5 days in advance, because 40% of households had not received the information" is one.

3Organisational learning

Humanitarian organisations produce many reports and learn little: the same mistakes are repeated from one crisis to the next, often because staff turn over quickly and lessons remain in documents that no one reads. An effective learning system:

• Defines priority learning questions for the organisation (for example: "how can monitoring quality be maintained when access is intermittent?") and directs the MEAL of several projects towards answering them.
• Captures lessons in usable forms: two-page briefs, checklists, document templates, rather than long reports.
• Circulates lessons at the right time: at the start of a new project, the lessons from similar projects are read (lessons review at the design stage).
• Values the reporting of failures, for example through regular sessions where teams present what did not work and what they learned from it.
• Shares with the sector: published evaluations, contributions to cluster working groups, case studies.

The role of the MEAL manager then changes: from a producer of data for donors, they become a facilitator of reflection who helps teams ask good questions, read the data and decide.

4Writing donor reports

A good-quality narrative report follows the donor's structure and meets three requirements: accuracy (figures consistent with the financial report and previous reports), analysis (not just what was done, but what changed and why) and honesty (gaps and difficulties explained).

For each result, a simple structure works: target, achieved, gap, explanation, consequence, action. For example: "Target: 3,000 households. Achieved: 2,450 (82%). Gap due to the closure of the road to X for 7 weeks. Consequence: two transfer cycles delayed in 4 villages. Action: mobile payment introduced in May; catch-up planned by August, at no additional cost."

Mistakes to avoid:

• Output figures presented as outcomes ("12,000 people reached by awareness-raising have improved their practices").
• Double counting between activities (the same person counted in each activity); unique beneficiaries must be distinguished from participations.
• Individual success stories presented as representative; a story illustrates, it does not prove.
• No mention of complaints received and responses provided.

The donor will find out about problems sooner or later. It is better that they hear about them from you, with the analysis and the measures taken, than through an evaluation or an audit.

5Programme closure and sustainability

Closure is prepared from the design stage (exit strategy) and implemented at least three months before the end. It includes:

• Informing communities and authorities about the end date and arrangements, and referral to other services.
• Transfer of assets (water points, equipment) according to the donor's rules, with written agreements with the recipients of these assets.
• Handover to partners, technical services or committees, with capacity strengthening that is genuinely planned and budgeted.
• Endline survey and evaluation, then feedback to communities.
• Archiving of data and documents, and secure destruction of personal data in line with the retention policy.

Sustainability is judged by the conditions in place: an institution or community that takes responsibility, resources for operation (public budget, contributions, cost recovery), skills, and genuine demand from users. Without these conditions, it is better to acknowledge it and look for a successor (other funding, other actor) rather than announce a sustainability that will not exist.

6Final project: the complete MEAL package

The final project of this Mini MBA consists of presenting a complete MEAL package for a real or realistic programme of your choice. It brings together everything you have learned in twelve weeks:

• A two-page needs analysis note: sources, severity, priority groups, coverage gaps, response options compared.
• A theory of change and a logframe with indicators, baselines, calculated targets and assumptions.
• A targeting strategy and, where applicable, the calculation of the transfer value.
• A MEAL plan with two indicator reference sheets, the sampling plan and the sample size calculation for the baseline survey.
• A complaints and feedback mechanism: channels, timeframes, sensitive channel, indicators.
• An evaluation plan: type, questions, method for estimating the effect and its validity conditions.
• A VfM analysis: 4E indicators and a comparison of options.
• A review schedule and three adaptive decision rules.

Quality criteria: consistency between the parts, correct and verifiable calculations, realism (MEAL budget of 3 to 10%), a genuine place given to people, and honesty about limitations. The case studies in the diploma exam draw on exactly these skills.