The Team That Lost Its Anchor

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.

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

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.

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

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.

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.

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.

Before WHY, there is WHO.

The team that lost its anchor did not lose a headcount. It lost a structural element of its operating system. Rebuilding it requires understanding what that element was — and finding it again, deliberately, rather than hoping the next hire fills a gap that was never clearly named.

When intuition stops scaling, but responsibility does not — there is a path.

Request Access.