The Decision Is Made at Role Level. The Reality Is Individual.

Why workforce plans keep producing beautiful slides and stuck transitions — and what it takes to fix that.


“Retention is an outcome. It shouldn’t be the goal.”

Zsuzsanna Friedl , CHRO of T-Systems International, put it that sharply in a recent LinkedIn post. Her argument: when an organization is transforming, the question is no longer how do we reduce attrition? But do we have the capabilities we need for the future? Sometimes that means retaining key talent. Sometimes reskilling. Sometimes making difficult decisions and allowing healthy attrition.

I agree with every word. And I want to push the thought one level deeper — because in my modelling work, this is precisely where most capability strategies quietly fail.

The question “do we have the capabilities we need?” is usually asked, answered, and planned at role level. But the reality is individual.

The role-level illusion

Workforce plans are born in role-level spreadsheets: headcounts per job, jobs per family, families per function. It’s a sensible abstraction for budgeting. It’s a dangerous one for transformation, because three layers of granularity get lost on the way down.

The task mix. AI doesn’t disrupt job titles; it disrupts tasks. Two roles carrying the semi-identical title can face completely different futures depending on what the people in them actually do all day. One “analyst” spends sixty percent of the week on work that’s automating fast; another “analyst,” similar title and same grade, spends twenty. Plan at the title level, and you will confidently retain people whose work is disappearing — and release people whose work is about to grow.

The skill profile. Even with identical task mixes, two people in the same role begin a reskilling journey from very different places. What determines the cost, the duration, and the probability of success of a transition is not the current title — it’s the distance between an individual’s skill profile and the target role. Averaging that distance across a role produces a reskilling budget that is precisely wrong for everyone.

The individual. And then the layer that no spreadsheet captures: a transition path is not an assignment. It’s an offer that a human being has to accept and carry through. Impact and potential shape who is worth investing in; ambition — the least measured and often the most decisive variable — shapes who will actually walk the path. You may not be able to model ambition itself, but you can certainly model what your plan looks like when a third of the people on it decline the journey.

The constraint nobody plans

Suppose you get all three layers right. There is still a binding constraint that almost never makes the slide deck: absorption capacity.

Target roles are not an infinite sink. Each one has a net number of openings, on a timeline, shaped by demand plans on one side and attrition on the other. If your transition logic sends forty people toward a target role that can realistically absorb twelve over the planning horizon, the other twenty-eight have not been “reskilled.” They’ve been queued. Every planned transition consumes capacity that the next transition no longer has — and attrition shifts that capacity dynamically, month by month.

This is why attrition, demand and transitions cannot be solved sequentially — first a demand plan, then an attrition forecast, then a matching exercise — and simply stapled together. They are one allocation problem, and they have to be solved together. Solved separately, they produce what I’ve come to call beautiful slides and stuck transitions: a plan everyone approves and nobody can execute.

From three labels to a portfolio

Seen this way, retain / reskill / release stops being three labels stamped onto roles and becomes a portfolio allocation under constraints. And like any allocation, it involves genuine strategic choices. Do you treat net openings as a hard constraint and plan strictly within them? Do you deliberately build a talent pool beyond today’s openings, betting on future demand? Do you protect current incumbents and move only through natural attrition?

These are legitimate strategies with different costs, different risks, and different messages to the organization. A leadership team should choose between them consciously — not inherit one silently from a spreadsheet default.

The bar: numbers a CFO accepts

None of this becomes a business conversation until it arrives in numbers a CFO accepts. Which tasks change, and when. What each transition path costs, per person, not per role. What the constraint-adjusted plan actually delivers, quarter by quarter — and what it costs to relax the constraint.

That’s the bar. Below it, “healthy attrition” remains a guess dressed up as a strategy. Above it, it becomes exactly what Zsuzsa’s post calls for: the right capabilities, delivered on time, to execute the business strategy.

This thinking is what we’ve built into gAIn, the strategic workforce planning tool we’ve been developing at Hybridge. But tool or no tool, the shift starts with a single question worth asking of any workforce plan on your desk right now:

Are we planning at the level where decisions are made — or at the level where reality happens?

Plan at the level where reality happens.

Explore gAIn →Book a call →