Home › Topics › Translating Monitoring Data for Management › The Monthly One-Pager

The Monthly One-Pager a Finance Director Understands


The monthly report took you most of a day. It has the availability graph for every service and a table of alerts by severity. It has the bandwidth charts for both internet lines, and an appendix of disk space per server. It went to the finance director on the first of the month. On the fourth, she asked you in the lift whether the network had been all right lately.


She was not being rude. She had opened the report, seen a page of graphs with legends, and closed it. That was because nothing on the first page told her whether she needed to do anything. A finance director gives each document the attention it earns in the first ten seconds. Yours earned ten seconds.


This guide replaces that report with one page, built around four questions a finance director actually has. You will learn what goes in each box and which single number from the monitoring data answers it. You will learn what to leave out, where each figure comes from and how long it should take. You will get a layout you can copy this afternoon. The report gets shorter. The attention does not.


In this guide

  • Why one page
  • The four boxes
  • One number per box
  • What to leave out
  • Where each number comes from
  • The layout template
  • A filled example
  • The plain-English footnote convention
  • A war story
  • The one-pager checklist
  • Where to go next

Why one page


One page is the length a busy reader gives to something that is not their own work. A finance director's month is budgets, forecasts, the auditors, and the board pack. Your report competes with all of it for a slot of attention measured in minutes, and a page fits in the slot. Nine pages do not; they get "I'll read it properly later," which is a filing decision dressed as a promise.


One page also forces the decision that is the real work: what mattered this month. A long report lets you avoid choosing. And every graph you include is a choice handed to a reader less equipped to make it than you. That choosing is what the finance director is paying for. The graphs are only where you got it from.


A page has an edge, and a report does not. Reports grow. Nobody has ever removed a section from a monthly report; sections are only added, usually because someone asked once, and then that someone left. (The section stays. It is loyal.) A single page cannot grow without something else being cut, which is the only discipline that has ever kept a report readable.


The guide to reports people actually read makes the general case: lead with the answer, show trends rather than snapshots. The one-pager is that advice applied to one reader with one question: does anything need her?


The four boxes


The page has four boxes, and each one is a question the finance director would ask if she had time to. Are we OK? What changed? What is getting worse? What do you need from me? Answer them in that order, and print the titles as questions rather than headings. "Availability summary" is a heading. "Are we OK?" is a question she recognises as her own.


Box one: Are we OK?

Box one says whether IT stopped anyone working this month. The finance director does not care whether a switch rebooted; she cares whether the warehouse stood still and for how long. The box holds one number: the hours in the month during which a service most staff depend on was unavailable in working hours. It also holds one sentence naming what it was. If the number is zero, say zero, and say it plainly. "No IT problem stopped anyone working this month" is the best sentence in the report, and it belongs at the top.


Box two: What changed?

Box two lists what happened this month that she would want to know about, in at most three lines with dates. A new internet line went live. The core switch was replaced on the Saturday. These lines explain why box one looks the way it does, and they are the things that turn up in conversation. If a director hears from the sales manager that "IT changed something," she should already know what.


Box three: What is getting worse?

Box three is the one that earns the report its keep. It names the one thing in the monitoring data that is trending toward a limit, and the date it gets there at the current rate. The shared drive fills in about eleven weeks. There will be several trends in the data; pick the one that arrives soonest or hurts most, and put the rest in a footnote. A box with five trends is a box with none.


Box four: What do you need from me?

Box four is the ask, and the finance director will read it first whatever order you put it in. It says what decision you need, by when, what it costs, and what happens if there is no decision. If you need nothing, write "nothing this month," because a blank box looks like a mistake. A report that never asks for anything trains its reader that it never needs reading. The phrasing of the ask is the fourth rung of the ladder in Speaking Business, Not Packets.


One number per box


Each box should carry one number where it can, because one number is what a reader remembers. The finance director will not remember your availability percentages, but she will remember "four hours," and she will notice when next month says "nine." A figure that changes month to month is a trend. And a trend is the only thing on the page that persuades anyone of anything.


BoxThe one numberCounted fromNever includes
Are we OK?Hours users could not work because of ITAvailability report, core services, working hours, unplanned onlyPlanned maintenance, test systems, outages nobody noticed
What changed?Changes made or incidents closed (up to three, dated)Change log, alert history filtered to resolvedAlerts that cleared themselves, routine patching
What is getting worse?The date the worst trend crosses its limitTrend graph over ninety days with a limit lineTrends more than a year from a limit
What do you need from me?The cost of the ask and the decision dateQuote from procurement, your own hours, the risk registerYour guess at a supplier's price

The number in box one needs the most care, because it is the one she will quote to the board. Count only hours in which a service most staff depend on was unavailable, during working hours, for a reason not announced in advance. Maintenance at six on a Saturday does not go in. The guide to honest availability math covers the arithmetic; the one-pager needs only the result and a footnote.


