What Does a Chief of Staff Do? Scope, Decision Rights, and When to Hire One

Chief of Staff is the least standardized title in the C-suite. Three companies can advertise the same role and be hiring three different people for three different reasons. That is why so many of these searches stall: the panel is not disagreeing about candidates, it is disagreeing about the job.

This guide is for the executive or board member about to open one. It covers what the role owns, the three versions in circulation, how to tell which one you need, and when a chief of staff is the wrong answer entirely.

What does a chief of staff do?

A chief of staff extends the capacity of a single executive, usually the CEO, by owning the operating system around them: the leadership meeting, the decision log, the follow through, and the information that reaches the principal's desk.

That is the common core. Everything else varies.

In practice the job is defined by two questions. What does this person decide without the principal in the room? And what reaches the principal only after passing through them? A chief of staff with real answers to both is a force multiplier. One with neither is an expensive coordinator, and good candidates work that out in the first interview.

The role is not an assistant, and it is not a deputy. An assistant manages the principal's time. A deputy can act in the principal's place with full authority. A chief of staff sits between those, holding process authority without line authority over the business.

What are the three versions of the role?

There are three patterns, and they do not share a candidate pool.

The operator. Owns the cadence. Runs the leadership meeting, sets the agenda, records what was decided, chases the owners of each decision until it closes. Success looks like decisions closing faster and fewer things falling between functions. Candidates come from operations, program management, or a business operations team.

The strategist. Sits in on everything, synthesizes, and writes the document that frames the quarter. No standing operational duties. Success looks like better framed choices reaching the leadership team. Candidates come from consulting, corporate development, or strategy.

The apprentice. A rotational seat created for a specific high performer being prepared to run a business unit. The role exists because of the person. Success is the person's next promotion. Candidates are almost always internal.

All three are legitimate. The failure is writing one job description that blends all three, because each interviewer then evaluates against whichever version they personally had in mind, and the debrief becomes an argument about the role rather than about the person in front of them.

How do I work out which one I need?

Start from the bottleneck, not the title.

Write down the last ten things that took longer than they should have at the leadership level. Then sort them. If most are decisions that were made but never executed, or work that stalled at a handoff between two functions, you need the operator. If most are decisions that were never properly framed, where the team went round the same question three times without a clear set of options, you need the strategist.

If the list does not separate cleanly, the honest reading is usually that you have an operator problem and a strategy problem, and hiring one person for both will get you a slower version of each. In that case the operator is almost always the higher leverage first hire, because an unexecuted decision costs more than an unframed one.

The apprentice version should be a deliberate development decision with a named person and a target seat, not a search. If you are running an external search for it, you are not doing the apprentice version.

What should the job description actually say?

Three things, before anything else.

The decision rights. Name what this person can decide alone. Meeting agendas, the format and deadline of the leadership update, which items reach the principal's desk and in what shape. If you cannot fill this in, stop and fix that before posting.

The escalation path. What happens when a functional leader disagrees with the chief of staff. If the answer is that the principal adjudicates every time, the role will not work, because the whole point is to reduce what reaches the principal.

The outcomes for the first year, in plain language, ideally with a date attached. Not "improve leadership alignment" but something a reasonable person could later agree was or was not achieved.

Write those first. The list of responsibilities almost writes itself afterward, and the interview panel finally has something to interview against.

Who should the chief of staff report to?

The principal, directly, with no dotted line into a function.

A chief of staff who reports to the COO or the head of strategy inherits that function's agenda, and the role stops being about the principal's capacity. The seniority of the title then works against you: functional leaders read it as a peer trying to direct them on someone else's behalf.

The person should also sit in the leadership meeting as a participant rather than a note taker. A chief of staff who is only allowed to record is not able to close decisions, and the role degrades into administration within two quarters.

How do you evaluate candidates for a role this fluid?

Interview for judgment under ambiguity, not for the resume pattern.

Two questions do most of the work. First: describe a decision your principal made that you disagreed with, and what you did. A strong answer involves having pushed privately, then executed properly, and being specific about both. A weak answer is either total deference or a story about being right.

Second: describe something that failed on your watch because a handoff broke. Anyone who has genuinely run an operating cadence has one of these and can name where the seam was. Anyone who cannot is describing a role they observed rather than held.

Be careful with candidates whose only experience is the strategist version if you are hiring the operator. The skills look adjacent on paper and are not. Framing a choice well and dragging thirty decisions to closure across a resistant leadership team are different capabilities.

When is a chief of staff the wrong hire?

Three situations.

When the real problem is a missing functional leader. If the leadership team has a hole where the head of operations or the CFO should be, a chief of staff will spend the year absorbing that gap and will leave without having done their own job.

When the principal will not delegate. The role only functions if things genuinely stop reaching the principal. If they intend to keep reading everything, the hire adds a layer rather than removing one.

When the role has no decision rights. Then it is a coordinator, and titling it Chief of Staff will cost you the candidates you wanted while setting up a title correction inside a year.

Frequently Asked Questions

Is a chief of staff the same as a COO?

No. A COO owns operational functions and the people in them, with line authority and a budget. A chief of staff owns process and information flow around one executive, without line authority over the business. Some chiefs of staff later become COOs, which is part of why the titles get confused. For the operating role, see what a COO does.

How long do people stay in the role?

It is usually a two to three year seat by design rather than a career destination, and the strongest candidates will ask what comes next. Have an answer. A chief of staff search with no articulated next step filters out exactly the ambitious operators you were hoping to attract.

Should the chief of staff be an internal promotion or an external hire?

Internal works well for the apprentice version and for the operator version in a company with deep institutional knowledge to navigate. External works better when you need process discipline the organization has never had, because an insider is often too invested in the current cadence to replace it.

Do we need to pay executive compensation for this?

Compensation should match the decision rights, not the title. A chief of staff with genuine authority over the leadership operating system and direct access to the principal prices near the senior director or vice president band in most markets. Pricing the title without the authority is how these roles get filled by people who leave.

How do we know if it worked?

Ask the leadership team, after two quarters, whether decisions are closing faster and whether fewer things are stuck at handoffs. That is the whole job. If the answer is no, the problem is usually the decision rights rather than the person.

Getting the scope right before you search

Most failed chief of staff searches were scoped wrong rather than sourced wrong. The candidate pool for each of the three versions is deep. What is scarce is a company that has decided which version it is hiring.

Engaged Headhunters runs executive search across healthcare, technology, finance and manufacturing, and calibration comes before sourcing on every mandate. In practice that means the first conversation is about the bottleneck rather than the title, and the shortlist gets built against decision rights you have actually written down.

If you are working out which version of this role you need, that conversation is worth having before the job description is written. Call (757) 720-7173 or start the scoping call.