When to Hire a Second-in-Command: COO or Chief of Staff?

There is a moment in every growing company when the CEO becomes the bottleneck they used to complain about. Decisions queue up outside your office. Your calendar is a wall of meetings other people could be running. Strategy lives in your head because there is no one with the altitude and context to hold it with you. You are working sixty hours a week and the company is still waiting on you for things it should not be waiting on you for.

The standard advice at this moment is to "hire a number two." It is also where most founders make a subtle, expensive mistake: they treat COO and Chief of Staff as interchangeable titles for "someone senior to take things off my plate." They are not interchangeable. A COO owns outcomes. A Chief of Staff owns your leverage. Confuse the two and you will either hire a heavyweight operator for a job that is mostly about your own attention — and lose them in a year — or hire a force multiplier and hand them a P&L they never signed up to run.

"You do not hire a second-in-command to do your job. You hire one so the company no longer has to wait for you to do everyone else's."

How to know you are actually ready

Readiness is not a headcount or a revenue number. It is a pattern. In my coaching work I look for four signals, and I want at least three of them persistent for a full quarter before we start a search:

• You are the decision bottleneck. Important calls wait days for your calendar. Not because you are indispensable in principle — because you have never transferred the context that would let someone else decide.
• Execution is outrunning your span. You have functional leaders who are individually strong but uncoordinated, and the coordination layer is you, in meetings, all week.
• Strategy keeps slipping. The important-but-not-urgent work — the next market, the pricing rebuild, the succession bench — keeps losing to the urgent. If this sounds familiar, pair this article with my piece on <a href="https://jasonleerannfeldt.me/insights/the-executive-calendar-how-to-spend-your-time">the executive calendar</a>.
• You are personally degrading. Shorter fuse, slower recovery, decisions made on fumes. The physiology of this is not a character issue; it is a load issue, and I have written about <a href="https://jasonleerannfeldt.me/insights/how-to-recognize-executive-burnout-before-it-costs-you">what executive burnout costs a company</a> when it goes unaddressed.

One signal for a month is a bad quarter. Three signals for a quarter is a structural problem. The distinction matters because hiring a second-in-command to fix a bad quarter is how you end up with an expensive executive and the same structural problem.

The COO: when you need an operator

A great COO owns business outcomes end to end. They run functions, hold P&L responsibility, manage executives, and convert your strategy into an operating plan they are accountable for delivering. The test for whether you need one: is the company's core problem that execution across functions is not getting done to standard, at the pace the strategy requires?

If yes, you need an operator. The COO profile that works depends on what kind of CEO you are. Visionary founders who generate ideas faster than the organization can absorb them need an integrator — someone who says no kindly, sequences the work, and builds the <a href="https://jasonleerannfeldt.me/insights/the-executive-operating-rhythm-that-scales-your-company">operating rhythm</a> that makes the machine run without you in the room. Operationally strong CEOs usually do not need a COO at all; they need a strategist or a strong Chief of Staff, because a COO in that structure becomes a very expensive duplication of the CEO's own instincts.

One warning I give every founder: do not hire a COO to avoid the parts of the CEO job you dislike. If you hate managing executives, a COO will not save you — they will just become the person everyone actually works for while you keep the title. That arrangement survives about eighteen months before it becomes a power struggle. Hire a COO to run the business with you, not instead of you.

The Chief of Staff: when you need leverage

A Chief of Staff is a different instrument entirely. They do not own functions or a P&L. They own your time, your information flow, and the follow-through on your priorities. A great one sits in your meetings, knows what you know, drafts what you would draft, runs the cross-functional projects that have no natural home, and tells you the truth about where your attention is actually going versus where you claim it is going.

The test for this role: is the company's core problem that you personally cannot get to everything that matters? If the executives under you are executing well and the gap is your bandwidth — board prep, strategic initiatives, decision hygiene, communication cadence — a Chief of Staff will return twenty hours a week to you within a quarter. It is the highest-leverage hire a bandwidth-constrained CEO can make, and usually at half the cost of a COO.

The failure mode here is hiring a junior administrator and calling them a Chief of Staff, or hiring a sharp generalist and never giving them real access. The role only works with full information and genuine trust. If you are not ready to let someone see the board deck drafts and the messy truth, you are not ready for the role — and that unreadiness is worth examining, because it usually signals the same control pattern I wrote about in <a href="https://jasonleerannfeldt.me/insights/how-to-delegate-as-an-executive-without-losing-control">how to delegate without losing control</a>.

