01
Build the directory
Move directory accuracy upward while holding specialization steady. The group improves without teaching anyone a new domain.
communicoupling
The group remembers
where to ask.
A good team does not copy every fact into every head. One person remembers the contract, another the deployment, another the client history—and everyone carries a rough directory of who knows what. The knowledge is differentiated; access to it is shared.
Daniel Wegner called this a transactive memory system. It lets a group store more than any member could, but it creates a peculiar fragility: lose the expert, corrupt the directory, or route every question through the same prestigious person, and knowledge that still exists becomes functionally unavailable.
specializationhow sharply expertise is divided
directory accuracychance a task reaches its expert
turnoverdirectory entries made obsolete
tasks solved
—
correct answers before the deadline
routing waste
—
queries sent first to a nonexpert
knowledge at risk
—
performance lost if the busiest expert leaves
A directory under load
green: solved work by batch · red: first-route errors; a new run changes the task order, not the parameters
Set the conditions
what to try
Separate stored knowledge from access to it.
02
Turn expertise into a dependency
Raise specialization with a weak directory. More knowledge exists, yet more work misses it on the first route.
03
Reorganize the names
Choose Reorganization. The expertise remains in the group while the map pointing to it goes stale.
the mechanism
Memory is expertise plus a routing table.
The instrument gives a team differentiated domains. A task has one best-qualified member. Directory accuracy determines whether the first query reaches that member; turnover invalidates part of the directory. A failed first route may still be recovered through a second search, but it consumes time and makes the nominal knowledge less usable.
Specialization therefore has two effects. It raises the expert's advantage, increasing the group's potential memory, while making accurate routing more important. Transactive memory combines individual recall with reliable knowledge about the distribution of recall.
the social payoff
Teams forget before their people do.
A reorganization can produce collective amnesia even when no document disappears: names, responsibilities, and informal consultation paths no longer point where they used to. Conversely, a mature pair can retrieve with a glance because each has learned what the other is likely to hold.
Directories, code ownership, escalation paths, and acknowledgements of expertise are memory infrastructure. They make knowledge addressable—but can also freeze stereotypes about who is supposedly good at what.
the mapping
Mechanism ↔ social life.
| In the model | In the world |
|---|---|
| expertise profile | The differentiated facts and skills stored across members. |
| directory | Shared expectations about who knows which domain. |
| routing error | Asking the visible person rather than the knowledgeable one. |
| turnover | A member, role, or responsibility changes while the old directory persists. |
| second search | Escalation, forwarding, or asking around after the first answer fails. |
where it tears
Limits.
Directories reproduce status.
A group can repeatedly route prestigious work to the person already seen as expert, denying others the experience that would revise the directory.
Knowing who knows is not knowing whether they are right.
Expert location and epistemic quality are separate problems. A precise directory can efficiently retrieve a shared mistake.
Some redundancy is insurance.
Perfect specialization is efficient only while people and channels remain available. Safety-critical teams deliberately duplicate knowledge that this model treats as waste.