Read the calendar before the org chart

Ask how a company is run and you will usually be handed an organization chart. I would ask for the calendar. The chart shows who reports to whom. The calendar shows where decisions get made, how often, by whom, and with what information in front of them. I spent nearly four years as a chief operating officer before I ran a finance function, and most of what I know about operations comes down to getting that calendar right.

One horizon per meeting

A working rhythm has a small number of recurring meetings, and each one looks a fixed distance ahead. The weekly meeting asks what is off track now and who will fix it. The monthly review asks whether the company is on its plan for the quarter and what should move if it is not. The quarterly session asks whether the plan itself is still right. Targets are set once a year.

Meeting	Looks ahead	Question it answers
Weekly	The week	What is off track, and who will fix it?
Monthly	The quarter	Is the company on plan, and what should move if it is not?
Quarterly	The year	Is the plan itself still right?
Annual	The next year	What are the targets?

Most of the trouble I see comes from mixing these. A weekly meeting drifts into a debate about strategy and nothing gets fixed that week. A quarterly session fills up with status updates and the plan goes unexamined for another three months. Holding each meeting to its horizon is most of the discipline.

Every recurring decision has a home

For the decisions a company makes again and again, such as a discount beyond the usual limit, a hire outside the plan, or a change to what gets built next, it should be obvious which meeting decides and which person has the final say. A simple test: when something goes wrong on a Tuesday, does everyone know where it will be dealt with, or does it get a meeting of its own?

Companies without a rhythm run on meetings called for the occasion. Those favor whoever is loudest or nearest to the chief executive, and they pull the chief executive into decisions that someone two levels down had better information to make.

Fewer goals, each with one name

I once built a goal-setting system across a company of more than four hundred people. The framework mattered much less than two rules. No team carried more than three objectives, and every objective belonged to one person. A goal shared between two leaders gets discussed by both and delivered by neither.

The harder half is deciding what stops. A new priority added to a full list takes its hours from somewhere, and if the company does not choose where, each team will choose differently.

Make the format dull

The same pages, in the same order, sent two days ahead, with the decisions needed listed at the top. When the format never changes, people stop spending attention on the document and spend it on the business. A review that opens with someone presenting slides the room could have read is using its most expensive hour badly.

Give bad news an appointment

What a rhythm changes most is how bad news travels. In a company without one, a problem has to be escalated, which means someone has to decide it is serious enough to interrupt a senior person. People put that off. When there is a meeting every Monday whose purpose is to hear what is off track, raising a problem is ordinary, and it surfaces while it is still small.

You can tell the rhythm is working when unscheduled meetings become rare, when the chief executive is involved in fewer decisions, and when the monthly numbers surprise nobody who was in the weekly meeting.