Home › Topics › Dashboard Design: The NOC Wall vs. the Boss's Browser › Design Review Checklist

A Dashboard Design Review Checklist (With a Worked Redesign)


Nobody reviews dashboards. Firewall rules get reviewed. Alert thresholds get reviewed. The change that adds a VLAN gets a ticket and a second pair of eyes. The screen tells the whole department whether the network is on fire. It gets built on a Friday afternoon by whoever had the idea, and then left. I have done this myself. The screen I built that way lasted three years and was wrong for two of them.


A dashboard is a change. It changes what people believe about the network, and it does so every minute it is on, for everyone who walks past. That is a larger blast radius than most firewall rules. It deserves the same ritual: an inventory of what is there, a checklist of what "correct" means, a second person, and a signature. The ritual takes thirty minutes, and this guide gives you every piece of it.


By the end you will be able to inventory any screen with a copyable table and run a joke-free review checklist against it. You will be able to work through a full redesign of a forty-panel "everything" screen into two screens people actually use. You will be able to run the review in half an hour, and sign it off with a template. The other guides in this pillar teach the design craft; this one is the procedure that makes the craft happen on a date.


In this guide

  • Why review a dashboard like a change
  • The panel inventory
  • The review checklist
  • Worked redesign: the forty-panel screen
  • The after: a wall and a browser page
  • Running the review in thirty minutes
  • The sign-off template
  • Where to go next

Why review a dashboard like a change


A change review asks four questions: what is this, who is it for, what could go wrong, and who is responsible. A dashboard needs exactly the same four, and it needs them for the same reason. The people affected by the change are not the people making it. The reader of the wall is the room; the reader of the manager's page is a person who will not ask. Neither was in the room when the screen was built.


The library's definition of a dashboard is that it answers one question, for one audience, at a glance. And the guide on what dashboards are for sets that out. The review is where you check that a real screen still meets it. Screens drift. A panel gets added because someone asked; a service gets retired and its tile stays; a threshold changes and the colour rule does not. None of those is a mistake at the time. Six months of them is a screen that no longer answers its question, and the only way to notice is to look on purpose.


Reviewing on a calendar also gives you the moment to remove things, which otherwise never arrives. Dashboard wallpaper explains the drift in detail and gives a quarterly prune. This guide is the fuller version, for when a screen is new, inherited, or being rebuilt. Other monitoring rituals work the same way: the threshold review ritual and coverage reviews are the same idea applied to thresholds and to what is monitored at all.


The panel inventory


The panel inventory is a table with one row per panel on the screen. And it is the first thing the review produces, because you cannot judge a screen you have not listed. Filling it in is the part that takes longest and teaches most. The act of writing "question it answers" beside a panel is where you discover that six of them answer the same question and four answer none.


Fill in every column for every panel, including the ones you are sure about. The source check column names the monitoring check the panel reads, so that the reviewer can confirm it still exists. The freshness column says how old the data may be before the panel says so. The owner is the role that reacts. The verdict is one word.


PanelAudienceQuestion it answersVisualSource checkFreshness ruleOwnerVerdict
Internet linkRoomIs the internet up?TilePing, two external targetsGrey after 3 pollsNetwork adminKeep
WAN traffic, inboundAdminHow busy is the link?Line graphSNMP interface countersNone shownNetwork adminMove to admin view
Storage growthManagerWhen does the shared drive fill?Number with dateWMI disk freeWeekly rebuild, datedServer adminMove to manager page
Old SAN statusNoneNone (device retired)TileCheck deletedGrey for 5 monthsNoneCut

Four rows are shown. A real inventory has as many rows as the screen has panels. For a forty-panel screen that is forty rows and about an hour. Do the hour. The inventory is also the document that survives you: the next admin will inherit the screen. And the inventory is the only thing that tells them what each colour is claiming and who to call.


The review checklist


