The operating cadence that runs a company without you in every decision

Most founders try to solve the bottleneck by delegating harder. They push decisions down, and for a week or two it holds — then the decisions float back up, because nothing changed about how decisions get made. Delegation without a system is just temporary relief. What actually removes the founder from the critical path is a cadence: a fixed, repeating rhythm in which the right people look at the right things and decide.

What an operating cadence actually is#

An operating cadence is not a status meeting. A status meeting reports what happened; an operating cadence decides what to do about it. The difference sounds small and is everything.

A working cadence has four moves, every cycle, in order:

• Look at the few metrics that matter — not a dashboard of forty, the handful that tell you whether the business is healthy.
• Decide what to do about anything that has moved past a threshold.
• Assign each action to a named owner, with a date.
• Close the previous cycle’s actions — confirm they happened, or escalate why they didn’t.

That fourth move — closing the loop — is the one almost everyone skips, and it’s the one that matters most. A cadence that opens actions but never closes them generates the comforting feeling of management without its substance. Accountability lives in the closing.

Why it removes you from the critical path#

Here is the mechanism. When the cadence is real, three things become true at once.

First, decisions have a home. People stop bringing you choices ad hoc, because there is a known place and time where decisions get made. The interruptions that fragment a founder’s week — "quick question, got a sec?" — collapse, because the answer is "bring it to the review."

Second, ownership is explicit. Every recurring decision has a named owner who is expected to make it, not escalate it. The cadence is where that ownership is exercised and visible, which is what makes it stick.

Third, problems surface early. Because you’re looking at leading indicators on a rhythm, you see the issue while it’s small and cheap — not when it has become a crisis that only you can resolve.

A founder is the bottleneck not because they won’t let go, but because the business has nowhere else to put the decision. Build the place, and the decisions go there instead.

How to install one#

You can stand up a basic cadence in a fortnight. The hard part isn’t the meeting — it’s the discipline around it.

Pick the metrics first. Before the cadence exists, decide the five-to-eight numbers leadership will steer by. Fewer than you think. If a metric wouldn’t change a decision, it doesn’t belong. Favour leading indicators — ones that move before the lagging results do.

Set the rhythm to the business. Weekly suits most operating companies; some functions need daily, some monthly. The rule is regular and protected — the cadence does not get cancelled because the week is busy. The busy weeks are exactly when it earns its keep.

Assign owners, not attendees. Every metric and every action has one accountable name. "The team will look into it" is how things die. "Priya owns this, closing next Thursday" is how they get done.

Keep a running action log. One list, carried cycle to cycle, that opens and closes actions. This is the spine. Without it, the cadence is theatre.

What it feels like when it works#

The change is unmistakable from inside the business. Your calendar stops being a queue of other people’s decisions. The team moves faster, because they’re not waiting on you. Problems show up in the review while they’re still cheap, instead of landing on your desk as emergencies. And you get the thing every bottlenecked founder actually wants: the ability to step back — for a holiday, for strategy, for the next thing — and find the business still running when you return.

None of this requires new software or a transformation programme. It requires the unglamorous discipline of deciding who looks at what, when, and who owns the result — and then holding it every single cycle, especially the busy ones. That discipline is most of what a fractional COO installs in the first two months, and it’s usually the change founders feel first.

The anatomy of one good cycle#

It helps to see what a single cycle looks like when it’s working, because the description sounds abstract until you watch it run. Picture a weekly operating review in a company of a couple of hundred people.

The meeting is forty-five minutes and starts on time whether or not everyone is there. The first ten minutes are the close: every action opened last week is read out, and each owner says "done," "done, here’s the result," or "not done, and here’s why." Nothing is discussed at length — this is a roll call of accountability, and the discipline of having to say "not done" out loud, every week, to the same people, does most of the work.

The next twenty minutes are the look and the decide, together. The five-to-eight metrics are already on the screen, already produced — no one is assembling numbers in the room. Attention goes only to what has moved past a threshold. A metric sitting inside its normal band gets no airtime; that’s the point of thresholds. For each number that has breached, the owner proposes what to do, the group pressure-tests it briefly, and a decision is made.

