Dashboard Design Principles for Reports People Actually Read
Most dashboards are not badly designed, they are undesigned. The page-level decisions that separate a readable report from an accumulated one.
Category
Turn dashboards into decisions — narrative, insight summaries, and presenting data to clients and executives.
Most dashboards are not badly designed, they are undesigned. The page-level decisions that separate a readable report from an accumulated one.
One person can really build dashboards and everyone else raises a ticket. How to spread the skill without losing sight of what clients are being shown — an…
Never present by screen-sharing an unfiltered dashboard. What to do instead: the first ninety seconds, two audiences in one meeting, bad news, and the ques…
Most writing on data storytelling is for data teams presenting quarterly. Marketers ship a report every month to someone who half-reads it. This is written…
Most metrics survive one "so what". A few survive two. The ones that reach three are the reason anybody opens the report. A test you can run on an existing…
A spike with no explanation generates a question; a spike with a label generates a decision. Four ways to annotate, compared — and the discipline that stop…
Twenty seconds to add and most client reports don't use them. What you can put a line on, the four kinds of target including the parameter nobody covers, a…
Most client reports are made entirely of lagging KPIs, which is why every meeting becomes an explanation of the past. What to stop reporting, what to repor…
You already have the dashboard, it has the right numbers, and nobody reads it. That is a structure problem. The frameworks that actually apply to marketing…
Every other page in your report answers what happened. This one answers what to do about it — and only works if a reader gets that in five seconds. What ea…
Nothing matches that yet.