Week 10 — Operating Cadence — Designing the Year

60-Second Summary

Week 10 of the 12-week program. Theme: Weekly, monthly, quarterly: the rhythm that runs the team.
Quarterly cadence review — the ritual you install this week.
60 min pre-read + 90 min cohort + Friday homework with a falsifiable artefact.
Reviewed by HR Director, line manager, and OB faculty lenses.

Teams without an operating cadence run on the manager's energy. Every decision requires a meeting; every priority shift requires a Slack thread; every review requires a fire drill. Teams with a cadence run on predictable rituals — Monday goal review, Wednesday metrics, Friday demos, monthly business review, quarterly planning — and the manager becomes a designer of the system, not its operator.

What the evidence says

Andy Grove (High Output Management): the manager's output is the output of the organisation under their influence. Operating rhythm is the multiplier.
McKinsey research on operating rhythm: high-performing executive teams have 3× the structured rituals of low-performing ones, but spend less time total in meetings.
Hackman (team effectiveness): a clear team rhythm with appropriate boundaries is one of the five conditions for effective teams.

Pre-read (60 minutes)

Read: The team operating system (weekly/monthly/quarterly rituals) — 20 min.
Read: Andy Grove on meetings as the medium of managerial work — 20 min.
Read: Async vs sync — what each is for — 15 min.
Reflect (10 min): map your team's current rhythm. Most managers discover they have no rhythm — just a calendar full of recurring meetings without a system.

Live session (90 minutes)

Cohort flow with a senior-manager coach

1
Rhythm design (25 min)
Coach walks through a template: Weekly (standup, 1:1s, demo), Monthly (BR, retros, skip-levels), Quarterly (planning, OKR setting, calibration). Each manager drafts their own.
2
Meeting audit (20 min)
Each manager lists their team's current recurring meetings. Coach helps classify: what's essential, what should be async, what should be cut, what's missing.
3
Async muscles (20 min)
What goes async (status, FYIs, decisions with clear context, async retros) vs sync (debates, hard conversations, brainstorming, alignment). Practice rewriting one current meeting as an async ritual.
4
Skip-levels (15 min)
Most new managers skip skip-levels. Coach walks through purpose (signal from below your immediate reports), frequency (quarterly minimum), and structure.
5
Commitments (10 min)
Each manager commits to: one meeting cut, one meeting moved async, one new ritual added if missing.

The ritual you install this week

Quarterly cadence review

Every quarter, take 60 minutes to review your team's operating rhythm. What's working? What's bloated? What's missing? Adjust deliberately. Without this ritual, calendar drift accumulates and within 12 months you're back to chaos. The cadence is a living system, not a one-time design.

Modern tools for this skill

Category	Examples (2026)	Use
Async standup	Geekbot, Standuply, Range, Slack workflow	Move status out of sync time
Goal tracking	Mooncamp, Quantive, Lattice Goals	Weekly review without meeting
Retros	Parabol, Miro, EasyRetro	Async-first retros save 2+ hrs/quarter
Notes & decisions	Notion, Coda, Linear docs	Permanent record outside meeting time
AI meeting assistants	Otter, Fireflies, Read.ai, Granola	Capture notes; don't outsource attention

Copy-paste AI prompt

Here is my team's current weekly/monthly recurring meeting list [paste], and our team's main goals [paste]. Audit: which meetings are essential, which should be async, which should be cut. Propose a redesigned operating rhythm with weekly, monthly, and quarterly rituals.

Friday homework — falsifiable artefacts

Team operating rhythm document written — weekly, monthly, quarterly rituals named with purpose.
Meeting audit completed; at least one meeting cut or moved async.
Skip-level cadence scheduled (every report's report, at least once per quarter).
Cadence shared with team and committed to publicly.
Submitted to coach: 1-page rhythm doc + meeting audit findings.

Success signal

By end of week 10, your team's week runs on rituals, not on your prompting. You can take a week off (mostly) without the team grinding to a halt. Your calendar has at least 4 hours of deep-work blocks protected per week.

Reviewer notes

HR Director (15+ yrs)

The teams with the highest engagement scores in our annual survey are not the ones with the most charismatic managers — they're the ones with the most predictable, well-designed rhythms. People feel safe when work is predictable. Predictability comes from cadence.

Line Manager (20+ yrs)

I run my year on three rhythms: weekly (people), monthly (metrics), quarterly (strategy). Every recurring meeting maps to one of those. If a meeting doesn't fit, I challenge whether it should exist. After 20 years, I have fewer recurring meetings than most first-year managers — and more output per quarter.

OB / HR Professor (25+ yrs)

Hackman's five conditions for team effectiveness include 'a sound team structure' and 'a supportive context'. Operating rhythm is how those conditions become daily reality. Without the rhythm, the structure is theoretical; with it, the structure becomes how the team breathes.

Written by Pawan Joshi.Sources cited inline.

First published 23 Jun 2026See site changelog →