This is how: We’re currently facing network issues, which is why some services are slow or not working. This affects email, shared drives, and internet access, leading to delays in daily tasks. Our IT team is working to fix it as quickly as possible. We’ll keep you updated, and thank you for your patiene and understanding.

The goal is not to turn your coworkers into network experts—but to help them feel informed, included, and reassured that the issue is under control.

"The best way to predict the future is to create it." – Peter Drucker Use simple analogies: Compare the network to a highway. When there’s too much data traffic, things slow down, similar to a traffic jam. Explain the impact on tasks: Let them know how specific tasks, like sending emails or accessing files, are impacted due to the downtime, and offer any temporary workarounds. Provide a timeline: Share an estimated resolution time to set clear expectations and reduce frustration while the issue is being fixed.

Depending on the issue, ask the non-technical staff of what they understand - then work with that to explain the 'downtime impact' "What's wrong?....what you understand with the issue?" From there - work with that to talk about it or draw some network diagram - if required, draw it as some road to a house - the network issue? some car crash in the middle of it. Throw in time frame of when it can be fixed.

Commitment and communication are the key. Key everyone informed and work towards the expectation. "Our network is experiencing some traffic—like a jammed highway—so systems may be slow or unresponsive. We’re working on it and expect things to clear up in about [insert time]. Thanks for your patience!"

I typically use a tool such as https://ThreatCaptain.com to tie and ROI to controls and risk. Not everyone understand things like vulnerable ports, misconfigured controls, or bad policies - but everyone understands the all mighty dollar.

Use simple terms—say the network is like a road, and it's blocked. So tools can’t “travel,” causing delays in emails, files, or apps.

Explain it like this: “The network is down, so our systems can’t talk to each other—like phones with no signal—so things slow or stop temporarily.”

I would explain the downtime impact in simple terms by comparing it to something familiar, like a traffic jam. When there’s a network issue, it's like a roadblock that prevents data from moving smoothly, causing delays and disruptions. This means systems or services that rely on that network, such as email, internal tools, or customer-facing platforms, can’t function properly. I’d also emphasize that resolving the issue is important to restore normal operations and minimize further disruptions.

A key enabler for people to do their job is not working. You need to structure your response. 1. Acknowledge the issue and its impact. 2. Explain the problem in plain language. 3. Emphasise what’s being done. 4. Offer guidance or next steps. 5. Reassure and close on a polite note.