What Does a Chief of Staff Actually Do?
Everyone defines it differently. Your CEO has one vision, LinkedIn has another, your board has a third. The confusion isn't an accident — it's because the role evolved without a framework. Here's the definitive answer from 20 years of practice.
Why Everyone Gets It Wrong
I've been a Chief of Staff four times at four different companies. Each time, the job description meant something different. At one company, I was running the operating system for a CEO who couldn't delegate. At another, I was architecting strategy while the CEO handled relationships. A third CEO needed me to be a force multiplier across the organization. A fourth needed someone to protect them from their own impulses.
All four roles were called "Chief of Staff."
This is the core problem. The title describes a proximity (Chief of Staff = you report to the CEO) but not a function. So when you're interviewing for the role, neither you nor the CEO can articulate what you're actually going to do.
The confusion gets worse when you compare it to other titles. Everyone knows what a CFO does. They know what a VP of Product does. But Chief of Staff? It's the role you describe by what you're not: "It's not really an EA. And not quite a project manager. Kind of like a mini-CEO, but you don't actually run anything."
That confusion costs you. It costs the CEO. It costs the organization.
The solution isn't to make everyone's job identical. The solution is to understand the three core functions that every Chief of Staff performs — and know which one your CEO hired you to lead.
The Three Functions Every CoS Performs
Every Chief of Staff, regardless of company or CEO, performs these three core functions. The question is which one dominates your role.
Strategic: You're in the room when strategy gets decided. You push back on thinking. You model rigor. You bring outside perspective. You help the CEO see around corners. You're a thought partner, not a yes-person.
Operational: You're designing how work happens. You build the CEO's operating rhythm. You create the systems that prevent chaos. You standardize how decisions get made. You're making the organization more efficient by making the CEO more efficient.
Connective: You're the person who knows what's happening everywhere. You connect dots across silos. You translate between departments. You amplify important signals. You're the nerve system that keeps information flowing.
Most Chiefs of Staff do all three. But the best ones know which function is their primary contribution in their specific role. That clarity changes how you prioritize every day.
What a Chief of Staff Is Not
This matters because many of the problems I see in Chief of Staff roles come from fuzzy boundaries.
Not an Executive Assistant: An EA manages the CEO's calendar, arranges travel, handles logistics. A Chief of Staff might do some of those things, but it's not your primary function. If you're spending 60% of your time on logistics, you're not performing as a Chief of Staff. You're performing as a highly paid assistant. There's nothing wrong with that job, but it's different. The confusion between these two roles destroys more CoS tenures than anything else.
Not a Project Manager: A project manager owns an outcome and drives to the finish line. A Chief of Staff might orchestrate projects, but your job isn't to execute them. You're not the final owner. The CEO is. You're there to make sure the right people own the right things.
Not a Mini-CEO: You do not run the company when the CEO is gone. You do not have direct reports (unless your scope explicitly includes that, which is rare). You do not have P&L ownership. You have influence, not authority. That's the whole point. Your power comes from proximity and trust, not from a span of control.
When you try to operate like a CEO without the authority, you create organizational confusion and personal frustration. Stay in your lane.
The three misunderstandings above are why some Chief of Staff roles feel like a trap. If you're unclear about what you are and are not responsible for, you'll work 60-hour weeks and still feel like you're failing.
The Four Flavors of Chief of Staff
After 20 years, I've identified four distinct archetypes. Most successful Chiefs of Staff fit primarily into one, with elements of the others.
Operations: You're the one who builds the systems. You create the CEO's decision cadence. You standardize how the leadership team operates. You're obsessed with process not because you love bureaucracy, but because process prevents chaos and creates space for the CEO to think strategically.
Strategy: You're the intellectual sparring partner. You challenge the CEO's assumptions. You bring data and rigor to conversations. You think a few moves ahead. You're not trying to make decisions for the CEO; you're trying to make the CEO's decisions better.
Transformation: You're the change leader. You own the implementation of major initiatives. You bridge the gap between what the CEO is trying to achieve and what the organization can actually execute. You're comfortable in chaos and good at unsticking stuck initiatives.
Executive: You're the organizational connector and representative. You know what's happening everywhere. You translate between the CEO and the organization. You're often the most visible CoS because you're in rooms across the company. People trust you as an extension of the CEO.
Your archetype determines what meetings you're in, who you spend time with, and how you create impact. The best advice I can give you: know your archetype. Own it. Don't try to be all four simultaneously — you'll dilute your impact and burn out.
What Your Calendar Actually Looks Like
Theory is useful. So is reality.
If you're a Chief of Staff, your calendar probably looks something like this: Leadership team meetings and one-on-ones. Strategy sessions and quarterly planning. CEO one-on-one (usually weekly). Board meetings and investor calls. Cross-functional working sessions where you're solving problems in real-time. Deep work blocks where you're actually thinking instead of reacting. Conversations across the organization where you're listening and connecting dots.
The percentage of time you spend on each varies dramatically by archetype and company. An Operations-focused CoS might spend 40% of their time on CEO operating rhythm and 30% on cross-org process work. A Strategy-focused CoS might spend 40% on deep thinking and 30% on leadership team engagement. An Executive-focused CoS might spend 30% just moving between the CEO and various departments.
But the baseline is the same: you're in the center of the organization, and information flows through you. You have one of the most informative vantage points in the company. That vantage point is your superpower — if you use it strategically instead of getting buried in reactive work.
Your calendar is not random. It's the visible representation of your role. If your calendar doesn't match your job description, you don't have a job description problem — you have an execution problem. And the fix is usually about boundary-setting, not a role redefinition.
Why Chief of Staff Roles Are Becoming Critical
I started my career when the Chief of Staff role was a rarity. Mostly found in military organizations and occasionally in mature corporations. Now? It's becoming standard in every growing company.
The reason is simple: the CEO's job has gotten too complex for one person to navigate alone.
You're dealing with increasing regulatory complexity. Artificial intelligence is reshaping how work gets done. Distributed teams make it harder to maintain organizational coherence. Board dynamics are more demanding. Investor expectations are higher. Employee expectations are different.
Meanwhile, the CEO is supposed to set strategy, maintain culture, nurture investor relationships, recruit and develop talent, make final decisions on critical issues, and stay sane.
That's not one job. That's three or four jobs packed into one title. The CEOs who survive are the ones who get smart help. And more and more, that help comes from a Chief of Staff who's doing the strategic thinking, building the operating system, and maintaining organizational coherence.
This role isn't going away. It's expanding. And the better you understand what it actually means, the more impact you can have.
Your Experience
You've probably experienced some of the confusion I described. I want to hear about your version of the role.
If you're a Chief of Staff: which of the four archetypes best describes your role? And do you feel like your CEO hired you explicitly for that archetype, or did you drift into it?
What's the most common misconception you encounter about what you do? How do you usually explain it to people outside the organization?
Looking at your calendar right now: what percentage of your time is spent on the three core functions (Strategic, Operational, Connective)? Is that distribution what you expected when you took the role?
If you're considering a Chief of Staff role: what questions would you ask in the interview to clarify which archetype the CEO actually needs?