Contents6
A dashboard nobody reads on a fixed schedule steers nothing: it decorates. Management rituals are the regular moments when a company looks at what its figures say and decides what it will change. They are what turn a flow into a loop: without them, improvement waits for the next incident. This guide from our section on process automation and business bots suggests a four-beat rhythm, and shows how automation prepares it so it does not cost one more meeting.
In short
A management ritual is a fixed, short appointment that ends with a decision.
Four beats are enough: alerts every day, queues and lead times every week, trends every month, direction every quarter.
Automations prepare the figures: the review starts with the decision, not with the data gathering.
Time for improvement has to be protected in the calendar, otherwise urgent work eats it.
Why does a company need rituals?
Because urgent work always beats improvement when nothing protects it. MIT researchers Nelson Repenning and John Sterman described it in 2001: under pressure for results, time for improvement is the first thing sacrificed, and the company locks itself into a “capability trap” where ever more effort is needed to hold the same level. A fixed ritual is the simplest way to reserve that time: it is in the calendar before the emergency arrives.
Rituals also give the loop its shape. In the PDCA cycle, plan, do, check, act, the last two steps are the ones that get skipped when nothing enforces them; our article Running your company as a system, not in reaction explains why that is where everything is decided.
The remedy is not to add meetings. According to Microsoft’s 2023 Work Trend Index, 68% of respondents already lack enough uninterrupted focus time, and inefficient meetings top the list of obstacles to their productivity. A good ritual replaces scattered exchanges, chasers and improvised meetings with a short, predictable appointment.
Which rhythm should you adopt?
Four appointments cover the essentials, from the most frequent to the most spaced out:
- Every morning
A report arrives on its own, and everyone looks at the alerts that concern them. No meeting: you only step in when a threshold is crossed.
- Every week
A thirty-minute review per flow, with the people who work on it. Queues, lead times, the current bottleneck, and one improvement decided.
- Every month
Leadership looks at trends, the cost of the automations and the thresholds to revisit.
- Every quarter
The direction. Next quarter’s objectives, the flows to rework, the indicators to keep or replace.
The daily glance
It needs no preparation. Every morning, an automation gathers what has moved, what is waiting and what has failed, and sends it where the team already reads its messages. You only read the exceptions: when all is well, there is nothing to do. The report’s absence must itself be flagged, though, because a task that has stopped warns nobody.
From the field
Two rituals that run without a meeting
On Palmora Property, a property portal we run, the team receives a report every morning showing the new properties, the approval queue, the synchronisation status and the age of the backup. Every month, a test also checks that the backup really restores. The second ritual is a reminder that a review also serves to check what you think is settled: a backup that has never been restored is only an assumption.
The weekly review
It is the heart of the loop. It covers one flow, brings together those who work on it and always follows the same order:
- The week’s figures
Prepared in advance: files in progress, lead times, waits.
- The current bottleneck
The step in front of which work piles up, and why.
- One improvement decided
With an owner and a date.
- An update on the previous one
Was it done, and what did it change?
Thirty minutes are enough when the figures arrive ready. Time spent hunting for them or debating their accuracy points to a data problem, not a meeting problem. The indicators to track are detailed in our guide Dashboards and KPIs: defining them with leadership, and how to deal with a bottleneck in our article on business bottlenecks.
The monthly check-in
Leadership looks at trends rather than today’s figures: is the end-to-end lead time falling, has the bottleneck moved, are the approval thresholds still right? It is also the moment to check what the automations cost and what they save. When they call an AI model, our guide on what AI costs a business explains how to forecast and cap it.
The quarterly direction
The quarter is the right rhythm for setting objectives. At Google, objectives and key results, or OKRs, are set for the year and the quarter, and graded in quarterly meetings; the company puts the sweet spot for a grade between 60 and 70%, a higher grade signalling objectives that were too cautious. The quarter is also the time to review the indicators themselves: one that has not triggered a single decision gets replaced.
How does automation prepare the rituals?
The hidden cost of a ritual is its preparation: extracting the figures, copying them, formatting them. Done by hand, it gets skipped as soon as the week is busy, and the ritual with it. Automated, it no longer depends on anyone:
What the automations prepare before the review
- Gathering
The week’s figures are pulled from the tools, with no data entry.
- Exceptions
A rule compares each indicator with its threshold.
- Summary
An AI writes a few lines from the figures, without inventing any.
- Review
The team starts straight with the decision.
One rule holds the whole thing together: numbers always come from the data, never from the model. AI puts into words what the gathering has measured; it calculates nothing used to decide. Gathering and comparison with thresholds remain rules, without AI, as our guide Automation without AI: when a rule is enough shows. And for gathering to run on its own, the tools first need to talk to each other, which our article Connecting your business tools: enter data only once details.
Which mistakes make a ritual fail?
A ritual rarely dies all at once. It wears down, for recurring reasons:
- no decision: a review that ends with no action and no owner becomes an information meeting, and people stop coming;
- too many figures: a review that goes over twenty indicators deals with none of them;
- disputed figures: if accuracy is being debated, the problem is in the data, and it gets fixed once, at the source;
- a ritual moved at the first emergency: when everything is on fire is when the review helps most;
- a trial rather than a review: it is about the flow; if it is used to judge people, the figures stop being reliable.
Where to start?
Start with a single weekly review, on a single flow, with three automatically prepared figures. Hold it four weeks in a row before adding the rest: a rhythm that holds is worth more than an ambitious calendar abandoned along the way.
Our digital and AI maturity audit helps you choose that first flow: a map of your processes as they really run, and projects ranked by impact. Our automation offer then takes over preparing the figures, from the morning report to the weekly review, with a meter showing what each automation costs.
Frequently asked questions
How long should a weekly management review last?
Thirty minutes is enough for one flow, provided the figures arrive prepared and the agenda stays the same each week: the figures, the current bottleneck, one improvement decided, an update on the previous one. A review that regularly overruns is dealing with too many indicators or too many flows at once. It is then better to split it than to lengthen it.
Who should take part in management rituals?
The daily glance concerns everyone for their own alerts, with no meeting. The weekly review brings together the people working on the flow and its owner. The monthly check-in and the quarterly direction belong to leadership, which can invite flow owners. The rule is the same at every level: only bring together those who decide or who do.
What is the difference between a management ritual and a meeting?
A management ritual comes back on a fixed date, always follows the same sequence, relies on figures prepared in advance and ends with a decision. A typical meeting often arises from a problem, is prepared at the last minute and can end without action. A good ritual actually makes some improvised meetings disappear, because everyone knows when the topic will be dealt with.
What if a review falls in a busy week?
Hold it anyway, in a short version. It is precisely when activity overflows that queues lengthen and the bottleneck moves: ten minutes to look at the figures and decide on a single action beat a cancelled review. If reviews are often skipped, it is a sign that their preparation still depends on someone, and that it needs automating.
Are OKRs essential?
No. OKRs are a method for setting ambitious quarterly objectives, useful when a company wants to align its teams on a few priorities. A company can perfectly well steer its flows with a dashboard, thresholds and a weekly review, without OKRs. What matters is having written objectives, reviewed on a fixed schedule, and figures that show whether you are getting closer.
Sources
- Repenning and Sterman, Nobody Ever Gets Credit for Fixing Problems that Never Happened, 2001 (new tab)mitmgmtfaculty.mit.edu
- Microsoft, Work Trend Index 2023 (new tab)microsoft.com
- Google re:Work, Set goals with OKRs (new tab)rework.withgoogle.com
Repenning and Sterman, Nobody Ever Gets Credit for Fixing Problems that Never Happened, 2001
Read on mitmgmtfaculty.mit.edu(new tab)Jim · founder of Brain Plus AI
Also in automation and bots

Practical guide8 min
Dashboards and KPIs: defining them with leadership
A useful dashboard does not compile everything that can be measured: it shows where work is waiting and where a decision is needed. How to choose your KPIs with leadership, feed them without data entry, and stop them turning into surveillance of people.

Understand9 min
Running your company as a system, not in reaction
Most companies move forward in reaction: a customer chases, someone searches, things get fixed. Thinking of the organisation as a system of loops shifts the effort: automations relay information, a dashboard shows where it piles up, and people keep the judgement.

Understand8 min
Business bottlenecks: how to find one and free it
A quote waiting for a signature, a single person who knows how: the bottleneck sets the pace for the whole company. How to spot it, why speeding up elsewhere achieves nothing, and how automation clears it without taking the decision away.
