Why the second time is not faster

A business opens a second outlet, launches a second product line, or enters a second market, and the reasonable expectation is that the second attempt will be faster than the first — after all, the business has already done this once and presumably learned something. Often it isn't faster. It takes nearly as long, makes many of the same mistakes, and the only advantage the second attempt has is a vague sense of déjà vu among the people who were there the first time.

Experience and reusable knowledge are not the same thing

The people involved in the first attempt genuinely did learn something. The problem is that what they learned lives in their memory, in the specific form their brain happened to store it, accessible only when they personally think to apply it to the new situation. It was never converted into something the business could hand to a different team, or even to the same team facing a slightly different version of the problem.

This is why "we've done this before" so often turns out to mean less than it sounds like. Doing something before builds personal experience. It doesn't automatically build institutional capability, and only the second one actually makes the next attempt faster for people who weren't there the first time.

Where this shows up most clearly

Opening a second location. The first outlet taught the business real lessons about local staffing, supplier logistics, and customer behaviour in that specific area. None of it transfers automatically to a second outlet unless someone deliberately extracts and reapplies it — see opening a second outlet without relearning the first outlet's lessons.

Repeating a project with a different team. A process improvement project run successfully once often gets run again from scratch for the next department, because the lessons lived in the project team's heads rather than in a reusable playbook anyone else could pick up.

Handling a recurring type of problem. A specific kind of customer dispute, supplier issue, or operational failure that recurs every year or two gets solved fresh each time, at full cost, because nobody wrote down how it was solved last time — only that it was.

Why this keeps happening even in disciplined businesses

Because capturing reusable knowledge takes deliberate effort at exactly the point when everyone involved is most relieved to be finished and least inclined to spend more time on it. The natural instinct after solving a hard problem is to move on. The habit that would actually pay off — writing down what was learned in a form someone else could use later — requires resisting that instinct at the worst possible moment for resisting it.

What makes knowledge reusable instead of merely remembered

Written specifically for someone who wasn't there, not as a summary for people who already lived through it. A retrospective written for the people who ran the project reads very differently from one written for a future team facing a similar problem for the first time.

Organised around the decision, not the narrative. "We decided to do X because Y, and it worked/didn't because Z" is more reusable than a chronological account of what happened, because it's structured the way someone facing a similar decision would actually need it.

Captured close to the event, not reconstructed for a report later. The details that make a lesson genuinely useful — the specific reasoning, the near-misses, the things that almost went wrong — degrade in memory quickly. A note taken during or immediately after the event holds far more than a summary written weeks later for a review meeting.

Common questions

Why doesn't experience automatically make a repeated task faster?

Because experience is personal — it lives in the memory of the specific people who lived through it — while making the next attempt faster requires that experience to be converted into something reusable that other people, or the same people facing a variation of the problem, can actually apply. That conversion doesn't happen automatically; it requires deliberate effort.

What kinds of situations show this problem most clearly?

Opening additional locations, repeating a project type with a different team, and recurring operational problems that come up every year or two. In each case, the business has technically "done this before," but the lessons stayed with specific individuals rather than becoming something the wider organisation could draw on.

Why is it hard to capture reusable lessons even when people know they should?

Because the moment a hard problem is solved is exactly when everyone involved is most relieved to move on and least motivated to spend more time documenting it. Capturing the lesson well requires resisting that natural instinct at precisely the point it's strongest.

What makes a captured lesson actually reusable later?

Writing it for someone who wasn't there, rather than as a summary for people who already know the context. Organising it around the decision made and why, rather than a chronological narrative. And capturing it close to the event, since the specific reasoning and near-misses that make a lesson useful fade quickly from memory.

Related: opening a second outlet without relearning the first outlet's lessons · what leaves with an employee that the erp never had · rehiring the same knowledge twice