Why do lessons learned reports go unread?
Most NGOs write them. Few use them. A typical report sits in a folder, written at the end of the project, when the team has moved on. The lessons are general (“improve communication”), have no owner, and nobody in the next proposal team knows they exist.
Lessons get used when they are specific, timely, owned and easy to find. All four matter.
What does a useful lesson look like?
A useful lesson has four parts:
- Situation. The context, in a sentence or two.
- What happened. The result, good or bad, and the cause as far as you know it.
- What to do next time. One clear action.
- Who should act. A role, and a place where the change will be written, such as a template, checklist or policy.
Compare “Procurement was slow” with “In the dry season, three quotations took six weeks to collect for rural sites. Next time, start quotation requests during planning and keep a standing list of suppliers for each region. Owner: logistics lead, to update the supplier list by the next quarter.”
Good lessons also record what worked. Teams often list only failures, but a practice that went well, such as a simple complaint box design or a way to schedule distributions, is worth copying. Mark each lesson as “keep doing” or “change”, so the next team knows which way to go.
Watch for causes. If the lesson names a symptom only, such as “deliveries were late”, ask “why?” at least three times before you write it down. The third answer is often the one you can act on.
When should you capture lessons?
Do not wait for the end. Memory fades and staff leave.
- After a key event. A distribution, a training, a response to an incident.
- At set points. Each quarter or at the mid-term.
- At closure. A final review that pulls the earlier lessons together.
A short session of an hour can work. Our article on running an after action review gives a simple format: what was planned, what happened, why, and what to do next.
How do you run the session?
- Invite the people who did the work, not only managers.
- Set a simple rule: this is about the process, not about blame.
- Ask the four questions of an after action review.
- Write each lesson in the four-part form, on the spot.
- Agree owners and dates before the session ends.
- Share the notes within a week.
Choose a place where people feel free to talk. If a senior leader joins, ask them to listen first, since junior staff often hold back when the director speaks early. For sensitive topics, such as a conflict with a partner, ask people to write their points on paper before the group talks.
Capture the notes in a standard template, so the lessons from different projects look alike and can be searched in the same way.
How do you make sure lessons are used?
This is the step most teams skip. Build the use into your normal work.
- Link lessons to a place of change. If the lesson is about procurement, update the procurement checklist. If it is about design, add a line to the proposal template.
- Ask for them at the start. Before a new project, make the design team read the lessons for the same sector and country.
- Tag them. By topic, sector, country and project, so people can find them in a minute.
- Check on actions. At each quarterly review, read the open lesson actions and close or renew them.
- Share across teams. A short monthly note with one or two lessons keeps them alive.
What should you avoid?
Avoid vague lessons, blame, and long reports no one reads. Avoid keeping lessons only with the project manager, who may leave. Also avoid private details about people in lessons that others will read; describe the situation, not the person.
Avoid also the trap of treating the lesson session as a box to tick for the donor. If the donor requires a lessons section, write it from the real sessions, not from memory the week before the report is due. Real lessons are often a little uncomfortable; that is a sign that they are honest.
Finally, keep the process light. A heavy method will be dropped when the team is busy. A one-hour session, a one-page template and a named owner will be used far more often than a long workshop that happens once. If you can keep only one habit, keep the quarterly review of open lesson actions, since it turns notes into change.
Where EMPOBase fits
In EMPOBase, After Action Review in Programs and Risk & Learning in MEAL give you a place to record lessons next to the project they came from, so they are not lost in a closing report. The Closure Checklist can remind the team to hold a final review. EMPOBase stores the records; it cannot make anyone read them, so owners and a start-of-project habit still matter. See the platform overview.