Run the cadence without becoming the place where all the status lives.
A Chief of Staff usually inherits the operating rhythm before anyone writes it down: the planning session, the weekly leadership meeting, the follow-up that makes decisions stick. The accountability is real and the authority is borrowed, so most of the work gets done by chasing. The risk is becoming the system yourself, because a cadence that only runs when you push it does not survive your next role.
What goes wrong from this seat
You are the system
The rhythm holds because you remember it. You know which owner is behind, which number was rounded up, which decision was actually made in the hallway afterwards. That is valuable, and it is fragile, because none of it is written anywhere your successor could read. The test is a two-week absence: if planning slips, the weekly meeting turns into a status round, and follow-ups stop, the cadence was you rather than a process.
The Sunday night status tax
Every leadership meeting is preceded by a round of direct messages asking for a number that already exists somewhere. You copy it into a deck, and by Tuesday the deck is the source of truth while the real number has moved. Hours go into assembly rather than the judgment you were hired for, and the executives read a version of reality that you, not the owner, are now responsible for.
Decisions with no paper trail
The room agrees, everyone leaves, and three weeks later two functions are working from different versions of what was decided. You end up relitigating instead of executing. A decision log costs one line per decision, recording what was decided, who owns it, and when it gets reviewed. It is the cheapest leverage in the role, because it converts your recall into something the company owns.
The meeting that reports instead of deciding
Ninety minutes of each function narrating its week, with the two items that actually needed a decision squeezed into the last five. The people who could have unblocked something spent the hour listening politely. Status belongs in writing, read before the room meets. The meeting's job is the small number of things that are off track and the decisions nobody can make alone.
What to look at, and how often
Framework-neutral. Whether you run OKRs, Scaling Up or 4DX, the rhythm below is the part that most often gets dropped.
| When | What |
|---|---|
| Weekly | Publish the numbers and the agenda before the leadership meeting rather than during it. Afterwards, write every decision and action with an owner and a date, and circulate the same day while the room still agrees on what happened. |
| Monthly | Audit follow-through, not intent. What share of last month's actions actually closed, and which owner keeps carrying items forward? The pattern across owners is the finding; a single slipped item is not. |
| Quarterly | Run the planning session and protect the cut: a short list, named owners, and an explicit not-doing list. Score the previous quarter first, before anyone starts advocating for what they want next. |
| Annually | Write the calendar. Lock the planning dates, the review dates, and the meeting structure for the year, so the rhythm is something the company scheduled rather than something you chase. |