I Forgot: Context Loss Is More Human Than You Think

We’ve been living with context loss for as long as humans have organized into groups. Every time a senior engineer quits and takes undocumented knowledge with them. Every time a project gets handed off and the new team rebuilds from scratch because the brief was a two-sentence Slack message. Every time a meeting produces action items that contradict the last meeting’s action items because nobody reviewed the notes. This is context loss. We’ve just never had good language for it.

AI gave us the language.

In large language models, context loss is measurable and precise. An LLM has a context window — a finite amount of information it can hold in working memory at any given moment. Research from Stanford has shown that when you put critical information in the middle of a long context, model performance degrades significantly — a phenomenon researchers call being “lost in the middle.” The model doesn’t flag that it’s struggling. It doesn’t ask for help. It just gets worse — confidently.

A 2025 study went further: even when a model can perfectly retrieve every piece of evidence in its context (reciting tokens with 100% accuracy), its ability to reason about that information still degrades as the context grows. The problem isn’t memory. It’s comprehension under load. The system has the information. It just can’t use it anymore.

Sound familiar? It should.

In 1975, Fred Brooks published The Mythical Man-Month and gave us a formula that should be tattooed on the forearm of every project manager: n(n-1)/2.

That’s the number of communication channels required when n people need to coordinate. Two people need one channel. Five people need ten. Ten people need forty-five. Fifty people need 1,225. The relationship isn’t linear. It’s combinatorial. And every channel is a potential point of context loss.

Brooks’s central insight — “adding manpower to a late software project makes it later” — has been validated across thousands of software projects over the following decades. The reason is always the same: new people don’t arrive with context. They have to acquire it. And acquiring context consumes the very resource (experienced people’s time) that was already scarce.

But Brooks only described the scaling problem. The deeper issue is what happens to context once it’s distributed across multiple minds.

According to research from IDC, Fortune 500 companies lose an estimated $31.5 billion per year to what researchers call “institutional forgetting” — or, less politely, corporate amnesia. Employees spend a full fifth of their work time searching for knowledge that already exists somewhere in the organization. Bloomfire’s 2025 research found that knowledge mismanagement costs companies an average of 25% of their annual revenue. The knowledge exists. It’s just distributed across so many memory banks — people’s heads, email threads, abandoned Confluence pages, someone’s notebook from a meeting in 2023 — that it might as well not exist at all.

The AI systems we’re building to solve these problems are developing the exact same failure modes. For the exact same structural reasons.

In 1967, Melvin Conway observed that ”organizations which design systems are constrained to produce designs which are copies of the communication structures of those organizations.” Conway’s Law has been a truism in software engineering for decades. It’s now becoming the defining law of AI agent architecture.

A company builds an agentic AI system. Customer support builds a support agent. Sales builds a lead qualification agent. Finance builds an invoice processing agent. Legal builds a compliance agent. Each agent is optimized for its domain, trained on its department’s data, governed by its department’s rules. The resulting system — a network of specialized agents that struggle to communicate across boundaries — is a pixel-perfect copy of the org chart.

The fault lines between agents follow the same boundaries as the fault lines between human teams. Agents owned by the same group share data easily. Cross-team agent collaboration is rare, brittle, and expensive. When an agent needs context that lives in another agent’s domain, the handoff is lossy. Information gets summarized, compressed, or dropped entirely.

Research on multi-agent systems from UC Berkeley quantifies this. Failure rates across seven major multi-agent frameworks range from 41% to 87%. These systems consume far more computational resources than theoretically necessary, not because the individual agents are inefficient, but because the coordination overhead is enormous.

The math is the same math Brooks described in 1975. Five agents create ten potential handoff pathways. Ten agents create forty-five. But it’s not just that more pathways exist — it’s that the consequences are identical. Each handoff is a point where context degrades, where nuance gets compressed into summary, where the receiving agent proceeds with slightly wrong assumptions.

As the Berkeley research team put it: ”Most ‘agent failures’ are actually orchestration and context-transfer issues.”

Replace “agent” with “team member” and you’ve described every failed enterprise project in history.

Context loss would be manageable if it were static — if you lost a fixed percentage of information at each handoff and could plan around it. But context doesn’t just disappear. It rots.

The term “context rot” emerged in mid-2025 to describe what happens when model performance systematically degrades as input context length increases, even when the underlying task remains simple. It’s not that the model forgets. Each piece of information slightly distorts the model’s processing of every other piece. The distortions compound. Speaker identities get confused. Timelines warp. Unrelated facts merge. The model doesn’t crash. It drifts.

A longitudinal study of multi-agent AI systems measured this drift precisely. Over extended interactions, task success rates dropped by 42%. Response accuracy declined by nearly 25%. The number of times humans had to intervene increased by 216%. And the pattern was consistent: the agent didn’t suddenly malfunction. It slowly became less reliable as ”each slightly wrong memory entry influenced the next summarization, which influenced the next recall, which influenced the next decision.”

Organizations experience the same compounding decay. It’s just slower, harder to measure, and easier to misattribute.

Every “let me loop in Sarah on this” is an expansion of the context window. Every set of meeting minutes is a lossy compression of the original conversation. Every status meeting where twelve people sit through updates relevant to three of them is noise being injected into the signal. Every time a project gets restructured and responsibilities shift, the tacit knowledge about why certain decisions were made — the context that never made it into documentation — drifts a little further from the people who need it.

