Category
Layout, colour, typography and UX for reports clients actually read. Design principles and reusable patterns for clean, on-brand dashboards.
A scorecard is the most-read component on any report and the least-designed. Usually left on defaults: a number, floating, with no idea what it's for.
Data Studio has dark themes. It does not have dark mode. One is a preference each reader sets; the other is a decision you make for everybody, permanently.
Data Studio's theme sets a font family. It does not set a font size. That one gap is why reports drift.
A Data Studio palette isn't a list of nice colours. It's an assignment to named slots, and most of the slots aren't chart colours at all.
"Can you make the report mobile-friendly?" is three different requests, and they have three different prices. One is a rebuild.
Images in Data Studio split into two different things, and most of the trouble comes from not noticing. The failures are the interesting part.
Data Studio has no cover page feature, which is why most cover pages look improvised. Here's what belongs on one and the four settings that make it read as…
Most people build a custom navigation bar before finding out what the built-in one does. Usually that's an afternoon spent rebuilding something worse.
A report that looks nearly right is almost never a taste problem. It's four numbers that were never set, and a menu two levels down.
A theme is how a report looks. A template is a whole report somebody means you to copy. The twist is that a theme can't be saved, so reusing one means maki…
There is no such thing as a saved brand theme in Data Studio. Here's how to build one properly, and the method that does make it reusable across clients.
Most dashboards are not badly designed, they are undesigned. The page-level decisions that separate a readable report from an accumulated one.
Nothing matches that yet.
