The Operating Cadence That Keeps a Scaling Company Coherent

In one quarter we discovered that sales was promising a feature that engineering had deprioritised, marketing was running campaigns for a segment we had decided to stop serving, and finance was modelling headcount nobody intended to hire.

Nobody had gone rogue. Every one of those teams was executing a plan that had been correct about ten weeks earlier. The plan had changed. The information had not travelled.

That is what drift looks like, and it is almost never caused by disagreement. It is caused by the absence of a forcing function — a moment in the calendar where everyone has to look at the same reality at the same time and say out loud what they are doing about it.

What a cadence actually is

An operating cadence is a small set of recurring meetings, each with a different time horizon, each answering a different question. Together they form a loop: decide, execute, observe, correct.

Most companies have meetings. Fewer have a cadence. The difference is that in a cadence, each meeting has one job, and no meeting does another meeting's job.

The failure mode is a single weekly leadership meeting where quarterly strategy, this week's blocked deal and a customer escalation all compete for the same hour. Urgency always wins. Strategy gets discussed for six minutes at the end, every week, forever.

The four layers

Weekly: what is blocked

Thirty minutes, same time every week, each team. One question: what is stopping us, and who is unblocking it.

Not a status report. Status belongs in writing, circulated beforehand. If people are reading updates aloud, you are using the most expensive coordination mechanism you have to transmit information that a document transmits better.

Every item leaves with a name and a date. No name, not an item.

Monthly: what the numbers say

Ninety minutes. Leadership plus function heads. The point is to look at actuals against what you expected, and to say what you are doing about the gaps.

The discipline that makes this work is publishing the numbers 24 hours in advance and expecting everyone to arrive having read them. The meeting is for interpretation and decision, not for presentation. We banned walkthrough decks and the meeting got roughly forty percent shorter and considerably more useful.

Five to seven metrics. If you have thirty, you have none — nobody can hold thirty numbers in mind well enough to notice when one is behaving strangely.

Quarterly: what we are choosing

Half a day. This is where you set three to five priorities for the next twelve weeks and explicitly name what you are not doing.

The "not doing" list is the part most teams skip, and it is the part that makes the exercise real. A priority list without a stop list is a wish list, and it produces the exact situation I opened with — teams executing plans that were quietly superseded.

Each priority gets one accountable owner and a measurable definition of done. "Improve onboarding" is not a priority. "Reduce median time-to-first-value from 11 days to 5" is.

Annually: what we believe

One or two days. The market, the bet, the shape of the company in eighteen months, the resourcing that implies.

The annual plan will be wrong in detail. That is fine — its value is that it makes the assumptions explicit enough to notice when they break. An assumption nobody wrote down cannot be falsified, so nobody ever updates it.

The rules that make it work

The structure is common knowledge. These are the parts that determine whether it functions or becomes theatre.

• Never move the recurring slots. The moment the monthly review gets rescheduled because something urgent came up, you have taught everyone it is optional. Ours has moved twice in three years.
• Written inputs, circulated in advance. Documents, not decks. Decks let you hide a weak argument behind good design; a document exposes it in the second paragraph.
• One owner per item, always a person. Teams do work. People are accountable.
• Decisions written down within 24 hours. What we decided, who decided, what would change our mind. The last part is what makes a decision reviewable rather than defensible.
• End every meeting with the actions read back. Sixty seconds. It catches the surprisingly common case where two people left with different understandings of what was agreed.
• Cancel anything without a decision to make. A meeting that only transmits information should be a document.

What this costs

Real hours, and it is worth being honest about them. For a 60-person company, the full cadence consumes roughly 3 to 4 percent of total working time, concentrated in leadership.

That is a genuine cost. It buys you the ability to change direction in weeks rather than quarters, which in my experience is worth several times the meeting time — most of the waste in a scaling company is not slow work, it is work that was pointed in a direction the company had already abandoned.

The cost only becomes unreasonable when the cadence stops producing decisions. A meeting that generates no decisions and no changes for two consecutive months should be deleted rather than defended.

Signs yours is broken

• The same item appears on the blocked list four weeks running. That is not a block, it is a decision nobody is willing to make.
• People hold pre-meetings to align before the real meeting. The real meeting is not safe.
• Quarterly priorities get quietly dropped without a conversation. There is no review, or the review is not honest.
• Bad news arrives late and informally. This is the most serious one. If a metric has been declining for six weeks and the monthly review is the first anyone hears of it, the problem is not the cadence — it is what happens to people who report bad news.

Where to start

If you have nothing, do not build all four layers at once. Start with monthly.

Pick five numbers. Publish them 24 hours before. Meet for ninety minutes with one question on the agenda: where did reality differ from what we expected, and what are we changing. Write the decisions down and send them the same day.

Do that for three months without moving the date once. It will surface more than any reorganisation you were considering — and it will tell you fairly quickly which parts of your company are running on evidence and which are running on momentum.