Every business owner I've ever worked with was, at some point, very good at doing the work. That's usually how they built the business in the first place. They were the best salesperson, the most capable designer, the engineer who could solve any problem.

This is not a coincidence. Competence is the seed of most businesses. Someone gets good at something — genuinely, demonstrably good — and they reach the natural conclusion that they should do it for themselves. Michael Gerber, in The E-Myth Revisited, named this the "entrepreneurial seizure": the moment a technician decides that their skill in the work is sufficient grounds for owning the business that does that work. The fatal assumption, as Gerber put it, is that understanding the technical work means understanding the business. It does not. And the gap between the two is where most founder stories quietly break down.

Marcus had been a structural engineer for eleven years when he handed in his notice. His colleagues weren't surprised. Clients had been asking for him by name for years. He had a quiet, methodical brilliance — the kind that made other engineers defer to him without feeling diminished. When he set up his own firm, he took three clients with him on day one. Word spread. By the end of year one he was turning work away.

He worked twelve-hour days and didn't mind. The problems were interesting. The solutions were his. The business, he felt, was working.

What Marcus was experiencing is not success misread — it is success, accurately read, in a phase that will not last. The early years of a founder-led business reward exactly what built the business: personal capability, relentless involvement, the willingness to be the answer to every question. The business grows because the founder is good. But growth is the mechanism that eventually turns that strength into a trap. The same behaviours that generate the first million become the ceiling on the second. The business cannot outgrow the hours in a founder's day.

By year three, Marcus had eight employees. He had also stopped sleeping properly. Every project that mattered had his name attached to it — not because he insisted, but because everyone had learned, quietly, that things ran smoother when Marcus was in the room. Junior engineers would send him questions at ten in the evening. Clients rang his mobile rather than the main line. He reviewed every drawing before it left the building.

He told himself this was quality control. It was, in part. But it was also the only way he knew how to feel useful.

♦

The transition from operator to leader is not primarily a skills problem. That is the thing most leadership development misses. The frameworks and tools exist — delegation models, management systems, strategic planning templates. The real difficulty is not procedural. It is psychological. Herminia Ibarra, in her research on leadership transitions at INSEAD, found that what stopped most capable professionals from stepping into leadership was not a lack of capability but a conflict of identity. What they were being asked to do — move away from doing the work — clashed directly with how they understood themselves. Their self-worth was built on competence. And stepping back felt, on some level, like becoming less.

"Many founders derive their self-worth from being busy, being needed, and being the hero. Letting go of that identity feels like a loss. But the true gain is influence." — Connor Robertson

His business coach asked Marcus a question he found surprisingly difficult to answer: What is your job?

He started with the technical description. Lead engineer. Quality sign-off. Client relationships. The coach waited.

"I suppose," Marcus said eventually, "I'm the person who makes sure nothing goes wrong."

"And if nothing could go wrong without you," the coach said, "what does that tell you about the business you've built?"

Marcus didn't answer. But that night, lying awake at 2am with his phone face-up on the bedside table, he turned the question over and over. He had spent three years making himself indispensable. He had not once asked whether that was the same as being good at leadership.

Gerber observed that the typical small business owner is 70% Technician, 20% Manager, and 10% Entrepreneur. The proportions matter less than the direction of travel: most founders are weighted toward execution at the very moment the business needs them to move toward vision. And because execution is what they are rewarded for — by clients, by results, by the daily feedback loop of problems solved — the gravitational pull toward doing never relents. The business trains the founder to stay in the role that is slowing it down.

It was a planning approval that forced the issue. A project had been waiting three weeks for Marcus to review a revised set of drawings. The client was chasing. The junior engineer who'd produced them — careful, competent, two years into the role — had stopped asking when Marcus might get to them. He had learned not to.

When Marcus finally opened the file, he found nothing wrong with the drawings. They were good. He approved them in twenty minutes and sent them across.

Three weeks. For twenty minutes of work he could have done on a Tuesday afternoon. The project hadn't been waiting for his expertise. It had been waiting for his permission.

♦

