How to build an operating rhythm

Every leadership team says it wants fewer meetings. Then a quarter goes badly, someone adds a weekly sync to "get visibility", and six months later the executives spend most of their week reporting on the business and little of it running the business.

This is how I'd build a rhythm that makes decisions: the layers, the one-page design, how to size it, the meeting templates, and how to tell if it's working. It goes deeper than the weekly template in our Chief of Staff handbook.

What is an operating rhythm?

An operating rhythm is the recurring schedule of meetings, reviews and written updates that turns a company's annual plan into weekly decisions. People also call it an operating cadence, a business rhythm or the rhythm of the business. Each layer looks at a different time horizon and should exist to make a specific kind of decision.

Jamie Dalton, a Chief of Staff at Adobe when we spoke, described this shape on our podcast about building operating rhythm from scratch: the annual operating plan breaks into quarterly commitments, then monthly or six-week cycles, then weekly check-ins, and the plan rolls forward a quarter at a time.

My take: judge the rhythm by the decisions its meetings are scheduled to make. If you can't name the decision a layer exists for, that layer is a reporting ritual, and it should probably be a written update.

Who owns what: the CEO or the Chief of Staff?

The CEO owns direction and the final call. The Chief of Staff owns the system that gets decisions made on time. Functional leaders own their goals, their numbers and the decisions inside their teams. When those lines blur, the CEO starts running agendas, or the Chief of Staff starts making calls nobody gave them.

Running the operating rhythm is one of the four core responsibilities of the role, and no functional leader owns the whole calendar. Under about 50 people, a founder or an ops lead can run two forums and a weekly note; a dedicated owner becomes hard to avoid between 100 and 200 people, when the leadership team can no longer see everything in one room.

Employers ask for this work more than anything else. Operating cadence tops the list in Chief of Staff postings in the Chief of Staff Network's 2026 Pathways Report, well ahead of strategy, communications and board work.

How do you build an operating rhythm from scratch?

Build it in six steps: take an inventory, name the decision for each layer, cut what has no decision, set the calendar a quarter ahead, publish it on one page, and review it after one quarter. Plan on four to six weeks for the first version, with your principal's backing.

Most Chiefs of Staff inherit something half-built, and it's usually overgrown: every problem got a meeting and nobody removed the old ones. Alexis Summit, Chief of Staff at Kroll (about 6,000 people) when we spoke, said on our podcast on resetting a company's operating rhythm that monthly CEO reviews plus separate meetings for every investment and launch left leaders without enough "time to actually run the business instead of reporting on it."

1. Take an inventory. List every recurring meeting, report and review your leadership team attends, with the hours each costs per leader per month. Shelby Sly started Ridgeline's reset here, with where managers, directors and executives were spending their time.
2. Name the decision for each layer. For annual, quarterly, monthly, weekly and async, write the one decision or output that layer must produce.
3. Cut, merge and convert. Remove any meeting that can't name its outcome, merge two that serve the same layer, and turn pure status meetings into written updates. Shelby called the first round the quick wins.
4. Set the calendar a quarter ahead. Fix board meetings, the quarterly review week, planning windows and the weekly leadership slot, sequenced so inputs flow upward: the weekly business review before the leadership meeting, monthly reviews before the quarterly one. Planning usually starts in the third quarter, and each quarterly review lands two to three weeks before the board meeting.
5. Publish it on one page: purpose, chair, owner, attendees, inputs due, decisions made and where the output goes, for each forum. The template below is that page.
6. Run it for a quarter, then hold a retro. Ask the leadership team what to keep, cut and change, change it once, and leave it alone until the next retro.

This week, pull your principal's recurring meetings for the next month and mark each one decision, status or relationship. The count of status meetings is your opening argument for a reset.

# Operating rhythm: [company], [year]

- Owner: [Chief of Staff] · Approved by: [principal] · Reviewed: end of each quarter

