The Anatomy of a Fleet Dashboard
You're building one screen to watch a fleet of agents. There are four design mantras everyone repeats — and they sound like they compete. They don't. Each lives on a different layer, and a good dashboard stacks all four.
Every window below reads the same fleet — one seeded set of accounts, orgs and agents. Change nothing about the data; just change the lens, and watch the screen reshape.
Show what needs you, not everything
How do you show a fleet of thousands at a glance? The instinct is a grid: one cell per agent, the whole fleet at once. Push the size up and feel that instinct break — then flip the lens.
Push the slider to 5000 and try to spot the red cells — then flip to Analyse-first and they're a short list.
At twelve agents, the overview is fine. At five thousand, it's noise: the handful of agents that are actually on fire are lost in a field of green. Analyse first — compute the exceptions and surface only those. (Keim et al., 2006: analyse first, show the important, zoom and filter, then details on demand.)
Once something needs you, how do you reach it?
The list told you what is wrong. Now you have to get to it. Drill down — and notice the shape never changes.
Click an account, then an org, then an agent — notice the rollup-filter-details shape never changes.
Account → org → agent → detail. At every level it's the same grammar: an overview that rolls the level up, a filter by status, and details on demand when you click. Learn it once, use it everywhere. (Shneiderman, 1996: overview first, zoom and filter, then details-on-demand — the visual-information-seeking mantra.)
Let the healthy stay silent
Which of these numbers actually deserves your eyes? Show a metric for every agent and you've built a wall no one reads. Fold the healthy away instead.
Flip to Exceptions: hundreds of healthy rows collapse to one, and the problems float up.
In Exceptions mode the hundreds of nominal agents collapse into a single line, and only what's off stays on screen. Management by exception: silence is the default; problems are what break it.
One UI for the novice and the expert?
A first-timer wants one number and a path. A power user wants to get out of the way — search, density, saved filters. The same screen can serve both if depth is disclosed on demand.
23 agents need attention.
Switch to Expert, then type a region or click a saved filter — depth that was hidden is now the default.
Guided shows the minimum and hides the rest behind a click. Expert promotes search and saved filters to first-class — because for someone who knows the fleet, typing a query is the disclosure. Progressive disclosure, expert-calibrated.
Four layers, one UI
None of these mantras replaced another. They stacked. Here is the same fleet assembled into one dashboard — toggle each chip to outline the part of the screen that mantra shapes.
Toggle the four chips: each lights up a different region. Together they are the whole dashboard.
What surfaces (Keim), how you navigate (Shneiderman), what stays silent (Few), how depth unfolds (progressive disclosure) — four layers, one screen.
A note on lineage: Keim et al. (2006) and Shneiderman (1996) are the named sources above. "Management by exception" is a classic management idea that Stephen Few applied to dashboards; progressive disclosure predates its NN/g formalisation (the term goes back to the 1980s). The mantras are older than any one dashboard — what's new each time is how you stack them.