Both roles get suggested at the same moment: when the owner is in too many decisions and the company is starting to wait on them.
They solve different problems.
A chief of staff extends the CEO's reach. A COO takes over the operation. Hire the wrong one and the problem you started with is still there a year later, now with a new salary attached.
The short version
| Chief of staff | COO | |
|---|---|---|
| Works on | The CEO's priorities | The company's operation |
| Authority | Borrowed from the CEO | Their own, over the operating leaders |
| Direct reports | Few or none | The operating leaders |
| Judged on | Whether the CEO's agenda moves | Margin, delivery, safety and the people running them |
| Typical tenure | Often a few years, then a move into another role | A permanent seat |
A chief of staff makes the CEO more effective. A COO makes the company less dependent on the CEO.
Start with the problem
The useful question is what's actually stuck. Look at where things wait.
If the operation is waiting on you, you have a COO problem. Project managers or branch managers report to you directly. Jobs slip and margins fade because the people below you don't have the authority to fix it.
If your own work is waiting on you, you have a chief of staff problem. The operation runs, but you're buried in meetings, follow-ups, bank and board preparation and special projects like an acquisition. Good ideas die because you don't have the hours to see them through.
Plenty of owners have both. Start with whichever one is costing the company more.
What goes wrong with each mistake
Hiring a chief of staff when you need a COO. You get a capable person with no real authority. They can prepare your decisions, but the operating leaders still report to you, so the decisions still wait on you. Within a year the chief of staff is frustrated and the operation hasn't changed.
Hiring a COO when you need a chief of staff. You give operating authority to someone and then keep making the calls yourself, because what you wanted was help with your own load. A strong COO won't stay in that seat. We've written about why a new executive's first year fails, and an owner who keeps every decision is high on the list.
What we see in founder-led companies
In construction and home services, the bottleneck is usually the operation. The founder built the company by running jobs, and the field still runs through them.
That usually points to a COO, or to a VP of Operations if the CEO wants to keep the strategy and the key client relationships. A chief of staff makes more sense once there's a leadership team in place and the CEO's own calendar is the constraint.
If your company runs on EOS, the integrator role sits much closer to a COO than to a chief of staff. It owns the operation and holds the leadership team accountable.
Decide the decision rights first
Whichever seat you hire, write down which decisions the new person owns before you start looking. It's the part owners most often skip, and it decides whether either hire works.
In a FireSeeds search this gets settled in the Bullseye Meeting, with everyone who has a say in the hire in the room. For a COO it covers how the CEO and COO will split the work. For a chief of staff it covers what they can decide in the CEO's name.
Can a chief of staff grow into a COO?
Sometimes. A chief of staff who has spent 2 or 3 years inside every part of the business knows it well, and some grow into the COO seat.
It works when they've already held real operating responsibility along the way, like running a division or an integration. It struggles when the role was mostly coordination, because the operating leaders will judge them on whether they've run anything.
If it's the COO seat
What we look for in a COO, and how we run the search, is on our construction COO search page. If you're not sure which seat you need, talk it through with us. Working that out comes before anything else.