| Forum | Layer | Purpose (the decision it makes) | Chair | Owner (runs it) | Attendees | Inputs due | Output and where it goes | Frequency and length |
|-------|-------|---------------------------------|-------|-----------------|-----------|------------|--------------------------|----------------------|
| Annual planning | Annual | Strategy, annual goals, budget | CEO | Chief of Staff + finance | Leadership team | Function plans: [date] | Annual plan, budget, goals doc | Once a year, kicks off Q3 |
| Quarterly business review | Quarterly | Next quarter's priorities and trade-offs | CEO | Chief of Staff | Leadership team + team leads | Pre-reads 3 days before | Priorities, decisions, board deck inputs | Quarterly, 2 to 4 hours |
| Monthly performance review | Monthly | Resourcing and course corrections by function | Function leader | Chief of Staff | Function leader + their leads | Metrics frozen: [day] | Actions, escalations to leadership | Monthly, 60 to 90 min |
| Weekly business review | Weekly | Which reds need leadership help | Chief of Staff or COO | Chief of Staff | Metric owners | Data frozen: [day, time] | Escalations to the leadership meeting | Weekly, 45 min, day before leadership |
| Leadership team meeting | Weekly | 2 to 3 decisions, one strategic topic | CEO | Chief of Staff | Leadership team only | Pre-reads the day before, noon | Decision log + read-back same day | Weekly, 60 to 90 min |
| Leader's weekly note | Async | Shared context without a meeting | CEO | Chief of Staff drafts | Whole company or org | Inputs from leaders: [day] | Sent [Friday] | Weekly, written |

## Rules
- Every forum names the decision it exists for. No decision, no meeting.
- Inputs flow up: weekly before monthly before quarterly.
- Change the rhythm once a quarter, at the retro.

The template comes pre-filled with six standard forums. Delete the ones you don't need before you add any.

A worked example: the inventory and the cut

Here's an illustration of steps 1 to 3 at a 200-person company with eight leaders. The inventory finds 23 recurring forums plus four weekly reports: about 14 hours a week per leader in recurring meetings and three more preparing reports.

Seven forums make a real decision: the leadership meeting, the monthly metrics review, two hiring committees, a pricing council, the product roadmap review and quarterly planning. Nine are pure status, including three launch syncs for launches that shipped. Seven are relationship meetings, mostly one-to-ones, which the reset leaves alone.

The first round cuts the three dead launch syncs, merges two overlapping product reviews, and turns four status meetings into a written Friday update per function. That leaves 17 forums and about 10 hours a week per leader. No decision moves to a worse forum, and four hours a week go back to running teams.

Judgment calls in the reset

If the CEO likes a meeting that's pure status, don't propose killing it. Propose a four-week trial with a written version, and let the CEO judge whether anything was lost. Cut the obviously dead meetings in week one, and wait on anything with a senior owner until you've talked to them. A recurring meeting is often how a leader stays visible to the CEO, so offer them a slot in the written update or a standing item on the leadership agenda.

Cutting status meetings creates an information gap for about a month. If the written updates arrive late or thin, someone will propose a new sync, and you're back where you started. Chase the first four updates personally, then adopt a one-in, one-out rule: any new recurring forum names the one it replaces. Don't launch with a big announcement either; change two forums, show they save time, then change the rest.

A functional Chief of Staff, say to a CTO, can only reset the function's forums, so mark which meetings the company owns. A remote company needs fewer live forums and stricter written ones. Ben Darfler, Chief of Staff at Honeycomb, described the end state on our podcast: strategy actions mapped almost one-to-one onto annual goals, team goals tied to those, and metrics reviews every week or two. Our OKR vs KPI guide covers the goal side.

If you'd rather react to a first draft than start from the template, paste this prompt into your AI tool with your own details. Treat the output as a draft to take to your principal; the tool doesn't know which leader will skip the new Monday meeting.

You are an experienced Chief of Staff. Help me design an operating rhythm.