The decision framework

When founders bring me this question, I run it through five questions in order. Answer honestly and the role usually names itself.

• Where does the company stall? If work stalls between functions — handoffs, priorities, accountability — that is an operator problem: COO. If work stalls on your desk — decisions, prep, follow-through — that is a leverage problem: Chief of Staff.
• What would this person own in month six? If you can name outcomes (gross margin, on-time delivery, a function's results), you are describing a COO. If you can name your own reclaimed hours and closed loops, you are describing a Chief of Staff.
• Can you afford the real version? A credible COO costs what a senior executive costs. If the budget is not there, a strong Chief of Staff is not a consolation prize — it is often the better first hire anyway, and some grow into the COO seat over two or three years.
• Are you ready to share power, or just tasks? A COO needs real authority, including the authority to overrule you in their domain. If that sentence made you uncomfortable, start with a Chief of Staff and do the control work first.
• What happens to this role in three years? A COO is a long-term structural hire. A Chief of Staff is often an 18-to-36-month tour that graduates into an operating role. Design the runway accordingly.

Hiring for the role

Everything I wrote in <a href="https://jasonleerannfeldt.me/insights/how-to-hire-a-senior-executive-without-making-a-million-dollar-mistake">hiring a senior executive without making a million-dollar mistake</a> applies here, with two additions. First, weight trust and judgment above résumé. You are hiring the person who will speak for you when you are not in the room; their judgment under ambiguity is the product. Probe it with real scenarios, not behavioral trivia: "Here is a decision I made last quarter. Walk me through how you would have pressure-tested it."

Second, run a working session before you offer. Give a finalist a real, current cross-functional problem and ninety minutes with your leadership team. You will learn more about the working relationship in that session than in six interviews. For a COO especially, watch how your existing executives respond to them — a COO your team will not follow is a reorganization waiting to happen, no matter how strong the résumé.

The first 180 days: making the partnership work

Most second-in-command failures are onboarding failures. The CEO hires well, then never transfers context, never declares the person's authority publicly, and wonders why nothing changed. The fix is deliberate design of the first two quarters:

• Days 1–30: context transfer. They shadow everything — board prep, one-on-ones, the hard conversations. You narrate your reasoning out loud, constantly. It feels inefficient. It is the entire job of month one. The mechanics mirror what I laid out in <a href="https://jasonleerannfeldt.me/insights/first-90-days-as-a-new-executive">the first 90 days as a new executive</a>, but the burden is on you, not them.
• Days 31–90: declared authority. You announce, in writing, what they own and what decisions are theirs without you. Then you honor it — especially when they decide something you would have decided differently.
• Days 91–180: full handoff of a real domain. A function, a strategic initiative, an operating cadence — something with outcomes you both measure. If by day 180 they still need you in every consequential meeting, either the hire was wrong or the authority was never real. Diagnose honestly.

One cadence that protects the relationship: a weekly one-on-one between the two of you that is never cancelled, run with the same discipline I described in <a href="https://jasonleerannfeldt.me/insights/how-to-run-executive-one-on-ones-that-are-worth-the-time">executive one-on-ones that are worth the time</a>. The number two relationship decays silently — misaligned assumptions, small resentments, drifted boundaries — and a protected weekly hour is where you catch the drift while it is still cheap to fix.

The mistake to avoid

The most common failure is not hiring too early or choosing the wrong title. It is hiring a second-in-command and then refusing to be led by them in their domain. Founders bring in a strong operator, feel the company start to run without their fingerprints on everything, and — without quite admitting it — begin re-litigating decisions, re-opening settled questions, and rebuilding their own indispensability. The strong hire leaves within two years, and the founder concludes that "no one can really be a number two here."

If you recognize that impulse in yourself, treat it as the real work. A second-in-command is not a way to avoid changing how you lead — it is the structure that forces you to. Done well, it is the single hire that turns a founder-dependent company into an institution. Done defensively, it is the most expensive way to stay exactly where you are.

If you are weighing this decision and want a thinking partner who has sat on both sides of it, that is the work I do with founders and CEOs. And if the bandwidth problem you are solving has a physical dimension — sleep, energy, the capacity to actually lead at the altitude this role demands — do not ignore it. The best operating hire in the world cannot compensate for a CEO running on an empty tank. Start there, and start honestly.