Automate the collecting, the surfacing and the reminding. Never automate the deciding. Most leadership teams manage the exact opposite: they chase updates by hand all week and then rubber stamp decisions in the last nine minutes of the meeting.
The rhythm is what turns a plan written in November into work that happens in March. It is also the first thing dropped when a quarter gets busy.
The three loops
Weekly, on what is off pace. Short, specific, and about exceptions rather than everything. This is the loop that decides whether anything happens at all, and the one most often skipped.
Monthly, on the measures. Are the numbers moving, and in the direction the plan assumed. Slower, and the place where a wrong assumption gets caught while there is still time.
Quarterly, on the commitments. Do these still make sense given what we now know. The only loop where a commitment is allowed to be dropped on purpose rather than by neglect.
What to automate
Collecting progress. Nobody should be chased for an update. Where progress is entered as the work happens, the status exists before the meeting rather than being assembled during it. This single change is usually worth the first half of most leadership meetings.
Surfacing what is behind. Anything off pace should raise itself. Relying on someone noticing means relying on the person least likely to want it noticed.
Reminding. Review dates in calendars from the day the plan is set. Dates decided afterwards get scheduled when it feels comfortable to look, which is not the same as when it would be useful.
Preparing the pack. The picture, assembled, before anyone walks in. Not the conclusions. The picture.
What to leave alone
The decision about what to do. That is the meeting. A team that automates it has automated the only part that was worth the hour.
Whether a commitment still holds. Dropping something on purpose is a leadership act with a reason attached. A system marking it stale is a system letting it quietly die, which is what was happening before anyone bought software.
The conversation with the owner. When something is behind, the useful next step is a person asking another person what is in the way. No amount of surfacing substitutes for that, and teams that try end up with accurate dashboards and nothing moving.
| Part of the rhythm | Automate | Why |
|---|---|---|
| Collecting progress | Yes | Chasing is the biggest time cost in the loop |
| Flagging what is behind | Yes | Noticing should not depend on who benefits |
| Booking the reviews | Yes | Decided later means decided conveniently |
| Assembling the pack | Yes | Assembly is not judgement |
| Deciding what to do | No | This is the meeting |
| Dropping a commitment | No | On purpose, with a reason, by a person |
Why the status meeting persists
Because the status was never collected. The meeting exists to assemble it, which is why it takes forty minutes and why everyone leaves feeling it achieved little. The agenda was never the problem.
Sull, Homkes and Sull found in Harvard Business Review in 2015 that the common failure in execution is coordination across teams rather than alignment up and down them. A status meeting is a coordination mechanism being used as a reporting mechanism, and it does the second badly while crowding out the first.
Collect the status continuously and the same meeting becomes the coordination conversation it was supposed to be, with no change to the agenda or the attendees.
The test for any automation here
Did it remove assembly, or did it remove the person.
Removing assembly buys back the first half of every meeting. Removing the person produces a very tidy dashboard that nobody acts on, and it is the more common outcome, because it is easier to build.
Where Empiraa sits
Empiraa GPS is a strategy and accountability platform that helps businesses deliver their priorities without chasing updates across spreadsheets and meetings. Every commitment carries one named owner, progress is collected as the work happens rather than requested before the meeting, and anything behind pace surfaces while there is still a quarter left to act. ANI is built into the platform, and GPS shipped its MCP in version 1.22, so a compatible assistant can work with that record within your permissions.
Related reading: why strategy execution fails, and strategy execution best practices that survive a quarter.
Why quarterly goals stall in week three is the same problem at a shorter interval.
