The Team That Lost Its Anchor

The Person Who Is Not in the Org Chart

Some teams have a person at their centre who is not the most senior or the most visible. They are not necessarily the team lead. They may not have a title that reflects their actual function. But they are the person the team orients around — the one whose operating nature provides a kind of gravitational stability that others, consciously or not, use to calibrate their own functioning.

When that person leaves, the team does not simply lose a contributor. It loses its anchor.

What the Anchor Function Is

The anchor function in a team is structural, not hierarchical. The anchor is the person whose operating nature most consistently provides what the team's collective cognition requires to function well. In some teams, this is the person who makes sense of ambiguity — who translates unclear direction into navigable action. In others, it is the person who holds the social coherence of the group — whose presence reduces interpersonal friction and maintains the conditions in which others can work. In others still, it is the person whose judgement on consequential decisions has become the implicit reference point everyone defers to.

These are different functions. What they share is that the team has built its operating rhythm around a particular person's signature.

The Departure That Breaks the System

When an anchor leaves, the team typically does not identify what it has lost with precision. The departure registers as the loss of a good person. The organisation processes it as an attrition event — the kind that requires a replacement hire. HR moves quickly. The vacancy is filled. But the replacement hire is a different person with a different operating nature. They cannot replicate the anchor function. They were not hired to replicate it, because the organisation did not understand that it was an anchor function that needed replicating.

The team's performance erodes. The interpersonal friction increases. Decisions that previously felt natural now feel laboured. The leadership tries various interventions. None of them reach the actual source of the problem, because the actual source has not been named.

Why the Anchor Is Invisible

The anchor function is invisible until it is gone because it works through operating nature — through the structural way a particular person's signature interfaces with the team's collective cognition. This is not visible in an org chart. It is not captured in a performance review. It is not part of the official account of how the team works. It is, however, very real. And when it disappears, the team's operating system is disrupted at a layer that conventional retention and replacement processes were not designed to see.

Research on high-performing teams consistently identifies what researchers call "informal network centrality" — the degree to which one person sits at the intersection of the team's functional relationships. People with high informal centrality are disproportionately load-bearing for the team's performance, and their departure disproportionately disrupts it. But this centrality is structural, not positional — and most organisations measure position, not structure.

Understanding the Anchor Before the Departure

Understanding the anchor function requires mapping the operating nature of the team — not just individually, but collectively. Seeing whose signature is load-bearing for the group's performance. Knowing, before the departure, what the team would lose and what it would need. That knowledge changes how organisations approach succession, team design, and the management of talent risk.

It does not require predicting who will leave. It requires knowing who the team actually depends on at the operating nature level — and making structural choices about how to distribute that dependency so that no single departure can collapse the system it was holding together.

Rebuilding After the Loss

When the anchor has already gone, rebuilding requires understanding what was actually lost — not the job description of the departed person, but the operating nature function they provided. What did the team use that person for? What did their presence enable? What has their absence disrupted at the level of how the team actually works?

Answering these questions with precision changes the replacement decision. Sometimes the right move is to hire a person with the same operating nature signature. Sometimes the right move is to distribute the anchor function across two or three people. Sometimes the right move is to rebuild the team's collective operating architecture from scratch, designing the new version around what is known rather than replicating what was assumed.

Request Access at planets9.com