How to Go From Executive Assistant to Chief of Staff: The Move Nobody Promotes You Into
Being a better Executive Assistant won't make you a Chief of Staff. The two jobs run on different kinds of authority, and the move is about earning the second kind before anyone changes your title. Here's how, and what founders should look for in the EA they already have.
After I wrote about the difference between a Chief of Staff, an Executive Assistant and an Operations Manager, the question that stayed with me didn't come from a founder. It came from the other side of the desk: how do you actually get from EA to Chief of Staff?
I spent more than a decade in Executive Assistant roles before I was a Chief of Staff, so I can answer this one from the inside.
The short version: you don't get there by being a better EA. You get there by starting to do a different job, in small and visible ways, before anyone gives you the title.
Why being a great EA doesn't get you there
An Executive Assistant owns the executive's logistics. The calendar, the travel, the inbox, the hundred small things that eat a founder's day. A Chief of Staff owns the executive's leverage. The decisions that go on the calendar, whether the right people are making them, and whether anyone follows through.
Those are different jobs. One is not the junior version of the other. The best EA I ever worked alongside could have run circles around half the Chiefs of Staff I've met. She owned a different thing, and she owned it completely.
Which is exactly the trap. Doing logistics brilliantly doesn't turn it into leverage. It makes you the person your executive can least afford to lose from the seat you're in. Nobody promotes you out of a job you do that well, into a job they've never seen you do.
So the move isn't a promotion in the usual sense. It's a job change that happens to be open to you because of where you sit.
What you already have
Start with the good news, because it's real. An EA who has been in the seat for a few years holds things a Chief of Staff hired from outside spends months trying to acquire.
You know how your executive actually decides. Not how they say they decide. You know what they need to see before they'll commit, which topics they put off, and what time of day to bring them a problem.
You know how the company actually works. The calendar is the most honest document in the building. You can see which meetings produce decisions and which produce another meeting, who gets time and who gets rescheduled, and which projects have quietly stopped being discussed.
And you have trust. You already hold the confidential things.
What you don't have yet is the one thing the Chief of Staff job runs on: authority that extends past your executive's door. Everything below is about getting it.
Three moves to make before you ask for the title
1. Stop tracking the meetings. Start tracking the decisions.
After every leadership meeting, know what was decided, who owns it, and when it's due. Keep the list. Then be the one who notices when something slips, and say so: "The pricing decision from the 4th doesn't have an owner yet. Do you want me to ask?"
This is the single most useful habit in the Chief of Staff job, and you can start it tomorrow without anyone's permission.
2. Tell your executive what they're not seeing.
You see more of the company than almost anyone in it. As an EA, the professional thing is to keep most of that to yourself. As a Chief of Staff, the professional thing is to say it out loud, with a recommendation attached.
Start small and be specific. "Two of your direct reports have asked me this week when the hiring plan is coming. I think they're waiting on you and don't want to say so." That isn't gossip. That's the job.
3. Ask for the authority, by name, on one thing.
Pick one cross-functional item that keeps stalling, and ask to own the follow-through: "Can I chase this with the department heads on your behalf?"
The whole difference between the two roles is whether your authority stops at one person's door. Nobody extends it by accident. It gets extended when your executive says to the leadership team, in the room, "she's following up on this for me." Ask for that sentence. Then deliver on the one thing, visibly, and ask for the next.
The part nobody mentions: you have to give up the calendar
Here is where most EA to Chief of Staff moves quietly fail. The title changes and the calendar doesn't go anywhere.
You can't hold both jobs. Logistics is urgent every hour of every day. Leverage is important and rarely urgent. So the calendar wins every time, and a year later you're an EA with a bigger title and the same work, which is the worst version of both.
So part of the move is planning your own replacement. Write down how the logistics actually run. Propose who takes them: a new EA, a shared assistant, or the scheduling and inbox tools that now handle a real share of that work. If the company won't backfill the seat, treat that as information about whether the new one is real.
Side by side
| Executive Assistant habit | Chief of Staff habit | |
|---|---|---|
| After a meeting | Notes sent, next one booked | Decisions logged, each with an owner and a date |
| When something slips | Reschedule it | Chase the owner, and tell the CEO if it matters |
| What you notice | Kept in confidence | Brought forward with a recommendation |
| Authority | Stops at the executive's door | Borrowed from the CEO, extends into the company |
| The calendar | Yours to run | Someone else's to run |
| Measured by | The executive's time | The executive's decisions |
| How the move fails | Too good at the seat to be moved | New title, same calendar |
Then have the conversation
When you ask for the title, don't ask for a promotion. Describe a job you're already doing.
Bring four things. The decisions you've been tracking, and what got unstuck because you tracked them. The one thing you owned with borrowed authority, and how it went. What you would own as Chief of Staff: the leadership meeting, the priorities list, the follow-through. And what you would hand off, with a plan for who takes it.
That's a short conversation when the evidence is already in the room.
If you're the founder
Read all of that from the other side of the desk. Your next Chief of Staff may already run your calendar.
The signs are easy to spot once you look. They tell you what you're not seeing, without being asked. They follow up on decisions nobody assigned them. People in the company already go to them to find out what you'd think.
If that's who you have, test it the cheap way. Hand them one cross-functional thing, with your name behind it, and watch what happens. It costs you almost nothing, and it will tell you more than any interview.
Two cautions if it works. Backfill the EA seat, or you'll get a Chief of Staff who books travel. And tell the leadership team, in the room, that the authority has changed. If you don't say it, the company keeps seeing an assistant, and so will the person you just promoted.
One more. Not every great EA wants this job, and that isn't a lack of ambition. It's a different job. Ask before you assume.
When the answer is no
Sometimes you make all three moves, ask clearly, and the answer is no. Then it's no again.
That usually isn't about you. It means the company doesn't have a Chief of Staff seat, or your executive isn't ready to lend their authority to anyone. Either one is worth knowing, because the habits you built don't stay behind. Tracking decisions, saying what you see, and owning the follow-through are the job, and they're the job anywhere.
What changed when I moved from EA to Chief of Staff wasn't that I got smarter. It was that my authority stopped ending at one person's door. You can't give yourself that. But you can make it very easy for someone to hand it to you.
