Every team has someone who knows the work from the inside. She was there when the approach was decided. She knows why that constraint exists, what was tried before, and what that means for anything similar now. When she is in the room, work moves. When she is not, things slow in ways that are hard to name.
The context travels with her. The work keeps none of it.
How people become load-bearing
Context that is not captured has to live somewhere. It lives in the people who were present when decisions were made, when scope changed, when tradeoffs were settled. Those people carry it forward, in their heads, in their judgment calls, in their presence at the right meetings.
The arrangement stays intact as long as the carriers stay available. Most of the time, it stays intact. The problem is not visible when it is working.
It becomes visible when someone is out for a week, or moves to a different role, or the team grows and context that one person kept informally needs to reach five people it has never reached before. At that point, the team finds that the work had no memory. The people did.
Why the work doesn’t capture its own context
Context capture requires a specific act at a specific moment. Most work processes do not include it.
The decision gets made in the conversation. Someone may write a note, or may not. The reasoning rarely gets recorded: why that approach, what was weighed and set aside, what the team would do if conditions changed. The context that took three weeks to develop gets compressed into an output, a document, a ticket, a task. The reasoning stays in the room where it was produced.
The output is retrievable… maybe. The thinking behind it is not.
What the team inherits
When a new team member joins, or a project resumes after a pause, the team inherits the outputs without the reasoning. Someone has to supply the gap. Usually it is whoever has been there longest.
That person becomes a single point of access for context the work should distribute on its own. The longer the project runs, the more context accumulates in her. The more it accumulates, the harder it is to transfer, because it is woven into informal knowledge that was never formally recorded. The team cannot write it down now, because it was never captured in the moment it was produced.
The team experiences this as a talented person who knows the work well. The gap becomes visible only when she leaves.
What changes when the work is designed to capture context
Work that captures its own context (decisions, reasoning, tradeoffs considered, current state) gives every team member access to the same starting point. A new contributor reads the record rather than scheduling a conversation with the person who keeps it. The work resumes after a pause without reconstruction. The update reflects where things stand because that is recorded, not because someone who remembers is in the room.
When context lives in the work, the carrier is freed to do what people are better suited to: judgment, evaluation, advancement. The organizational memory belongs to the organization, not to whoever has been around the longest.
What lives only in people leaves when they do. Work designed to carry its own context does not.
👉 Find out where your team’s work is losing context: https://amykennedyleadership.com/choose-your-diagnostic/