Why Your Team Needs an Operating Cadence

Most of the writing about operating cadence, including our own, starts at the company level: the leadership meeting, the monthly business review, the quarterly reset. That is where the calendar is visible and where the cost is easiest to point to. It is also the wrong place to start if the actual complaint is that a single team cannot get its own work through in a predictable order.

A team without an agreed rhythm does not run without one. It runs on whichever question was asked most recently, by whoever was in the room to ask it. The engineer with the loudest manager gets unblocked first. The project that has a founder's attention this week jumps the queue. Work that was scheduled for Tuesday gets bumped by something that arrived Monday afternoon and felt urgent, because nothing on the calendar said otherwise.

The team feels the absence before the company does

This is not a company-wide cadence problem, and fixing the leadership team's meeting rhythm does nothing for it. A team of eight people shipping a product, running a campaign, or closing a pipeline has its own coordination loop, and if nobody has set its rhythm deliberately, escalation becomes the default mechanism — which means the loudest voice, not the most important work, decides what happens next.

A company can be well run at the top and badly run at the level where the work happens. The monthly business review can be sharp, the quarterly plan can be sound, and a product team two layers down can still be reprioritising its backlog three times a week because nobody ever decided how often that team, specifically, gets to change its mind.

This gap is easy to miss because company-level cadence and team-level cadence look like the same problem from a distance — both are about how often something gets reviewed. They are not solving for the same thing. Company cadence sets how fast the business as a whole notices a shift and responds to it. Team cadence sets how a small group of people, working closely together every day, decides what to do next without needing to ask.

What a team's own loop actually returns

A team's coordination loop is shorter and more granular than anything a company-wide review can see. A weekly business review will never catch that a team has been resequencing its own priorities daily for a month; it only becomes visible once it has cost a deadline. The team is where the smallest, most frequent decisions happen, and it is exactly those decisions that a company-level cadence is too slow and too coarse to govern.

The case against giving a team a fixed rhythm is usually speed: a standing structure feels like ceremony, and answering questions as they arrive feels responsive. It is responsive to whoever asked. It is not responsive to the work.

Ad hoc coordination answers whoever asked. A cadence answers the work.

Three things happen inside a team running on ad hoc coordination, and none of them show up until they have already cost something:

• Decisions get made twice, once informally in a hallway conversation and again, differently, in the next meeting someone happened to be in.
• Context lives in whoever was present for the conversation, so the same explanation gets repeated to everyone who was not, at a cost nobody tracks.
• The person managing the loudest stakeholder becomes the de facto prioritiser, regardless of whether they hold the context to prioritise well.

The cost shows up as thrash, not as a missed deadline

None of this looks like a cadence problem from inside the team. It looks like thrash — work started and restarted, priorities that seem to change without explanation, a sense that everyone is busy and little is finishing. Thrash is what an unset cadence looks like once enough people are affected by it to notice.

The instinct once a team recognises this is to add a meeting. That is the same mistake companies make at the top, described in how a cadence gets built to scale — starting from frequency instead of from what the frequency is meant to resolve. A team cadence does not need more time on the calendar. It needs three questions with a standing, known answer — the same narrow test behind setting up a weekly rhythm that actually works:

• How often does this team's priority list change, and who is allowed to change it?
• What decision, made this week, would otherwise be re-litigated three more times before it sticks?
• What does not need a meeting at all, because it was already decided and only needs to be executed?

Most of the fix is subtraction, not addition

A team that answers those three questions has usually found that it needs less standing time, not more, because most of what was filling the week was re-deciding the same thing from a slightly different angle. One short weekly checkpoint that actually holds — where a change to the plan requires showing up to make the case, rather than a side conversation with whoever is available — replaces four ad hoc conversations that were each partial, each undocumented, and each binding only until the next one contradicted it.

Naming this does not fix it, because the team did not arrive at ad hoc coordination by accident. It arrived there because nobody was ever explicitly given the authority to say no to an interruption, and because the team's manager has usually been rewarded for being reachable, not for protecting a rhythm. Fixing it means someone has to hold a line that will occasionally look unresponsive in the short term to be reliable in the medium term.

That is the part training tends to carry better than a one-off redesign: a team can be handed a good structure in an afternoon and lose it within a month if nobody on it has practised holding the line when the first loud exception arrives. The structure is the easy half.

This sits underneath the same argument that runs through everything in operating cadence — that the rhythm a group of people actually runs on, not the one written down for them, is the real operating model. At the company level that rhythm is a leadership calendar, and the leadership team is where the accident is easiest to overlook, because that room has no rhythm above it to have inherited. At the team level it is smaller, faster, and far more often set by accident.