The Meeting That Could Have Been a Dashboard

Research into how managers actually spend their working hours has produced a consistently uncomfortable finding: a large share of the week — in some widely cited studies, well over half — goes to meetings, and a meaningful portion of those meetings exist primarily to relay a status update that already exists somewhere in writing. The meeting isn't generating new information or a new decision. It's a live, synchronous replay of something that was already true before anyone sat down.

That specific category of meeting — the pure status relay, with no decision attached — is worth isolating from meetings in general, because the case against it is much clearer than the case against meetings as a whole. A meeting that genuinely requires live discussion, debate, or a decision earns its place on the calendar. A meeting that exists only to say out loud what a dashboard or a shared document could have said in writing, on everyone's own schedule, is a different category entirely.

How to tell which category a given meeting actually falls into

The test is simple: if every piece of information shared in this meeting already existed somewhere in writing before the meeting started, and no decision was reached that required live discussion, it was a status relay, not a working session.

A useful diagnostic question for any recurring meeting is whether everything communicated in it already existed, in writing, somewhere accessible before the meeting began — and whether anything was actually decided during the meeting that required live back-and-forth to reach. A meeting that passes both tests as "no new information, no decision reached" is, functionally, a scheduled reading of material everyone could have reviewed on their own, at whatever pace suited them.

Why these meetings persist even once they stop adding value

A status meeting that used to serve a real purpose rarely gets cancelled once that purpose fades — the recurring calendar slot keeps existing by default, long after anyone would actively choose to create it from scratch.

Many pure-status meetings started out serving a genuine purpose — a team was smaller, information wasn't yet tracked anywhere consistent, and a live sync was the only reliable way to get everyone aligned. As the team grew and better tracking tools got put in place, the original reason for the meeting often quietly disappeared, while the meeting itself kept its recurring slot, because cancelling a standing meeting requires someone to actively notice it's outlived its purpose and take the slightly awkward step of removing it from everyone's calendar.

What this costs across an entire organization

A thirty-minute weekly status meeting with ten attendees isn't costing thirty minutes — it's costing five hours of combined work time, every single week, for information that existed in writing already.

The cost of a pure-status meeting scales with how many people attend it, not with how long it runs. A thirty-minute meeting that pulls in ten people isn't a thirty-minute cost — it's a five-person-hour cost, every week, indefinitely, for the privilege of hearing information live that was already sitting in a document or a dashboard anyone could have checked on their own schedule. Multiplied across a growing organization with several such meetings running in parallel, the aggregate cost becomes substantial, even though no single instance of it looks dramatic in isolation.

Why dashboards and written updates solve this more completely than people expect

A well-built dashboard or written status update delivers the same information asynchronously, letting each person absorb it at the moment that's actually convenient for them, rather than at a fixed time that's convenient for nobody in particular.

The alternative to a live status meeting isn't the absence of communication — it's communication delivered asynchronously, through a dashboard or a written update that each person reviews on their own schedule. That shift doesn't lose any of the actual information; it just removes the requirement that everyone absorb it simultaneously, at a scheduled time chosen by whoever first set the meeting up, rather than at whatever moment best fits each individual's own workflow.

Why this change meets resistance even when the logic is clear

Cancelling a long-standing meeting can feel like removing a sense of connection or oversight, even when the actual informational content of the meeting could be fully preserved another way.

Resistance to cutting a status meeting rarely comes from disagreement about the informational redundancy — it comes from a felt sense that the meeting provides something beyond the information itself: a sense of visibility, of connection, of the team being watched over. That felt need is real and worth taking seriously, but it's a different problem than the one a status meeting was originally built to solve, and it's worth addressing directly rather than using a redundant status meeting as an indirect, inefficient substitute for it.

What auditing meetings this way tends to reveal

Running this test against every recurring meeting on a team's calendar typically identifies a handful of clear status-relay candidates, worth cancelling or converting to a written update, without touching any meeting that's actually earning its place.

Applying this test systematically across a team's full set of recurring meetings tends to surface a specific, identifiable handful that clearly belong in the status-relay category — worth converting to a dashboard, a written update, or simply cancelling outright. The rest of the calendar, the meetings that genuinely involve live discussion or a decision that needed real-time input, stays exactly as it was. The goal isn't fewer meetings for their own sake — it's removing the specific ones that were never actually meetings in any meaningful sense to begin with.