They Promoted the Expert. Nobody Trained the Manager.

On Friday, you were the person everyone came to for the answer. On Monday, you have a team.

You still understand the code, the architecture, the model, the client and the technical risks. That part feels familiar. What is new is that one person wants a promotion, another seems to be running out of energy, someone else is missing expectations, and a fourth wants to know what to do about a conflict with a colleague.

At some point it becomes obvious: the management role did not ship with documentation.

The promotion often rewards the skill the new job needs less of

This is a common trap in expert environments. You are technically strong. You solve hard problems. You take ownership. People trust your judgement. The organisation sees leadership potential and gives you more responsibility.

But management is not “senior specialist plus meetings”.

The unit of value changes. As an expert, you often create value by being able to find the answer yourself. As a leader, you increasingly create value by building conditions in which other people can think, decide, take responsibility and grow without waiting for you.

That is a very different muscle.

Under pressure, we return to what made us successful

The developer starts correcting everyone’s code. The analyst checks every measure. The architect takes over the design. The BI expert opens every model because “it will be quicker if I just fix it”.

In the short term, it works. In the long term, it creates a manager-shaped bottleneck.

The team learns that difficult decisions eventually come back to you. You learn that everything moves too slowly without you. Together, you accidentally design a system in which you never have enough time to lead.

Micromanagement does not always begin with a desire for control. Often it begins with competence, good intentions and a deadline.

“I’ll do it quickly.” “Send it to me, I’ll finish it.” “I’ll join the meeting because I know the context.”

Any one of those choices may be reasonable. The problem is when they become the operating model.

You need a new definition of a good day’s work

Expert work has visible outputs. The pipeline is fixed. The analysis is delivered. The architecture is agreed. The client accepts the solution.

A manager’s most important work is often harder to point at.

A question that helped someone think. A conflict you did not solve for the team, but helped them address. A decision you deliberately did not make. A one-to-one in which someone finally said what had been sitting under the surface for weeks.

There may be no green checkbox next to any of it. It may still be the highest-value work you did that day.

Delegation is not task distribution

If you hand over the task but keep every decision, you have not delegated ownership. You have delegated execution.

Real delegation needs clarity about the outcome, the non-negotiable boundaries, the decisions the other person can make independently, when they should come back to you and what they actually need from you — context, resources, feedback or trust.

Then comes the uncomfortable question: are you prepared for someone to do it differently from you?

If the only acceptable route is your route, you have not transferred responsibility. You have outsourced the typing.

Conversation becomes part of the infrastructure

For many first-time managers, this is the surprising part. One-to-ones are not time away from “real work”. Feedback is not a soft extra. Clarifying expectations is not something you do only after things have gone wrong.

This is the infrastructure of the work.

When two technical systems integrate, you expect some form of contract. When two people collaborate, clarity matters just as much: what belongs to whom, what “good” looks like, how decisions are made, when to escalate and how to raise a problem without waiting for it to become a crisis.

When that infrastructure is missing, we often call the consequences a people problem.

You do not need a fully formed leadership style on day one

A new title can trigger an identity project. Should I be more decisive? More empathetic? More strategic? More coaching-oriented? More assertive?

It is easy to start performing a version of leadership borrowed from the best manager you ever had — or to become the exact opposite of the worst.

A more useful question is: what does this team need from me in this situation, and which part of that can I deliver authentically?

Leadership does not have to become your personality. It is a series of choices made in context.

What are you still doing because you are good at it, even though you should no longer own it? Where is the team waiting for a decision it could make without you? What happens inside you when someone works more slowly or differently? Are you able to have the difficult conversation while the problem is still small?

And perhaps the biggest one: what is your job now, if your job is no longer to be the best expert in the room?

Leadership coaching can create space to work through that transition without giving you another generic management playbook. A promotion changes the title immediately. The way you think about value usually takes a little longer.