Chief of Staff vs. Executive Assistant vs. Operations Manager: Three Jobs Founders Keep Hiring Into the Same Seat
Founders hire an Executive Assistant and expect a Chief of Staff. Or they hire a Chief of Staff, use them as an Executive Assistant, and lose them inside a year. The confusion is worse than Chief of Staff vs. COO, and it's cheaper to fix, if you know what each job actually owns.
I wrote recently about the difference between a Chief of Staff and a COO. The short version: a COO owns outcomes, a Chief of Staff extends the CEO, and the whole decision falls out of that one distinction.
The question I keep hearing since then is a step earlier: okay, but I'm not at COO yet. I need someone to help me run my day and my company. Is that a Chief of Staff, or an Executive Assistant, or one of those Operations Manager titles I keep seeing?
Good question. Those are three different jobs, they get hired into the same seat constantly, and the mismatch costs you either the person or a year.
What each one actually owns
Forget seniority for a minute. The way to tell these apart is by what each role owns: what it's accountable for, what it's allowed to decide, and what falls apart if the role is empty.
An Executive Assistant owns the executive's logistics. Calendar, travel, inbox triage, meeting prep, expenses, the hundred small things that eat a founder's day. A great EA makes a founder twice as effective, and I mean that literally. The difference between a founder with a great EA and without one is a working day a week. The EA's authority is entirely on behalf of the executive, and it stops at the executive's door. They don't make business decisions and they shouldn't be asked to.
A Chief of Staff owns the executive's leverage. Not the calendar, but the decisions that go on the calendar. Are the right things getting decided, by the right people, on time, and does anyone follow up? A Chief of Staff runs the leadership meeting, drives the priorities the CEO set, chases the cross-functional things that fall between departments, and tells the CEO what they're not seeing. Their authority is borrowed from the CEO, but it extends into the company. A Chief of Staff can walk into any department and get an answer, because everyone knows who they're asking for.
An Operations Manager owns a piece of the operation in their own name. A process, a function, a team. Onboarding. Vendor management. Fulfillment. The finance close. The Operations Manager doesn't work for the founder the way the other two do. They work for the company, running something that has to run whether or not the founder is in the room. Their authority is held directly, inside a defined scope.
Three different sources of authority. Three different things that break when the seat is empty. That's the whole distinction.
The two mismatches, and what they cost
The first mismatch is hiring an EA and expecting a Chief of Staff.
This one is usually a budget decision. The founder knows they need "someone to help run things," looks at Chief of Staff compensation, and hires an EA with an expanded job description instead. Then they're frustrated when the EA doesn't push back on the leadership team, doesn't own the priorities, doesn't tell them what they're missing. Of course they don't. Nobody gave them the authority to, and everyone in the building knows it. You bought logistics and you're mad it isn't leverage.
The cost here is quiet: the founder stays the bottleneck, and concludes that the role doesn't work.
The second mismatch is hiring a Chief of Staff and using them as an EA.
This one is usually a discipline problem. The founder hires a strong, senior Chief of Staff. Then, because the calendar is on fire and the inbox is a disaster, hands them the calendar and the inbox. Just for now. Just until things settle. Things never settle, the Chief of Staff spends eighteen months booking travel with an MBA, and then leaves for a company that will actually use them.
The cost here is loud: you lose a good person, a year, and a reputation among the next three candidates you try to recruit.
There's a third, less common mismatch: hiring an Operations Manager and expecting either of the other two. Founders do this when they want someone to "own operations" but haven't decided which operations. The Ops Manager arrives, asks what they own, gets told "everything," and discovers that means nothing. Give them a scope or don't hire them yet.
Side by side
| Executive Assistant | Chief of Staff | Operations Manager | |
|---|---|---|---|
| Owns | The executive's logistics | The executive's leverage: decisions, follow-through, priorities | A defined piece of the operation |
| Authority | On behalf of the executive; stops at their door | Borrowed from the CEO; extends into the company | Held directly, inside a scope |
| Works for | The executive | The CEO, on behalf of the company | The company |
| What breaks without them | The founder loses a working day a week to small things | Decisions stall, priorities drift, nobody follows up | The specific thing they run stops running |
| Right moment to hire | The founder's calendar is the bottleneck | The founder's decisions are the bottleneck | A function has outgrown being run in someone's spare time |
How to tell which one you need
Three questions, and they're different from the ones in the COO article on purpose.
1. What's actually eating your day?
Write down what you did yesterday. If most of it was logistics (scheduling, rescheduling, chasing a signature, answering email that someone else could have answered), you need an EA, and you need one before anything else on this list. This is the cheapest, fastest leverage a founder can buy, and I'm regularly surprised how many founders at forty people are still doing their own calendar.
If most of yesterday was deciding, or worse, being asked to decide things that shouldn't have needed you, keep reading.
2. When something falls through the cracks, is it a task or a decision?
Tasks fall through the cracks when nobody tracked them. That's logistics. Decisions fall through the cracks when nobody owned getting them made: the cross-functional thing that three departments each assumed someone else was handling. That's leverage, and it's a Chief of Staff's job.
3. Is there a specific function that has no owner?
If you can name it (onboarding, vendors, the close, delivery), you don't need a generalist. You need an Operations Manager for that function, with a scope written down and the authority to run it. Hire for the function, not the title.
The order usually goes EA, then Chief of Staff, then Ops Managers
Not always. But there's a natural sequence here that mirrors how a company grows.
An EA comes first because the founder's time is the scarcest resource in the company, and logistics is the cheapest thing to take off their plate. A Chief of Staff comes next, when the founder's decisions become the bottleneck and someone needs to hold the leadership team together. Operations Managers come as functions form and outgrow being run in someone's spare time. This is where a company starts to look like it has an operation rather than a founder with helpers.
And then, somewhere past that, the Chief of Staff and the Ops Managers together start to look like they need someone to report to who isn't the founder. That's the COO conversation, and it's the article I wrote last time.
None of these roles is junior to another in any way that matters. They're different mechanisms for different problems. The mistake isn't hiring the "wrong level." It's hiring one mechanism and expecting it to do the job of another.
