LeadershipIntermediate6 min read

Leadership Team Rituals

Leadership team rituals are the recurring practices — beyond the weekly e-staff meeting — that create the operating rhythm of the executive team. Examples: monthly business reviews, quarterly strategy days, weekly metrics standups, biweekly 1:1s between every VP pair, monthly customer empathy sessions, weekly written CEO update to leadership. The rituals collectively form the 'operating cadence' of the company. Done well, they create predictable rhythm where decisions surface, get debated, and resolve at known cadences (no one wonders 'when do we decide pricing?'). Done poorly, they pile up as ceremonial overhead — every ritual was a good idea once, none have been killed, and the leadership team is in 18 hours of recurring meetings per week. The KnowMBA position: rituals require explicit lifecycle management. Every ritual should have an owner, a stated purpose, and an annual sunset review.

Also known asOperating CadenceLeadership RhythmsTeam Cadence ArchitectureRituals & Ceremonies

Challenge a friend Browse library

The Trap

The trap is ritual accumulation without ritual subtraction. Every quarter someone has a good idea ('we should do a monthly business review'), it gets added, and nothing is ever removed. After 3 years, the leadership team has 12 recurring meetings, half of which were added by someone who's no longer at the company, and no one can remember why. The opposite trap: ritual minimalism — the CEO who refuses to add any recurring structure 'because we want to stay agile,' and the company runs on heroic individual effort with no shared rhythm. Real teams need real rituals; the discipline is matching the ritual set to the company's actual operating needs at this stage, not at a stage 2 years ago. Stripe famously revisits their operating rituals annually; most companies don't, and it shows.

What to Do

Run an annual ritual audit: (1) LIST every recurring leadership-team meeting, ceremony, or process — typically 8-15 items. (2) FOR EACH, document: owner, stated purpose, time consumed (per person + total), value created. (3) CATEGORIZE: KEEP (essential, working), MODIFY (right purpose, wrong design), KILL (no longer needed). Force at least 20% to KILL. (4) ANNOUNCE the new ritual set explicitly to the leadership team — including what was killed and why. (5) ADD only with explicit replacement: every new ritual must replace or shrink an existing one. (6) Quarterly: retro on the ritual set — what's working, what's not. The discipline is treating the operating cadence as a designed system, not an organic accumulation.

Formula

Ritual Health = (Active Rituals With Clear Purpose ÷ Total Active Rituals) × (1 − Ritual Time / Total Leadership Time) — target ≥0.7

In Practice

Stripe and Atlassian have both publicly documented their operating cadence as a designed system that gets explicitly revisited annually. Stripe's Patrick Collison has discussed in interviews how the company runs an annual 'operating cadence review' where every recurring meeting is justified or killed; the practice keeps the leadership team's calendar-load roughly constant even as headcount and complexity grow. Atlassian's Team Playbook explicitly includes 'health monitors' — recurring rituals that the team rates and prunes regularly. Both companies are cited as examples of 'designed cadence' culture, distinct from the organic-accumulation default that produces meeting-heavy executive teams at scale.

Pro Tips

01
The single best test for any recurring ritual: 'if I cancelled this for 3 months, what would break?' If the answer is 'nothing,' kill it. If the answer is 'I'm not sure,' run the experiment — actually cancel it for 3 months and see. Most leadership teams discover 30-40% of their rituals fall in the 'nothing breaks' category.
02
Rituals with no explicit owner die slowly into ceremonial overhead. Every ritual needs ONE person who owns the agenda, the cadence, and the decision to keep or kill. 'The team' as owner means no owner. Make ownership explicit and put it on the calendar invite.
03
Watch for 'phantom rituals' — recurring meetings that someone else added 18 months ago that everyone shows up to but no one would defend if asked why. The annual audit is the only time these surface, because no one wants to be the person who proposes killing someone else's meeting in week-by-week operating life.

Myth vs Reality

Myth

“More rituals = more disciplined operating”

Reality

Past a certain point, additional rituals reduce operating discipline by consuming the time that would otherwise go to actual work. The best-operated leadership teams are deliberate about a small set of essential rituals and ruthless about killing everything else. Discipline is measured by what you don't do, not by what you add.

Myth

“Rituals should be set once and held forever”

Reality

Operating needs change as companies scale. The right ritual set at $5M ARR is the wrong ritual set at $50M ARR. Annual ritual audits are the mechanism for keeping the cadence matched to current needs. Companies that don't audit accumulate dead rituals and operate increasingly heavy as they grow.

Try it

Run the numbers.

Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.

🧪

Knowledge Check

Your leadership team currently runs 11 recurring meetings: weekly e-staff (90 min), weekly metrics standup (30 min), biweekly leadership 1:1s (60 min × pairs), monthly business review (3 hr), monthly customer review (90 min), monthly all-hands prep (60 min), quarterly strategy day (full day), quarterly board prep (4 hr), plus 3 functional reviews. What's the right move?

Industry benchmarks

Is your number good?

Calibrate against real-world tiers. Use these ranges as targets — not absolutes.

Leadership Team Recurring Meeting Load

VP-level recurring leadership-team meetings (excludes 1:1s with directs)

Disciplined

5-7 hours/week per person in rituals

Functional

8-10 hours/week per person

Heavy

11-15 hours/week per person

Crushing

16+ hours/week per person

Source: Hypothetical: Composite of operator interviews and Stripe/Atlassian published cadence

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

💳

Stripe — Operating Cadence Review

2010s-present

success

Patrick Collison has discussed in multiple interviews and in Stripe's engineering blog how the company runs an annual 'operating cadence review' where every recurring leadership-team meeting is justified or killed. The discipline keeps the leadership team's calendar load roughly constant as headcount grows from hundreds to thousands of employees. The annual audit forces the conversation that organic accumulation prevents — what to subtract — and is widely cited as a key factor in Stripe's ability to maintain decision velocity at scale.

Audit Frequency

Annual

Forcing Function

Justify or kill each ritual

Outcome

Calendar load roughly constant as headcount grows

Operating cadence is a designed system that requires periodic redesign. Companies that don't audit accumulate dead rituals; companies that do audit can grow without growing their meeting load.

Source ↗

🟦

Atlassian — Team Playbook & Health Monitors

2010s-present

success

Atlassian's publicly-available Team Playbook includes 'Health Monitors' — recurring rituals where the team rates the health of the work and explicitly decides what to keep, modify, or kill. The mechanism makes ritual lifecycle management an explicit team practice rather than something that depends on the CEO noticing. The Playbook has been adopted by hundreds of companies and is a widely-cited operating framework for distributed and growing teams.

Mechanism

Health Monitors (rate-and-prune)

Public Resource

Atlassian Team Playbook

External Adoption

Hundreds of companies

Make ritual lifecycle management a recurring team practice, not a CEO-only concern. Teams that own their own cadence kill dead rituals faster than teams that wait for top-down audits.

Source ↗

Related concepts