Skip to content
Back to insights
Systems Thinking

Career competence vs subject expertise: the Survivor game

The most capable people I have worked with rarely had the most successful careers.

It is an uncomfortable observation. But it holds in enough cases to be a pattern, not an anecdote.

In mid-sized and large organizations there is a competence that is never mentioned in job profiles but determines who advances. I call it career competence: the ability to navigate internal politics, position yourself correctly, say the right thing in the right meeting, avoid risks and appear capable in your manager’s eyes. It is the Survivor game, but with salary negotiations.

I have nothing against ambition. Ambition can drive people to do good things. The problem arises when career competence is systematically rewarded more than subject expertise. And it is. Often.

Who survives, who gets voted off

Picture a mid-sized organization (200 people, three layers of management) with a planner who has been in the role for eight years. She knows which shifts can absorb a late delivery, which customers will accept a reschedule by phone, and which forklift driver tends to call in sick on Mondays. None of this is in any document. It lives in her head.

Next to her sits a younger colleague who joined eighteen months ago. He is not as good at planning, but he sits in on the right calls, reframes problems in the language his manager uses, and volunteers for cross-functional projects that get visibility. When the team lead position opens up, he gets it. She does not. Her manager will tell you, without irony, that he could not afford to move her. She was too valuable where she sat.

That is the mechanism. The organization needs the expert in place. Moving her up creates a competence gap. Keeping her where she sits creates no visible problem. Nobody complains. Nobody measures the missed career as a cost. But it is a cost. The signal value spreads. Everyone sees who advances and why.

Six months later she starts looking. A year later she is gone. Her replacement needs eighteen months to reach 70% of her output, and some of what she knew is simply lost because it never made it into any system. The org chart looks the same. The capability is not.

The same game, different boards

I have seen this in three different worlds. Startup, public sector, large corporation. The scale varies. The mechanism is identical.

In the startup it was most transparent. Ten people, everyone saw everything, and you could not maneuver without being noticed, which kept the game honest most of the time. In the large corporation it was most pronounced. Thousands of employees and enough layers for internal politics to become a full-time occupation. Someone could spend two years building relationships across three departments without producing a single deliverable, and end up promoted on the strength of “stakeholder alignment”. In the public sector there was its own variant: whoever stayed the longest gained the most influence, regardless of competence. Seniority as career strategy.

This is not about individual people. It is about what the organization rewards. If the system rewards those who are visible more than those who know, the system produces managers who are visible and experts who quit.

What the org chart does not show

There is an irony in it. Organizations talk about being “knowledge-driven” and how “the right competence in the right place” matters. At the same time, promotion decisions reveal what is actually valued. And it is rarely the deepest subject expertise. It is the ability to communicate expertise upward, whether you own it or borrowed it from someone else.

I do not think this can be solved with a new HR process. It runs deeper. As long as management appointments reward visibility over substance, the pattern will persist. But you can become aware of it. And you can ask an uncomfortable question.

How many subject experts has your organization lost in the last five years? Not because they were laid off. But because they were overlooked enough times.

That may not show up in any KPI. But it shows in what the organization knows. And in what it gradually stops being able to do.