The weekly status workbook is more expensive than it looks

There is a workbook somewhere in your company that gets updated every Friday and read every Monday. Someone spends most of an hour on it. It is opened for about ninety seconds per recipient, mostly to look at two cells.

The forty minutes is annoying but survivable. What makes it genuinely expensive is subtler.

It is stale by the time it is read

A workbook is a snapshot with a timestamp nobody checks. By Wednesday it describes a world that has moved, and everyone knows this, so decisions get deferred to "when we have the new numbers" — which is Friday, which means the organisation operates on a weekly clock regardless of how fast anything else can move.

A published report is a frozen layout over live data. The layout does not shift under you, which is the thing people actually want from the workbook, but the figures are current whenever someone opens them. Wednesday stops being a dead zone.

It forks the moment it is sent

Send the workbook to six people and there are now seven copies. Someone filters a column and saves. Someone adds a tab. Two weeks later a meeting stalls because two people are looking at versions that diverged in a way neither can see.

A report at a single address cannot fork. That is most of its value, and it is the part that is hardest to appreciate until you have lost an afternoon to reconciling two workbooks that were the same file in March.

It is a person, not a process

The workbook's real dependency is whoever maintains it. They know that column H is pasted from a different export, that the top row is a manual override, and that the figure in J12 has been wrong since a supplier changed their format and it was easier to hardcode it.

None of that is written down anywhere, because there is nowhere in a workbook to write it. When they leave, the workbook becomes a liability that everyone is slightly afraid of and nobody will rebuild.

What replacing it actually requires

Not a dashboard. Dashboards are easy and they do not, on their own, kill a workbook — plenty of companies have both, which is the worst outcome.

Killing it requires three things:

1. The report has to arrive. People who currently receive a workbook will not go and look at a URL. In Dashful a schedule sends the report itself — headline figures, the first rows of the tables, a link to the live page — daily, weekly or monthly. What lands in the inbox is the thing, not a notification telling someone to go and find the thing.
2. It has to carry their filters. Two schedules on one report can carry two regions' numbers, executed at send time, because "the report" was never one thing to the six people receiving it.
3. The manual overrides have to go somewhere honest. This is the one people skip. The hardcoded J12 exists for a reason. Encode it as a stated assumption on the dataset, where the next person can find it and argue with it, rather than pretending the problem it was solving has gone away.

Do the third one and the workbook dies. Skip it and the workbook comes back, because it was still the only place the truth lived.