Organizational knowledge doesn’t sit still. It degrades with every transfer, every translation, every new person who inherits a project and fills in the gaps with assumptions. Knowledge management is entropy management — slowing the inevitable diffusion of critical context into inaccessible corners of the system.

The stakes vary by domain. In knowledge work, context rot costs money — poor communication contributes to more than half of project failures , according to PMI research. In AI, it costs credibility — Gartner predicts 40% of agentic AI projects will be canceled by 2027. In healthcare, where communication failures are the leading cause of sentinel events, it costs lives — linked to an estimated 150,000–250,000 patient deaths annually. The mechanism is always the telephone game: information distorting as it passes through nodes, each handoff stripping away nuance that seemed unimportant to the sender but turns out to be critical for the receiver.

Different domains. Same rot. Same math.

Companies are racing to deploy multi-agent AI systems — Gartner reports a 14x surge in multi-agent system inquiries from early 2024 to mid-2025 — while simultaneously failing to manage context in their human organizations. They’re building AI architectures that inherit all the communication pathologies of the teams that built them, then wondering why the AI systems exhibit the same coordination failures.

Jensen Huang at CES 2025: ”The IT department of every company is going to be the HR department of AI agents in the future.” If that’s true, then organizations deploying agents at scale are about to confront context loss at a speed and visibility they’ve never experienced before. When a human team loses context, the failure unfolds over months. People compensate. They ask around. When an AI agent loses context, the failure is immediate, measurable, and reproducible. You can’t explain away a 42% drop in task success in a quarterly review.

That visibility is an opportunity. Because it turns out the solutions are the same for both systems.

There’s a reason “context engineering” is becoming the defining skill of AI development. The people building the most capable AI systems have realized that the quality of your context matters more than the power of your model. You can upgrade to the latest frontier model, but if your context is garbage — irrelevant information, missing information, poorly structured information — you’ll get garbage output with better grammar.

The same is true of organizations. You can hire the most talented people in the world, but if critical context lives in one person’s head, if handoff protocols don’t exist, if institutional memory resets every time someone leaves, those talented people will spend their time rediscovering things the organization already knew.

Anthropic’s engineering team captured the underlying principle: ”The quality of an agent often depends less on the model itself and more on how its context is structured and managed.”

A mediocre team with excellent knowledge management will outperform a brilliant team drowning in silos. That’s always been true. We just didn’t have a precise way to say it until we started watching AI agents fail in exactly the same ways our teams do.

The disciplines that prevent context rot in AI systems are the same ones that prevent it in human organizations. Here’s how to apply them:

1. Bound the state

For AI: Effective agents maintain a compact cognitive state — goals, constraints, confirmed decisions — rather than trying to hold everything in context.

For teams: Keep a living “project state” document that fits on one page. Goals, current blockers, recent decisions, next actions. If someone asks “where are we?” the answer should take thirty seconds, not thirty minutes.

The test: Can a new person (or agent) get oriented in under five minutes? If not, your state is too diffuse.

2. Structure the handoffs

For AI: Free-text handoffs between agents are the leading source of context loss. The fix is schema-validated payloads — structured formats that force explicit transfer of key information.

For teams: Create a handoff template and actually use it. What’s the current state? What decisions have been made and why? What’s been tried and didn’t work? What does the next person need to know that isn’t written down anywhere?

The test: Could someone take over this project from your handoff document alone, without a synchronous conversation? If not, your handoff is too loose.

3. Externalize the memory

For AI: Retrieval-augmented generation pulls relevant information from external knowledge bases on demand rather than stuffing everything into the context window.

For teams: Build a knowledge base that people actually use. Decision logs. Post-mortems. A searchable record of why things are the way they are, not just what they are.

The test: When someone asks “why did we decide X?” — can you find the answer in under two minutes without asking a person? If not, your memory is too volatile.

4. Budget the attention

For AI: Context windows are finite. Every irrelevant document chunk you inject degrades the system’s ability to process what matters.

For teams: Attention is finite. Every person you add to a meeting, every “FYI” email you send, every status update that could have been async — it’s all noise competing with signal.

The test: For every piece of information you’re about to share, ask: does this person need this to do their job? If not, don’t send it.

5. Consolidate regularly

For AI: Systems that periodically compress and consolidate their accumulated context show significantly less drift over extended interactions.

For teams: Sprint retrospectives, post-mortems, lessons-learned sessions. The practice of regularly stopping to ask: “What do we know now that we didn’t before? What should we remember? What can we let go?”

The test: Does your team have a regular ritual for turning experience into institutional memory? If not, you’re relying on individual recall — which means you’re one resignation away from forgetting everything.

 — -

The parallel isn’t perfect. AI context windows and human working memory aren’t mechanically identical — an LLM can “look back” at earlier parts of its context in ways human short-term memory can’t. The analogy is structural, not literal. But the structural similarity is what makes it useful. Both systems degrade when overloaded. Both lose critical information at handoff points. Both compensate for missing context by filling in gaps — humans with assumptions, AI with hallucinations. And both respond to the same interventions.

The organizations that take context engineering seriously for their AI systems will inevitably start applying those same disciplines to their human teams. Once you see the failure mode clearly in one domain, you can’t unsee it in the other.

And the organizations that don’t? They’ll build AI systems that inherit every communication pathology their human teams already have, then scale those pathologies at machine speed.

AI didn’t invent context loss. It just made it impossible to ignore.