Excel in the role

What should a new Chief of Staff do first: the mandate, the operating rhythm or the weekly update?

Start the weekly update first, in your second week. Then write the mandate, then take over part of the operating rhythm. You won't have much to report yet, but the decisions section works from day one, and the habit is easier to start than to introduce later.

Draft the mandate yourself at the end of week 3, after you have met the leaders your principal works with. Agree it with your principal in one 60-minute session in week 4. In month two, take over one part of the rhythm end to end, usually the leadership team meeting, and pick one metric you own. By day 60, people should know what you own.

Hold a full rhythm reset until you have listened. A first version takes four to six weeks and needs your principal's backing. If you are the second Chief of Staff in the seat, read your predecessor's notes, then run your own listening tour and agree your own mandate. Our first 90 days plan puts all three on one calendar.

How do you stop a Chief of Staff role from turning into "chief of stuff"?

Write down what the role won't do, and route every new request against that list. A new Chief of Staff often says yes to everything, each favor becomes a standing task, and by month six the role is a pile of inherited work nobody would have designed.

The fix is the Not own list in your mandate, with an owner named for every item: calendar and travel (the executive assistant), expenses (finance). Then run each request through a scope check. Which responsibility does it belong to, which outcome does it serve, and who owns it after you? Take what fits. Route work that belongs to a slow team to its owner and unblock them. Take important work with no owner only with an exit date and a named next owner.

Keep it visible. List new requests in the scope check line of your weekly update, so the next mandate review runs on evidence. Taraneh Ansari, who moved from HR into the role at OpenSponsorship, summed up the early-stage ethos as "nothing is not my job". Even a generalist needs a short list of what they won't own.

How do you go from executor to strategic partner as a Chief of Staff?

Get into decisions before they are made, with a view, and get your decision rights in writing. Many Chiefs of Staff are trusted to make everything work and are still called operational. Part of the reason is timing: if your principal mostly sees you after decisions, carrying them out, that becomes your reputation. David Kirby, former Chief of Staff at Ford, calls this the doer trap. The way out is to move from doing the work to orchestrating it.

Two habits change what your principal sees. In your weekly update, attach a recommendation to every decision you ask for, which turns a status report into judgment. In your mandate, fill the Decide list, the decisions you make alone: a mandate with an empty Decide list describes a coordinator, however senior the title. If your principal won't grant one, ask for one decision for 30 days and review it together.

Then hand off the steady machinery. Take a week off as a test: if agendas still go out and the weekly review still runs, you have built a system, not a dependency on yourself.

Should a Chief of Staff stay and grow the role or leave for a bigger one?

The data favors staying, if your principal will grow the role with you. In the Chief of Staff Network's Pathways Report, 61% of Chiefs of Staff step up when they stay at the same company, against 48% when they leave. About 8% of completed stints end with a bigger Chief of Staff title at the same company. And 37% of Chiefs of Staff want to stay and expand their role, according to the Chief of Staff Network's 2025 Salary Report (nearly 500 respondents).

Growth in place rarely happens by default. Bring your principal a rewritten mandate: what you own today against the original page, fewer doing items and more decision rights, the support you need, and a level and a date. Bring it a month before the annual review, with a year of weekly updates as your record.

Your principal's answer decides it. If the answer is "not this year" twice, treat that as information about their choice, and make yours. Timing matters too. The Pathways Report puts the median stint at 20 months, and those who leave inside a year are the least likely to step up next (38%, against 57% at two to three years).

How do you measure a Chief of Staff's impact when the role has no clear metrics?

Measure outcomes you agreed in advance, and keep a written record of the rest. Your mandate names three outcomes for the next six months, each with a measure, such as "annual planning closes on time with an owner for every priority". From month two, also own one metric your principal watches that nobody owns today, such as time to a hiring decision.

Measure the operating rhythm like any other system: decisions per leadership meeting, pre-reads sent on time, actions closed, decisions reopened, leader hours in recurring meetings, and surprises at the quarterly review. Each quarter, report leadership hours in recurring meetings next to the decisions made. If hours fall while decisions hold steady, the rhythm is handing executive time back to the business.

Your weekly updates supply the record. Once a quarter, pull the outcomes, the risks you caught and the decisions you shaped into a one-page recap. Put a return next to each item where you can name one: hours your principal got back, a decision closed a week earlier, a renewal protected.

How should a Chief of Staff's operating rhythm change as the company grows?

What you rank first, and how much structure you build, change with company size and with your principal. A startup CEO's Chief of Staff usually ranks cross-functional projects first, a functional executive's Chief of Staff the operating rhythm, and an investor's Chief of Staff priorities and decisions.

The rhythm changes most. At about 50 people, a goal reset each quarter, one leadership meeting for decisions only and a founder's weekly note are enough. At about 200 people, add a monthly metrics review and a weekly business review. At about 2,000, each layer filters what goes up to the next, rooms get smaller and more runs on writing. A dedicated owner becomes hard to avoid between 100 and 200 people. At a small company, don't build the 2,000-person version.

At a startup the mandate changes fastest, so it often needs a quarterly review. In a functional role, such as Chief of Staff to a CTO, you can only reset the function's forums. A remote company needs fewer live forums and stricter written ones. Our guide shows how to size an operating rhythm for each stage.

How much decision-making authority should a Chief of Staff have?

As much as your principal will put in writing, and more as your level rises. Decision rights come in three tiers: Decide (you decide alone), Recommend (you shape it, your principal decides) and Not own (another owner, named). The Decide list is where your principal gets hours back. If leaders can't find your decision rights in writing, expect them to check every call you make with your principal.

Your level sets the size of the list. An Associate-level role might have two or three Decide items, mostly about process. A Director should decide the leadership agenda, the calendar and which requests reach the principal. At VP level and above, some company decisions move into Decide, such as a cross-team trade-off when the principal is away.

The limits matter as much. In the operating rhythm, the CEO keeps the final call, and the Chief of Staff owns the system that gets decisions made on time, not the decisions, unless the mandate says so. And don't ask for decisions in your weekly update that your mandate already lets you make. Our guide covers decision rights in the mandate.