Here's a situation most awareness professionals have been in. You walk into a meeting with solid data, you've done the work, the numbers tell a clear story, and somewhere in the middle of your presentation you lose the room.
Usually this isn't a data problem but a communication problem. More specifically, it’s likely a mismatch between what you're presenting and what your audience actually needs from you. Different audiences need different things from the same data, and I’m going to help you figure out which is which and adjust accordingly.
What leadership needs
I’ve found that senior leaders aren't usually interested in the mechanics of your programme. They're interested in risk, trends, and whether they need to worry. They want to know: are we better or worse than we were, where are the biggest risks, what are we doing about them, and what do you need?
So lead with the headline and not with methodology, not with caveats, and definitely not with a story that requires fifteen slides of context before you get to the point. Deliver the point first, and the supporting detail after. Then translate any metrics you have into business terms where you can. A phishing click rate is a technical metric, and to them it likely means nothing. However, if you describe a thirty percent reduction in credential-harvesting susceptibility in finance since we launched targeted training, that means something and is a business outcome. Same data, but a completely different frame.
What technical audiences need
Security and IT teams want the detail. Methodology, confidence levels, the edge cases, and the stuff you're not sure about. They're also often better placed than anyone else to challenge your interpretation, so let them. Present your data and your conclusions, be honest about the limitations, and then invite pushback.
These audiences are comfortable with nuance. You don't need to sand everything down into a clean story. Uncertainty, acknowledged openly, can actually help to build your credibility rather than undermining it.
The common mistakes
Presenting the same thing, the same pane of glass, to everyone is tempting but it almost never works well. Having too many metrics is another one. If you have a dashboard with twenty-five metrics, there’s a good chance that it isn’t communicating anything, and it likely signals that you haven't done the work of deciding what actually matters. Metrics without a narrative is a problem too, because numbers without context are just numbers, and the answers to 'what does this mean, is this good or bad, and why did it change' have to come from you.
And burying the headline is probably the most damaging mistake. If your most important and powerful insight is down deep on slide twelve, most of the room has already mentally moved on.
A practical approach
Build a core dataset that contains everything, but then build different views from it for your different audiences. A one-page summary for leadership, have a deeper dashboard for operational review, and then a detailed breakdown for technical discussion. It’s the same underlying data, but just with different presentations. And yes, it takes more preparation and work to build it out but it's much more effective.
Think about it the same way you think about targeted training. You already know that the same message delivered to everyone regardless of their role or risk profile has less impact than something built around what that specific audience actually needs. Presenting data works the same way.
Good data presented badly is almost as useless as bad data. The goal isn't to show how much you've measured. It’s to influence how people think about risk and what they decide to do about it. Know your audience before you open the deck, then build the presentation around what they need rather than around everything you have.
