The toughest teams I have seen were never lacking in talent or effort. What they possessed was skill for work that had, almost unnoticed, ceased to be the real work. The job titles did not change. The work beneath them did. By no choice of their own, a set of seasoned professionals ended up underqualified for roles they already held.
This is among the most frequent patterns in transformation, and also one of the least truthfully discussed. Capability gaps are often spoken about as if they were purchasing issues: identify the missing ability, acquire the training, eliminate the gap, carry on. Yet what is actually present in the room is more intricate. Competence is tied to how people understand their place at work. When it disappears, something bigger than output disappears with it.
Leaders often misread the first warning signs. The team takes longer to commit. Estimates grow. Questions once raised openly begin to surface in hallways, or vanish altogether. Work returns late, wrapped in justification. It can look like resistance, and then it is handled as resistance, meaning it is treated as an attitude issue. Usually, it is not. It is a group trying to safeguard the last part of its working identity that still feels intact.
Name the gap without indicting the person
The natural response is to make it gentler. Leaders speak of uplift, journeys, and everyone being on a learning curve, while the team hears a manager who has noticed the problem and refuses to name it. Ambiguous comfort is not kindness. It leaves people alone with a reality they already sense, and it teaches them the topic is off limits.
The better move is precision, and to place the change rather than the person at the centre of the sentence. You are not behind. The work shifted. Here is where it shifted, here is the distance, here is the time I believe it will take. That is not a euphemism. It is plain accuracy: almost no one in these situations failed at anything. They were rewarded for years for being excellent at something that has now been automated, reorganized, outsourced, or overtaken.
What matters is that the team hears this from its leader before it hears it through a restructure, a performance review, or a job posting for a role that sounds uncomfortably like theirs in different language. Once people discover the message came from somewhere else first, support loses credibility.
Protect some ground where they are still expert
Transitions break down when people lose every source of standing at once. A person who is a beginner in every area has nowhere to stand while learning, and the quickest escape from that discomfort is to defend the old method loudly or depart quietly.
So the design question is not only what they need to learn. It is also what they still know better than anyone else. In almost every case, there is something: the customers, the failure points, the regulatory past, the reason an earlier version of the idea collapsed, the informal map of who really makes decisions. Intentionally pair that knowledge with the new capability instead of replacing it, and two helpful things happen. The learning takes place inside real work for a reason, and the person retains a place at the table that is not charity.
Then create a safe place for them to be bad at the learning. Training gives vocabulary. Repetition in real work builds skill, and repetition only comes from accepting a stretch of time when the output is slower and rougher than before. Someone must absorb that expense. If the leader refuses to carry any of it, the team will infer that learning is a personal risk borne in their own time, and they will do the sensible thing and stop.
Timing matters more than programme structure. A person can be a true beginner in one area, maybe two, at once. A capability plan that demands five simultaneous transitions is not bold; it is a way to ensure nothing sticks and everyone feels inadequate as it fails.
A capability gap is not a judgment on a person. It becomes one only when a leader handles it as something the person is not permitted to know.
Be honest about who is not crossing
Not everyone gets across. To pretend otherwise is cruelty in the costume of optimism, because it postpones the conversation until the only option left is an exit that lands as a shock.
The truthful version includes a real runway with a stated timeline, feedback specific enough to use, and a decision point both people can see approaching. When the answer ends up being no, the person should hear it early enough to make choices and leave with their reputation preserved. This is not a minor concern. A team watches much more closely how the person who did not make it is treated than how the successful ones are praised, and it adjusts its sense of how safe honesty is according to what it sees.
There is a version of this leadership that is mostly administration: courses scheduled, mentors matched, a matrix of green cells filling in over time. It is not pointless, and it is not what determines the result. What determines the result is whether people can be openly unskilled for a period without deciding they have become worthless.
That is the real task of leading a team through this, and it is more demanding than it sounds because it requires the leader to hold two truths at once for months. What this person cannot yet do. Who this person is. Most people cannot maintain that distinction about themselves while they are struggling. For a time, someone else must hold it for them.