The final ten minutes are the assign. Every decision becomes an action with one named owner and a date, written into the log in the room so there is no ambiguity afterward about who agreed to what. The meeting ends on time. That last detail matters more than it seems: a cadence that reliably ends on time is one people stop dreading, and a cadence people don’t dread is one that survives.

The cadence is a stack, not a meeting#

A single weekly review is where most companies start, but a mature operating rhythm is a stack of cadences at different frequencies, each feeding the next. Getting the layers right is what stops either daily firefighting or quarterly drift.

Daily, where the work demands it — a short stand-up in delivery, support or a newsroom — exists to catch problems within hours, not to make strategic decisions. It is tight, operational, and often standing-room only by design.

Weekly is the spine: the operating review described above, where the business is actually steered. Most recurring decisions live and die here.

Monthly lifts the gaze — performance against the plan, trends rather than incidents, the questions a week is too short to see. This is where you notice the slow drift a weekly cadence is too close to detect.

Quarterly is for direction — priorities, resourcing, whether the strategy still holds. It sets the targets the weekly cadence then steers toward.

The discipline is to keep each layer doing its own job. When strategic questions leak into the daily stand-up, the stand-up bloats and stops being useful. When operational firefighting consumes the quarterly, direction never gets set. A founder removed from the critical path is usually one who has pushed the operational decisions down to the daily and weekly layers, and reserved their own attention for the monthly and quarterly — where it actually belongs.

The goal isn’t to attend fewer meetings. It’s to move your attention up the stack — out of the daily decisions and into the direction only you can set.

Where cadences quietly fail#

I’ve seen more cadences die than thrive, and the failures are remarkably consistent. Knowing them in advance is most of the battle.

The close gets dropped first. When a week is busy, the temptation is to skip the roll call of last week’s actions and "just get to the new stuff." Do that twice and the cadence is finished — actions become suggestions, and everyone learns that nothing assigned in the room actually has to happen.

It becomes a status meeting again. Slowly, without anyone deciding it, the review drifts back to people narrating their week. The tell is that no decisions get made — everyone reports, nobody resolves. The fix is to ruthlessly cut narration and ask, every time, "so what are we doing about it, and who owns that."

The metrics stop being trusted. If the numbers on the screen are disputed in the room, the cadence stalls into an argument about whose figure is right. The cadence depends on a scorecard people believe — which is why definition and a single source of truth come before the meeting, not after.

The founder keeps taking the side channel. The cadence can be immaculate and still fail if the founder answers the "quick question" in the corridor an hour later. Every decision made outside the cadence teaches people that the cadence is optional. The founder has to hold the line hardest of anyone: "good question — bring it to the review."

Owners aren’t empowered. If the named owner of a metric can’t actually act without the founder’s sign-off, the cadence just relocates the bottleneck into a meeting. Ownership has to come with the authority to decide, within agreed bounds, or it isn’t ownership.

How to know it’s working#

The proof of a cadence isn’t in the meeting — it’s in everything around it. A few signals tell you it has taken hold.

• The corridor questions dry up. People stop ambushing the founder with decisions, because there’s a known place for them.
• Actions close on time. The proportion of last week’s actions actually completed climbs and stays high. This is the single best health metric for the cadence itself.
• Problems arrive small. Issues show up in the review while they’re minor, rather than landing on the founder’s desk as emergencies.
• The founder can disappear. The hard test: the business runs through a two-week absence without stalling. When that’s true, the cadence has done its job.

If you want one number to watch, watch action-closure rate — the share of committed actions completed by their date, cycle on cycle. A cadence with a high, stable closure rate is real. One where closure quietly slides toward zero is theatre, however good the meeting looks.

Where to start#

Don’t try to build the whole stack at once. Start with a single weekly operating review and get it genuinely working before you add a daily stand-up or a monthly. Pick the five-to-eight metrics leadership will steer by, name an owner for each, open one running action log, and hold the meeting on the same day and time every week — beginning with the close, every time.

For the first month it will feel clunky, and old habits will keep pulling decisions back to the founder. Hold the discipline anyway, especially through the busy weeks, because the busy weeks are exactly when the cadence proves its worth. By the fifth or sixth cycle the corridor questions thin out, actions start closing on time, and the founder notices they’re being asked for things far less often. That is the bottleneck dissolving — not through working harder or delegating louder, but through building the one place where decisions are supposed to happen, and then refusing to make them anywhere else.