"Let us sync on it"
Recurring meetings appear when state is nowhere trustworthy — jobs, priorities, and blockers all living in verbal updates. The calendar becomes your database and everyone pays a tax every morning repeating what a queue should already show. Cancel the meeting only after one queue holds truth and owners update it as part of their work — not as preparation for the call.
If the daily stand-up is where status gets updated, you do not have a workflow. You have a calendar tax. This is the same family of problem as email is not a workflow: information living in a medium nobody can query, sort, or age.
What the meeting is substituting for
Usually it is a combination of things: a single queue with owner and dates; permissions so the right people can update status without needing admin access; definitions everyone agrees on — "done" means what finance needs, not only what the floor feels; and trust that the queue matches reality, which often requires one report the room trusts or fixing the underlying CRM versus finance mismatch.
Meetings also substitute for decision rights — the founder bottleneck dynamic — when every priority waits for verbal sign-off. Encode the thresholds and the meeting gets shorter.
Shrinking the meeting deliberately
Week one: require the queue updated before the call. No update, no speaking slot. Week two: time-box to exceptions only. Week three: cancel one occurrence and measure what breaks. That breakage is your backlog. Do not cancel until something else holds truth — otherwise you only hide problems until customers ring you.
This links to everyone busy, nothing moving, where meetings feel like work while throughput stalls, and to a quarterly check-in for system health rather than daily status theatre.
When meetings still earn their place
Cross-functional exceptions, incidents, and relationship repair are genuinely better face-to-face or live. Not for reading lists aloud that a dashboard or queue already shows. Train async updates for routine state and reserve the live call for judgement.
Cost the calendar tax honestly
Count attendees times minutes times loaded cost for a month of status meetings. Compare that to fixing one queue and one report. The meeting often persists because it feels like control — but control without trustworthy state is theatre. Founders especially confuse being in the loop with the business running.
Replace "what did you do yesterday" with "what moved the queue" — blockers only. If the answer is always verbal, your tooling or permissions are wrong, not your people.
Experiment: cancel one recurring status meeting for two weeks with a written note — "update the queue daily instead." Document what breaks. That is your build backlog, not proof the meeting was sacred.
Tools that make status updates harder than talking will lose — fix permissions, mobile access, and required fields before you blame culture. The training that survives go-live guidance applies to managers too.
Leadership should update the queue themselves for work they own. If executives only read status aloud in meetings, the floor correctly learns that talking is the real system. Model the behaviour you want from the floor.
Book — Teesside and the North East. Process audit to name the queue, and build when your tools fight the habit.