Home › Topics › Making Invisible Work Visible With Monitoring Data › What Do We Pay You For

Answering "What Do We Pay You For?" Without Getting Defensive


Sooner or later someone with a budget will ask it, in a corridor or a meeting or an email with no greeting: "Remind me what we pay you for?" It lands like an accusation, and the reflex is to answer like one has been made. You start listing things. You explain how monitoring works. You mention the weekend you spent on the storage array. Somewhere around the third item the person who asked has stopped listening. That is because the answer they wanted was a page and what they are getting is a speech.


The question is usually not hostile. It is a request for a document that does not exist yet. That document is a short, factual record of what the team kept running, what it caught before it broke, and what it is doing about what is left. The person asking does not have that page, and has never had it. They are asking in the only words available to someone who cannot see the work. I have been asked it three times in my career, and the first two times I gave a speech.


By the end of this guide you will be able to recognise the question for what it is. You will be able to avoid the three wrong answers. You will be able to give the three sentences that answer it. You will be able to build the one-page record those sentences rest on from the logs in the rest of this pillar. You will be able to keep the tone calm, and follow up so the question does not come back. And you will be able to handle the rarer case where it really is hostile.


In this guide

  • The question is a request for a page
  • The wrong answers
  • The three sentences
  • The one-page record
  • Tone: calm, factual, brief
  • The follow-up
  • When the question is hostile
  • The meeting where the page did the talking
  • The conversation script
  • The checklist
  • Where to go next

The question is a request for a page


"What do we pay you for?" is what a person says when they have a cost with no record next to it. The cost is visible: a salary line, a licence, a support contract. The record is not, because nothing about a service staying up produces a document on its own. The invisible work problem explains why. An outage is an event and its absence is not, so a year of good work leaves no trace unless someone leaves one.


Hearing the question as a request changes what you do next. A request is answered by handing something over. If you have the page, you hand it over and the conversation is short. If you do not, the honest answer is "I will have that for you by Friday", followed by the page on Friday. What you should not do is treat the question as a verdict, because it is not one yet. It becomes one if the page never arrives.


The page is built from records that this pillar has already described. These are the work log, the quiet month reports, the availability record, and the prevented-incident log. If those exist, the page takes an hour. If they do not, start them today; the page you produce this week will be thin, and the one you produce next year will not be.


The wrong answers


Three answers come naturally, and each one fails for a reason worth understanding, because the reason points at what works.


The list of everything you did

The first reflex is to prove effort: patches, tickets, the firewall upgrade, the printer, the weekend. It fails because effort is not what was asked about. The person asking does not doubt that you are busy; they doubt that the busyness connects to anything they care about. A long list also reads as defensive, however calmly delivered, because nobody produces a long list unless they feel accused. The record that works is short, and it names outcomes, not tasks.


The sigh

The second reflex is exasperation: the pause, the look, the "well, if you have to ask". It fails because it converts a request into a conflict, and conflict is the only version of this conversation you can lose. The person asking is not being unreasonable; they are missing information. Treating a missing page as an insult guarantees that the next time they need the information, they will ask someone else.


The offer to resign

The third reflex, usually after the sigh, is "if you don't think I'm worth it, I can go". It fails because it is a bluff the other person did not ask for. It makes the conversation about you rather than the infrastructure. Occasionally someone accepts it. (Nobody has ever been asked "what do we pay you for?" and answered "here is a page" and then been shown the door. I have looked.)


All three wrong answers share a root: they respond to the feeling of the question instead of its content. The content is "show me". The right answer is a page, and the page is three sentences long before it is anything else.


The three sentences


The answer fits in three sentences, and each sentence is backed by a record you already keep. Say them in this order; the page underneath is the evidence.


What we kept running

"The five services the business depends on were available for over 99.9 per cent of working hours this year, with one interruption longer than an hour." This is the availability record described in uptime reporting as reputation defence. The record provides one number per service per month, from the monitoring system, planned windows excluded, kept for years. State the worst service honestly and the interruption honestly; the sentence is stronger for containing them.


What we caught before it broke

"We recorded nine prevented incidents this year; three would have stopped invoicing, and each has a graph." This is the prevented-incident log from counting the outages you prevented, kept under the conservative rules so that every entry survives a question. Name the top three in business terms and stop. Do not attach a cost figure you did not derive.


What we are doing about the risks that remain

"The internet link reaches capacity in about four months and the backup server is out of support next year; both are in the budget request with dates." This is the "what is coming" section of the quiet month report, gathered over the year. It is the sentence that turns the conversation from the past to the future. And it is the one most people forget, because it admits that things are not perfect. Say it anyway. A record with no remaining risks is a record nobody believes.


