The organisation converts its best technical judgement into its weakest management, then reads the result as a performance problem in the individual.
An engineering firm promotes its most accomplished structural engineer to lead a major delivery program. She has fifteen years of technical mastery, an unblemished record, and the respect of everyone who has worked with her. Eighteen months later she is exhausted, the program is behind, and her performance review contains phrases like needs to delegate more and should focus on the bigger picture.
Nobody in that story did anything unreasonable. The firm promoted its most capable person. She accepted a job she was told she had earned. Her reviewer described accurately what he observed. And yet the outcome was close to predictable from the day the appointment was made, because the promotion was not a promotion at all.
It was a career change, dressed as an advancement, and funded as neither.
The Strategic Context
Every enterprise depends on a small number of people to convert intent into outcome. Strategy is decided in one part of the organisation and realised in another, and the connective tissue between them is a role — variously titled project manager, delivery lead, program director — whose occupants are drawn almost entirely from the technical disciplines they now oversee.
This is not an accident of hiring. It reflects a reasonable belief: that credibility with a technical team requires technical standing, and that someone who has done the work will understand what the work requires. Both propositions have merit. The problem is the inference drawn from them — that technical mastery is therefore preparation for the role, and that someone who has mastered the discipline needs only a title to lead its delivery.
One of the more candid statements in the practitioner literature puts it plainly: moving from technical expert to project manager is not a promotion, it is a career change. That framing is worth taking literally rather than rhetorically. Organisations behave very differently toward the two. A career change comes with an induction, a learning period, a mentor, and an unspoken agreement that competence will take time. A promotion comes with an announcement, a larger remit, and an assumption of immediate capability.
The enterprise consequence is that the capability on which strategy execution most depends is the one capability the organisation systematically declines to build.
What Leaders Commonly Misread
The first misreading is that the role is an extension of the discipline. It is not. Robert L. Katz's durable distinction between technical, human and conceptual skill remains the clearest way to see this. Technical skill is proficiency in a specific kind of work — the methods, processes and tools of a discipline. Human skill is the capacity to work effectively with and through other people, and to build cooperative effort within a group. Conceptual skill is the ability to see the enterprise whole: how its functions depend on one another, and how a change in one part propagates through the rest.
Katz's contribution here is the distinction itself. The further claim — that a delivery role draws chiefly on the second and third categories while the promotion was awarded for the first — is the argument this article is making, supported by the teaching literature's own observation that managers promoted from technical fields tend to over-emphasise involvement in their area of expertise when what the role requires is attention to the management process, leaving others to perform the technical work.
The second misreading is that struggle in the role indicates the wrong person. The failure modes are too consistent across too many industries to be individual. The literature names them with unusual precision. Managers leading their own discipline delegate to the point of abandoning their own responsibility, because they trust specialists and feel unqualified to direct them. Managers leading outside their discipline reduce leadership to giving orders, achieving compliance at the cost of a disengaged team. Both types retreat into the office to get some "real work" done, and are then excluded from the conversations where the project is actually decided. Both dismiss risk and communication work as administration. Both micro-manage, because the technical detail is the only terrain where they still feel competent.
A pattern this reliable is not a hiring problem. It is what happens when capable people are put in an unfamiliar profession without being told it is unfamiliar.
The third misreading is that the fix is training. Courses help. They are not the constraint. The constraint is that the individual has been given no licence to be a novice — no period in which not knowing is expected, no framing that makes asking for help a sign of adjustment rather than of unsuitability. A person who has been expert for fifteen years and is suddenly a beginner, without anyone acknowledging the transition, will retreat to the ground where they are still expert. That retreat is the whole failure, and no course prevents it.
Reframing the Issue
The useful reframing is this: the promotion is an appointment to a different profession, and should be resourced the way a lateral hire into an unfamiliar function would be resourced.
Consider how a professional services firm treats a senior tax partner moving into the managing partner role. Nobody assumes the tax expertise transfers. There is a handover period, an explicit development plan, a peer they can call, and a shared understanding that the first year will be spent learning a job they have not done. The same firm will promote a delivery lead on a Friday and expect a program plan on the Monday.
The difference is not the difficulty of the two transitions. It is that one is recognised as a change of profession and the other is not.
Two consequences follow. First, the organisation should stop reading early struggle as evidence about the person and start reading it as evidence about the transition it designed. Second, and more uncomfortably, it should accept that some of its strongest specialists should not make this move at all — not because they lack potential, but because the enterprise loses more by removing them from the work than it gains by adding another under-supported delivery lead.
There is a related structural problem — that these roles routinely carry full accountability with very little formal authority — which compounds everything described here. That is a different argument with a different remedy, and it is treated separately in [Related article: Accountability Without Authority: How Organisations Design Delivery Leadership to Fail]. This article is about what the transition itself demands of the person making it. Nor is it about which leader to put on which initiative — a selection question answered from the shape of the work rather than from a competency list, and treated in [Related article: Read the Constraints, Not the Deliverables].
Strategic Analysis
The value at stake is not the individual's career
An organisation with fifteen delivery leaders, of whom perhaps five made the transition well, is not carrying a talent problem worth a line in the people review. It is carrying an execution problem across two-thirds of its change portfolio. Every under-supported transition shows up somewhere else as a late program, a benefit that never materialised, or a specialist team that has quietly stopped escalating problems because escalation has produced nothing useful.
The costs are invisible because they are attributed elsewhere — to scope, to suppliers, to an unrealistic schedule. The transition rarely appears in the diagnosis because by the time the consequences arrive, the promotion is two years old and nobody connects the two.
What the role actually asks for, and why it is hard to acquire
Three demands sit at the centre of the transition, and each runs against the grain of a technical career.
The first is relinquishing the how. A specialist is valued for knowing how. A delivery leader must set what and when, and leave how to the people who do the work — not out of humility but because a group can generate options an individual will not. This is a genuine loss, and it should be named as one rather than presented as an obvious efficiency.
The second is working laterally rather than downward. Specialists usually work with autonomy and a defined task; they are, in the literature's phrase, generally left alone to focus. A delivery leader's day is a stream of interruptions and continuous negotiation with peers who control resources they need and owe them nothing. Nothing in a technical career develops this.
The third is operating without the comfort of being the expert in the room. This is where integrity becomes the working currency. Saying I don't know, and I will find out is the behaviour that preserves a leader's standing when they cannot rely on expertise — with the corollary, worth enforcing as a personal rule, that the same question is never answered that way twice.
The interface problem sits immediately behind this one
Everything above concerns the person. What the role consists of, once the person has adjusted to it, is a separate question — and the answer is mostly interfaces: between people, between organisational units with incompatible goals and vocabularies, and between the technical components of the work itself. That is the subject of [Related article: The Work Happens Inside Functions. The Value Is Lost Between Them.], which is the second part of this series.
Decision Framework
A leadership team can test its own position with four questions, in order.
1. How many of our delivery leaders are in their first three years in the role? If the answer is most of them, the organisation is running its execution capability on people in transition, and should expect the pattern described above rather than be surprised by it.
2. What did we provide at the point of appointment? Not what was available — what was actually provided, and used. A named mentor outside the reporting line, a defined learning period, an explicit statement of what the person is not expected to know yet, and a reduced technical load. If none of these was provided, the organisation did not fund the transition it asked for.
3. What are we measuring in the first year? Measuring a first-year delivery leader chiefly on delivery outcomes measures the inheritance, not the transition. The more useful early indicators are behavioural: is the person still making technical decisions that belong to the team; are they present in the lateral conversations where resources are settled; are they escalating early or late.
4. Where would this person create more enterprise value? Some specialists are worth more in the discipline than in the role, and saying so openly — with a technical career path that carries comparable standing and reward — is a legitimate strategic answer rather than a failure to develop someone.
From Strategy to Execution
Immediate. Identify every delivery leader appointed in the last twenty-four months and establish which of them received any structured transition support. This takes a week and usually produces an uncomfortable number. For those still inside the first year, put a mentor in place who does not sit in their reporting line and who has made the same transition themselves.
Medium term. Redesign the appointment itself. The change worth making is not another training course but an explicit transition period — six to twelve months — with a reduced technical load, a defined development plan built around the two skill categories the promotion did not test, and a review at the end that assesses the transition rather than the delivery record. Make it a standing part of how the organisation appoints, not an intervention for people who appear to be struggling.
None of this development spending is free, and only part of what it buys stays with the organisation once the individual moves on — a distinction examined in [Related article: What Does the Enterprise Own After a Capability Investment?].
Long term. Build a technical career path with equivalent standing, so that the delivery role stops being the only route to seniority. As long as the sole way to advance is to stop doing the work you are best at, the organisation will keep converting excellent specialists into struggling managers and calling it development.
Signals to Monitor
- Escalation latency. Delivery leaders who are still operating as specialists escalate late, because escalation feels like an admission of technical failure. A rise in the interval between a problem becoming visible to a team and becoming visible to governance is an early indicator.
- Technical decisions arriving at the delivery leader's desk. If specialists are routing design choices upward for approval, the leader has not relinquished the how, and the team has adapted to that.
- Absence from lateral forums. Track attendance at the meetings where resources, sequencing and dependencies are negotiated. Sustained absence indicates a leader who has retreated to the work they can control.
- Regretted attrition among newly promoted specialists. People who leave within two years of promotion frequently leave the role rather than the organisation, and exit conversations should be specific enough to distinguish the two.
- External hiring of delivery leadership. A rising proportion of externally hired delivery leaders is not necessarily a bad decision, but it is evidence that the internal transition is not producing, and should prompt the question rather than settle it.
Questions for the Leadership Team
- Of the people currently accountable for converting our strategy into outcomes, how many were selected for a capability the role does not primarily require?
- What, specifically, did we provide the last person we promoted into delivery leadership — and would we have provided more if we had hired them from outside into the same job?
- Are we able to distinguish, in our performance data, a delivery leader who is failing from one who is transitioning?
- What is the enterprise cost of the specialists we have removed from the work in order to fill these roles, and have we ever estimated it?
- If we told a newly promoted delivery leader that we did not expect them to be competent for nine months, what would break — and what does the answer tell us about how we are running execution?
- Does an ambitious specialist in this organisation have any route to seniority that does not require them to stop being a specialist?
Closing Perspective
The organisations that handle this well are not the ones with the best training. They are the ones that have stopped pretending the move is a promotion.
That single change of framing does most of the work. It makes a learning period defensible, makes asking for help ordinary, makes early struggle diagnostic rather than damning, and makes it possible to say out loud that a particular specialist should stay a specialist. None of it requires new budget; all of it requires an executive team willing to describe accurately what it is asking people to do.
The alternative is what most enterprises currently run: a capability system that takes its scarcest technical judgement, places it in an unfamiliar profession without saying so, and then treats the predictable result as a series of individual disappointments. The individuals are not the variable. The design is.
About the author
Kevin Jogin is Founder & Principal Advisor at EraNorth. Meet the Founder.