The operating system that runs without you

Operations · ~7 minute read

A centre that runs on "we know what we’re doing" doesn’t scale and doesn’t survive leadership change. A centre on a deliberate operating system runs reliably, adapts predictably, and gives the leader space to lead rather than fight fires.

Four cadences

Daily — the rhythm of operating (huddle, real-time, end-of-day). Weekly — the rhythm of management (ops review, 1:1s, skip-levels). Monthly — the rhythm of governance (performance, QM, risk, people, customer outcomes). Quarterly — the rhythm of direction (business review, strategy, capability planning).

Each has its purpose; each connects; no rhythm should duplicate another.

Design the rhythm explicitly

What runs at each cadence. Who attends (decision-makers, not observers). What’s prepared (pre-read, standing agenda, outputs). What’s decided (explicit, tracked, actioned). What’s deferred (not indefinitely; routed to the right cadence).

Without explicit design, the rhythm accumulates — meetings added; ceremonies repeating; calendar full but operation poorly served.

The two-week test

A well-designed operating system means: the daily rhythm runs whether the leader is in or out; the weekly rhythm has clear decision rights; covers run smoothly; the monthly is calendar-locked; the quarterly engages the leadership team, not just the leader.

A two-week leader absence should not disrupt the operating system. If it does, the system depends on the person, not on the design.

The rhythm that runs the leader

A failure pattern: the leader’s calendar fills with the inherited rhythm. Audit quarterly. Retire ceremonies that don’t earn their keep, including your own. Decline meetings the leader doesn’t need to attend. Make space for unscheduled time — judgement, strategic thinking, walking the floor.

Design the rhythm or be run by it.

The operating system — four cadences Cadences ▸ Daily — operating ▸ Weekly — management ▸ Monthly — governance ▸ Quarterly — direction ▸ Annual — the parent Two-week test ▸ Daily runs without you ▸ Weekly has clear decision rights ▸ Monthly is calendar-locked ▸ Quarterly engages the team ▸ Audit quarterly; retire what fails Design the rhythm or be run by it

The closing principle

The two-week absence test is the discipline. If the operating system depends on you, you don’t have one. Design the rhythm explicitly, audit it quarterly, distribute decision rights, and reclaim time for what only you can do.

See also