A team I worked with ran a product launch last year. The people who built the original launch process had moved on to other roles. The team didn’t track them down. The process was in SharePoint, with a worked example beside it, and every gate carried the reasoning for why it was there. The team read it, applied it to a situation the original authors had never seen, and ran the launch.

No one called the authors. No one scheduled a meeting to work out what the process really meant.

The launch ran cleanly because the work remembered. The reasoning lived in the work itself, available to people who had never met its authors. That is a property of how the work was designed, and most work is designed the other way.

What the team didn’t have to do

Start with what was absent, because the absence is the whole point.

No one reconstructed the history of why the process existed. No one pinged a former colleague to ask what a step was for. No one sat in a meeting translating a document written for one situation into guidance for a different one. The launch started from where the recorded work left off.

Most teams run the other version. The process exists, technically, but the reasoning behind it lives in whoever set it up. When that person is gone, the work stops until someone reconstructs what they knew.

The reconstruction is invisible in every plan and real in every calendar.

What you’re crediting to your people

When a team orients a new hire quickly, when a handoff goes clean, when a decision from last quarter still holds, it’s natural to read these as evidence of strong people. The experienced contributor who remembers. The careful operator who documents. The person you can always ask.

Those people are real and worth keeping. But the outcomes you’re crediting to them are produced by something else: work that records its own decisions and state as it goes. When orientation is fast, it’s because the work holds what a new person needs to know. When a handoff is clean, it’s because what the next person needs was written where they can find it.

The difference matters because people leave and design stays.

Continuity that depends on the right person being available is one resignation away from gone.

Continuity built into the work survives the resignation.

What work with a memory holds

Three outcomes follow when the work keeps its own record, and each is concrete enough to look for.

A decision that survives the quarter. A choice made in January still governs the work in June, and anyone on the team can say why, because the reasoning was recorded when the decision was made, not reconstructed later from memory.

An orientation measured in hours. A new contributor reads the record and starts contributing the same week, because what she needs is in the work rather than in a series of conversations with the people who have been there longest.

An update that is short because it is complete. The status update is four sentences and leaves nothing out, because the record underneath it is current. The long update is long because the writer is reconstructing state in real time. The short, complete update is a sign the work already holds it.

What to check this week

Take one process or recurring decision your team relies on. Read it as if you had never seen it.

Ask whether it records why, not just what. A gate with its reasoning beside it can be followed in a new situation by someone who wasn’t there when it was written. A step with no reasoning attached can only be followed by someone who already knows the intent, which means it depends on that person staying reachable.

If you find the reasoning missing, you’ve found where the work is leaning on a person instead of holding itself.

The test of whether your work has a memory is what happens when the people who built it aren’t in the room. A team that can run the launch without them has work that remembers. A team that has to find them first has people doing the remembering.

A team that can run the launch without them has work that remembers. A team that has to find them first has people doing the remembering.

👉 See where your team’s work depends on who’s in the room: https://amykennedyleadership.com/choose-your-diagnostic/