Why We Keep Relearning the Same Lessons

Somebody stands up in a planning session and announces the new thing. From now on, they say, we are going to talk to customers before we build, we are going to write down what a feature is actually for, we are going to stop measuring ourselves on how many tickets we finish and start asking whether any of it helped. There is a small ripple of agreement in the room, a sense that this is a fresh and slightly brave idea.

And you sit there with the strange feeling of having been here before. Not something like this. This exact thing. Three years ago, a different manager, a different offsite, the same realisation delivered with the same conviction. The lesson was learned, written up, celebrated, and then quietly lost. Now it is being discovered again, from scratch, as if for the first time.

This quarter I am writing about seeing practice, and this is the pattern I find hardest to watch, because it is so easy to mistake for progress. A team relearning something it already knew looks, from the outside, exactly like a team learning.

The lesson was never really kept

We tell a comfortable story about organisations getting smarter over time. Each project teaches us something, we fold that into how we work, and the next project starts from a higher floor. Experience compounds.

Sometimes it does. Often it does not. What actually happens, more than we admit, is that a hard-won lesson lives brightly for a while in the people who earned it, and then those people move on, or get reorganised into different teams, or simply get busy, and the lesson goes with them. The next generation of the team inherits the tools and the org chart but not the understanding. They keep the wiki and lose the reason it was written.

I have watched an organisation run the same discovery-versus-delivery argument three times in five years. Each round arrived convinced it was inventing the answer. Each round produced a deck, a new ritual, a burst of energy, and then faded as the people who cared about it drifted elsewhere. Nobody was incompetent. The knowledge just had nowhere durable to live, so it evaporated on the usual schedule, and the organisation reset to zero and started paying for the lesson all over again.

Documents hold information, people hold knowledge

The obvious fix is to write things down, and every organisation tries it. Post-mortems, retro notes, a Confluence page called Lessons Learned that nobody has opened since the day it was created. The instinct is right and the result is thin, and it is worth being honest about why.

What survives being written down is information: the decision, the date, the outcome, the tidy summary. What does not survive is the knowing underneath it. The feel for why that call was hard, the argument that nearly went the other way, the context that made the trade-off obvious to the people in the room and invisible to everyone else. That kind of understanding is tacit. It lives in people and in the relationships between them, and it only really transfers when someone who holds it works alongside someone who does not, on real work, with enough unhurried time for it to surface.

So a filed post-mortem is not the lesson. It is a receipt for the lesson. When the people who understood it leave, the receipt stays and the understanding walks out the door, and the next team reads the page, nods, and learns nothing, because the words on their own were never where the knowledge was.

Why the same lessons, and not others

Notice that we do not relearn everything. Nobody rediscovers version control every eighteen months, or has a brave offsite about the importance of writing tests. Those lessons stick, because they are built into tools and habits that make the right thing the easy thing. The knowledge is held in the practice itself, not in anyone's memory of a good intention.

The lessons we keep relearning are the human, judgement-heavy ones. Talk to customers before committing. Say no to work that does not fit. Do not confuse being busy with making progress. These never resolve into a tool you can install, because they are not really facts to be known. They are practices to be kept, and a practice that stops being practised does not leave a gap where it used to be. It just quietly disappears, and the space closes over as if it was never there.

This is also why the cargo-cult version of good practice never protects you. A team copies the visible form of something that worked elsewhere, the ceremonies and the artefacts and the vocabulary, without the understanding that made it work. The form travels easily because it is information. The understanding does not travel at all, because it was tacit and situated and stuck to the people who had it. So the ritual gets performed, the results do not follow, everyone concludes the idea was overrated, and the lesson is not just lost but actively discredited, ready to be reinvented later by someone who does not remember it failing.

Amnesia is manufactured, not natural

It is tempting to treat all this as inevitable, the natural entropy of any group of people. Some of it is. But a lot of organisational forgetting is manufactured by choices we could see if we looked.

We reorganise for reasons that have nothing to do with the work, and each reshuffle scatters the small groups where tacit knowledge actually lived. We reward the visible arrival of a lesson, the offsite and the announcement, and never the unglamorous maintenance of one that is already known. We treat a departing person as a headcount to backfill rather than a library about to be deleted, and we let them leave with two weeks of handover notes standing in for years of context. We prize the fresh start, the new leader with the clean slate and the bold plan, over the continuity that would have made the plan unnecessary.

Each of these is a decision. None of them feels like a decision to forget. But together they are exactly that, and the recurring amnesia we then complain about is not bad luck. It is the predictable output of a system optimised for motion and novelty over continuity and understanding.

Seeing practice through what we forget

I do not have a five-step programme for this one, and I am a little suspicious of anyone who does, because a durable fix for forgetting that lives in a document would be its own small joke. Reflection is more useful here than prescription.

What I can offer is a habit of attention. The next time your organisation gets excited about a new realisation, ask quietly whether it is genuinely new, or whether it is a lesson you already paid for and let lapse. If it is a rerun, the interesting question is not what the lesson is, since you clearly know that. It is why it did not survive last time, and what would have to be different for it to survive now. That question is uncomfortable, because the honest answer usually implicates how the organisation treats people, time, and continuity, not how it writes its notes.

And when you find someone who holds one of these hard lessons, the person who remembers why a thing was decided and what it cost, treat that as the fragile and valuable thing it is. Give them time with the people who will inherit the work. Not a handover document. Actual shared work, long enough for the tacit part to pass across. That is slow, it does not show up on a board, and it is very nearly the only thing that turns a lesson into something an organisation can keep.

We do not forget because we are careless. We forget because remembering is a practice, and we keep choosing not to make time for it.