What a chief of staff actually does in their first ninety days

Most chief of staff hires arrive thinking the role is calendar management, that the CEO needs someone to triage their inbox, run the executive ops cadence, and shield them from the things only the CEO should be doing. That part of the job is real. It's also the smallest part.

The job, in the first ninety days, is mapping the decision flow. Where do calls actually get made? Which meetings produce decisions, and which produce the appearance of decisions? Where does context die between functions, and where does it stay alive long enough to inform the next call? The CEO has a fragmented view of this, they only see the rooms they're in. The COS gets to see all of the rooms, and that's the leverage.

The first thing most COSes find is that the org has more decision-shaped meetings than decisions. The leadership sync that runs every Monday produces alignment on three things and re-litigates the same two open questions every week. The exec all-hands that runs every other Thursday is more recap than decision. The roadmap review, the strategy sync, the cross-functional escalation, they all happen, they all consume hours, and the rate at which actual decisions emerge is lower than the calendar makes it look.

The temptation, fresh into the role, is to cancel meetings. It's the wrong move, even when the meetings deserve to be cancelled. Cancel a meeting and the work it was holding doesn't go away; it just scatters into DMs and one-off pulls on the CEO's time, which is the thing you were hired to prevent.

The better move is to change what the meetings produce. The leadership sync stops being a status report and becomes the place where async decision threads get closed. The roadmap review opens with the four themes already surfaced from the team, not from the room. The exec all-hands moves from recap to forward-looking, because the recap landed in writing the day before.

What this requires is infrastructure the COS has to build. Some of it is a system, a place where async input gets collected before the meeting starts, where decision trails get captured so the rationale isn't lost in DMs three weeks later, where the synthesized overview lands in the calendar invite that the executive is going to open anyway. Some of it is cultural, getting the leadership team to weigh in async before the synchronous slot, which always feels harder the first time and lighter the third.

By day ninety, the COS who's done the job right has not made themselves indispensable. They've made the system around them sturdier. The CEO's calendar is not lighter because the COS is in the meetings; it's lighter because the meetings are decisions, not context-gathering. That's the work.