Three sentences, three records, no adjectives. The person who asked now knows what stayed up, what did not fall over because of you, and what you need from them. If they want more, the page is underneath. If they do not, you are done, and the conversation lasted a minute.


The one-page record


The one-page record is the document behind the three sentences. It is a single page, rebuilt once a year and refreshed once a quarter. It is assembled from the work log, the quiet month reports, and the availability record. It is joke-free and adjective-free, and it fits on one side. Copy the template and fill in the placeholders from your own records.


IT RECORD  -  <team>  -  twelve months to <month>

WHAT WE KEPT RUNNING
   <service>: <xx.xx%>   <service>: <xx.xx%>   <service>: <xx.xx%>
   Unplanned interruptions over one hour: <count>  (longest: <duration>, <service>, <month>)
   Method: monitoring checks every <n> seconds; planned windows excluded.
   (source: availability record)

WHAT WE CAUGHT BEFORE IT BROKE
   Prevented incidents recorded: <count>
   Top three:
   - <month>: <signal>; <action>; would have <consequence in business terms>.
   (source: prevented-incident log; every entry has evidence)

CHANGES MADE SAFELY
   Maintenance windows completed: <n> of <n> planned; follow-up incidents: <count>
   (source: change record; alert history after each window)

CAPACITY BOUGHT BEFORE THE PAIN
   - <resource>: <bought or extended> in <month>, <n> weeks before projected limit.
   (source: capacity register; trend graphs)

WHAT IS NEXT
   - <resource or risk>: <trend or condition>; decision needed by <date>; <in budget / not yet>.
   (source: quiet month reports, "what is coming")

Full records available on request. Next update: <date>.

Each block maps to one source, and the sources are the point. The availability line is copied from the record, not recomputed. The prevented-incident count is the number of rows in the log that were not withdrawn. The windows come from the change record. The "what is next" block is the last few quiet month reports' final sections, merged. Nothing on the page is written from memory, which is why it can be handed to a sceptic.


If the records live in spreadsheets, the counts are formulas rather than typing, which means the page cannot drift from the logs. These are illustrative; adapt the sheet and column names to your own layout:


Illustrative spreadsheet formulas (adapt sheet and column names)

Prevented incidents in the last twelve months, excluding withdrawn rows
(Prevented sheet: column A = date, column G = status):
   =COUNTIFS(Prevented!A:A, ">="&EDATE(TODAY(),-12), Prevented!G:G, "<>withdrawn")

Worst month for one service in the last twelve months
(Record sheet: column A = service, column B = month end, column C = availability):
   =MINIFS(Record!C:C, Record!A:A, "Invoicing", Record!B:B, ">="&EDATE(TODAY(),-12))

The worst-month formula is deliberate. The page shows each service's availability and, if asked, its worst month. It never shows an average across services. That is because the person asking will find the one service that was bad and wonder what else the average hid.


Tip: build the page once, before anyone asks. The first version takes an afternoon because you will discover which records are missing. The second version takes an hour. The version you build the evening before a meeting, from memory, takes all night and convinces nobody, including you.


Tone: calm, factual, brief


The page and the three sentences work because of how they sound, and they sound the same way: calm, factual, brief. Calm means no defence and no complaint; the page does not say how hard the year was. Factual means every line is a number or a dated event with a source, and nothing is "critical", "proactive", or "robust". Brief means one side of one page and three sentences aloud. Anything longer is a speech, and a speech is the first wrong answer wearing a suit.


The translation into business terms is what makes the facts land, and it happens at the moment of writing each line, not in the meeting. "Volume extended" means nothing to the person asking; "invoicing would have stopped saving" means everything. Speaking business, not packets is the full guide to that translation. The rule here is simply that every consequence on the page names a service the reader uses and the people who would have noticed.


If you find yourself adding a sentence that begins "to be fair" or "what people don't realise", delete it. The page is not fair or unfair. It is a record, and records do not have feelings about being read.


The follow-up


The question comes back unless something arrives regularly in its place, so the follow-up is to offer the monthly quiet month report. "I can send you a short version of this every month, one page, same shape, so you have it before you need it." Most people say yes, because they have just discovered they would like to know this and had no way to find out. Then send it, on the same day each month, and the question is retired, because the answer is already in their inbox when it forms.


If the person asking signs the budget, the monthly one-pager, with its four finance-facing boxes, may suit them better than the IT-team version. In that case, offer whichever they will read. Reports people actually read is honest about how few reports survive their third month. The ones that do answer a question the reader already has, and this reader just asked it out loud.


When the question is hostile


Sometimes the question really is hostile: a budget has to be cut, a decision has been half-made, and the question is a formality on the way to it. The answer is still the same page. The page is not a defence; it is a record, and a record does not change depending on who is reading it or why. If the decision is going to be made regardless, the page ensures it is made with the facts in the room. That is the most you can do and is not nothing.


