Your non-technical stakeholders don't grasp your security concerns. How do you communicate effectively?
Communicating network security concerns to non-technical stakeholders can be challenging. The key is to simplify your language and relate your concerns to their business priorities. Here's how:
- Use relatable analogies: Compare security issues to everyday problems, like locking doors or protecting valuables, to make the concepts more understandable.
- Highlight business impact: Explain how security risks can affect the company's bottom line, reputation, or operational efficiency.
- Provide actionable steps: Offer clear, practical recommendations for mitigating risks, making it easier for stakeholders to take action.
How do you effectively communicate technical concerns to non-technical stakeholders?
Your non-technical stakeholders don't grasp your security concerns. How do you communicate effectively?
Communicating network security concerns to non-technical stakeholders can be challenging. The key is to simplify your language and relate your concerns to their business priorities. Here's how:
- Use relatable analogies: Compare security issues to everyday problems, like locking doors or protecting valuables, to make the concepts more understandable.
- Highlight business impact: Explain how security risks can affect the company's bottom line, reputation, or operational efficiency.
- Provide actionable steps: Offer clear, practical recommendations for mitigating risks, making it easier for stakeholders to take action.
How do you effectively communicate technical concerns to non-technical stakeholders?
-
Know your audience. You need to explain the cost of a resulting incident in relatable ways to the stakeholder(s), and for each person's role, the way this is done can be very different. For some stakeholders this could be explained through financial losses or opportunity cost due to a tarnished name. Others may better relate to the potential legal or regulatory repercussions. Explain the cost of mitigation versus the potential losses due to exploitation. It may not be possible to put in plain numbers what these are, but a sensible person will likely understand the lower cost to mitigate the problem than the higher cost of an incident.
-
There are a number of important points to use in order to get your message across successfully, the first is to highlight what they have at risk and what could possiblly be lost. This helps them to understand the scale of the risk you are talking about in something they see value in. Next you need to build them a story or analogy of something simple they know. For performance topics I often use a car analogy, and for security I use their house/home. I always try to have a plan B in my back pocket in case they dont understand it. The tone of your voice is important too as you dont want to patronise them.
-
First and foremost, approach it in a "what's in it for me?" manner. If they don't see value in it, it is unlikely that they will WANT to understand it. Explain the risk, outcomes, and benefits. Even better if you use something relatable to explain it. An analogy is a great way to make them connect technical matters to practical concerns. For example: "That's like closing the door but not locking it. It will not really keep anyone out, if they want to get in."
-
It’s one of the main components of Cybersecurity, we call it “Human Risk Management”. Simply, it means: The biggest vulnerabilities often come from human error, so making security a habit is key. I believe that Instead of overwhelming stakeholders with technical stuff, show them how simple daily actions—like verifying emails, using strong passwords, and staying alert—can protect the business. When security feels personal and practical, it becomes second nature.
-
The best way to communicate when you don't have a shared level of concern is understanding where they are at, make the information relatable to them, before you even propose technical solutions. Once you can both agree on the "why it matters", they will be more receptive to the "how" that you are trying to convey.
Rate this article
More relevant reading
-
CybersecurityHow can you make sure your incident response simulations are realistic?
-
IT ManagementYou're facing a challenging IT issue. How can you effectively communicate the solution to stakeholders?
-
Information SecurityHere's how you can resolve common conflicts in the field of Information Security.
-
Threat & Vulnerability ManagementHow do you validate and verify the results and outputs from your threat and vulnerability assessment tools?