Documentation written after the project is fiction

I’ve read post-project reports that bore almost no resemblance to the project I’d watched unfold.

Clean narrative. Sensible logic. Reasonable-sounding decisions the whole way through. And false.

Not because anyone set out to lie. That’s the thing worth understanding. Nobody sat down to deceive. It’s that hindsight rewrites everything on its own, quietly, and the person writing the report is the last one who’d notice.

Here’s what happens. You reach the end of a project. You know how it turned out. Now you sit down to describe how you got there, and every messy, uncertain, panicked decision gets reinterpreted through the lens of the outcome you now know.

The dead end you spent six weeks in becomes “an early exploration.” The lucky break becomes “strategy.” The decision that nearly sank everything gets a paragraph that makes it sound deliberate and considered, because you can’t quite remember how frightened you were at the time, and the version where you knew what you were doing is more comfortable to write.

If you’re writing the story of a project after it’s finished, it’s already fiction. Not a record. A reconstruction, and reconstructions flatter their authors.

That matters more than it seems, because these documents get used. The next team reads them. They take the tidy version as a guide, they follow the reasoning that was reverse-engineered rather than actually applied, and they walk into the same wall you did, wondering why it isn’t working the way the document said it would.

You’ve passed on your conclusions and hidden your uncertainty. The uncertainty was the useful part.

Real records get written in the moment, while the outcome is still unknown and the truth is still inconvenient. A short note at the point of deciding: what we chose, why, what we knew at the time, what we were worried about. Ugly, hedged, honest. That version is worth ten polished reports.

It’s also the version nobody wants to write, because it commits you to a position before you know whether it was right. That’s exactly what makes it valuable. It’s the same discomfort that keeps the real risks off the register and the honest status out of the report.

So capture decisions as you make them. The aim was never a tidy archive for the shelf. It’s holding on to the real reasoning before hindsight launders it into something cleaner than what actually happened.

The next team will trust the honest version far more. And so, eventually, will you.


Ben Webb is an award-winning project leader and strategist. Named Australian Institute of Project Management Project Manager of the Year in 2022 and nominated for the International Project Management Association’s World Project Manager of the Year in 2023, he writes about delivery, leadership and the difference between managing a project and actually getting it done.

Leave a Reply

Discover more from BEN WEBB

Subscribe now to keep reading and get access to the full archive.

Continue reading