Most dashboards are built for someone who doesn't exist: the executive with 20 free minutes and a login. The people doing the work don't open them. The fix isn't a better dashboard — it's a digest.
Dashboard vs. digest
A dashboard demands a ritual: someone remembers it exists, logs in, filters to the right period, and interprets it. Every step leaks. A digest inverts it: the number arrives where attention already lives (email, Slack), already filtered and already interpreted. Nobody has to remember anything.
The three-number rule
A digest that reports 20 metrics gets skimmed into wallpaper within three issues. Pick the three numbers the team can actually move this quarter, and let the digest defend them: the number, the trend arrow, the delta against last week. Everything else belongs in the dashboard the digest links to.
Design rules that keep it opened
- Same time every week. Monday 07:00. Predictability is the feature; it becomes part of the team's rhythm.
- Sixty seconds, top to bottom. If reading it takes longer, the anomalies hide. Put the "you should look at this" items at the very top.
- Numbers have opinions. Not "Revenue: $41,203" but "Revenue $41.2k — down 6% WoW, driven by 2 paused campaigns." A number without an interpretation is homework.
- Anomalies flag themselves. Thresholds and week-over-week deltas; anything out of band gets a mark. The reader's eye goes where the machine already looked.
- One unsubscribe-honest owner. If the digest isn't earning its slot in the inbox, someone must have the power to kill it or fix it. Wallpapers die slowly otherwise.
What it looks like in practice
One of our clients replaced a 14-sheet "analytics workbook" with a Monday digest: three numbers, two anomalies, one link. Six weeks later the workbook was archived and the digest was being forwarded to the board. The data didn't change. The delivery did.
Greyflows builds digests like this as part of almost every data engagement — often the first workflow we ship, because it proves the pipeline before anything fancier rides on it. Curious what your three numbers would be? Ask us.
Want this in your stack instead of your reading list? Start a project →