Your Operating Cadence Is Your Strategy's Immune System
BLUF/Summary
Most strategies don't fail because they're wrong. They fail because the organization has no recurring rhythm to keep them alive between the January offsite and the December review. Your operating cadence — the cascading system of annual, quarterly, monthly, and weekly meetings that connect strategic intent to daily work — isn't a meeting schedule. It's your strategy's immune system. Without it, good ideas quietly die of neglect. With it, the organization self-corrects before small drifts become fatal.
How Strategies Actually Die
Nobody announces the death of a strategy. There's no memo that says "we've officially abandoned the goals we set in January." Instead, it happens like this:
The leadership team comes out of a planning offsite energized. The strategy is clear. The goals are specific. Everyone is aligned. For the first two weeks, there's momentum. People reference the goals in meetings. Someone puts the strategic plan on the shared drive.
Then the quarter starts in earnest. Client escalations pile up. A key hire falls through. A project goes sideways and absorbs leadership attention. The daily pressure of running the business crowds out the strategic goals — not because anyone decided they weren't important, but because nothing in the organization's rhythm forced them back to the surface.
By June, the strategic plan is a document nobody has opened in months. By October, half the leadership team couldn't recite the annual goals without looking them up. By December, the strategy review is a retrospective on what happened to the organization rather than what the organization did — because the strategy stopped being an active force sometime around February.
I've seen this pattern so many times. The strategy was fine. The execution system — the recurring rhythm that was supposed to keep the strategy alive — didn't exist.
What an Operating Cadence Actually Is
An operating cadence is a structured, cascading system of recurring meetings, each with a defined owner, purpose, frequency, attendees, and output. It's sometimes called a "battle rhythm" — a term borrowed from military planning that describes the predictable tempo of how an organization makes decisions, reviews progress, and adjusts course.
The word "cascading" matters. An operating cadence isn't a random collection of recurring meetings. It's a hierarchy where each level feeds the next:
Annual strategy sets the destination. Once a year, the leadership team analyzes the market, assesses organizational performance, and defines the strategic theme and goals for the year ahead. The output is a clear, communicable strategy with a small number of measurable objectives assigned to specific leaders.
Quarterly strategy reviews check the heading. Every quarter, leaders present progress against their strategic objectives. The question isn't "what have you been busy with?" — it's "are we on course, and if not, what are we adjusting?" This is where the organization formally course-corrects: goals are reaffirmed, modified, or deprioritized based on what's actually happening.
Monthly operational reviews connect strategy to performance. These bring together project status, budget performance, key metrics, client feedback, and resource allocation. The monthly review is where leaders see whether the operational reality matches the strategic intent — and where problems are surfaced before they become crises.
Weekly priority check-ins drive execution. Every week, leaders and their teams publish and review their top priorities, report progress against last week's commitments, and identify blockers. This is the heartbeat of the cadence — the fastest feedback loop, and the one that keeps daily work tethered to strategic objectives.
Each level serves the ones above and below it. The weekly check-in produces data that feeds the monthly review. The monthly review surfaces issues that inform the quarterly strategy adjustment. The quarterly review determines whether the annual strategy needs revision. Information flows up; intent flows down. When this cascade works, strategy isn't a document. It's a living system.
Why This Is Your Strategy's Immune System
I use the immune system metaphor deliberately. A healthy immune system doesn't wait for a crisis to activate. It's constantly monitoring, detecting small deviations from normal, and making corrections before problems become systemic. It operates at multiple scales — local responses handle minor issues, while systemic responses mobilize for major threats.
An operating cadence works the same way.
It detects drift early. When a leader presents their quarterly progress and the numbers don't match the plan, the cadence forces a conversation that might otherwise never happen. Without the quarterly review, that drift continues undetected until December, when it's too late to correct. The cadence is the early warning system.
It makes accountability structural, not personal. I've written before about how high-agency cultures are built through systems, not hiring. The operating cadence is one of the most powerful examples of this principle. When every leader knows they'll present progress against their goals every quarter — in front of their peers — accountability becomes a natural feature of the rhythm. The system is the "bad guy," not the CEO. The leader isn't chasing people down to ask for updates. The cadence creates the expectation, and the expectation drives the behavior.
It forces prioritization. The weekly priority check-in is deceptively powerful. When every person has to name their top five priorities for the coming week — with action verbs, specific deliverables, and a clear finish line — they're forced to make choices. They can't say "I'm working on a lot of things." They have to decide what matters most. That act of prioritization, repeated weekly across the entire organization, is how strategy gets translated into action at the individual level.
It creates organizational memory. When meetings have published notes, when quarterly reviews produce documented assessments, when weekly priorities are tracked against outcomes — the organization builds a record of what it decided, why, and what happened. This memory is invaluable for onboarding, for continuity during leadership transitions, and for the kind of retrospective analysis that drives genuine improvement. Organizations without a cadence have no memory. They repeat the same mistakes because nobody documented the lessons.
What a Real Operating Cadence Looks Like
When I built the operating infrastructure for a company that grew to over 500 employees, the cadence looked something like this:
Annually: The CEO led a strategy session with the executive team, portfolio managers, program managers, and principals. The output was a strategic plan with a defined theme and a limited number of measurable objectives, each assigned to a senior leader.
Quarterly: The CEO led a strategy review with the same group, assessing progress against the plan and adjusting priorities for the upcoming quarter. Separately, each department held its own quarterly planning session to decompose enterprise goals into team-level objectives and plan the next quarter's sprints.
Monthly: Several reviews ran in parallel — project reviews led by the COO, business performance reviews led by the CSO (covering finance, metrics, budget, and rates), quality audits led by the quality manager, and resource planning sessions led by HR. Each had a defined template, a defined owner, and a defined attendee list.
Weekly: The operations team reviewed project-level priorities. The executive team reviewed enterprise-level priorities. The business development team reviewed pipeline and gate decisions. The resource planning team reviewed open positions and hiring priorities. Every leader and employee in the organization submitted their top five priorities for the coming week, with progress updates against last week's five.
Every single one of these meetings had an owner, a documented purpose, a defined attendee list, and associated templates or documents. None of them were optional, and none of them were status updates disguised as decision-making forums. Each one had a job to do in the cascade.
Was this a lot of meetings? Yes. But here's the counterintuitive truth: a well-designed operating cadence reduces the total number of meetings in an organization, because it eliminates the ad hoc "let's get together to figure out where we are on this" meetings that proliferate when there's no rhythm. When everyone knows that project status will be reviewed on the third Tuesday of every month, nobody needs to schedule a one-off meeting to ask about project status. The cadence replaces chaos with predictability.
The Three Mistakes That Kill an Operating Cadence
Even organizations that build a cadence often undermine it with one of three mistakes:
Mistake 1: Meetings without owners. Every recurring meeting needs a single person who prepares for it, runs it, and ensures that outputs (notes, action items, decisions) are published. When meetings are "shared" responsibilities, they deteriorate. The agenda gets lighter. The preparation gets sloppier. Eventually the meeting becomes a ritual without purpose. One owner, every meeting.
Mistake 2: Status updates instead of decisions. The most common way an operating cadence decays is when reviews become status updates. The monthly project review devolves into each project manager reading their status slide while everyone else checks email. The quarterly strategy review becomes a PowerPoint marathon instead of a decision-making forum. The fix is structural: every review meeting should start by stating the decisions that need to be made or the questions that need to be answered. If there are no decisions and no questions, the meeting should be shorter — or it shouldn't happen at all.
Mistake 3: No documentation of outputs. If a meeting produces decisions, action items, or insights, and nobody documents them, the meeting didn't happen. Published notes within one business day. Action items with single owners and tracking (not "the team will follow up" — an actual person, with a ticket). This isn't bureaucracy. It's the mechanism by which the operating cadence builds organizational memory instead of just consuming calendar time.
The Keel Connection
In the Keel Framework, the operating cadence sits at the heart of the Enterprise Operating System. I describe it as the mechanism that translates strategic intent into operational reality. The roles matrix tells you who owns what. The knowledge management system tells you how things work. The operating cadence tells you when and how often the organization checks its heading and adjusts.
Without an operating cadence, you can have a brilliant strategy and a well-documented operating system and still drift, because there's nothing in the rhythm of the organization forcing it to look up from daily work and ask: "Are we still headed where we said we were going?"
The AI era makes this more urgent, not less. As I've written in posts on AI agents and process assets and the AI Automation Trap, AI tools accelerate whatever system they're plugged into. If your organization has a strong operating cadence, AI can help you monitor progress, surface anomalies, prepare reviews, and identify drift faster than any human could. If your organization has no cadence, AI accelerates the chaos. The wind doesn't care whether you have a rudder.
Where to Start This Week
If your organization doesn't have a formal operating cadence, don't try to build the entire cascade at once. Start with two things:
First, establish a weekly priority rhythm. Ask every leader and their direct reports to publish their top five priorities for the coming week, every Friday. Require action verbs. Require specific, measurable deliverables. Require a progress update against last week's five. This single practice — done consistently — will do more for accountability and alignment than any other intervention I've seen. It takes 30 minutes per person per week and it changes the culture within a month.
Second, establish a quarterly strategy review. Put it on the calendar for the next four quarters. Define who attends, what they present, and what decisions will be made. The first one will feel awkward. The second one will feel forced. By the third one, your leaders will tell you it's the most valuable meeting they attend — because it's the only meeting where they step back from daily operations and ask whether the organization is actually headed where it intends to go.
Build those two bookends — the weekly heartbeat and the quarterly course correction — and you have the skeleton of an operating cadence. The monthly and annual layers can come later, as the rhythm matures.
Your strategy deserves a system that keeps it alive. Build the cadence, and the cadence will do the rest.
This is part of an ongoing series on building enterprise operating systems. Read more about the full approach in the Keel Framework, or explore related posts on the ambiguity tax of unclear roles, process assets and AI readiness, high-agency culture as a systems problem, and compliance as an operating system.