With the inventory filled in, walk the screen against this list. Every line is a yes or a no. The review is not complete until every line is a yes or has a dated action beside it. The list is short on purpose; each line points to a longer explanation elsewhere in this pillar. And the review is not the time to reread them.


  • Audience named. The screen names one audience: the room, the admin at a desk, or a specific manager. Not "everyone".
  • Question stated. The one question the screen answers is written on the screen or in its title, and every panel helps answer it.
  • Reading distance tested. For a wall, every service name is readable from the door with the lights on. For a browser page, everything fits on one laptop screen without scrolling.
  • Freshness marker present. The time of the newest data is shown, and any panel whose data is older than its freshness rule changes appearance to say so.
  • Colour rule written. The screen uses at most four state colours, each defined in writing. And every state shown by colour is also shown by a word or shape.
  • Units and dates on every graph. Every axis has a unit; every graph shows the time range and the date of its data; graphs on one screen share a time range.
  • Owner per panel. Every panel has an owner role in the inventory, and the screen itself has a named owner.
  • Retire date set. The screen has a review date on the calendar, and any panel added "temporarily" has a removal date beside it in the inventory.

The retire date is the line people push back on, because it feels like planning to fail. It is the opposite. A screen with no review date is a screen that will be reviewed by the next outage. And the next outage is a poor reviewer: it only checks one panel, and it does not write anything down.


Worked redesign: the forty-panel screen


Here is the review applied to a screen you will recognise. Acme Distribution ran a single dashboard called "Network Overview" on a television in the IT office. It also ran in a browser bookmark shared with the operations director. It had forty panels. It had been built over three years by four admins, none of whom had removed anything. And it was shown to visitors as evidence that the network was monitored, which it was. It was also read by nobody, for reasons the inventory made obvious in the first twenty rows.


The forty panels broke down into eight groups. Rather than forty inventory rows, here they are grouped, with the verdict the review reached for each group. The full inventory had every panel, and the groups below are how it was summarised for the sign-off.


Panel groupCountAudience it actually servedWhat the review foundVerdict
Interface traffic graphs, one per uplink and WAN link12Admin, when investigatingUnreadable from the door; time ranges differed between graphs; two interfaces no longer existedMove 10 to admin view; cut 2
Server CPU and memory graphs8Admin, rarelyNone had changed a decision in a year; thresholds already alert on themMove to admin view
Up/down tiles for core devices7RoomCorrect and useful, but sized to fit between the graphs, so too small to readKeep on wall; enlarge
Disk space gauges5Manager (storage purchase)Gauges with no dates; one had been amber for four months while a purchase was approvedMove to manager page as a number with a fill date
Wi-Fi client count graphs3NobodyInteresting on launch day; never sinceCut
Printer status table1Facilities, who had their own listEighteen rows in a font nobody could read from anywhereCut
Backup job status2Room and managerUseful but buried bottom-right; one panel read a job that had been renamed and showed "unknown"Keep one as a wall tile; fix the source; add a row to the manager page
Retired SAN status tile1NoneGrey for five months; the device had been recycledCut
Clock, weather, and a photograph of the data centre1VisitorsThe clock was wrongCut; replace with a last-data clock

Forty panels, then. Twenty moved to the admin's desk view, where they can be clicked. Six moved to the manager's page, rewritten as words and dates. Eight were cut, including two panels that read from devices that no longer existed and one that showed the wrong time. Seven tiles stayed on the wall and were enlarged. That accounting is the whole output of the review, and it took an afternoon.


How many tiles fit on a wall is not a matter of taste, and the review worked it out in front of the room. The NOC wall guide derives a font size of about fifty-five pixels for a name readable from three metres on a common television. A twelve-character name at that size needs roughly 360 pixels, plus padding. So call the minimum tile width 460 pixels and the minimum height 300. The capacity is then:


tiles across  = floor(screen width px  / min tile width px)   = floor(1920 / 460) = 4
tiles down    = floor(screen height px / min tile height px)  = floor(1080 / 300) = 3
readable tiles = tiles across x tiles down                    = 12

