"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.

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.

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.