What distinguishes an operator from a leader is not skill, seniority, or intention. It is the direction of their attention. Operators manage by proximity — they lead by being present, answering questions, jumping in. Leaders manage through direction, systems, and the development of other people's judgment. The work of leadership is to make the organisation less dependent on any single person, including the leader. This is the shift that most founders resist not because they don't understand it intellectually, but because it requires them to give up the thing that made them feel most capable: being the one who does it best.

The change did not come from a book or a course. It came from a conversation with Elena, his most senior engineer, who told him — with the careful diplomacy of someone who had been waiting for the right moment — that she was considering leaving.

Not because of the work. Because she never got to own any of it.

Marcus listened for a long time. Then he asked her what she would do differently on the approval process if he weren't in the room. She told him, precisely and without hesitation, because she had been thinking about it for months.

He had been so focused on staying in the loop that he had never thought to ask what loop she was trying to build.

Ibarra's research offers a useful corrective to the instinct to think our way through a leadership transition. Most founders, when they recognise the trap, respond with introspection: they reflect, they plan, they try to understand their patterns. But introspection anchors people in the past. It amplifies existing self-concepts rather than disrupting them. Ibarra's argument — what she calls the "outsight principle" — is that leaders change not by thinking first but by acting first. New experiences, new behaviours, new interactions: these are what reshape identity from the outside in. The founder who wants to lead differently has to start behaving like a leader before they feel like one. The feeling follows. It does not precede.

Marcus started small. He stopped putting himself on the distribution list for every drawing set. He asked Elena to run the weekly team meeting. He introduced a brief — a single page — that project engineers had to complete before bringing a decision to him, setting out what they'd considered and what they recommended.

At first it felt like performance. Like he was playing a version of a managing director he'd seen in films. He kept wanting to pick up the work again, to show he still could. Twice in the first month he caught himself taking back a task he'd just delegated.

But something was shifting, slowly. The engineers were solving problems he would previously have absorbed. Clients were building relationships with the team, not just with him. He started arriving at the office later, not because he'd given up, but because he no longer needed to arrive first to keep the day from falling apart.

♦

There is a particular kind of fatigue that belongs to founders who haven't made this transition. It is not the tiredness of hard work — most founders are comfortable with that. It is the exhaustion of a system with no redundancy, of a business in which every load-bearing element routes through one person. Without documented processes or empowered colleagues, the founder becomes the default decision-maker for everything from major contracts to minor admin. This kills speed and erodes morale, but it also, gradually, makes the founder resentful — not of the people around them, but of the business itself. The thing they built becomes the thing they're trapped inside.

The firm won a contract larger than anything they had taken on before — a mixed-use development that would occupy the team for eighteen months. In the old days, Marcus would have put himself at the centre of it, the hub through which everything flowed.

Instead, he put Elena in charge. He sat in the first client meeting, then stepped back. He reviewed progress at monthly intervals. He was available, but not present.

The project ran well. There were problems — there always are — and Elena solved most of them before they reached him. The ones that did reach him were genuinely strategic, the kind that needed someone with a view across the whole business, not just across a single set of drawings.

He recognised, for the first time in years, that he was doing his actual job.

The operator trap is not a character flaw. It is a structural inevitability for anyone who builds something from the ground up using their own hands. The qualities that create the business — personal excellence, deep involvement, the refusal to let standards slip — are the very qualities that must be consciously deprioritised if the business is to become something larger than the person who built it. This is a genuine loss, and it is worth naming it as such. Founders give up something real when they stop being the best person in the room for the core work. They are not pretending to leave behind something trivial.

But what they gain is a different kind of capability — and a different kind of influence. The measure of a leader is not what they can do. It is what they can enable others to do. The business that can run, decide, and grow without the founder's constant involvement is not a business the founder has abandoned. It is the business the founder has finally built.

A young engineer joined the firm last spring. Eager, technically sharp, the kind who reminded Marcus of himself at that age. In their first one-to-one, she asked him what his job was.

Marcus smiled, because the question had once floored him.

"My job," he said, "is to make sure the firm doesn't need me to be the best engineer in the room. We already have those. My job is to make sure they have what they need to do the work I used to do — and the work I never had time to see."

She wrote it down. He hadn't expected that.

Later, walking back to his desk past a team that was deep in a problem he didn't need to solve, he thought: this is what it was supposed to feel like all along.