Method · 12 March 2026
Dashboards that force a decision
If a colleague can close your first screen without changing their week, you built a mural. Here is the audit we run before Signal Architecture students touch a chart builder.
Most product dashboards fail politely. They load. They look expensive. Nobody is embarrassed to share them. And yet the real argument in the room still happens on a spreadsheet someone rebuilt at 22:40.
We ask students to screenshot the first screen only — not the whole folder — and to write, in one sentence, the decision that screen is supposed to support this week. If they cannot, we do not discuss colour, tool, or “executive simplicity.” We inventory decisions first.
Three questions that usually empty the page
Would a miss on this number change a backlog item before Friday? If not, demote it. Could two honest PMs disagree about what the number even is? Then you have an event problem, not a visualisation problem. Would last week’s reader understand why the line moved without Slack? If not, you are missing annotation, not another breakdown.
Those three questions sound obvious. In a Bangkok marketplace cohort they removed five panels from a home canvas in forty minutes. The remaining three were uglier and more useful.
Density is not the enemy
Teams often “clean up” by spreading the same vanity rates across more pages. That is not composition. Composition is hierarchy: one decision metric, a health strip that tells you whether the instrument is lying, two mechanism cuts you already fight about, and a dated sentence. That is the Telemetry Canvas shape. It looks busy to people who like whitespace. It looks professional to people who have to decide.
If you want the critique version of this audit, sit Signal Architecture. If you only wanted the sequence, you already have it: screenshot, sentence, three questions, then — and only then — open the builder.