The moment you stop being an operator and become a leader.

There is no ceremony. No document to sign. Nobody who tells you "now you are a leader". There is only a moment — often silent, often uncomfortable — when you understand that your value no longer lies in what you know how to do, but in what you manage to get others to do.

That transition is the most difficult a professional can go through. Not because it requires new skills — though it does. But because it requires stopping using the skills that got you where you are. And stopping doing well something you are good at, to instead do something you do not yet master, is counterintuitive at almost a physical level.

I delayed that transition for years. I kept doing things myself, being the technical reference point, feeling useful through execution. And in the meantime, the team did not grow. It could not grow — because I was still at the centre of the operational system instead of being outside it, building the system itself.

Why the transition is so difficult

Almost every leader I know arrived at leadership through operational excellence. They were good at something — very good. And that skill was recognised, valued, promoted. The problem is that recognition of operational excellence reinforces a deep identity: "my value lies in what I know how to do."

When someone on the team needs help, the natural impulse is to do it for them. Every time you give in to that impulse, you are choosing your comfort at the expense of the team's growth. Not from malice — from identity habit.

The real transition is not acquiring new leadership skills. It is changing the answer to the question "what does my value consist of?". From "in what I do" to "in what I build". From "in my execution" to "in others' ability to execute".

The signals you are still in operational mode

You solve problems instead of teaching how to solve them. The leader's response: "what have you already tried?", "how do you think it could be approached?", "what would you need to solve it yourself?"

You are the first to respond even when you should not be. Every time you answer a question someone else could have answered, you remove a growth opportunity from someone else and consolidate your own centrality in the system.

Your work quality concerns you more than the team's. The operator measures their own excellence. The leader measures the system's excellence.

You feel more comfortable with the concrete than the abstract. Building a process gives immediate visible results. Training someone, building culture — these are long, uncertain processes. The operator prefers the concrete. The leader learns to stay with the abstract.

The competence paradox

The more competent you are at something, the harder it is to stop doing it. Not just for identity reasons. But because seeing someone else do that thing less excellently than you would is genuinely uncomfortable.

The operator cannot make this calculation: the short-term cost of lower quality is worth the long-term benefit of scalability. But that person executing at 70% of your standard today, if supported correctly, will execute at 85% in three months. And in the meantime you were able to build something you could never have built if you were executing yourself.

Accepting the temporary 70% to gain the future multiplier is not lowering standards. It is choosing which type of excellence matters most.

How the transition happens — concretely

Three small daily choices: when someone brings you a problem, ask one question instead of giving the solution — "what have you already thought about this?". Identify one thing you do every week that someone else could do with the right instructions — shadow them on the first execution, then let go. Stop measuring your day in things done and start measuring it in capabilities created in the team.

None of these choices is dramatic. Each is tiny. But accumulated over time, they build something no single operational action could ever have built: a team that grows without you.