I hear some version of this from founders more often than I'd like. What follows is a composite, built from several of those conversations rather than any one client, so if you think you recognize yourself, you're probably recognizing the pattern.
A founder hires a COO to take operations off his plate. Maybe it's someone he's known for years, maybe even a close friend. A year later, he's frustrated. Things still land on his desk. Decisions he expected the COO to make keep coming back to him. He's starting to wonder whether he hired the wrong person.
When a founder tells me that, the first thing I want to do is slow it down. I'll ask to see what the COO was actually given. The goals. The milestones. What a good quarter was supposed to look like. Which decisions are theirs to make. Sometimes there isn't much on paper. Sometimes there isn't anything.
That doesn't tell us the COO is the right person. It tells us we don't yet have a fair basis for judging. The COO may be very capable. They may be missing skills the role needs. The role may be badly designed. The founder may be undercutting them without realizing it. Or several of those may be true at once. I'm not interested in swapping "the COO is the problem" for "the founder is the problem." I want to know what's actually going on before anyone decides anything about someone's job.
Delegation, abdication, and micromanagement
There are three different things a founder can do when they hand over a role, and most of us move between them without noticing.
Delegation is assigning ownership of clearly defined outcomes, transferring the authority needed to deliver them, providing the support required, and agreeing on how progress will be reviewed. Abdication is handing off responsibility without enough clarity, support, authority or follow-through. Micromanagement is keeping control over how the work gets done, even after you've said the outcome is someone else's.
Here's the swing I see. A founder hires a COO and disappears. That's abdication. Results disappoint, and the founder swings the other way and starts requiring approval for everything. That's micromanagement. Neither one lets the COO become an actual executive.
I know the first half of that swing well. At Diversified Industrial Staffing, a huge part of how I screwed up the company was that I would hire people with experience, essentially say, "Okay, you got it," and go sit in the background. I was paying them a lot of money. I figured that meant they'd know what to do. Andy Grove, who ran Intel, made the point in *High Output Management* that delegating without following through amounts to abdicating. I lived a version of that for years before I had words for it.
Responsibility without authority
This is the piece I think gets missed. A COO can have crystal-clear goals and still not be able to hit them, because the founder handed over the responsibility and kept the authority.
The COO is accountable for operations but still needs the founder's sign-off to hire, to change a process, to restructure a department or to spend a reasonable amount of money. On paper they own the outcome. In practice the founder still owns the decisions that produce it. That isn't delegation. You can't reasonably hold someone accountable for results while keeping control over the decisions they'd need to make to get them.
One question I'll ask a founder: "What decisions can your COO make without asking you, and what happens when they make a decision you wouldn't have made?" The answer usually tells us a lot about whether the founder is ready to let someone else lead.
Do you actually know what you want?
Founders often believe they know exactly what they want from a COO. Sometimes that's true. Sometimes the standard lives only in the founder's head, and it shifts as circumstances shift. An executive can hit the original target and still disappoint, because the target moved and nobody told them. I've watched how demoralizing that is for good people. They're being measured against something they can't see.
So I'll ask, "Are your expectations clear enough that someone else could describe success the same way you do?" And a follow-up that's often harder: "If they get the result you agreed on, are you willing to let them get there differently than you would have?" A lot of the friction lives in the gap between the outcome a founder wants and the method the founder prefers.
The founder has a role to redefine too
We spend a lot of time talking about what the COO needs to own. We spend far less on what the founder needs to stop owning. A founder can say the COO runs operations and still step into staffing, customer issues, scheduling and department priorities whenever something feels off. When that happens, the COO becomes the founder's assistant instead of an executive with real authority.
Both roles need to be defined. What the COO owns. What the founder is no longer going to own. And when the COO decides on their own, when they consult, and when something has to come back up.
When the COO is also a friend, there's another layer. Two relationships have to live side by side, and that's hard. Sometimes the founder avoids difficult feedback to protect the friendship. Sometimes the friend assumes the trust buys extra room. Sometimes the rest of the team starts wondering whether the same rules apply to everyone. None of that is a given. It's worth asking yourself, though: "What conversation am I avoiding because this person is my friend, and what is avoiding it costing the business, my friend and our relationship?"
Responsibility isn't the same as blame
I want to be careful here. Founders are responsible for how they lead and for the conditions their people work in. That doesn't mean they personally caused every problem. An executive may genuinely lack the capability or the commitment. The market may shift. A customer may blow up a quarter. The founder didn't cause those things. They're still responsible for how they respond. Looking at your own contribution doesn't require you to take the blame for everything.
What it takes to hand over a senior role
If you're putting a COO or any senior leader in place, here's what I'd want clear before judging their performance.
**Outcomes.** What specific results does this person own, and how will success be measured?
**Authority.** Which decisions can they make on their own, and which need consultation or escalation?
**Resources.** Do they have the people, information, budget and support to deliver?
**Cadence.** How and when will you review progress, obstacles and decisions together?
**Development and consequences.** When results fall short, what support or correction comes first, before anyone makes a final call about the person?
And remember that a COO should be held to outcomes and judgment, not managed through a list of daily tasks. The goal isn't more meetings or more oversight for its own sake. It's clear ownership and the right level of accountability.
Why this matters to the business
When the role isn't clear and the authority hasn't moved, decisions keep drifting back to the founder. The founder looks at the pile and concludes they can't trust anyone with anything, which is the exact problem they hired the COO to solve. Meanwhile a quarter or two goes by with the wrong things getting attention, a capable executive may walk out the door, and the founder starts the search over with the same unclear role waiting for the next person.
Here's a question I think gets underneath all of this: Did you hire a COO because you were ready to let someone else lead, or because you were exhausted from leading everything yourself? Those aren't always the same thing. You can badly want relief from day-to-day operations and still be uncomfortable with someone else exercising real authority.
So think about the senior person on your team who frustrates you most right now. Could you hand me their goals, their deadlines and the date of your last honest conversation about their performance? Could you tell me which decisions they own without needing your approval?
If you can't, what do you need to clarify about your own leadership before deciding whether they're the wrong person for the role?
If that's a conversation worth having before you make a call, have it with someone who can see it from the outside. A mentor, a Forum mate, or me. Let's talk.
Let's get after it. Todd
P.S. If you've got a senior role in your company that's never been properly defined, hit reply and tell me which one. I'll help you think through what it should own, and what you'd have to let go of.
