A small business promotes its best technician to lead the team. They are skilled, reliable and respected by everyone. Twelve months later they are exhausted, the team is behind, and their manager’s feedback includes phrases like “needs to delegate more” and “should focus on the bigger picture”. The technician is quietly wondering why they took the job.
Nobody in that story behaved unreasonably. The business promoted its most capable person. The person accepted a job they were told they had earned. The feedback described what was happening. Yet the outcome was close to predictable on the day of the appointment, because the promotion was not really a promotion. It was a change of profession, presented as a step up the same ladder and supported as neither.
This article explains why moving from specialist to leader is a different job rather than a bigger version of the old one, the predictable ways the transition goes wrong, how to support it, and why for some people a technical career path is the better answer for them and the business. It is general information for owners and managers making or managing these promotions.
A different job, not a bigger one
A useful old distinction separates three kinds of skill:
- Technical: knowing how to do a specific kind of work, its methods and its tools.
- Human: working effectively with and through other people, and building cooperation in a group.
- Conceptual: seeing how the parts of the business depend on each other, and how a change in one affects the rest.
A specialist is promoted for technical skill. A team leader’s job draws mainly on human and conceptual skill. Technical credibility still matters, because a leader needs to understand the work well enough to recognise risk and ask good questions. But it is no longer the main thing they are paid for. As responsibility grows further, the balance shifts again: judgement, integrity under pressure and the ability to adapt when experience no longer applies become the deciding capabilities.
Three demands sit at the centre of the change, and each runs against the grain of a technical career:
- Letting go of the how. A specialist is valued for knowing how to do things. A leader sets what and when, and leaves the how to the people doing the work, partly because a group generates options an individual will not. This is a real loss for someone whose identity rests on expertise, and it helps to name it as one.
- Working sideways, not just downwards. Specialists often work with focus and autonomy on a defined task. A leader’s day is a stream of interruptions and negotiations with peers, customers and suppliers who control things the team needs. Nothing in a technical career prepares people for this.
- No longer being the expert in the room. The leader will regularly face questions they cannot answer. Saying “I don’t know, and I will find out”, and then finding out, preserves trust far better than bluffing.
How the transition predictably goes wrong
The failure patterns are consistent enough that they should be treated as signs of an unsupported transition, not of the wrong person:
- Doing the work instead of leading it. The new leader takes the hardest jobs themselves, because that is where they feel competent and useful. Meanwhile, planning, coordination and people issues wait.
- Over-delegating within their own field. Trusting other specialists completely, they step back so far that they stop checking or directing.
- Reducing leadership to instructions when leading people outside their field, getting compliance and losing engagement.
- Retreating to “real work”. They disappear into technical tasks and miss the conversations where priorities and resources are decided.
- Treating risk, planning and communication as admin to be done after the “proper” work.
- Micro-managing, because the technical detail is the only ground where they still feel sure of themselves.
Each is a retreat to familiar ground. Training alone rarely prevents it, because the underlying problem is that the person has been given no permission to be a beginner. Someone who has been the expert for years, and is suddenly a novice without anyone acknowledging it, will move back to where they are still expert.
Support the transition like a change of career
When someone changes careers, people expect a learning period, an induction, a mentor and patience while competence develops. When someone is promoted, they get an announcement and an assumption of immediate capability. Treat a specialist’s move into leadership as the first kind of change:
- A defined transition period, often six to twelve months, with an explicit statement of what the person is not yet expected to know.
- A reduced technical load, stepped down over the period, so leadership work is not squeezed into the gaps.
- A mentor outside their reporting line, ideally someone who has made the same move. In a small business this may be an owner from another business, an adviser or an industry peer.
- A development plan built around human and conceptual skills, the parts the promotion did not test.
- Regular conversations about the job, not just the work: what is getting easier, what still feels uncomfortable, where they are tempted to retreat.
Match the first leadership role to the person
Not all leadership roles are equally hard, and size is a poor guide to difficulty. A large, routine job with a settled team and a familiar customer may be easier to lead than a small one with new technology, several outside parties, a demanding customer and decisions that are hard to reverse. When judging how stretching a first leadership role will be, look at:
- How new the work is, technically and for the business.
- How many handoffs it involves with other people, teams and suppliers.
- How much disagreement there is among customers or stakeholders.
- How reversible the important decisions are.
A good first role stretches the person on human and conceptual skills while keeping the technical and commercial risk manageable. Harder roles can follow as confidence and evidence grow.
Measure the transition, not the inheritance
In the first year, judging a new leader mainly on the team’s results mostly measures what they inherited. Earlier and more useful indicators are behavioural:
- Are they still making technical decisions that belong to the team?
- Are they present in the planning and priority conversations?
- Do they raise problems early or late?
- Are team members developing, or waiting for the leader to solve things?
These tell you whether the transition is working before the results show it. The developing people through real assignments article covers designing stretch work with support.
Some specialists should not make the move
Some of a business’s best specialists will create more value by staying in the work. That is not a failure of ambition or a lack of potential. Removing an exceptional technician from technical work to become an average team leader can cost the business twice: once in lost expertise and again in weaker leadership.
The trouble is that in many businesses, management is the only route to higher pay, status and influence. As long as that is true, good specialists will either take leadership roles that do not suit them or leave. A technical career path with genuine standing solves this: a senior or principal technical role with comparable recognition, pay and influence over technical decisions, without people management. In a small business this does not need a formal framework. It needs the owner to say clearly that deep expertise is valued as highly as leading people, and to back that with pay and decision rights.
Progression also does not have to mean moving up. People can grow through broader responsibility, cross-functional work, mentoring others, leading improvement projects or taking on a new customer area. A business with few senior roles can still offer development, and that matters for keeping capable people, since careers now often move between organisations.
Choose deliberately
Before promoting a specialist, ask:
| Question | What to look for |
|---|---|
| Do they want to lead people, or do they want recognition? | If it is recognition, consider a technical path |
| Have they shown human skill in real situations? | Helping colleagues, handling difficult customers, resolving disagreements |
| Can they see the bigger picture? | How their work affects other parts of the business |
| Where would they create more value? | In the role, or in the work |
| What support can we provide? | Time, a mentor, a reduced load, a learning period |
The career anchors article covers how people’s underlying motivations shape which roles suit them.
A worked example
This is an illustration. A 12-person IT support business promotes its most experienced technician to lead a team of five technicians. Within six months, problems appear. The new team leader takes the most complex tickets personally, rewrites colleagues’ fixes, misses the owner’s weekly planning meetings because of “urgent” technical work, and raises client escalations only when they are already serious. The owner’s first instinct is to question the appointment.
Instead, the owner treats it as an unsupported transition and resets it:
- The transition is named. The owner tells the team leader directly that the role is a different job, and lists what they are not yet expected to be good at: planning capacity, difficult performance conversations and client account reviews.
- The technical load is reduced. Personal ticket work is capped at about 30% of the week for three months, then 15%.
- A mentor is arranged. A service manager from another business, met through a local business network, agrees to meet monthly. They are outside the reporting line and made the same move a few years earlier.
- Behavioural measures replace ticket counts. The owner and team leader review four questions each fortnight: which technical decisions were left to the team, whether planning meetings were attended, how early escalations were raised, and which team member learned something new.
- An alternative is offered. The owner also describes a senior technical role, with similar pay and responsibility for technical standards and complex projects, and says either choice is respected.
After three months, the team leader chooses to stay in the leadership role. Escalations reach the owner earlier, and two technicians start handling complex tickets that previously went to the team leader. A year later, the business creates the senior technical role anyway and fills it with another strong technician who did not want to manage people.
How this applies to a small Australian business
- Treat specialist-to-leader moves as career changes, with a learning period.
- Name what the person is not yet expected to know.
- Reduce their technical load deliberately and in stages.
- Arrange a mentor outside their reporting line.
- Measure behaviour in the first year, not just results.
- Offer a technical path with real standing, pay and decision rights.
- Ask what the person wants, not just what they are good at.
- Broaden what progression means beyond moving up.
Signals worth watching
- New leaders taking the hardest technical work themselves.
- Planning and people issues waiting while technical work gets done.
- Late escalations from a new leader.
- Team members bypassing the leader to get technical answers elsewhere.
- Strong specialists leaving because management is the only way up.
- Leadership promotions treated as rewards for technical performance.
Common mistakes
- Assuming technical excellence prepares people for leadership.
- Reading early struggle as the wrong appointment.
- Relying on a course instead of supporting the transition.
- Keeping the full technical load alongside new responsibilities.
- Offering no route to recognition except management.
- Judging first-year leaders only on inherited results.
Frequently asked questions
Should leaders still do technical work? Some, especially in small teams, and it helps credibility. The risk is when technical work crowds out leading. Agree a limit and review it.
How long does the transition take? Often six to twelve months before someone is comfortable, and longer to be skilled. Plan for it.
What if the person wants to go back? Make that possible without stigma. A move back to a senior technical role can be a good outcome for everyone.
Can we hire leaders externally instead? Sometimes. External hires bring leadership experience but lack knowledge of the business and the team’s trust. Either way, the first months need support.
Is a technical career path realistic in a small business? Yes, at small scale. It can be one senior role with clear responsibility for technical standards and pay that reflects its value.
Questions to ask
- Why are we promoting this person: for leadership, or as a reward?
- What will they need to stop doing, and how will we help?
- What are they not yet expected to know?
- Who will mentor them, outside their reporting line?
- How will we know in three months whether the transition is working?
- What route do our best specialists have to recognition without managing people?
Bringing it together
Moving from specialist to leader is a change of profession, not a bigger version of the same job. It needs human and conceptual skill more than technical mastery, and the predictable struggles are signs of an unsupported transition rather than a wrong choice. Give new leaders a learning period, a lighter technical load, a mentor and permission to be a beginner, and judge them on behaviour before results. Offer a technical path with real standing, so that the only way to be valued is not to stop doing the work you are best at.
Source: KEVOS notes, drawing on teaching material on technical, human and conceptual skills (after R. L. Katz), the transition from technical expert to project manager, project manager career models (K. Bredin and J. Söderlund, 2013), boundaryless careers and leadership capability. Examples and figures in this article are illustrations. This article is general information.
