We evaluate projects to learn. Then nobody reads the evaluation

Almost every project model has a step called evaluation. In practice it is often a meeting where everyone is tired, a few points are written down and the document ends up in a folder. The next project starts from scratch.

This applies to big projects too

When the Swedish National Audit Office reviewed government agencies' strategic digitalisation projects in 2025, it found that agencies did not work systematically with benefits realisation and often did not evaluate the benefits actually achieved in completed projects. In an earlier review of cost increases in infrastructure projects, one of its conclusions was that knowledge of what caused the cost deviations was missing.

Two sides of the same problem. If nobody finds out what went well and what went badly, there is nothing to learn from.

What I see is that the energy runs out at delivery. The whole organisation has been working towards a date, and once the system or change is in place there is rarely any strength left to evaluate, follow up the benefits and make sure the effects are actually realised. The project is closed, people move on to the next thing, and the most important part of the work never gets done.

Why evaluations are not used

They come too late. By the time the project ends, the project manager has already moved on and the team has dispersed.

They cover the wrong things. Many evaluations look at time and budget, but not at whether the project delivered the effect it was meant to.

Nobody owns the lessons. A list of lessons learned with nobody responsible for carrying them forward is a diary, not a tool.

A simpler approach

I suggest skipping the big final evaluation and doing two things instead. A short meeting right when the project delivers, with a single question: what would we do differently next time? And a follow-up six to twelve months later, looking at whether the project delivered the benefit it promised.

Most importantly, someone in the leadership team should be responsible for making sure the lessons are actually used in the next project. Otherwise it is just another report.

A question for your next leadership meeting

Which lesson from our last major project have we actually used in the current one?

Sources: Swedish National Audit Office, RiR 2025:8 on strategic digitalisation projects (Swedish) · Swedish National Audit Office, review of cost increases in infrastructure projects (Swedish)

What does it look like in your organisation?

Take the project evaluation assessment to see how you learn from experience, or book 30 minutes with me about a project that needs an honest review.