At some point, every founder decides they need a number two.
The reasoning is sound. The business has grown past what one person can hold. There are too many decisions, too many people, too many fires. So the founder hires or promotes someone capable, gives them a title like General Manager or Head of Operations or Chief of Staff, and tells them, with real sincerity, “I want you to run things so I can focus on growth.”
Eighteen months later, the same founder is sitting across from me saying some version of this: “He’s good. He works hard. But everything still comes to me.”
I have heard this enough times that I no longer think it is a hiring problem. The person is rarely the issue. What has gone wrong is much more specific, and it happens so gradually that neither of them notices.
How a Decision-Maker Becomes a Messenger
Here is what it looks like from the inside.
In the first month, the new number two makes a decision. Maybe it is a small thing, like approving an extra day of leave, or a moderate thing, like renegotiating a vendor’s delivery schedule. They do it because that is the job they were given.
Then the founder finds out. Not in a formal review, just in passing. And the founder, who has run this business alone for years, has a reaction. Sometimes it is a correction: “I wouldn’t have done it that way.” Sometimes it is a question: “Did you check with me?” Sometimes it is just a pause, a slight change in tone, and nothing said at all.
The number two is intelligent. They read the signal accurately. The signal says that decisions are safer when the founder has seen them first.
So the next time, they check. And the founder, relieved to be consulted, answers quickly and moves on. Nobody registers that anything has changed. But something has. A decision that was meant to be delegated has just become a decision that is discussed, and the discussion has a clear owner, and it is not the number two.
Repeat that fifty times over a year and you have a person with a senior title whose real job is to collect questions from the team, carry them to the founder, and carry the answers back. They are not running things. They are routing things. The team figures this out long before the founder does, and begins going directly to the founder because it is faster.
At that point the founder looks at the situation and concludes that the number two has not “stepped up.” The number two, meanwhile, has learned that stepping up is exactly what got them corrected in month one.
The Mistake Is in the Role, Not the Person
When I sit down with a founder in this situation, I ask a simple question: “What decisions can this person make that you will never revisit?”
The answer is almost always silence, followed by something like, “Well, anything reasonable.”
That is not an answer. That is the absence of one. “Anything reasonable” means that every decision is subject to a test that only the founder can apply, after the fact. Which means every decision is effectively provisional. Which means the safest course for the number two is to pre-clear everything, which is exactly what they are doing.
The founder has given away a title without giving away a single decision. And you cannot lead with a title. You can only lead with decisions that are actually yours.
A Story From a Logistics Company
I worked with a mid-sized logistics operator in western India where the founder had promoted his most trusted operations manager to General Manager. On paper, the GM ran the entire business. In practice, the founder still approved every hire, every rate card change, every customer credit extension and every vehicle purchase.
When I asked the founder why, he said, “He’s not ready to decide those things alone.”
When I asked the GM the same question, he said, “He’s never told me I can.”
Both were telling the truth. The founder was waiting for the GM to demonstrate readiness by taking ownership. The GM was waiting for the founder to demonstrate trust by granting it. Each was waiting for the other to move first, and the business had been standing still in that doorway for two years.
What Changed in Ninety Days
We did not send anyone on a leadership programme. We wrote a list.
The founder and the GM sat down and went through every category of decision in the business. For each one, they agreed on one of three answers: the GM decides and does not need to inform anyone; the GM decides and informs the founder afterwards; or the founder decides. Nothing was allowed to sit in between.
The first pass was revealing. The founder wanted to keep about seventy per cent of decisions for himself. When I asked him to justify each one, most of the reasons came down to habit. He had always done it, so he assumed he should continue. Where there was a real commercial reason, we kept it with him. Where there was not, it moved.
By the end, the GM owned hiring below a certain level, all operational scheduling, vendor negotiations within a spending band, and customer credit up to a defined limit. The founder kept large capital spend, any new customer above a certain revenue size, and anything involving a legal or regulatory exposure.
Then came the harder part. The founder had to agree that decisions in the GM’s column would not be second-guessed. Not corrected in passing. Not questioned in front of the team. If a decision turned out badly, it would be reviewed at the monthly meeting as a learning, not relitigated the same afternoon.
The founder found this difficult. He told me honestly that the first month felt like watching someone else drive his car. But he held to it.
Within ninety days, the GM’s decision volume had gone up roughly four times. The founder’s inbox had emptied of operational queries. The team had stopped going around the GM, because going around him no longer worked. And the founder had, for the first time, three uninterrupted days a week for the growth work he had been promising himself for years.
Why This Is Harder Than It Sounds
I want to be honest about why founders resist this, because the resistance is not irrational.
A founder’s judgement is often the single most valuable asset the company has. It has been refined over years of mistakes and near-misses. Handing decisions to someone else feels like handing over the thing that made the business work. And there is a real risk. The number two will get some decisions wrong that the founder would have got right.
But the alternative is not that the founder gets those decisions right forever. The alternative is that the founder stays trapped as the single point through which everything must pass, the business grows only as fast as one person’s attention allows, and the capable person hired to change that slowly becomes a very expensive messenger.
The question is not whether the number two will make mistakes. It is whether the business is willing to pay for their learning, in exchange for the founder’s time.
A Simple Exercise to Start Right Now
If you have a second-in-command and you feel that everything still comes to you, do this before your next one-to-one.
Take a sheet of paper and list the last ten decisions that reached you from the team. For each one, write down whether your number two should have been able to make it alone. If the answer is yes, ask yourself honestly why they did not.
If your answer is “because they lack confidence,” look harder. In my experience the real answer is that you have never told them, in writing, that the decision is theirs and that you will not take it back.
Then tell them. Specifically. In writing. And keep your word when the first one goes wrong.
If you want to understand how this kind of work gets done inside a company, reach out. You can connect with me on LinkedIn, or send a query through this website. I am happy to talk through what this could look like for your business specifically.