The Boss's Browser: A Dashboard for Someone Who Will Not Ask
Somewhere above you in the organisation is a person who opens your dashboard in a browser. They look at it for eleven seconds between meetings, and close it. They will not hover over a panel. They will not click "details". And they will not send you an email asking what "wan0 utilisation in" means. Asking would reveal that they do not know, and they have decided that they should. So they guess. Every panel you put in front of them is a guess you are inviting them to make.
That reader is not a problem to be managed. They are the most important audience your monitoring has, because they decide the budget. They read your screen the way you read a bank statement: quickly, looking for anything wrong, and forming an opinion of the sender. A dashboard that makes them guess makes them guess about you.
By the end of this guide you will be able to name the three questions a manager is actually asking. You will be able to label every panel so it explains itself and replace numbers with words that carry meaning. You will be able to show direction instead of raw values and fit it all on one screen. And you will be able to test the result against the toughest reader in the building. There is a one-screen template you can copy, and a war story about a decimal that travelled a long way.
In this guide
- The reader who cannot ask
- The three questions a manager is actually asking
- Labels that explain themselves
- Words instead of numbers
- Arrows instead of values
- One screen, no scrolling, no clicking
- Keep the numbers on a second page
- The "manager's manager" test
- The one-screen template
- Pitfalls
- The checklist
- Where to go next
The reader who cannot ask
The management dashboard is the one screen you build that will be read without you in the room. The guide on what dashboards are for defines a dashboard as one question for one audience at a glance. It names management as the third audience, the one asking "are we meeting our commitments?" This guide is about designing that screen to answer without help, because help will not be requested.
A manager cannot ask what a panel means for three practical reasons. They open the page at seven in the morning, before you are in. They are often looking because someone else has asked them a question, and they need an answer now, not a conversation. And admitting they do not understand a screen from their own department feels like admitting they do not understand their own department. None of that is unreasonable. It just means the screen must carry its own explanation.
The consequence is a design rule you will not need for any other screen: every panel must survive being misread. Ask of each one, "if someone assumed the worst about this, what would they assume?" Suppose the honest answer is "that the network is losing data" or "that we need to spend money". If neither is true, the panel is not finished.
This is also why the manager's screen is not the wall screen in a smaller font. The NOC wall is read by a room that knows what the tiles mean. The manager's page is read by one person who does not, and who will form a view anyway.
The three questions a manager is actually asking
Underneath every request for "a dashboard with the key metrics", a manager is asking three questions, and only three. Are we all right now? Is anything getting worse? Is anything going to cost money? Every column, panel, and word on the page should answer one of those, and anything that answers none of them is decoration.
"Are we all right now?" is a status question, and its answer is a word, not a number. The manager does not want the latency of the internet link. They want to know whether the internet is fine, and if not, whether someone is dealing with it. The classic form of this answer is the network health scorecard: a short list of named services, each with a grade.
"Is anything getting worse?" is a trend question, and its answer is a direction. Better, steady, or worse, compared with last month. A manager who sees "worse" beside the file server will ask about it, which is what you want. A manager who sees "steady" will move on, which is also what you want.
"Is anything going to cost money?" is a forecast question, and its answer is a date or a plain "no". "File server storage: full in about seven months" is an answer a manager can plan around. "Disk 78%" is a number they will either ignore or panic about, depending on their last meeting. (There is no third option.)
Labels that explain themselves
A panel label on the manager's page must name the thing in the words the manager uses for it. You call it wan0. The manager calls it "the internet at head office". Both are correct, and only one will be understood by the person reading the page, so use that one. Where you must keep the technical name for your own sake, put it on the second page.
The rule for a self-explaining label is that it names the service, the place, and, where it matters, the people affected. "Wi-Fi in the warehouse" beats "AP cluster B". "Phones at the Riverside office" beats "SIP trunk 2". A label a new starter in accounts could read aloud and understand will survive being read by a director.
| What the monitoring tool calls it | What the manager's page calls it |
|---|---|
wan0 utilisation in | Internet at head office |
fs01 C: % free | File server storage (everyone's shared drives) |
AP-07 client count | Wi-Fi in the warehouse |
SIP trunk 2 registration | Phones at the Riverside office |
DC01 LDAP response | Staff logins |
Backup job NIGHTLY-FULL | Last night's backup |
ups01 battery runtime | Server room power protection |
If you find yourself writing a label that needs a footnote, you have found a panel that belongs on the second page.
Words instead of numbers
A status word is a single plain word that replaces a number and carries a judgement with it: Fine, Watch, or Problem. The judgement is the point. A number asks the reader to know the threshold; a word tells them the threshold has already been applied by someone who knows. "Packet loss 0.4%" is a number. "Fine" is a verdict, and the manager wanted the verdict.
Pick three words, define them once at the top of the page, and use no others. My set is below. The exact words matter less than the fact that there are only three and their meanings are written where the reader can see them.
| Status word | What it means on this page | What the reader should do |
|---|---|---|
| Fine | Working normally; nothing for IT to act on. | Nothing. |
| Watch | Working, but a measure is outside its usual range, and IT is aware. | Expect to hear from IT if it changes. |
| Problem | Not working properly for some or all users; IT is acting on it. | Read the note beside it. |
Notice that "Watch" and "Problem" both say IT already knows. That sentence does more for your reputation than any graph. The fear behind most management questions is not "is it broken" but "does anyone know it is broken". Put the answer in the vocabulary and every row answers it.
Colour may accompany the word but must never replace it. A green cell that says "Fine" works for everyone, including the reader who cannot tell green from amber and the reader holding a black-and-white printout. A green cell with no word works for neither.
Arrows instead of values
A trend arrow shows the direction of a measure over a period without showing the measure. Better, steady, worse; up, flat, down. It answers the second question directly, without requiring the reader to hold last month's number in their head. They do not, because it is not their job to.
Define the comparison period and the band that counts as "steady", and write both on the page. "Compared with the previous month; a change under ten per cent counts as steady" is enough. Without the band, every wobble becomes an arrow, and a page of arrows pointing in different directions tells the reader only that something is happening.
If your monitoring tool does not draw the arrows for you, a spreadsheet will. With last month's value in column B and this month's in column C, for a measure where lower is better (latency, incidents, disk used):
=IF(C2>B2*1.1,"Worse",IF(C2<B2*0.9,"Better","Steady"))
For a measure where higher is better, such as availability, swap the two words. The 1.1 and 0.9 are the ten per cent band from the note on the page, and they are an example. A measure that swings naturally by twenty per cent needs a wider band. Otherwise, every month will be "Worse" then "Better" and the arrows will mean nothing. What is a baseline covers learning a measure's normal swing.
One screen, no scrolling, no clicking
The whole page must fit on one screen of an ordinary laptop, with nothing below the fold and nothing that has to be clicked to be understood. A manager reads what is visible when the page opens and nothing else. The row that needed a scroll is the row they will later say was not on the dashboard.
One screen means about eight to twelve rows. If you have more services than that, group them. "All branch offices: Fine" with a note listing exceptions is one row, and a better row than twelve identical ones. Service-based monitoring is the discipline of naming services rather than devices, and it produces exactly the rows this page needs.
A weekly refresh is fine, and for most of this page it is better than real-time. The status column can update as often as the monitoring does. But the trend and forecast columns should change on a schedule the reader can predict. That way, "this month" means the same thing every time they look. Put the date the page was last built in the top corner in plain words: "Data to Friday 5 pm". A page with no date will be assumed current, and one day it will not be.
Real-time graphs on a management page have one reliable effect: the reader watches the graph. It moves, so it must matter. (It does not.)
Keep the numbers on a second page
The numbers do not disappear; they move. Every row on the one-screen page can link to a second page showing the measures behind the word. These are the availability figure, the month's graph, the threshold that made it "Watch", and the technical names you removed from the first page. The manager who wants to know more can open it. The manager who does not is never made to.
Write the second page for the second reader, which is often the manager's technical adviser, an auditor, or you in six months. It can be dense. It can have acronyms. It still needs units and dates on every graph, because the person opening it is opening it precisely to check something. A graph with no date cannot be checked. Report templates per audience applies the same two-layer idea to reports. The link between the pages should say what it is: "Show the measurements" beats "Details".
The "manager's manager" test
The test for a management page is whether your manager's manager would understand it without anyone in the room. Not your manager, who has absorbed some of your vocabulary over the years. The person above them, who has not, and who may one day be forwarded the page with the question "should I be worried?"
Run it like this. Print the page, or open it on a screen with no mouse. Hand it to a colleague outside IT and ask them to tell you, in one sentence per row, what each row is saying. Do not help. Do not explain. Write down every row they got wrong or hesitated over, and fix those rows. Then do it again with a different colleague, because the first one was being polite.
Two outcomes count as failures. The first is any row they misread as worse than it is, because that is the row that will start a rumour. The second is any row they could not summarise at all. A row that says nothing on a management page will be filled in by the reader's imagination.
At Northgate Retail the finance director opened the IT dashboard one Monday and saw "Packet loss: 0.4%" in red beside the head office link. She asked, by email, whether the 0.4% was money. Nobody in IT read the email until Tuesday. By then it had been forwarded to the operations director with the subject line "network losing data?" and a meeting had been booked. The row now reads "Internet at head office: Fine". The note says "slight loss, within normal range". And the number lives on the second page with a sentence explaining what a fraction of a per cent of lost packets does and does not mean. The meeting still happened.
The one-screen template
Here is the page. One row per service, in the order the manager would list them if asked what IT is for, which is rarely the order you would choose. Five columns, with the status vocabulary and the trend period defined in a line under the title. Copy the table, replace the rows, and resist the sixth column.
| Service | Status | Trend (vs last month) | Note | Owner |
|---|---|---|---|---|
| Internet at head office | Fine | Steady | Network admin | |
| Internet at branch offices | Fine | Steady | Riverside link upgraded last month | Network admin |
| Staff logins | Fine | Steady | Server admin | |
| Fine | Better | Queue delays from last month resolved | Server admin | |
| Phones | Watch | Worse | Call quality complaints at Riverside; investigating the new link | Network admin |
| File server storage | Watch | Worse | Full in about 7 months at current growth; proposal due next month | Server admin |
| Wi-Fi | Fine | Steady | Network admin | |
| Last night's backup | Fine | Steady | All jobs completed; test restore done this month | Server admin |
| Server room power protection | Fine | Steady | Battery replacement scheduled | Facilities |
The note column is where the third question gets answered. A blank note means "nothing to add", and a page with mostly blank notes is a page reporting a healthy network. A note is one sentence, in plain words, saying either what is being done or when something will happen. "Full in about seven months; proposal due next month" is a forecast and a plan in nine words. It is the row most likely to be quoted back to you approvingly. Utilisation to purchase timing covers turning a growth graph into that kind of date.
The owner column names a role, not a person, because people go on holiday and pages outlive them. Its job is to answer "who do I ask?" before the question is asked.
Tip: if your monitoring tool can build this page from its own service definitions, let it. In that case, send the link rather than a screenshot. A screenshot is frozen on the day it was taken and will be forwarded for months. If the tool cannot, a spreadsheet rebuilt on a schedule is an honest substitute. The guide on killing hand-built spreadsheets explains how to stop it being hand-built.
Pitfalls
Three mistakes account for most management pages that fail the test, and each one felt reasonable when the page was built.
Colour without words
A row that is green but says nothing relies on the reader knowing that green is good and being able to see green. It also relies on them trusting that whoever chose green meant "fine" rather than "on". Some readers cannot distinguish the colours you chose. Some will read the page printed. All of them deserve the word. Colour is a highlight, and a highlight of nothing is nothing.
Acronyms
Every acronym on the page is a small test the reader might fail in private. They will not tell you they failed it. They will simply value the page a little less. And the next time someone suggests the monitoring budget could be trimmed, the page will not defend itself.
Gauges with no scale meaning
A gauge is a dial with a needle, and it works only when the reader knows what the far end of the dial means. A fuel gauge works because "empty" is a universal concept. A gauge showing "CPU 62%" does not, because the reader does not know whether 62 is near the edge. A needle two-thirds of the way round a dial looks like a warning to anyone who drives a car. If a gauge cannot be labelled in words the reader already understands, replace it with a status word.
The checklist
Before the link goes out, walk the page against this list. Every line is a yes or a no.
- The audience is named: a specific manager or role who will not ask questions.
- The page answers all three questions: all right now, getting worse, going to cost money.
- Every label names a service and a place in the manager's own words, with no unexplained acronyms.
- Status is a word from a set of three, defined on the page.
- Trend is a direction, with the comparison period and the "steady" band written on the page.
- Every note is one sentence that says what is being done or when something will happen.
- Every row has an owner role.
- The whole page fits on one laptop screen; nothing needs a click, hover, or legend.
- The date of the data appears in plain words at the top.
- A second page holds the numbers, with units and dates on every graph.
- A colleague outside IT has summarised every row correctly without help.
- A review date is on the calendar.
Where to go next
The manager's page is the quietest dashboard you will build and the one that travels furthest. It will be forwarded, screenshotted, and quoted in meetings you are not in, and every word on it will be taken at face value. Write it so that face value is the truth: plain labels, three status words, a direction, a note, an owner, and a date. Then keep the numbers one click away for anyone who wants them, and be pleased when nobody does.
For the screen at the other end of the building, read the NOC wall. Visual hierarchy covers the position, size, and colour rules that apply to any screen. The design review checklist shows a forty-panel screen being split into exactly these two. All of them are part of Dashboard Design: The NOC Wall vs. the Boss's Browser.
Put this into practice with SysPeep Monitor
The hard part of a management page is having trustworthy status behind every plain word. SysPeep Monitor collects device and service health over SNMP, WMI, and SSH. It applies thresholds and dependency rules so a row means what it says. It presents dashboards and reports from one web console you can share by link rather than screenshot. The free trial installs on a Windows machine if you want to build the table above against your own network.
Download Free TrialLearn About SysPeep