Suppose you’ve hired a second-in-command, introduced them to the team, and asked your managers to work through them. Then a familiar question arrives in your inbox: can we move this deadline?
You answer because it’ll only take a minute. Later, the COO discovers that the decision affects two other projects. Managers now have different instructions, and you are back in the operational discussion you meant to leave.
The COO title hasn’t settled who gets the final say. For a second-in-command to take operational responsibility off the founder’s desk, the business has to understand which decisions have moved and which still belong with the CEO.
Begin with decisions that recur
Before writing a lengthy delegation document, review the questions that reached you over the last few weeks. Look for repeated decisions about staffing, delivery dates, customer exceptions, suppliers, or competing project priorities.
For each category, agree who prepares the recommendation, who needs to contribute, who makes the decision, and who carries it out. Include any approvals that genuinely cannot be delegated.
Bain’s RAPID framework separates these responsibilities into Recommend, Agree, Perform, Input, and Decide. Bain also advises applying that level of formality where the decision is important or frequent, rather than building an elaborate process around every minor choice. 10
A founder-led business can start with a small number of troublesome decisions. Start with the decisions that keep bouncing back to you.
Take a request to add a contractor. The department leader identifies the need and recommends a candidate. Finance checks the budget. The COO approves within an agreed limit, while commitments beyond that limit go to the CEO.
Your limits may be different. Set them according to the company’s financial position, the operator’s experience, and any approvals you need to retain. Write down the arrangement you actually intend to follow.
Give the team one operating answer
The founder’s behavior matters after you’ve agreed on authority. If a manager asks you to revisit an ordinary decision within the COO’s remit, direct the discussion back to the COO. You can remain approachable without creating an alternative approval route.
You should still be able to raise serious concerns independently, including misconduct or decisions outside the agreed boundaries. Respecting the COO’s authority doesn’t mean ignoring a serious risk.
For routine disagreements, however, avoid settling the matter privately and leaving the COO to discover it later. Ask what information was considered and whether anything new changes the decision. When the decision does need to change, communicate the change together.
The same discipline applies to new ideas. Tell the COO whether you are exploring a possibility or directing a change in priority. Those are different conversations. An interesting suggestion should not become an urgent assignment simply because it came from the founder.
Make disagreement part of the relationship
A CEO’s second-in-command needs room to challenge assumptions. That might mean questioning a launch date, pointing out the staffing implications of a new offer, or saying that the team can’t absorb another project this quarter.
Set aside regular time to discuss those matters without the whole leadership team present. Bring the operating facts and the commercial objective into the same conversation. The founder may know why an opportunity matters; the COO may see a delivery consequence the founder has not considered.
EOS Worldwide’s description of the Visionary and Integrator gives these roles complementary responsibilities: the Visionary develops direction and important external relationships, while the Integrator brings the business functions together and manages execution. It is a partnership, not a requirement for one person to agree with the other automatically. 9
Once a decision is made, the team should hear a consistent position. Reopening it repeatedly without new evidence makes it harder for managers to commit their own people and plans.
You’ll still need visibility, of course. Agree on the information that helps you lead: progress against priorities, significant performance changes, decisions needing your input, and risks that exceed the COO’s authority. Agree on when you will review it.
You don’t need to attend every working meeting to stay informed. Where confidence is still developing, review a sample of decisions together and adjust the boundaries as you learn.
The COO Solution positions its fractional COOs as embedded second-in-command leaders for founder-led businesses. That arrangement needs a real transfer of responsibility, with the founder and operator following the same rules when a difficult decision comes along. 11
Start small enough to make the transfer real. Choose a recurring decision you will stop owning, agree the limits, and tell the people affected. Then follow the arrangement the next time that question lands in your inbox.