Twelve. Not forty. The number is an example for that screen and that distance, and yours will differ, but the shape of the sum does not. A wall's capacity is set by the door, and no amount of enthusiasm changes where the door is.


The after: a wall and a browser page


The single "Network Overview" became two screens with different audiences and different questions, plus the admin's desk view. That view already existed and simply received the graphs. Here is what each one holds and why.


The wall: twelve tiles

The television now shows a status strip, a four-by-three grid, a narrow alert ticker, and a last-data clock. The seven surviving device tiles were joined by five service tiles that the review found were missing. Nobody had noticed that a screen with twelve traffic graphs on it had no tile for "email". Every tile has a name readable from the door, one status word, and an owner in the inventory. Red means someone acts now. Amber must clear or promote within a week. Nothing rotates.


STATUS STRIP: ALL CLEAR | Open incidents: 0 | On call: (name)      | ALERTS
INTERNET     | FIREWALL    | CORE SWITCH | WI-FI                     | (newest
DNS          | DHCP        | EMAIL       | FILE SERVER               |  first)
PHONES       | VPN         | BACKUPS     | UPS / POWER               |
LAST DATA hh:mm:ss     grey after 3 missed polls

The browser page: nine rows for the operations director

The shared bookmark now opens a one-screen page built the way the boss's browser describes. It has one row per service in plain words. Each row has a status word from a set of three, a trend against last month, a one-sentence note, and an owner. The five disk gauges became one row, "File server storage", with a note that reads "full in about five months; purchase approved, delivery next month". The page is rebuilt weekly and says so at the top. A link at the bottom, "Show the measurements", opens the graphs for anyone who wants them.


ServiceStatusTrend (vs last month)NoteOwner
Internet at the depotFineSteady Network admin
Internet at the branch officesFineSteady Network admin
Staff loginsFineSteady Server admin
EmailFineSteady Server admin
Warehouse scanners (Wi-Fi)FineBetterTwo access points replacedNetwork admin
File server storageWatchWorseFull in about five months; purchase approved, delivery next monthServer admin
PhonesFineSteady Network admin
Last night's backupFineSteadyTest restore done this monthServer admin
Server room power protectionFineSteady Facilities

What was deleted, for the record: two interfaces that did not exist, three Wi-Fi client graphs, the printer table, the retired SAN tile, and the clock that was wrong. Nobody has asked for any of them back. The photograph of the data centre was offered to facilities, who declined.


What was learned: the wall had been missing five of the services the room most needed. Nobody had noticed because the screen was so full that absence was invisible. That is the finding a review produces and an outage does not. An outage tells you one panel was wrong. An inventory tells you which panels were never there.


Tolworth Engineering skipped the review for four years, and the cost arrived in one morning. A new admin, on her second day, saw a grey tile labelled "SAN-02" on the wall. She assumed it was down and spent the morning tracing cables in a rack that had been empty since before she was hired. The device had been recycled; the tile had been grey for two years; the three admins who knew that had all left. The dashboard inventory she wrote that afternoon was the first document in the department to mention SAN-02's retirement. It was eleven words long, and it has saved every new starter since.


Running the review in thirty minutes


The review is a meeting with three people and a timer. The people are the screen's owner, one person from its audience, and one reviewer who did not build it. Thirty minutes is enough for a screen of up to about fifteen panels once the inventory has been filled in beforehand. A forty-panel screen needs the inventory done in advance and an hour; do not try to inventory in the meeting. Here is the agenda, with the clock.


  • Minutes 0 to 3: state the audience and the question. The owner says who the screen is for and what one question it answers. If that takes longer than three minutes, stop and write the answer down before continuing, because everything else depends on it.
  • Minutes 3 to 8: the reading test. Everyone stands where the audience stands: the door for a wall, a laptop with no mouse for a browser page. Each person names the panel they saw first and whether anything looked wrong. Record the answers.
  • Minutes 8 to 20: walk the inventory. One row at a time, the reviewer reads the question the panel answers and the verdict. The audience member says whether they agree. Any "cut" or "move" that gets an objection is written down with the objection and settled later, not now.
  • Minutes 20 to 26: the checklist. Eight lines, yes or no, with a dated action for every no.
  • Minutes 26 to 30: sign-off and the next date. The owner and reviewer sign the template below, the next review is put on the calendar, and the actions are assigned.

