Ask ten people what a Chief of Staff does and you'll get ten different, mostly vague answers. "Right hand to the CEO." "Does a bit of everything." That vagueness is exactly why so many EAs get the title and then spend six months doing their old job with a new signature line.
Here's the concrete version: what a Chief of Staff actually owns, day to day, not the theory of it.
It's not a task list. It's four ongoing responsibilities.
An Executive Assistant's job breaks into tasks you can check off: the calendar is accurate, the inbox is triaged, the trip is booked. A Chief of Staff's job breaks into standards you hold the business to, continuously, whether or not anyone asked:
- The leadership operating rhythm. Meeting cadence, agendas that aren't assembled ten minutes before the call, decisions captured in writing, an owner named for every one of them.
- The decision log. The place where "what did we actually agree to in March" has a real answer, instead of the same argument happening again in June because nobody wrote it down.
- One or two cross-functional initiatives, owned start to finish. A market entry. A systems migration. A partnership that touches three departments and would otherwise drift for months because no single person is accountable for the whole thing.
- Board and investor operations. Not assembled in a panic the night before, but running on a calendar, three days ahead, every quarter.
Notice what's missing from that list: nothing about the calendar, the inbox, or travel. That's not because those things stop mattering. It's because they stop being your job to hold. A Chief of Staff who's still personally managing the CEO's calendar six months in hasn't made the shift yet, no matter what the title says.
The real skill isn't a skill. It's timing.
People ask me what qualification actually earns the title, expecting a checklist. There isn't one. It's a track record of being right about what matters before anyone tells you what matters.
Concretely: in your next leadership meeting, don't just take notes on what was said. Notice what wasn't decided, and follow up on it before your principal has to ask. When you see a process breaking two months before it becomes a fire, flag it with a suggested fix attached, not just the warning. When someone hands you a task, ask whether the task actually solves the underlying problem, and say something if it doesn't.
None of that requires permission. It requires you to start operating like the job before anyone gives you the title for it. That's how the shift actually happens, in the vast majority of cases I've seen, including my own.
Why "acts across the whole leadership team" is the line that matters
An EA's authority is clear and bounded: you operate on behalf of one person, inside a scope they've defined. A Chief of Staff works with borrowed authority, holding people accountable who don't report to them, across departments that didn't ask for another layer of oversight. That's a genuinely different kind of pressure, and it's why the jump isn't just "EA, but more senior." It's a different job built on a different kind of trust.
This is the surface. The full breakdown of this shift, the exact scope difference, and a real case study of watching someone make this jump, is Module 1 of the Great Talk Africa workbook, free to read in full.
If you're already recognizing pieces of your own week in this list, that's worth paying attention to. And if you want a fast, honest gut check on whether your current instincts already lean EA or Chief of Staff, the ten-scenario quiz takes about two minutes.