Averages go nowhere near this box. An average availability across six services turns one dead system into a rounding error. And the rounding error is the department that could not work. Report hours and name the service. If a number cannot be sourced from the monitoring data, leave it off.


What to leave out


Leave out everything the finance director cannot act on, which is most of what the monitoring system produces. Raw graphs with legends. Device names and port numbers. CPU and memory percentages. Response times in milliseconds. The count of alerts by severity, which measures how noisy the monitoring is rather than how healthy the network is. The bandwidth chart for each internet line, unless one of them is the trend in box three.


Leave out the incident timing metrics. Mean time to detect is the average delay before a fault is noticed. Mean time to repair is the average time to fix it once it is noticed. These are useful numbers with a place of their own. That is the quarterly review described in reporting incident metrics to management. On a monthly page for a finance director they are two more figures competing with the four that matter.


Leave out the engineering scorecard. If your team keeps a one-page network health scorecard, that is the page for the people who fix things, with error counts and utilisation on it. The one-pager is its business-facing cousin, and the two should never be the same document. A scorecard tells an engineer where to look. A one-pager tells a director whether to worry.


Leave out good news that needs a chart to prove it. "Availability was 99.6 percent" needs a definition and a comparison before it means anything; "no IT problem stopped anyone working" needs nothing. A page that says "nothing broke, here is the one trend, I need nothing" is a good month reported well.


Where each number comes from


Every figure on the page comes from a report the monitoring system already produces, or should. The work of the one-pager is not gathering numbers; it is choosing four and writing the sentences around them. If the gathering takes longer than the writing, the reports are not set up yet. The guide to report templates per audience covers building a management-facing report the system runs for you. And scheduled delivery gets it into your inbox on the first of the month.


BoxMonitoring sourceTime
Are we OK?Availability report for the month, core services only, working hours; alert history for the dates and durations10 minutes
What changed?Change log; alert history filtered to incidents resolved this month10 minutes
What is getting worse?Capacity and utilisation trend graphs, ninety-day view with the limit drawn on; one projection sum15 minutes
What do you need from me?Risk register; quote from procurement; your own estimate of hours10 minutes
Writing and footnotesLast month's page15 minutes
TotalAbout an hour

The projection in box three is the only arithmetic on the page. Read two points off the trend graph thirty days apart, and the date comes out of one spreadsheet cell:


=TODAY() + (B1 - B2) / ((B2 - B3) / 30)

B1   the limit           (for a disk, the size of the volume)
B2   used today          (read from the graph)
B3   used 30 days ago    (read from the graph)

Result: the date the line crosses the limit at the last
month's rate of growth.

The formula assumes the last thirty days are typical. Check the date against a ninety-day view before you write it down, and say "at the current rate" in the footnote every time. A month with a big project in it gives you a date that is wrong by a season, in whichever direction embarrasses you more.


If you can query the monitoring database directly, the outage hours for box one are a count rather than a hunt. Table and column names differ between products, so treat this as the shape and check the documentation for yours:


SELECT SUM(duration_minutes) / 60.0 AS hours_down
FROM   outages
WHERE  service_tier = 'core'
AND    planned      = 0
AND    started_at  >= '<first day of month>'
AND    started_at  <  '<first day of next month>';

Compare the query's answer to the availability report for the first few months. When the two agree, you have a number you can put your name to.


Tip: produce the page for two months before you show it to the finance director. The first attempt always has a definition you want to change. Changing one after she has seen the number means explaining why last month's four hours has become six.


The layout template


The template below is the whole page. Copy it into whatever document tool the finance director already uses, keep the box order, and fill the blanks from the table above. The numbered footnotes are where the definitions live; the boxes stay clean.


IT MONTHLY ONE-PAGER            Month: __________    Prepared by: __________

1. ARE WE OK?
   Hours this month that IT problems stopped people working: ____ [1]
   (last month: ____)
   What it was: ______________________________________________
   One sentence: _____________________________________________

2. WHAT CHANGED?
   - ______________________________________________ (date)
   - ______________________________________________ (date)
   - ______________________________________________ (date)

3. WHAT IS GETTING WORSE?
   ____________________ reaches its limit around __________ [2]
   at the current rate.
   What happens then: ________________________________________
   Plan: _____________________________________________________

4. WHAT DO YOU NEED FROM ME?
   Decision: _________________________________ by __________
   Cost: __________ (quote attached / hours of IT time / none)
   If no decision by then: ___________________________________

Footnotes (one line each, plain English)
   [1] Counts: __________  Excludes: __________  Source: __________
   [2] Counts: __________  Excludes: __________  Source: __________
   Other trends watched, none within twelve months of a limit: ______

All figures from the monitoring console reports for the month.

A filled example


Here is the page for a fictional parts distributor, Meridian Parts, in a month with one outage and one trend worth naming. Every figure is invented, and the currency is whatever yours is.


IT MONTHLY ONE-PAGER            Month: this month    Prepared by: J. Okafor

