Home › Topics › Translating Monitoring Data for Management › Speaking Business, Not Packets

Speaking Business, Not Packets: A Translation Guide


You wrote a careful status email. It said the secondary uplink was at 85 percent utilisation with intermittent CRC errors. It also said you recommended a transceiver swap in the next maintenance window. It was accurate. It was complete. Nobody replied, and three weeks later your manager stopped you in the corridor to ask whether "the network thing" was sorted.


The problem is not that managers do not care. The email was written in a language they do not speak. Nothing in it told them whether it was a warning, an update, or a request. Monitoring produces facts about ports, packets, and percentages. Managers make decisions about people, money, and risk. Somebody has to carry the facts across that gap, and the monitoring system will not do it for you.


This guide teaches the carrying: a four-step method for turning any technical finding into a sentence a manager can act on. It includes a glossary of common status lines with their translations, five worked rewrites, and a short list of words to stop using. None of it is about dumbing anything down. It is about making the meaning survive the journey.


In this guide

  • The question behind every management question
  • Why technical accuracy loses the room
  • The translation method in four steps
  • A technical-to-business glossary
  • Five status lines, rewritten
  • Words to stop using
  • When to keep the technical term
  • From samples to a sentence
  • A war story
  • The translation checklist
  • Where to go next

The question behind every management question


When a manager asks "is the network OK?", they are not asking about the network. They are asking whether anything is about to stop people working or cost the organisation money. The network is what they ask about because it is what you look after, not because it is what they care about. Nobody has ever wanted a network. They want the order system to take orders and the phones to ring.


Every management question has one of three questions underneath it. "Are we OK right now?" means "is anyone unable to work at this moment?" "Are we going to be OK?" means "is anything getting worse that will hurt us before you can fix it?" And "what do you need?" means "is there a decision or a sum of money you are waiting on from me?" The guide to the manager's dashboard builds a screen around those same three questions. This guide does the same thing for your sentences.


Answer the question underneath and you are done. Answer the question as asked and you will be asked again, usually by someone more senior. (The second time, the question is shorter and the tone is not.)


Why technical accuracy loses the room


A technically accurate sentence is not the same as a meaningful one. "The core switch is showing 0.4 percent output discards on the uplink to the distribution layer" is true and precise. It is useless to a person who does not know what a discard is or whether 0.4 is a lot. Accuracy says what happened. Meaning says what it does to them. You have supplied the first and asked them to work out the second.


They cannot work it out, so they file it. A manager who receives a sentence they cannot evaluate can ask you to explain it. That costs them time and a little face. Or they can put it in the folder of things that are probably fine. The folder wins. That is not laziness; it is what any sensible person does with information they cannot act on. Your email sounded calm, so it was treated as calm.


The other failure is worse: they act on the wrong word. "Intermittent" sounds minor. "Secondary" sounds like a spare. A finding that should have produced a purchase order gets read as "the spare has a small glitch". The reply, if there is one, is "keep an eye on it." The guide to reports people actually read makes the same point about whole documents: lead with the answer, because nobody will dig for it.


The translation method in four steps


The method is a ladder with four rungs: the fact, the effect on people, the effect on money or risk, and what you want done. You start at the bottom with what the monitor told you and climb until you reach a sentence that lives in the manager's world. Most status updates stop on the first rung.


Rung one is the fact, exactly as the monitor reported it. "The uplink between the warehouse and the office is at 85 percent utilisation every afternoon." Keep this sentence for when someone asks how you know. Just do not lead with it.


Rung two is the effect on people. Who notices, and what do they notice? "Anyone in the warehouse opening a drawing from the office file server waits noticeably longer after two o'clock." If you do not know who notices, the translation is not finished. Go and find out, or say honestly that nobody has noticed yet, which tells the manager they have time.


Rung three is the effect on money or risk. This is where a slow file server becomes a business finding. "Two pickers spend perhaps twenty minutes each afternoon waiting on drawings, and the link has no headroom left for the scanner system due next quarter." You are not inventing a cost figure, only naming the shape of the cost. The guide to framing findings as risk and cost shows how to put an honest range on it.


Rung four is what you want them to do. Every translated finding ends in an ask, even when the ask is "nothing yet; I will raise it again if it passes ninety percent." Managers act on requests, not on descriptions, however vivid. "I would like approval to get a quote for a faster link before the scanner project starts" can be answered with yes or no. That is the entire point.


Write the four rungs down before you write the email. The template below is the whole worksheet.


TRANSLATION WORKSHEET

Fact (what the monitor says, with date):      ______________________
Effect on people (who notices what, when):    ______________________
Effect on money or risk (shape, not a guess): ______________________
What I want you to do, and by when:           ______________________

Email order: ask, risk, effect, then the fact in brackets.

A technical-to-business glossary


The table below is a starting glossary of status lines and their translations. Every row climbs the ladder from fact to phrasing you can send. The numbers are examples. Replace them with yours, and replace the middle column with what your users actually experience.


