Chief of Staff vs COO vs Executive Assistant
The three roles differ on two things: whether anyone reports to them, and which layer of your work they operate on. An executive assistant has no authority and works on logistics. A Chief of Staff has no authority and works on judgment. A COO has full line authority and works on execution.
Get those two axes straight and the choice becomes obvious. Most bad hires in this area happen because someone matched a title to a feeling of being overwhelmed rather than to a specific failure.
I hold the Chief of Staff role, so I will be direct about where mine is the wrong answer.
The comparison, at a glance
| Executive Assistant | Chief of Staff | COO | |
|---|---|---|---|
| Line authority | None | None | Full |
| Operates on | Logistics | Judgment | Execution |
| The question they answer | When should this happen? | Should this happen, and does it need you? | Are we delivering? |
| Owns outcomes | No | No | Yes |
| People report to them | Nobody | Nobody | Functions and their leaders |
| Typical tenure | Years | 18 to 24 months | Years |
| Hire when | Coordination is the bottleneck | You are the routing layer | You cannot scale execution |
| Rough US cost | $70K to $120K | $160K to $210K base | $250K and up, plus equity |
Scroll the table sideways to compare all three.
The row that decides most of these choices is the second one. Logistics, judgment, execution. Three different problems that all feel like being too busy.
Executive Assistant
What it is: the role that removes friction from the mechanics of your working life. Calendar, travel, expenses, scheduling, meeting logistics, inbox triage at the administrative level, and the hundred small coordination tasks that consume an hour a day if nobody else does them.
The problem it solves: your time is being lost to arrangement rather than to work.
Hire one when you are double booked regularly, scheduling anything across three people takes four days, travel eats an afternoon to organise, or you are personally handling logistics that any competent person could handle better than you.
The thing people undervalue: a genuinely excellent EA is transformative and is much easier to hire than the other two. A significant share of executives who hire a Chief of Staff needed this instead, and would have got more value for a third of the cost.
The limit: an EA optimises the execution of what has already been decided. They will not tell you that a standing meeting has produced no decisions in four months, because that is not their remit and it is not what they were hired to notice.
Chief of Staff
What it is: the role that runs your operating system. What reaches you, what your week is shaped around, what decisions are waiting and on what, and what work should be leaving your desk. The full picture of the job is here.
The problem it solves: you have become the routing layer of your own organization.
Hire one when requests, approvals, and escalations all arrive at you personally and get sorted by you personally. When your team describes itself as blocked rather than overloaded. When you could not say what your directs are waiting on right now.
The distinguishing feature: no line authority. Nobody reports to a Chief of Staff. Everything the role does runs on borrowed authority from you, which is why it depends entirely on the relationship and why it collapses if you undermine their calls in public.
The limit: a Chief of Staff cannot own an outcome, cannot direct another function, and cannot make decisions in their own name. If what you need is someone to run a part of the business, this is not that role, and asking it to be that role is how good people get frustrated and leave.
Chief Operating Officer
What it is: an executive with real authority over how the company delivers. Functions report to them. They own outcomes and carry accountability for them.
The problem it solves: the organization cannot execute at its current scale, and someone other than the CEO needs to own that.
Hire one when there are enough functions to coordinate that coordination is a full time job, when you as CEO are spending most of your time on internal delivery instead of on the things only a CEO can do, and when there is enough organization underneath for a COO to actually run.
The limit: hiring a COO before there is an organization to operate produces a very expensive person doing project work. It also creates a structural question about what the CEO is now for, and that question is easier to answer at 400 people than at 40.
So which one is actually senior?
This is the most common follow-up question, and the honest answer is that it does not quite work as asked.
The question assumes one ladder. There are two.
A COO and a Chief Administrative Officer are line executives. They sit on an org chart with an organization beneath them, they own outcomes, and they can be ranked against each other without much difficulty.
A Chief of Staff and an Executive Assistant are not on that ladder at all. Neither has anybody reporting to them. Both operate on borrowed authority, which means their influence comes from proximity and trust rather than from position. Asking whether a Chief of Staff outranks an Executive Assistant is a bit like asking whether a lawyer outranks an accountant.
That said, people asking the question want a practical answer, so here is one.
Where each role actually sits
| Role | Line authority | Reports to | What they own |
|---|---|---|---|
| Executive Assistant | None | The executive they support | Logistics, calendar, coordination |
| Chief of Staff | None | The principal, directly | The principal's operating system |
| Chief Administrative Officer | Yes | CEO, sometimes the COO | Internal support functions: HR, facilities, IT, legal |
| COO | Yes | CEO | Core operations and delivery |
Scroll the table sideways to see every column.
The two highlighted roles are not on the same ladder as the two below them. Neither has anyone reporting to them, so their influence comes from proximity and trust rather than position.
On compensation, the usual order runs COO, then CAO, then Chief of Staff, then Executive Assistant. That holds often enough to be a reasonable default and it breaks constantly.
On influence, the order inverts regularly. An Executive Assistant who has worked with a CEO for eleven years has more real influence over that person's decisions than a newly hired Chief Administrative Officer does. Proximity compounds, and it does not appear on any org chart.
If you are choosing between these roles as a hire, the seniority question is the wrong one to optimize. The useful question is which kind of problem you have, which the table above and the section before it are both trying to answer.
Where a Chief Administrative Officer fits
This title comes up often enough to be worth naming, partly because it overlaps with two of the others.
One thing to clear up first. CAO means Chief Administrative Officer in most companies and Chief Accounting Officer in some, particularly in finance and in public companies. Those are entirely different jobs. Check which one a job posting means before reading anything into it.
The Chief Administrative Officer, in the first sense, runs internal administrative and support functions. Depending on the company that means some combination of HR, facilities, IT, legal, procurement, and corporate services. It is a real functional executive role with an organization underneath it.
The cleanest distinction from a COO: the COO owns what the company delivers, and the CAO owns the internal machinery that lets it deliver. Operations versus infrastructure. In most structures the CAO sits a tier below the COO in scope, and reports either to the CEO directly or through the COO.
The distinction from a Chief of Staff is much sharper, and it is the same one that separates a Chief of Staff from a COO. A CAO has an organization. A Chief of Staff has nobody. A CAO owns a defined set of functions permanently. A Chief of Staff works across every function and owns none of them.
Companies sometimes consider the two interchangeably, and that is usually a sign the problem has not been diagnosed. If specific administrative functions are running badly and need an owner, that is a CAO. If those functions are fine and the executive is drowning in what reaches them, that is a Chief of Staff. Those are different problems and the same hire does not solve both.
What about an Executive Assistant to a COO?
A smaller question, but it comes up.
Executives at every level have Executive Assistants, and supporting a COO is a different job from supporting a CEO. A CEO's calendar is largely external: board, investors, customers, press. A COO's calendar is internal and operational, which means the assistant is coordinating across functions and dealing with a much higher volume of short-notice change.
Neither is harder in general. They demand different things, and someone excellent at one does not automatically transfer.
Match the symptom to the role
The fastest way through this is to describe what is actually going wrong.
"My calendar is chaos, scheduling takes forever, logistics are eating my week." Executive assistant. Do not overthink this one.
"Everything comes to me. I am the bottleneck and I cannot tell what is stuck." Chief of Staff. This is precisely the routing problem the role exists for.
"We cannot execute. Functions are not coordinated and delivery is slipping across the company." COO. This is an authority problem and neither of the other two roles has any.
"Projects slip across teams and nobody owns the cross functional work." None of the three. That is a program manager, and program management is a real profession that deserves its own title rather than being dressed up as a Chief of Staff role.
"Decisions pile up on my desk and I am the reason things move slowly." Possibly a Chief of Staff, but try something cheaper first. Write down what does and does not need you. Unclear ownership always pushes decisions upward, because asking carries no personal risk and deciding does. Four or five lines of written criteria solves a surprising amount of this and costs an hour rather than $200,000.
"I am drowning in inbound and I cannot keep up with the volume." Try counting your channels before you hire anyone. Most senior leaders have nine to twelve separate ways people can reach them and guess four. That is a design problem, not a staffing problem.
"I genuinely cannot tell which of these it is." That is the most common and most honest answer, and it is worth resolving before you spend money on any of them.
The four mis-hires that happen most
Hiring a Chief of Staff when you needed an EA. By far the most common. The tell: you describe the problem in terms of scheduling, coordination, and logistics, but the title felt too junior for the seniority of your pain.
Hiring a Chief of Staff when you needed a COO. The tell: you want them to own something. A Chief of Staff who owns a function is a COO with the wrong title and no authority to match, which is the worst of both.
Calling a program manager a Chief of Staff. Usually done to make the offer more attractive during hiring. It produces a confused role, an unclear scope, and a person doing valuable work under a title that sets everyone's expectations wrong.
Hiring any of them as a reward. The Chief of Staff role in particular requires an unusual temperament: comfort with invisible work, no authority, and constant proximity to someone else's decisions. Excellent operators frequently hate it, and promoting your best performer into it is a good way to lose them.
Can you have more than one?
Yes, and the combination is common at scale.
EA plus Chief of Staff is the standard pairing for a CEO past a few hundred people. They do not overlap. The EA runs logistics, the Chief of Staff runs the operating layer, and the two of them working together is considerably more effective than either alone.
COO plus Chief of Staff also works, and the Chief of Staff usually sits with the CEO rather than with the COO. If both report to the same person, the boundary needs to be written down or it becomes contested within a quarter.
All three is a large company structure and rarely a question anyone is asking at the point they read an article like this one.
NOTE: If your company runs on EOS, the Entrepreneurial Operating System, the Integrator comparison is one to make note of, and I wrote an article that addresses how the Integrator role compares to a Chief of Staff role.
Before you hire any of them
Every one of these roles is expensive, and two of the three are hard to hire well. The costly mistake is not picking the wrong title. It is hiring a person to fix a problem you have not correctly diagnosed.
Most executives report a time problem. In most cases the actual constraint sits somewhere else: in what reaches them, in decisions that never got delegated, or in work that never left their desk. Four components determine what a senior leader produces, and the whole system moves at the speed of the tightest one.
If you fix the wrong component, or hire someone to fix the wrong component, you spend a quarter and a salary learning something you could have found out in five minutes.
The Executive Operating Index scores all four and names the one actually holding you back. It is free, and your score appears before you are asked for anything.
If it turns out you need the Chief of Staff function but cannot justify the headcount, that gap has a smaller answer.
FAQ
What is the difference between a Chief of Staff and a COO? Authority. A COO has functions reporting to them and owns outcomes. A Chief of Staff has no line authority and works entirely through the principal's borrowed authority. A COO runs part of the company. A Chief of Staff runs the executive's operating system.
What is the difference between a Chief of Staff and an executive assistant? Layer. An EA works on logistics and optimizes the execution of what has been decided. A Chief of Staff works on judgment adjacent questions and influences what gets decided in the first place.
Should I hire a COO or a Chief of Staff? If the problem is that the company cannot execute and functions need coordinating under one accountable leader, that is a COO. If the problem is that everything routes through you personally, that is a Chief of Staff.
Can a Chief of Staff become a COO? Frequently, and it is one of the most common paths out of the role. The Chief of Staff seat provides an unusually complete view of a company, which is good preparation for running part of it.
Do I need a Chief of Staff or just better systems? Often the second. Written decision rights and a designed intake solve a meaningful share of what people hire a Chief of Staff for, and both cost hours rather than salaries. Try those first.
Which should I hire first? For most companies, an excellent executive assistant, and considerably earlier than they do. It is the cheapest of the three, the easiest to hire, and it removes a category of friction that otherwise persists for years.
What is higher, a Chief of Staff or an Executive Assistant? They are not on the same ladder, so the comparison does not quite work. Neither has direct reports and both run on borrowed authority. Compensation usually favors the Chief of Staff, but influence tracks proximity and tenure, so a long-serving assistant often has more of it.
What is the difference between a Chief Administrative Officer and a Chief of Staff? A Chief Administrative Officer runs internal support functions such as HR, facilities, IT, and legal, with an organization reporting to them. A Chief of Staff has no direct reports and owns no function permanently. One is a line executive, the other works across every function and owns none.
What is the difference between a CAO and a COO? The COO owns what the company delivers: operations, product, supply chain. The Chief Administrative Officer owns the internal machinery that supports delivery. In most structures the CAO sits a tier below the COO in scope and reports either to the CEO or through the COO.
Bob Stanke is a Chief of Staff and Executive Advisor. He writes about the operating layer of executive work: what reaches you, where your attention goes, how decisions clear, and what leaves your desk.
