The Operating Rhythm - The Well-Run Company Series/Article 4 of 9

Every January I watched the same thing happen at companies I ran, companies I advised, and companies whose owners I sat next to in peer groups. Leadership went offsite, wrote a strategy everyone believed in, came home energized, and then Monday arrived. Customers called, a truck broke down, someone quit, and the strategy went into a drawer to wait for next January, when a new offsite would produce a new version of roughly the same document.

The documents were usually good. What was missing was anything in the company's normal week built to keep them alive. Strategy dies between meetings, and in most companies, between meetings is almost all of the time.

Rhythm beats willpower

The fix is rhythm: a small set of recurring meetings, each with a job, that together keep the company's attention where leadership decided it should be. Same day, same time, same agenda, decisions made, actions owned. When the rhythm is real, execution stops depending on anyone's memory, mood, or willpower, which is good, because all three run out by Thursday.

I resisted this for years, by the way. I came up as an operator who believed meetings were what happened instead of work. I was wrong in a specific way: undisciplined meetings are what happen instead of work. The disciplined kind are where the work of running a company actually occurs. The drift between undisciplined meetings costs far more than the hour a disciplined one takes.

The weekly leadership meeting

The center of it is a weekly leadership meeting, ninety minutes, same slot every week, protected like a customer commitment. Mine generally follow the same simple arc.

Numbers first. The scorecard gets five minutes. Every number gets read against its target, no storytelling, and anything materially off track moves to the issue list. Explaining every variance can wait; the review exists so that nothing important can drift for three weeks without the whole team seeing it.

Priorities second. Each quarterly priority gets a one-word status from its owner: on track or off track. Off track goes on the issue list. No speeches.

Then the issue list, which is most of the meeting. Real problems, named honestly, worked one at a time, starting with the most important. Each one either gets solved in the room or leaves as an action with one owner and a date. And every commitment made last week gets checked this week, which is what makes accountability routine instead of occasional.

Teams tell me they do not have ninety minutes a week for this. In every case I have seen up close, the leadership team was already spending triple that on ad hoc firefighting conversations, hallway re-decisions, and meetings about the meeting. The rhythm gathers up time the team is already spending in worse ways and gives it one disciplined home.

The quarterly reset

Every ninety days, the leadership team steps out of the week for a day and answers two questions: how did we do against last quarter's priorities, and what are the few priorities that matter most for the next ninety days. Few is the operative word. Three to five, for the company, with one owner each.

The first time a team does this, the priority list wants to be eleven items long, because everything feels important and nobody wants their project left off. Hold the line. In my experience, a company that names three priorities has a real chance of finishing three. A company that names eleven usually finishes only a few of them well, and everyone quietly knows which three mattered anyway. The quarterly reset is where leadership earns its pay: choosing among good ideas, making those choices visible, and putting one name beside each of them.

A ninety-day interval works well for a reason. A year is too long to hold focus and too slow to correct course. A month is too short for anything real to finish. A quarter is long enough to accomplish something meaningful and short enough that a wrong bet costs you one season instead of one year.

The annual session

Once a year, the same team takes two days and goes back to the big questions: who are we, where are we going, and how are we going to get there. The annual session reviews the strategy against reality, resets the longer-term targets, and feeds the first quarter's priorities. It is also where the leadership team itself gets examined: the seats, the owners, and whether the structure that got you here can carry what you are now asking of it.

None of this is exotic. That is precisely the point. The strategy that used to die by February now gets looked at every week, reset every quarter, and rebuilt once a year, and no single one of those mechanisms is impressive on its own. What is impressive is what a leadership team looks like after four quarters of actually running this way: issues surface in days instead of months, commitments close, and the strategy stops living in a drawer.

I have installed this rhythm in companies I led and helped install it in companies that brought me in, and the first time someone proposed it to me, I was the biggest skeptic in the room. If strategy keeps disappearing beneath the demands of the week, start with one move: put a recurring leadership meeting on the calendar, give it a fixed agenda, and protect it for twelve weeks before judging whether it works. And if you want help installing the rhythm, my door is open.