How to Go From Chief of Staff to COO: Moving From Borrowed Authority to Your Own
A Chief of Staff makes sure the right decisions get made. A COO makes them, and answers for them. The move between the two seats is about building real ownership before anyone changes your title. Here's how, and what founders can do to set their Chief of Staff up for it.
A couple of weeks ago I wrote about moving from Executive Assistant to Chief of Staff. The question that came back most often was the obvious next one: what about Chief of Staff to COO?
I've made that move, so here's the view from the inside.
The short version: the work changes less than you'd expect. The authority changes completely. As a Chief of Staff, your authority is borrowed from the CEO. As a COO, it's yours. The move is learning to hold your own.
Why the Chief of Staff seat is a great place to start
A good Chief of Staff already has most of what a COO needs, and it's worth naming, because it's real.
You see the whole company. You sit in the leadership meetings, you know where decisions get stuck, and you know which functions are running well and which ones are held together by one person's effort.
You know how the CEO thinks. You know what they need to see before they commit, and which calls they'd rather someone else made.
And you have relationships across every team, because your job has been to make things move between them.
What the seat doesn't give you on its own is ownership. A Chief of Staff makes sure the decision gets made. A COO makes it, owns the result, and answers for it when it's wrong. Everything below is about building that.
Four moves to make before you ask for the title
1. Own one thing end to end.
Not a project. A function, or a number. Something that stays yours after the launch is over.
Projects end. Ownership doesn't. Ask for one area where you're accountable for the result month after month: a function that has no clear owner, a process that keeps breaking, a metric nobody watches. Then run it like it's yours, because it is.
2. Bring a decision, not options.
A Chief of Staff's instinct is to frame the choices clearly and hand them to the CEO. It's a good instinct. It's also the habit a COO has to grow past.
Start bringing your recommendation, and then the decision itself, for the things in your area. "Here's what I'm doing and why" instead of "here are three options." Then live with the result, including the ones that don't work out. Owning the outcome is the job.
3. Learn the money.
COOs are judged on what things cost and what they return. If budgets, margins, contracts, and vendor spend have mostly been someone else's area, start learning them now. Sit with finance. Read the P&L every month until it's boring. Know what your area costs to run.
This is often the biggest gap between the two seats, and it's very learnable.
4. Take the work nobody owns yet.
Every company has work that sits between functions with no clear owner. Right now, the biggest one is usually AI. Tools get adopted team by team, and when the output is wrong, nobody is sure whose job it is to notice.
That's an ownership gap, and ownership gaps are COO work. Volunteer to own it: which tools are in use, who approves what, and which steps stay with a person. It's a natural first area to run in your own name, and it builds exactly the kind of authority a COO needs.
The part nobody mentions: you step out of the CEO's shadow
A Chief of Staff's power comes from being close to the CEO. People listen because you speak for them.
A COO needs a different kind of standing. People need to follow your calls because they're yours, not because they assume the CEO is behind every one. That means stepping back a little. Fewer "the CEO wants" and more "I've decided." Building your own team, and leading people who report to you rather than coordinating people who don't.
It can feel strange at first, because closeness to the CEO is what made you effective. But a COO who is still seen as the CEO's voice never fully gets the room.
Part of the move is also planning who takes the Chief of Staff work. If nobody picks it up, you'll keep doing both jobs, and the COO work will lose to the urgent things every time.
Side by side
| Chief of Staff habit | COO habit | |
|---|---|---|
| Authority | Borrowed from the CEO | Held in your own name |
| Decisions | Make sure they get made | Make them and answer for them |
| Brings to the CEO | Options, clearly framed | A decision, already made |
| Scope | Projects and priorities | Functions and numbers |
| The money | Someone else's area | Your area |
| Team | Coordinates people who report elsewhere | Leads people who report to you |
| Measured by | Whether the CEO's time goes to the right things | Whether the business runs without the CEO |
Then have the conversation
When you ask for the title, describe a job you're already doing.
Bring four things. The area you've owned, and what changed because you owned it. The decisions you made on your own, and how they turned out. The numbers you know cold. And a plan for the Chief of Staff work: who takes it, or whether it goes away.
If you're the founder
Your next COO may already be your Chief of Staff. The signs:
They bring you decisions instead of questions. They know the numbers in their area without looking. People across the company follow their calls even when you're not in the room.
If that's who you have, set them up for the move the simple way. Hand them one function with a real number attached, and step back. Don't approve every call. Let them own it for a quarter and see how it runs.
If it works, say it out loud to the leadership team. Authority that isn't announced doesn't take hold. And remember that not every great Chief of Staff wants to be a COO. Some love being the CEO's partner, and that's a real career too. Ask.
When the timing isn't right
Sometimes the company isn't ready for a COO yet, or the CEO isn't ready to hand over real ownership. That's useful information, and it doesn't undo anything you've built. Owning outcomes, making decisions, and knowing the numbers go with you to the next seat.
When I moved from Chief of Staff to COO, I didn't suddenly know more. I'd been seeing the problems clearly for years. What changed was that I could fix them in my own name. You can't give yourself that authority. But you can build so much ownership that handing it to you is the obvious call.
If you're a founder working out whether your company needs a COO yet, or how to grow the one you have, that's the work I do. Let's talk.