What changes in the hostile case is only the follow-up. Hand over the page and say the three sentences. Then say what the record implies about the proposed cut, once, without heat: "If the monitoring goes, the nine catches on this page become nine outages next year, and the availability line becomes an estimate." Then stop. The person deciding either wants to know that or does not, and no amount of further talking changes which. Justifying monitoring spend covers the budget case in full if the conversation moves to numbers.


If you are the only administrator, the hostile version is harder to hear, because the page is about you as much as the infrastructure. It is still just a page. Solo admin burnout is about the cost of carrying the record in your head; the page is one way of putting it down.


The meeting where the page did the talking


At Acme, the new finance director scheduled thirty minutes with the IT manager under the heading "IT costs review". The IT manager, who had been keeping the records for two years, brought one sheet of paper and said three sentences. The director read the sheet for about a minute. She asked what "prevented incident" meant, and was shown the log's top entry with its graph. Then she asked whether the internet link upgrade on the "what is next" line was already costed. It was. She approved it in the meeting, asked for the page quarterly, and used the remaining twenty minutes to ask about something unrelated. The IT manager's notes for the meeting, prepared over the previous weekend and running to four pages, stayed in the folder.


The page did the talking because it was the only thing in the room that could be checked. Every line pointed at a record; every record pointed at the monitoring system. The finance director did not have to trust the IT manager, whom she had never met. She had to trust the page, and the page had a source for everything on it.


The conversation script


This is the shape of the exchange when it goes well. It is not a script to recite. It is the order of things and the length of each, so that you notice when you are drifting into a speech.


THEM:  Remind me what we pay you for?

YOU:   Three things. I have a page; here it is.
       First, the services the business depends on were available
       <xx.x> per cent of working hours this year, with <n>
       interruption(s) over an hour.
       Second, we recorded <n> prevented incidents; <n> of them
       would have stopped <service>. Each has evidence.
       Third, <resource> reaches its limit in about <n> months and
       <risk> is unresolved; both are in the budget request with dates.

THEM:  What is a prevented incident?

YOU:   A monitoring signal, an action we took because of it, and a
       specific failure that did not happen. Here is the top one,
       with the graph.  [show one entry]

THEM:  How do I know these numbers are right?

YOU:   Every line has a source on the page. The availability figures
       come from the monitoring system's reports, planned maintenance
       excluded, and the raw data is available on request.

THEM:  Fine.

YOU:   I can send a one-page version of this every month, same shape,
       so you have it before you need it. Shall I?

[Stop talking.]

The last line is the important one. Every version of this conversation that went badly for me went badly after the point where I should have stopped. The page has answered the question; anything you add is you answering a question that was not asked. And the person listening will wonder why.


The checklist


Run through this before the page goes into anyone's hands, and once a quarter whether or not anyone has asked.


  • The page fits on one side and has no adjectives.
  • The availability line is copied from the availability record, per service, planned windows excluded, with the method stated.
  • The worst service and the longest interruption are on the page, not hidden.
  • The prevented-incident count matches the number of non-withdrawn rows in the log, and the top three are in business terms.
  • No cost figure appears unless it was derived from stated assumptions.
  • The "what is next" block has at least one item, each with a date and a budget status.
  • Every block names its source, and every source exists and can be produced on request.
  • You can say the three sentences aloud, from the page, in under a minute.
  • The offer of a monthly report is ready, and you know which version the reader would use.
  • The page was built before anyone asked, and the next update date is on it.

Where to go next


"What do we pay you for?" is a request for a page that does not exist yet. The wrong answers — the list, the sigh, the offer to resign — all fail because they answer the feeling instead of the request. The right answer is three sentences: what we kept running, what we caught before it broke, and what we are doing about the risks that remain. Each is backed by a record from the monitoring system. Build the page before anyone asks, keep it calm and short, offer the monthly report afterwards, and stop talking when the page has finished.


The records behind the page are the rest of this pillar. The work log is in the invisible work problem. The monthly page is in the quiet month report. The availability table is in uptime reporting as reputation defence. And the log is in counting the outages you prevented. Keeping all four for a year is a sign of a practice that has grown up. And the monitoring maturity model describes what that looks like from the outside. All of them are part of Making Invisible Work Visible With Monitoring Data.


Put this into practice with SysPeep Monitor

The one-page record is only as quick to build as its sources are to reach. SysPeep Monitor keeps alert history, per-service availability reports, and scheduled reports in one web console. It is fed by a central Windows service and optional remote probes. So the three sentences can be checked against the same system that produced them. The free trial installs on a Windows machine if you would like to build the page from your own network before anyone asks for it.

Download Free TrialLearn About SysPeep