What a Chief of Staff Actually Does
A Chief of Staff runs the operating system of a single executive: what reaches them, where their attention goes, how decisions clear, and what leaves their desk. The title describes a relationship rather than a function, which is why job descriptions for it are so consistently vague.
I currently hold the role of Chief of Staff. What follows is what the job is actually like, rather than what the job postings say.
Why nobody can give you a straight answer
Search this question and you will find a dozen articles listing responsibilities: strategic projects, meeting facilitation, communications, special initiatives... All technically true, however also all useless, because they describe what the role touches rather than what it is for.
The reason the definitions are vague is that the job is shaped by whatever the principal is worst at.
A Chief of Staff to a founder who is brilliant at product and avoids conflict spends their time on organizational issues that are being left to fester. A Chief of Staff to an operator who decides fast and communicates badly spends their time translating. Two people with the same title at two companies are barely doing the same job!
This is a feature. The role exists precisely because the gap it fills is specific to the person.
What the job actually is
Underneath the variation, the work is consistent, and it maps to four things.
Deciding what reaches the principal. Requests, escalations, reports, introductions, meeting invitations, complaints, and ideas. Someone has to sort it, and if nobody does, the executive becomes the sorting machine. Most of the value of the role is created here, and almost none of it is visible.
Protecting and shaping their attention. This is not about calendar management. Deciding what the shape of the week should be given, what the quarter requires, then defending it against a hundred reasonable requests. This is where the real fight happens, and it is mostly a fight about the aggregate rather than any single meeting.
Keeping decisions moving. Knowing what is waiting, for how long, and on what. Chasing the input that is actually blocking it. Pushing back when something that belongs two levels down has arrived on the desk anyway. Nobody in a company measures how long decisions sit, which is why so many sit.
Making sure work leaves and stays gone. Finding what the principal is holding that belongs elsewhere, and making the handoff survive contact with a busy month.
Which gives you the honest one line version of the job:
A Chief of Staff is a person hired to run someone else's operating system, because that system has outgrown the person's ability to run it while also doing their actual job. For me personally in the Chief of Staff position I am in currently, it means making sure the Visionary has the time and attention to look ahead.
What a week actually looks like
Concrete beats abstract, so here is the shape of a normal one.
Monday is about alignment and planning. All meetings that bring alignment to the organization happen right out of the gate. For me currently, that means a quick 30-minute all staff meeting to share updates on current initiatives, the weekly 90-minute leadership team meeting (we run on EOS, so this is our Leadership L10), and important meetings with Finance and Revenue Operations. Monday is also about connecting briefly with my principal to touch base on what is genuinely urgent and what decisions have been sitting.
Tuesday and Wednesday are where the real work sits. This is when I am digging into specific roadblocks, like a decision that has been stuck for eleven days and nobody could say why, a project where two teams believe they own the same thing, a report going to the board that says something the numbers do not support, etc. This is also the part of the week where I am doing 30-minute check-ins with project stakeholders, and currently, my direct reports. Currently the leadership team members report to me, so I am doing deep-dives with them.
Thursday and Friday are follow through. What was decided, who owns it, when it lands, and who has quietly not started. This is also when I am blocking large, uninterrupted areas on my calendar to work on strategic projects.
And running underneath all of it, constantly: what is being escalated that should not be, and why.
Chief of Staff vs Executive Assistant
These get conflated more than any other pair, and the difference is not seniority.
An executive assistant manages logistics. Calendar, travel, expenses, scheduling, coordination. Done well, it is a demanding job that removes an enormous amount of friction, and a great EA is genuinely hard to replace.
A Chief of Staff manages judgment adjacent work. Not when the meeting happens, but whether it should. Not booking the review, but noticing the review has produced no decisions in four months.
The clearest test: an EA optimizes the execution of what has been decided. A Chief of Staff influences what gets decided in the first place.
Many executives would be better served by an excellent EA than by a mediocre Chief of Staff, and quite a few who hire the second actually needed the first.
Chief of Staff vs COO
The critical difference is authority, and it is counterintuitive.
A Chief of Staff has no line authority. Nobody reports to them. They cannot direct another function, override a leader, or make a call in their own name.
Everything the role does runs on borrowed authority, which changes the job completely. You cannot instruct. You persuade, you convene, and you occasionally say a version of "I do not think she will go for that" and let the room adjust.
A COO owns outcomes and has an organization to deliver them. A Chief of Staff acts in the principal's absence and works entirely through influence and proximity.
This is also why the role fails when it is treated as a stepping stone to command. The moment a Chief of Staff starts issuing instructions, the organization stops trusting the role, and the borrowed authority evaporates.
The parts nobody writes about
Four things that are true about this job and rarely appear in an article about it.
Almost all of your best work is invisible. The meeting that did not happen. The escalation that got resolved two levels down. The decision that reached the principal already framed, with a recommendation attached, so it took four minutes instead of forty. None of that shows up anywhere. You have to be genuinely comfortable with a job where the evidence of competence is an absence.
You run entirely on one person's trust. No line authority means the role has exactly one source of power, and it is the principal's confidence in your judgment. That relationship is the job. When it is strong, the role is one of the highest leverage seats in a company. When it is not, you become a very expensive project manager.
You can become the bottleneck you were hired to remove. If everything routes through you instead of being routed by you, you have simply moved the queue by one desk. The version of the job that works builds rules and paths that operate without you. The version that fails makes you indispensable, which feels excellent and is a failure state.
It is a role you are supposed to leave. Most tenures run eighteen to twenty four months, and that is by design rather than by attrition. You learn the whole company from the best possible vantage point, and then you go and run something. A Chief of Staff who is still in the seat at year five is usually either extraordinary or stuck.
When the role works, and when it does not
It works when the principal genuinely delegates judgment rather than tasks, the scope is written down, the organization understands the role is not a shadow executive, and the principal is willing to be told things they do not want to hear.
It fails when it is created as a reward, when the principal cannot let go of the decisions they claim to have delegated, when the scope is "help me with stuff," or when the hire is really a project manager with an inflated title.
The last one is the most common. A great deal of what gets called a Chief of Staff role is program management, and program management is a genuine profession that deserves its own name.
Do you actually need one?
Four questions, and they are more useful than any job description.
Are you the router? If requests, approvals, and escalations all arrive at you personally and get sorted by you personally, that is the function you are missing.
Do decisions sit? Not because they are hard, but because they are waiting for you and there are too many. That is a capacity problem in the decision layer, and it is exactly what the role addresses.
Do you know what your team is waiting on right now? If the honest answer is no, nobody is holding that list, and nobody will start holding it without being asked.
Would things stop if you were unavailable for a week with no notice? Not a planned holiday. Planned absence hides this, because everyone prepares for it. The unplanned version is the real test.
If three of those four land, you have the problem the Chief of Staff role solves. Whether you need a full time person to solve it is a separate question.
Most people who need this will never get one
There are a few thousand Chief of Staff roles in the United States. There are hundreds of thousands of leaders with the problems described above.
The role is expensive, hard to hire for, and difficult to justify below a certain scale. Which leaves an enormous number of executives carrying a job that a well designed system could carry instead.
That gap is the work I do now, in two forms.
Fractional Chief of Staff. The function without the headcount, for founders and executives who need the operating layer run properly but cannot justify a full time hire.
Executive advisory. Measuring your operating system, finding the one component actually holding it back, and rebuilding it so the fix holds. Frequently the better starting point, because most executives are wrong about which of the four is their constraint.
If you want to know which one is yours, the Executive Operating Index scores all four in about five minutes and names the binding one. It is free, and the score appears before you are asked for anything.
FAQ
What does a Chief of Staff do day to day? Triages what reaches the principal, protects and shapes their week, tracks what decisions are waiting and on what, and makes sure delegated work actually leaves and stays gone. Much of the value is created by things that never reach the executive at all.
Is a Chief of Staff the same as an executive assistant? No. An EA manages logistics and optimises the execution of what has been decided. A Chief of Staff works on judgment adjacent questions and influences what gets decided. Many executives who hire the second actually needed the first.
Does a Chief of Staff have authority? No line authority. Nobody reports to them. The role operates entirely on the principal's borrowed authority, which is why it depends so completely on that relationship.
How long do people stay in the role? Typically eighteen to twenty four months. It is designed as a vantage point rather than a destination, and most people move into an operating role afterward.
When should a company hire a Chief of Staff? When the executive has become the router for requests and decisions, when work is visibly waiting on one person, and when that pattern has persisted for more than a quarter rather than through one busy period.
What is a fractional Chief of Staff? The same function delivered part time, usually for founders and executives who need the operating layer run properly but cannot justify a full time hire.
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.