Technical status lineWhat it means for peopleSay it like this
Uplink at 85% utilisation at peakThe connection between two buildings is nearly full in the afternoon"The link between the warehouse and the office is nearly full at peak; file transfers slow down after two in the afternoon."
Primary WAN down, failover to secondary activeInternet works, but on the slower backup line, with no further backup"We are running on the backup internet line. Everything works but slower, and if that line fails too we are offline."
File server volume at 92% usedThe shared drive is nearly full; when it fills, saving fails"The shared drive has about two weeks of space left at the current rate. When it fills, people cannot save files."
3% packet loss to the phone providerCalls have crackle and dropped words"Phone calls to and from the office are breaking up. Roughly one word in thirty is lost."
Latency to the data centre up from 12 ms to 90 msScreens in the hosted application feel sticky"The stock system feels slow to everyone in the branch; each screen takes noticeably longer to load."
Access point AP-07 downA Wi-Fi dead zone in one part of the building"There is no Wi-Fi in the east meeting rooms until the access point is replaced."
UPS on battery, 18 minutes remainingMains power has failed; servers shut down in a quarter of an hour"The server room has lost mains power. We have about fifteen minutes before the servers shut themselves down."
Certificate on the customer portal expires in 9 daysBrowsers will block the website"In nine days the customer website will show a security warning that most people will not get past, unless we renew it before then."
Backup job failed three nights runningNothing newer than last week can be restored"If we lost the file server today, the newest copy we could restore is four days old."
Input errors rising on the core switch port to the server rackA fault on a critical cable is getting worse"A cable between the main switch and the servers is failing slowly. It causes occasional slowness now and will fail completely at some point."
Route flapping on the WAN link to the branchThe branch connection drops and reconnects repeatedly"The branch keeps losing and regaining its connection to head office, a few seconds at a time, all day."
Monitoring server unreachableNothing will be noticed until it is fixed"Our warning system is down. Until it is back, we will find out about problems when people report them."

Notice what the right-hand column never contains: a percentage, a port name, a protocol, or a millisecond. It contains buildings, people, times of day, and the word "we". That is what a translated fact looks like.


Five status lines, rewritten


The glossary handles single facts. Real status lines bundle two or three, so here are five typical ones rewritten in full. Read each "before" and ask what a manager would do with it. The honest answer, most of the time, is nothing.


1. The unstable backup line

Before: "Secondary WAN circuit flapping since 03:10, BGP session resetting every 4–6 min, primary unaffected."

After: "Our backup internet line has been unstable since the early hours. Nothing is affected yet because the main line is fine, but until this is fixed we have no working backup. I have logged it with the provider and will update you by the end of the day."

The rewrite adds the one consequence that matters (no backup) and says when the manager will hear next. The word "flapping" did not survive, and nobody misses it.


2. The filling disk

Before: "FS01 D: volume at 91% used, growth approx. 2 GB/day, no automatic cleanup configured."

After: "The shared drive will be full in about three weeks at the current rate. When it fills, people cannot save their work. I need a decision by Friday on whether to add storage (a quote is attached) or archive last year's project folders. Archiving is free but needs sign-off from the project managers."

A percentage has become a date, with two options and a deadline. A manager can decide that one in the time it takes to read it.


3. The phone quality complaint

Before: "Increased RTT and 2–4% loss to SIP trunk provider during the 09:00–11:00 window, Tue and Wed."

After: "Phone calls sounded broken during the morning rush on Tuesday and Wednesday. The fault is between us and the phone provider, not inside the building. I have raised it with them. No action is needed from you unless it continues past Friday, in which case I will ask you to escalate it with our account manager."

This one says where the fault is, which is what the sales team will ask, and gives the manager a role only if the provider stalls.


4. The failing cable

Before: "Core-SW1 Gi1/0/48 input errors incrementing, 14k in 24h, port is the uplink to SRV-SW2."

After: "The cable between our main switch and the server rack is developing a fault. Right now it causes brief slowness. If it fails completely, the servers go offline for everyone. I want to swap it on Thursday evening, which means the shared drive and email are unavailable from six until seven. Please tell me if that clashes with anything."

The rewrite gives the manager the one thing they can contribute: whether Thursday evening is a bad time. It also makes the cost of waiting explicit, which is how a cable swap gets approved without a debate.


5. The quiet month

Before: "All services nominal for the period. No P1/P2 incidents. Two P3 (resolved)."

After: "Everything the business relies on was available all month. Two minor problems were fixed within the day and nobody outside IT noticed. No action is needed."

Even good news needs translating. "Nominal" and "P3" mean nothing outside the team.


Words to stop using


