The dashboard most teams end up with is a decorated spreadsheet. A dozen tiles, each a different shape; two of them the same list under different names; a pie chart with nineteen slices and a legend that needs scrolling. It took an afternoon to build and nobody reads it, because reading it takes longer than opening the pages it was meant to summarise. The manager who built it still looks at it every morning, out of loyalty, and then opens the pages anyway. Ask her what the dashboard told her this week and she will name the one number she already knew. Ask what it hid and she will not know, because a chart that cannot be read does not announce what it is not saying.
A ring chart is a promise: the whole is divided into a few parts you can compare by eye. The promise breaks in three ordinary ways. A slice too thin to see is a lie of omission. The legend says the medical team holds two per cent of the radios, the ring shows nothing at that angle, and the eye reports zero. Twenty colours cannot be told apart, so the fourteenth share borrows a hue from the third and the reader matches the wrong name to the wrong number. And a ring with no gap between its slices reads as one blob at the distance a glance happens at; the thin gaps are what make the parts countable. None of the three is a bug anyone files; each is a chart doing exactly what it was told.
The rules that follow are small. Give every slice a floor, a width you can see even when the number behind it is tiny, and take the difference from the biggest slices, which will not miss it. After a handful of shares, and eight is about where the eye stops counting, fold the rest into one grey remainder and keep every share named in the legend, so nothing is hidden, only grouped. Keep a thin gap of the background between slices. Choose colours that stay apart from one another and from the colours that mean something elsewhere in the same app, the red of a loss and the green of a return, so that a ring never looks like an alarm by accident. When a person rests on a name in the legend, light its slice. When the chart is opened large, draw a short line from each slice to its name, because a legend is a lookup and a label is an answer.
A slice you cannot see is a number you will not believe.
The second ordinary failure is duplication. A dashboard grows two activity tiles, one called Recent and one called Live, that read the same log with different columns, and the team argues about which one is right. There should be one kind of log tile. And a list should say what it is showing: “the newest 12 of 345” tells you the size of what you did not see, where a bare dozen rows pretends to be everything. A tile that keeps a top also prints it in its footer, so a reader two desks away knows the list is cut before they count it. Two tiles that agree are decoration; two tiles that disagree are an argument.
The third is the first day. A new workspace should not open on an empty dashboard and a widget builder. The administrator who has just typed in two hundred items and forty people does not want to decide between fourteen widget types; they want to see their store. The honest offer is the essentials in one press: the equipment, the people, stock by location, what is running low, the activity log and the quick actions, placed exactly as a careful administrator would have placed them. The offer should appear only when the board is bare, add nothing to a dashboard that already has tiles, and come back if every tile is removed.
None of this needs a bigger screen or a longer legend. It needs a few decisions taken once, by the tool, so that the manager who looks at the dashboard every morning gets an answer in the time a glance takes, and opens the pages only when the glance says to. The test is simple. Stand two desks away from the screen and ask what the store looks like this morning: how much is out, where the gaps are, what moved since yesterday. If the answer needs a scroll, a hover or a second look at the legend, the dashboard is still a spreadsheet with a frame around it.
This is how the GearLogs dashboard works. A ring draws its first eight shares and one grey Other for the rest, with a thin gap between slices and a floor under a share too small to see, while the legend still names every share; the eight chart colours are kept apart from each other and from the colours that mean a loss, a return or a warning; the legend row under the mouse lights its slice, and a ring opened large draws a short line from each slice to its name. There is one kind of activity tile, Log Table, and a tile with a top says “Showing the newest 12 of 345” and prints the top it keeps in its footer. An administrator whose dashboard has no tiles sees one green button, Start with the essentials, which places the six essential tiles for everyone in the workspace, adds nothing to a dashboard that already has tiles, and is back the moment the last tile is removed.
The manager still looks at the dashboard every morning. Now it takes a glance, and most mornings the glance is enough.