The audience member is the person most often left out and the one who matters most. The owner knows what the panels mean; the reviewer knows the checklist; only the audience member knows whether the screen is read. Their contribution is usually a single sentence, and it is usually "I have never looked at that one".


Tip: do the first review of any inherited screen before changing anything on it. The urge on inheriting a bad dashboard is to fix the obvious panel immediately. Inventory first; the obvious panel is rarely the one that has been misleading people, and you will only find that one by listing them all. Dependency thinking is the companion exercise: it tells you which services deserve a tile at all.


The sign-off template


The sign-off is a short plain-text record, stored with the monitoring documentation beside the inventory. It exists so that the next reviewer, or the next admin, can see what was decided and by whom without asking. Copy it, fill in every line, and keep every past copy. The history of a screen's reviews is the history of what the department thought mattered.


DASHBOARD DESIGN REVIEW - SIGN-OFF

Screen name:            ______________________________
Location / URL:         ______________________________
Audience (one):         [ ] room   [ ] admin desk   [ ] manager: ____________
Question it answers:    ______________________________
Screen owner (name):    ______________________________

Review date:            ____________
Reviewer (not builder): ______________________________
Audience member:        ______________________________

Inventory:              ____ panels listed   ____ keep   ____ move   ____ cut
Checklist:              ____ of 8 lines yes   ____ actions open (listed below)

Reading test result:    first panel seen: ________________
                        anything wrong visible? [ ] yes  [ ] no  [ ] unclear
Freshness marker:       [ ] present   grey/stale rule: ______________
Colour rule written at: ______________________________

Actions (owner, due date):
  1. ______________________________________________
  2. ______________________________________________
  3. ______________________________________________

Next review date:       ____________   (on the calendar: [ ] yes)

Signed, owner:          ____________   Signed, reviewer: ____________

Two lines on the form do most of the work. "Reviewer (not builder)" makes it impossible to review your own screen and call it done. "Next review date, on the calendar: yes" makes the review a series rather than an event. Everything else is evidence for the next time someone asks why a panel was removed.


Where to go next


Put the review on a calendar. That is the whole recommendation, and every template in this guide exists to make the calendar entry easy to keep. Quarterly is right for a wall in a busy room. Twice a year is enough for a manager's page that changes weekly anyway. And any screen that has just been built, inherited, or rebuilt gets one within the month. A dashboard reviewed on a date stays a dashboard. A dashboard reviewed by the next outage becomes wallpaper, and then an anecdote, and the anecdote is never flattering.


The craft the review checks is taught in the rest of this pillar. The guide the NOC wall covers the screen read from the door. The guide the boss's browser covers the reader who will not ask. The guide on visual hierarchy covers position, size, and colour. And the guide on dashboard wallpaper covers the slow drift and the quarterly prune. They all live under Dashboard Design: The NOC Wall vs. the Boss's Browser.


Put this into practice with SysPeep Monitor

A review is easier when the source checks behind the panels are in one place and the retired device really is gone. SysPeep Monitor keeps discovery, SNMP, WMI, and SSH collection, thresholds, dependencies, dashboards, maps, and reports in a single web console on a Windows machine. So the inventory column that says "source check" has one place to be verified. The free trial installs in an afternoon if you want to rebuild the twelve-tile wall and the nine-row page above with your own devices.

Download Free TrialLearn About SysPeep