Look at your calendar. There is, almost certainly, a recurring weekly leadership meeting on it. There has probably been one for years. Now ask yourself a slightly more uncomfortable question. In the last four weeks, what was decided in that meeting that wouldn't have been decided without it? If you can name two things, the meeting is working. If you can't, you don't have a weekly operating rhythm. You have a weekly meeting.
That distinction matters more than it sounds.
The difference between a meeting and a rhythm
A meeting is a scheduled event. A rhythm is a system. The meeting is what shows up on the calendar; the rhythm is what changes in the organisation as a result of the meeting having happened. Most leadership teams have the first and assume they also have the second. They don't.
The tell is what happens on Friday. After a real weekly rhythm, by Friday, somebody's plan has changed. A team has shifted priority. An owner has been re-assigned. A blocker has been removed. After a weekly meeting that isn't a rhythm, Friday looks identical to Monday — and the only artefact of the meeting is a Notion page with bullet points nobody will read.
What a rhythm has that a meeting doesn't
A weekly operating rhythm has four properties that most weekly meetings quietly lack. None of them are exotic. All of them are unenforced in most companies.
A fixed agenda tied to strategic goals, not project lists. The meeting agenda should not be "updates from each team." Updates from each team is a status meeting wearing leadership clothing. The agenda should be structured around the three to five objectives the team is collectively responsible for moving this quarter. What is the health of objective A? What changed about it since last week? What needs to change about it this week? The work updates are inputs to that conversation, not the conversation itself.
One decision per session, minimum. If a weekly meeting ends without a decision having been made, it was a reporting session in disguise. Every rhythm should produce at least one decision — a priority shift, a resource reallocation, a blocker resolved, a scope change approved, a goal explicitly de-prioritised. If you're not deciding, you're not operating. You're being briefed.
A 48-hour action window. Any action item that comes out of the rhythm should have a named owner and a resolution path by the next meeting. Items that sit open across three weeks aren't action items; they're agenda decorations. The rhythm should be ruthless about closing them or explicitly killing them. Half-open items rot the credibility of the whole format.
A visible link between weekly actions and quarterly targets. The rhythm only works if the people in the room can see, in real time, how this week's decisions connect to the objectives they're accountable for. Without that link, every weekly decision quietly optimises for local efficiency — the loudest fire, the squeakiest stakeholder — instead of strategic progress. The leadership team becomes a fire brigade that calls itself a strategy team.
How to build one in four steps
Step one: anchor the agenda to goal health, not project status. Write down your top three to five objectives for the quarter. Make each one a standing agenda item. Ask about objective health rather than project completion. The question isn't "did we ship feature X." It's "did we move objective A, and if not, why not."
Step two: pre-read everything, discuss only what matters. Require written updates twenty-four hours before the meeting. Use the meeting itself for the two or three things that genuinely require conversation — the trade-offs that no individual can make alone, the blockers that need executive air cover, the decisions that can't be made asynchronously. Protect the meeting time from status reporting like it's the most expensive hour of the company's week, because it is.
Step three: explicitly identify the one decision. Before closing the meeting, somebody — ideally the same person every week — asks: what is the one thing we decided today? If there isn't one, don't end the meeting until there is. If there genuinely isn't a decision to make, the meeting probably shouldn't have happened, and that's useful data too.
Step four: connect every action to an objective. Every action item that comes out of the meeting gets tagged to the objective it serves. This sounds trivial. It is not. It is the structural mechanism that turns the meeting into a rhythm — because three weeks later, when someone looks back, they can see which objectives are getting weekly attention and which ones are being quietly orphaned by the leadership team itself.
What good looks like
A well-run weekly rhythm takes about forty-five minutes. It covers the three to five objectives that matter most this quarter. It produces between one and three decisions. Everyone leaves knowing exactly what changed and why it changed. The next week's meeting begins by reviewing whether last week's decisions had the intended effect — closing the loop, instead of stacking new items onto old open ones.
That's a rhythm. Everything else is a recurring calendar invite.
The Vindaris view
A weekly meeting becomes a weekly rhythm at the moment the room can see — without anyone preparing a slide for it — which work is moving which objective, what's stalled, and what was decided last week. The system has to make that visible cheaply. If producing the picture takes a Chief of Staff three hours of prep on Sunday, the rhythm collapses back into a meeting within about two months, because the cost is unsustainable.
The hour every Monday isn't expensive because of the people in the room. It's expensive because of what those people aren't doing during that hour. The least you owe that hour is a real decision and a real change. The most useful thing a system can do is make both unavoidable.