1. ARE WE OK?
   Hours this month that IT problems stopped people working: 2.5 [1]
   (last month: 0)
   What it was: the warehouse scanners lost the network on the
   afternoon of the 14th when a switch failed.
   One sentence: dispatch stopped for the afternoon; the switch was
   replaced the same day.

2. WHAT CHANGED?
   - Failed warehouse switch replaced with the spare (14th)
   - Second internet line went live; switch-over tested (22nd)
   - Phone provider fixed last month's call quality fault (9th)

3. WHAT IS GETTING WORSE?
   The shared drive reaches its limit around the 20th of the month
   after next [2] at the current rate.
   What happens then: staff cannot save files until space is freed.
   Plan: archive last year's project folders (free, needs project
   managers' sign-off) or add storage (quote attached).

4. WHAT DO YOU NEED FROM ME?
   Decision: archive old projects, or buy storage       by the 30th
   Cost: archive, none; storage, quote attached; 4 hours of IT time
   either way
   If no decision by then: I will start the archive, as the free
   option, and tell the project managers why.

Footnotes
   [1] Counts: working hours (08:00-18:00, Mon-Fri) in which a
       service most staff use was unavailable.  Excludes: maintenance
       announced two days ahead.  Source: availability report.
   [2] Counts: space used on the shared drive, projected from the
       last 90 days.  Source: disk trend graph, file server.
   Other trends watched, none within twelve months of a limit:
   internet line peak use; warehouse Wi-Fi client counts.

All figures from the monitoring console reports for the month.

Notice what the finance director can do with it in two minutes. She knows one thing went wrong, what it stopped, and for how long. She knows the shared drive is on a clock. And she knows that there is a decision with her name on it, a date, and a free option. She does not know what a volume is, and she does not need to. The last line of box four means the page never needs chasing: the clock, it says politely, does not stop for her diary.


The plain-English footnote convention


Every number in the boxes gets a numbered footnote that says in one line what it counts and what it leaves out. The boxes stay clean. The definitions are on the page for anyone who wants them. And the same number means the same thing every month. That is why a finance director can trust a figure she did not calculate herself.


A footnote has three parts: what is counted, what is excluded, and where it came from. The word that does most of the work is "excludes," because it is the word that stops a good month from being suspected of being a redefined one.


Write the footnotes once and reuse them. If a definition must change, say so in that month's footnote and show both numbers side by side. A number whose definition moves quietly is worse than no number, because the first person to notice will be the one you least want to.


The footnotes are also where the second and third trends go, the ones that did not make box three. One line, no numbers. The page stays one page. The director knows you are watching more than one thing. When the internet line does become box three in the spring, nobody can say it came from nowhere.


A war story


The IT manager at Northgate Retail sent a nine-page monthly report for two years. It had a page of availability graphs and a table of every alert sorted by severity. It had the bandwidth charts for both internet lines, and an appendix of disk usage per server. The finance director's assistant filed each one in a folder named after the month. When the IT manager asked for money to replace the core switch, the finance director said she was surprised. That was because she had not heard of any problems. The rising error count on that switch had been on page seven, in a chart, every month for six months. The review described the report as comprehensive.


One page would have carried the switch in box three, with a date, for six months running. And the request in box four would have been the fourth time she had seen it rather than the first. Nine pages held more information and delivered less of it. That is the usual ratio.


The one-pager checklist


Run the page through this list before it goes out. It takes about as long as the finance director will give the page itself.


  • The page fits on one side, in the finance director's own document tool, and the boxes are titled as questions.
  • Box one leads with whether anyone was stopped from working, and says so plainly when the answer is nobody.
  • Each box carries one number taken from a monitoring report, with a footnote.
  • Box three names one trend and one date, with the other trends in a footnote.
  • Box four contains a decision, a date, and a cost, or the words "nothing this month."
  • No graph, device name, port number, CPU percentage, or millisecond appears on the page.
  • Every footnote says what is counted, what is excluded, and where it came from.
  • The definitions match last month's, or the change is stated and both numbers are shown.
  • Producing it took about an hour; if it took a day, the reports behind it need automating.
  • It went out on the same day of the month as last time.

Where to go next


The one-pager is the written form of the four questions that the manager's dashboard answers live on a screen. If you build both, keep the definitions identical. Framing Monitoring Findings as Risk and Cost is where the cost in box four comes from. The article Presenting Monitoring Data in a Meeting covers the month she asks you to walk her through it. And Building a Budget Case From Monitoring Data is what box four becomes when the ask outgrows a quote. All of them live under Translating Monitoring Data for Management.


Put this into practice with SysPeep Monitor

The four numbers on this page come from reports the monitoring system runs anyway. SysPeep Monitor builds dashboards and reports from one web console over what it collects by SNMP, WMI, and SSH. It can send scheduled reports by email so the availability and trend figures are waiting in your inbox on the first of the month. Check the product documentation for the report types available. The free trial installs on any Windows machine in minutes.

Download Free TrialLearn About SysPeep