Terms  /  Architecture  /  The Expertise Trap
05 · Architecture

The Expertise Trap

Context and knowledge locked on one person's machine, inaccessible to the team.

The Expertise Trap happens when one person builds up extensive AI context — prompt libraries, agent configurations, memory stores, workflow patterns — and that knowledge exists only in their local environment. When they're out sick, on vacation, or leave the company, the team loses access to everything they've built. This is the AI equivalent of the developer who never documents anything and keeps all the architecture in their head, except it's worse because the "documentation" is literally stored context that another person can't access.

Example
A senior engineer has spent three months training an AI agent on their team's codebase. The agent knows the architecture, the conventions, the deployment process, and the quirks of their legacy systems. It's stored in a local configuration that lives on the engineer's laptop. When the engineer takes two weeks off, the team can't access any of that context. They're back to vanilla AI with no project knowledge. When the engineer returns, nothing the team did in their absence is reflected in the agent's memory. The Expertise Trap created a two-week knowledge gap.

More in Architecture