Some words are fine between admins and poison outside the team. They are not wrong; they are simply not understood, and a listener who meets an unknown word either stops listening or guesses. The usual offenders, and what to say instead:


  • Latency — say "delay", or "how long each screen takes to respond".
  • Jitter — say "uneven delay"; for phones, "calls sound choppy".
  • Saturation, utilisation — say "the link is full" or "nearly full".
  • Flapping — say "keeps dropping and coming back".
  • MTU — do not say it at all; say "a size setting on the connection was wrong".
  • Packet loss — say "some of the data does not arrive and has to be sent again"; for phones, "calls break up".
  • Failover — say "switched to the backup".
  • Redundant, redundancy — say "has a backup".
  • Uplink, trunk, interface — say "the connection between X and Y".
  • Nominal — say "normal" or "working".
  • P1, P2, Sev 1 — say "stopped people working" or "nobody outside IT noticed".

"Redundant" deserves its own warning. To you it means "we have a spare". To everyone else in the building it means "surplus to requirements". An email announcing that the file server is now fully redundant gets read with more interest than you intended.


When to keep the technical term


Keep the term when the manager will meet it again somewhere you are not. If it will appear on the quote, the contract, the provider's ticket, or the auditor's letter, they need to recognise it. The pattern is the term, then a plain definition in brackets, once, then the plain word for the rest of the document. For example: "the BGP session (the arrangement by which our router and the provider's router agree on a path) has been resetting."


Keep it when the manager already uses it. Some managers came up through IT, and some have absorbed the vocabulary from years of being told about it. Translating "VPN" for a person who says "VPN" three times a day is faintly insulting. Listen for the words they use unprompted and use those back.


Keep it when the term is the name of the thing you want to buy. A "10 gigabit uplink module" is what goes on the purchase order. So call it that in the ask, with a plain description beside it. A purchase order for "a faster connection between the buildings" comes back from procurement with a polite question.


Everywhere else, drop it. The test is simple: if the manager could not repeat the sentence to their own boss without looking at it, the term should go.


From samples to a sentence


The effect on people usually needs a number the monitor does not report directly. The monitor stores 288 five-minute samples of utilisation per day; the manager needs "the link is full for about three hours every afternoon". Getting from one to the other is a small piece of arithmetic. And "about three hours a day" is the kind of number that gets a decision. "85 percent" is not.


If you export a day of samples to a spreadsheet, one formula does it. Put the 288 utilisation values in column B, then:


=COUNTIF(B2:B289,">85")*5/60

Samples above 85 percent, converted to hours.
A result of 2.75 is "nearly three hours above
the limit today".

Run it for each working day of the month. The sentence that comes out is "the link between the warehouse and the office was full for between two and four hours every working afternoon last month." It carries a place, a time, a range, and people you can picture waiting. Nobody needs to know it started life as 288 samples a day.


Tip: keep the untranslated fact, with its date and graph, somewhere you can find it. The manager will not ask how you know. The manager's manager, the auditor, and the provider's engineer all will.


A war story


The network administrator at Meridian Parts sent a status email that read, in full, "BGP flap on the secondary, monitoring, no impact." It went to the operations director, the finance director, and a shared mailbox. Nobody replied, because nothing in it sounded like a request, and "no impact" sounded like the end of the matter. Nine days later a contractor cut the primary fibre in the car park. The secondary took over. Its failing line card, which was what the flap had been all along, dropped the whole company offline for an afternoon. The review recorded that the secondary's fault had been reported in advance, which was true in the sense that a footnote is a report.


The translated version would have ended in an ask. "Our backup internet line is faulty. Until it is fixed we have no backup, so a single cable cut takes us offline. I need approval for an engineer visit this week; the quote is attached." A manager can act on that between two meetings. Nobody can act on "flap".


The translation checklist


Run every status email and report line through this list before it leaves your desk. It takes a minute, and it is the difference between being read and being filed.


  • The first sentence says whether anyone is affected right now.
  • The second sentence says what happens if nothing is done, and roughly when.
  • Every technical term is either replaced or defined in brackets at first use.
  • Each finding names who notices and what they notice.
  • Each finding ends in an ask, even if the ask is "no action needed".
  • The numbers are ones a manager can picture (hours, people, days left), not ones the monitor reports (percent, milliseconds).
  • The date and source of the evidence are kept, in brackets or at the end.
  • The manager could read it aloud to their own boss without a diagram.

Where to go next


Translation is the base skill of this pillar. Framing Monitoring Findings as Risk and Cost puts an honest range on the third rung of the ladder. The Monthly One-Pager turns a month of translated findings into a page a finance director will read. And Presenting Monitoring Data in a Meeting covers saying it out loud. All of them live under Translating Monitoring Data for Management.


Put this into practice with SysPeep Monitor

Every translation in this guide starts with a fact you can point at. SysPeep Monitor collects device and service health over SNMP, WMI, and SSH. It keeps live dashboards and reports in one web console. So the "how do you know?" question always has a graph behind it. SysPeep Monitor can also email reports to the people who read them. The product documentation lists the report types and scheduling options. The free trial installs on any Windows machine in minutes.

Download Free TrialLearn About SysPeep