Module 4 — Operating System at Scale — Cadence, Metrics, Reviews

60-Second Summary

Module 4 of the Advanced Manager-of-Managers program. Theme: The system your org runs on.
Your org's operating system v1 — the real artefact you produce.
4-hour monthly intensive + biweekly coached practice on real work.
Reviewed by CHRO, VP/Director, sitting CEO, and OB faculty lenses.

At your old layer, you ran rituals on a team. At this layer, you design the operating system for an org. The cadence determines what gets attention; the metrics determine what gets optimised; the review structure determines what gets decided. Most directors inherit an inadequate system and never redesign it, then wonder why everything depends on their personal involvement.

What the evidence says

Andy Grove (High Output Management): the manager's output is the output of the organisation under their supervision — and the operating system is the lever.
Doerr on OKRs at scale: cadence and review discipline matter more than the OKRs themselves.
Sutton & Rao (Scaling Up Excellence): replication of working practices depends on installed rituals, not memo distribution.

Pre-read (90 minutes)

Grove — High Output Management, the operating sections — 45 min.
Doerr — Measure What Matters, cadence sections — 20 min.
Your current operating calendar (weekly, monthly, quarterly) — 25 min.

Monthly intensive (4 hours)

Cohort flow with a senior practitioner coach

1
Cadence audit (60 min)
Each leader maps their current operating calendar. Coach surfaces gaps and redundancies.
2
Metric selection (60 min)
Each leader proposes 5–8 metrics for their org. Cohort attacks: which are leading? which are vanity? which create bad incentives?
3
Review design (60 min)
Design a monthly business review that produces decisions, not status. Walk through agenda, pre-reads, decision logging.
4
Stop-doing list (45 min)
Identify rituals to kill. Most orgs have 3–5 zombie meetings that cost 10+ hours/week of leader time.
5
Wrap (15 min)
One ritual installed, one killed, this month.

The artefact you produce

Your org's operating system v1

A one-page doc covering: weekly, monthly, quarterly, annual rituals; the metrics reviewed at each; pre-read and decision-logging expectations. Shared with your direct-report managers and your own manager.

Tools at this layer

Layer	Examples (2026)	Use
Cadence	Notion operating calendar, Asana goals, Mooncamp, internal BR template	Make the cadence visible and durable
Metrics	Looker, Mode, internal dashboards, Lattice/CultureAmp for people metrics	Curate; don't collect
Decision logging	Notion decisions DB, Confluence decision log, internal RFCs	Decisions get worse when they're not written down
AI for ops	Granola/Fathom for review summaries, Claude for pre-read synthesis, internal LLM for query against operating data	Synthesis aid only

Copy-paste AI prompt

Here's my current operating calendar [weekly, monthly, quarterly meetings] and metrics I review [list]. Help me: (1) identify cadence gaps and redundancies, (2) classify each metric as leading/lagging/vanity, (3) propose a redesigned monthly business review agenda that produces decisions, (4) list 3 rituals likely worth killing.

Between-session homework

Cadence audit completed; redesigned operating calendar published.
Metric set curated to 5–8; rationale documented.
Monthly business review redesigned and run once with the new format.
At least one ritual killed; time reallocated documented.

Success signal

By end of this module, your org runs on a documented operating system that doesn't depend on your personal involvement to function. Decisions get logged. Reviews produce action, not summary. The system survives your two-week vacation.

Reviewer notes

CHRO (20+ yrs)

The directors with installed operating systems are the ones I can promote with confidence. The ones whose orgs depend on their personal cadence are flight risks for their own teams.

VP / Director (15+ yrs, 3+ scaled orgs)

Document the operating system as if you were about to leave. That's the only way to make it real. Anything that lives only in your head is a single point of failure.

Sitting CEO

Show me your operating calendar. That single doc tells me more about how you lead than any presentation you'll ever give me.

OB / HR Professor (25+ yrs)

Grove's insight is durable: management is leverage, and leverage at this layer comes from system design. The operating system is the dominant lever; everything else is downstream of it.

Written by Pawan Joshi.Sources cited inline.

First published 23 Jun 2026See site changelog →