Context:
- Company: [stage, headcount, remote/hybrid/in-office, time zones]
- My principal: [title] and their direct reports: [list roles]
- Current recurring meetings: [name, frequency, attendees, length, what it's for]
- Planning and goals today: [annual plan? OKRs? KPIs? board meeting dates?]
- Biggest pain: [e.g. decisions stall, too many meetings, surprises at quarter end]

Do this:
1. Map my current meetings onto five layers: annual, quarterly, monthly, weekly, async. Flag gaps and overlaps.
2. For each layer, name the one decision or output it should produce.
3. Propose a new rhythm: forums to keep, cut, merge or convert to written updates, with frequency, length, owner and attendees.
4. Sequence it so inputs flow upward (weekly before monthly before quarterly).
5. Estimate hours per month for each leader before and after.
6. List the 3 changes I should make first, and how I'd explain them to my principal.
Ask me up to 5 questions first if anything important is missing.

How do you size an operating rhythm for your company?

Design the rhythm for the company you are now and for the next doubling. A 50-person startup needs two or three forums and a strong written habit. A 2,000-person company needs layered reviews where each level filters what goes up to the next.

A rhythm designed for 30 people breaks at 300. Shelby Sly, Chief of Staff at Ridgeline, explained on her episode about moving from meeting-heavy to async that a biweekly all-staff worked when everyone fit in one room, and stopped scaling as the company grew from about 200 to more than 450 people. Three things change as you move right across the table.

The number of filters grows. At 2,000 people, each layer decides what goes up and what stays down. After Kroll moved to two business units, Alexis Summit's 11 service line leaders kept monthly performance meetings, while CEO reviews moved from monthly to quarterly deep dives on each business, with leadership committees on sales, technology and employee experience meeting monthly in between.

Rooms get smaller. Jamie Dalton ran Adobe's quarterly business reviews as open sessions, but her steering committees, every four to six weeks, were a limited group with a set agenda and an expected outcome; everyone else got the output. And more runs on writing: at Ridgeline, Shelby's leader started a Friday note to the whole company, and decision meetings required a one-pager in advance. [SCOTT: one line on how the rhythm worked at Spring, e.g. how board prep set the quarter's cadence?]

If you're a fractional Chief of Staff or the first operator at a small company, resist building the 2,000-person version. I also wouldn't run a daily leadership standup above about 50 people: at that size a daily status call takes leaders away from running their teams, so use a written async update for the daily layer.

How do you run a leadership team meeting that makes decisions?

The CEO chairs the leadership team meeting, and the Chief of Staff runs everything around the chair: the agenda, the pre-reads, the clock and the read-back. The agenda, notes and follow-up templates are in our meetings guide.

Run the meeting on decisions and shared goals, and keep departmental updates in writing. Jamie Dalton replies to any invite without context by asking for the objective and the agenda, and a leadership meeting that can't answer those two questions shouldn't happen that week. The structure I recommend has five parts:

1. Open actions, exceptions only. Call out what's late or blocked, without walking the whole list.
2. The scorecard, reds only. The weekly business review already covered the numbers.
3. Two or three decisions, each with a one-page pre-read: the question, the options, a recommendation, and who must agree.
4. One strategic topic: something that won't be urgent until it's too late, such as a hiring plan or a pricing risk.
5. Read-back. In the last five minutes, the Chief of Staff reads out the decisions, owners and dates, and anyone who disagrees with the record says so now.

Decisions go first because attention runs down over an hour. Whatever sits last gets cut when the meeting runs over, so put status there, where it's safe to drop because it's already in writing. Invite only the people who make or block the decisions on the agenda; the Chief of Staff usually holds that line, because when the CEO removes someone, it reads as a judgment on the person.

Round-robin updates are the clearest sign a meeting has no decision attached. Jamie Lynn White, Chief of Staff for marketing at Notion when we spoke, told me on our podcast about systems thinking that she never runs them, because they reinforce siloed thinking; her agendas are built around company goals and the programs that serve them.

One decision, start to finish

Here's an illustration of a single decision through one weekly cycle at a 300-person company.

1. Thursday: the Chief of Staff pre-wires. The question is whether to delay a product launch by three weeks to fix an onboarding problem. She talks to the heads of product, sales and customer success one to one. Sales is against it, because two big deals were promised the launch date.
2. Friday: the one-page pre-read goes out. The question, two options, a recommendation (delay two weeks and ship the fix behind a flag), and sales' concern stated in sales' own words, which the head of sales has checked.
3. Monday, 25 minutes into the meeting: ten minutes on this decision. The head of sales proposes calling both customers personally. The CEO agrees to the two-week delay on that condition.
4. Monday, last five minutes: the read-back. "Launch moves to the 24th. Product owns the fix by the 20th. Sales calls both customers by Wednesday. Revisit if the fix slips past the 20th."
5. Monday, within two hours: the line goes into the decision log and out to the leadership team.

It works because sales' objection was heard on Thursday, and because the read-back gave the CEO's condition an owner and a date.

When the answer changes

A functional Chief of Staff runs the same structure for their principal's staff meeting, plus a standing slot for what the function needs from the company's leadership meeting. A hybrid or remote team should hold the read-back in writing, in the meeting channel, before people drop off. A leadership team of four or five can skip the scorecard section.

When your CEO goes off the agenda in week two, don't fight it in the room. Note the topic, give it a slot next week with a pre-read, and ask your principal whether it should replace something. A CEO who sees the agenda absorb their urgent topics stops working around it.

# Leadership team meeting: [date]

- Owner: [Chief of Staff] · Chair: [principal] · 60 minutes
- Pre-reads due: [day before, 12:00] · Notes and decisions sent: same day

## 1. Open actions: exceptions only (5 min)
- [Action] · [owner] · was due [date] · status: late / blocked / needs help

## 2. Scorecard: reds only (10 min)
- [Metric] · target [x] · actual [y] · owner explains: cause, fix, help needed

## 3. Decisions (30 min)
### Decision 1: [the question, phrased as a yes/no or a choice]
- Pre-read: [link] · Recommender: [name]
- Options: A / B / C · Recommendation: [ ]
- Must agree: [names] · Informed after: [teams]
### Decision 2: [ ]

## 4. One strategic topic (10 min)
- [Topic] · Why now: [ ] · What we need from this group: [input / direction / owner]

## 5. Read-back (5 min)
| Decision | Owner | Due | Who tells whom |
| --- | --- | --- | --- |
| | | | |

Not on this agenda: department status updates. Those go in the written weekly update.

# Leadership team meeting: Monday, June 1

- Owner: Chief of Staff · Chair: CEO · 60 minutes
- Pre-reads due: Friday, 12:00 · Notes and decisions sent: same day

## 1. Open actions: exceptions only (5 min)
- Pricing page copy · Head of Marketing · was due May 27 · status: blocked on legal review

## 2. Scorecard: reds only (10 min)
- Trial-to-paid conversion · target 18% · actual 14% · Head of Product: drop-off at onboarding step 3; the fix is decision 1

## 3. Decisions (30 min)
### Decision 1: Delay the June 10 launch to fix onboarding?
- Pre-read: one page, sent Friday · Recommender: Head of Product
- Options: ship on the 10th / delay two weeks, fix behind a flag / delay three weeks · Recommendation: delay two weeks
- Must agree: Heads of Product, Sales and Customer Success · Informed after: account executives, support
### Decision 2: Start Q3 planning on July 6?
- Pre-read: planning calendar · Recommender: Chief of Staff
- Options: July 6 / July 20 · Recommendation: July 6, so the plan is set before the August 19 board meeting
- Must agree: CFO · Informed after: all team leads

## 4. One strategic topic (10 min)
- Support hiring for the enterprise tier · Why now: two enterprise deals close in Q3 · What we need from this group: an owner for the hiring plan

## 5. Read-back (5 min)
| Decision | Owner | Due | Who tells whom |
| --- | --- | --- | --- |
| Launch moves to the 24th | Head of Product | Fix by the 20th | Head of Sales calls both customers by Wednesday |
| Q3 planning starts July 6 | Chief of Staff | Templates out June 22 | Chief of Staff emails all team leads today |
| Enterprise support hiring plan | Head of Customer Success | Draft by June 15 | Brings it to this meeting |

If the meeting still runs over, move one decision to a smaller group with a deadline and report the result next week.

This week, rewrite next week's leadership agenda so the first item is a decision, and send the read-back within two hours of the meeting ending.

How do you get leaders aligned before a decision?

Build alignment before the meeting. Talk to every key stakeholder one-to-one before a contested decision, send a one-page pre-read, ask each leader to name what must be true for the plan to work, and log the decision the same day so nobody can reopen it in week three without a reason.

You've seen the pattern: every executive nods at the kickoff, and by week three engineering says the date assumed people it doesn't have and finance hasn't released the budget. Nobody wants to slow things down in a room full of peers, so the objections exist on day one and don't get said. Shelby Sly connects one-to-one with each attendee before a decision meeting, even if only over Slack, to understand where they stand.

Pre-wire, test, log

Before any decision that affects more than one leader, have the one-to-one conversations, then send the one-pager with the question, options, recommendation and trade-offs. If a leader's concern changes the recommendation, change it before the meeting. Our post on data-driven decision-making covers the evidence side of a good pre-read.

Before the group commits, ask each leader for two lines: the one thing that has to be true for this to work, and the one thing that would make them want to stop it. If someone says "sounds good", ask for the two lines anyway. Then log the decision the same day: what, why, owner, who disagreed and what would make you revisit it. When someone tries to reopen it later, you point to the revisit trigger.

Talk to each leader one to one before a contested decision reaches the room.

Judgment calls on pre-wiring

If the meeting only rubber-stamps what you settled in private, the people you didn't call feel the decision was made around them. Talk to everyone the decision affects, including the leader you expect to agree, and bring the strongest disagreement into the room in its owner's words.

When a leader won't engage beforehand, send the pre-read with one question, "What would make you vote against this?", and a deadline. If they object in the room anyway, log it as a late objection; after two or three, it's a pattern your principal should raise. CEOs often need pre-wiring most, because one offhand reaction can sink a recommendation. If yours has already decided, say so in the pre-read, because a decision dressed up as a debate teaches leaders the meeting is theatre. By month three, leaders start pre-wiring each other without you.

# Decision log: [team or program]

- Owner: [Chief of Staff] · Updated: same day as each decision

| # | Date | Decision (one sentence) | Options considered | Why this one | Owner | Due | Must-be-true | Disagreed (and commits?) | Revisit if | Status |
|---|------|------------------------|--------------------|--------------|-------|-----|--------------|--------------------------|-----------|--------|
| 1 | | | | | | | | | | Open / Done / Reopened |

## Rules
- A decision is logged within 24 hours or it isn't a decision.
- Every row names one person as owner.
- "Revisit if" is a condition, e.g. "pipeline below $X by week 6".
- Reopening a decision needs the revisit condition to be met, or the principal's call.

# Decision log: leadership team

- Owner: Chief of Staff · Updated: same day as each decision

| # | Date | Decision (one sentence) | Options considered | Why this one | Owner | Due | Must-be-true | Disagreed (and commits?) | Revisit if | Status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 15 | Jun 1 | Q3 planning starts July 6 | July 6; July 20 | The plan is set before the August 19 board meeting | Chief of Staff | Jul 6 | Finance closes H1 actuals by July 2 | None | The board date moves | Open |
| 14 | Jun 1 | The launch moves from June 10 to June 24, with the onboarding fix behind a flag | Ship on time; delay two weeks; delay three weeks | Fixes the step 3 drop-off without losing two promised deals | Head of Product | Jun 20 | Sales reaches both customers by Wednesday | Head of Sales (commits, on the condition she calls both customers) | The fix slips past June 20 | Open |
| 13 | May 18 | New mid-market deals sign annual contracts only | Annual only; monthly and annual | Cash runway for H2 | VP of Sales | Jun 1 | Discounts stay at 15% or less | Head of Customer Success (commits) | Mid-market win rate under 20% for a full month | Done |

Over a year, the log is the best evidence of how the leadership team decides, which is useful when you hire a Chief of Staff and need to show them how decisions get made. Our guide to context management covers keeping it searchable.

What should a weekly business review cover?

A weekly business review is a 30 to 60 minute look at the same small set of metrics every week, presented by the people who own them. It should cover where each metric is against target, why the reds are red, what the owner is doing about it, and what needs leadership help. Keep it separate from the leadership meeting, and keep slides out of it.

When the same eight to fifteen numbers appear in the same order every week, leaders start to see patterns, such as a lead indicator that always dips before a bad month. Three rules keep it honest: the metric's owner explains the variance, even if an analyst built the chart; green metrics get no airtime; and every red ends in a fix with a date or an escalation to the leadership meeting.

Hold it a day before the leadership meeting, so the leadership agenda pulls only the reds that need a decision. Our OKR vs KPI guide separates weekly KPIs from quarterly goals and has a scorecard to copy, and our post on tracking KPIs and benchmarking goes deeper on measurement.

# Weekly business review: week of [date]

- Owner: [Chief of Staff] · 45 minutes · Day before the leadership meeting
- Data frozen: [day, time] · Pre-read sent: [day, time]

## Scorecard
Same 8 to 12 metrics, same order, every week. Use your weekly KPI scorecard; paste only the reds and ambers below.

## Reds and ambers (owner explains)
### [Metric]
- What happened: [ ]
- Why: [root cause]
- Fix and date: [ ]
- Help needed from leadership: [none / decision / resources]

## Escalations to the leadership meeting
- [Decision needed] · Owner: [ ] · One-pager: [link]

## Watch list (not red yet)
- [Lead indicator moving the wrong way]

If you can't fill the scorecard from your systems in under an hour each week, fix the data before you add the meeting. A review that runs on numbers rebuilt by hand on Monday morning trains everyone to distrust them.

How do you run a quarterly business review?

A quarterly business review compares what each team committed to with what it delivered, explains the misses, and agrees on next quarter's priorities and trade-offs. Send a written pre-read two to three days before, use the meeting for discussion and decisions, and look two quarters ahead.

At Adobe, Jamie Dalton's teams report against last quarter's commitments (delivered, or not delivered and why), then look two quarters out. At Kroll, Alexis Summit's team runs deep dives on each of 11 businesses that roll up into a shorter review with the CEO. The common mistake is a 60-slide deck presented live; put the numbers in the pre-read and spend the meeting on three or four decisions. Our post on implementing QBRs and OKRs covers the goal side.

If your principal reports to a board, land the QBR two to three weeks before the board meeting, so the deck is built from decisions already made. The fourth-quarter review feeds next year's plan; our post on why annual planning and budgeting is hard for midsize companies covers that side.

# QBR pre-read: [team / business unit], Q[ ] [year]

- Owner: [team lead] · Due to Chief of Staff: [date, 3 days before] · Max 3 pages

## 1. Headline (3 sentences)
What we committed, what we delivered, the one thing leadership should know.

## 2. Commitments vs delivery
| Commitment last quarter | Delivered? (Yes / Partly / No) | If not, why | What we learned |
|-------------------------|--------------------------------|-------------|-----------------|
| | | | |

## 3. Metrics
| Metric | Target | Actual | Trend | Comment |
|--------|--------|--------|-------|---------|
| | | | | |

## 4. Next quarter: our 3 priorities
1. [Priority] · Success looks like: [measurable] · Owner: [ ]
2. [Priority] · Success looks like: [measurable] · Owner: [ ]
3. [Priority] · Success looks like: [measurable] · Owner: [ ]

## 5. Two quarters out
- What we expect to need, start or stop by then: [ ]

## 6. Risks and dependencies
- [Risk] · Likelihood / impact · Who we depend on: [team]

## 7. Decisions and asks for leadership
- [Decision or resource ask] · Options · Our recommendation

The QBR tests the whole rhythm. If the weekly and monthly layers work, nothing in it should surprise the leadership team.

How is AI changing the operating rhythm?

AI is taking over the collection work of the rhythm: notes, update roll-ups and first drafts of pre-reads. The judgment stays human: what goes on the agenda, how a decision is framed, and the one-to-one conversations that make alignment real.

Jamie Lynn White built an agent at Notion that collated team documents, workstreams and Slack threads into one update per program, so the roll-up that took hours of chasing arrived as a draft. Your company will set limits: security, compliance and ethical concerns were the most common barrier to AI adoption, cited in about 41% of responses, according to the Chief of Staff Network's Chief of AI Report (2025). Check the policy before you point a tool at board materials, and see our guide to AI and the Chief of Staff.

My take: fix the design before you automate anything. An AI summary of a meeting that made no decisions arrives faster and still contains no decisions.

How do you know your operating rhythm is working?

Measure the rhythm like any other system: count the decisions it produces, how fast they happen, how reliably actions close, and how much leadership time it costs. Review those numbers once a quarter in a short retro with the leadership team, and change the rhythm only when the data or the company's shape says so.

These thresholds are my judgment; set your own after the first quarter. Report one number to your principal every quarter: 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.

In the quarterly retro, ask three questions: which forum helped you decide something, which could you have skipped, and where did you hear something too late? Change no more than two things each time, as Shelby Sly did at Ridgeline over several quarters. Save big resets for big changes, such as a reorg or a new CEO, as Alexis Summit did when Kroll moved to two business units.

The test I care about most is a week off. If agendas still go out and the weekly review still runs, you've built a system; if it stops, you've built a dependency on yourself, which limits your next step too.

Take a week off: if agendas still go out, the decision log stays current and the weekly review still runs, the rhythm works without you.

This week, start a tracker with the six signals above, fill in this week's numbers, and put a 30-minute rhythm retro on the leadership calendar for the last week of the quarter.