Your data is solid. Your meeting might still fail. Here's why
Most advice on data storytelling assumes the hard part is the analysis, picking the right data, choosing the best visuals or weaving it all together well. Those things are genuinely tricky, and they're skills worth building. But there's a bigger problem that rarely gets talked about: standing up in a meeting and actually landing the story with the people in front of you.
That's because the moment you start sharing a data story, you run into something predictable, wildly mixed confidence and skill levels sitting in the same room. Some people speak fluently in metrics. Others think in anecdotes. And some are quietly staring at a chart, trying to figure out what it even says, or second-guessing whether what they think they see is right. If you don't design for that reality, the meeting plays out the same way every time: the confident voices interpret and dominate the discussion, the unsure ones go quiet, and decisions get made on partial understanding and momentum rather than genuine buy-in.
This isn't a step-by-step process to run in your next meeting. It's a set of principles drawn from years of working in data strategy and data storytelling - ways to help you deliver well and bring every person in the room into the conversation, regardless of their skill level.
1. Lead with purpose, not proof
Open with the decision you're trying to make, not the data. Lead with charts and you're quietly asking the room to figure out what matters on their own they scramble to work out what to look for and what it means. Lead with purpose, and you've already told them what to listen for.
In the moment, it sounds like:
"By the end of this meeting, we're deciding X."
"The data is here to help us choose between A and B."
"We've been noticing that X has been a problem lately."
This one move makes the meeting accessible to everyone in the room, whatever their technical background, because they're all orienting towards the same outcome from the first minute.
2. Make clarity a respected contribution
In a mixed-skill room, confusion rarely announces itself it goes underground instead. So you need to actively signal that clarity questions are valuable, even vital, not embarrassing. When you normalise asking questions and seeking clarity, you get far stronger engagement and real buy-in from everyone in the room, not just the loudest few.
In the moment, it sounds like:
"If something isn't clear, please ask. Our decisions will only be as good as our understanding."
"Plain-language questions are a sign we're doing this properly."
Once clarity is respected, participation widens and you stop mistaking silence for agreement.
3. Separate understanding from interpretation
One of the fastest ways to lose half the room is jumping from chart to conclusion before anyone's agreed on what they're actually looking at. I always talk about decoupling the analysis stage from the action stage. In practice, that means keeping a clean separation between:
What's happening (shared observation)
What it means (shared interpretation)
What we'll do (shared decision-making)
In the moment, it sounds like:
"Let's agree on what we're seeing first."
"We'll get to interpretation in a moment, What do we notice on the chart?"
This cuts down on the unproductive back-and-forth between interpretation, action and analysis and makes it much easier for less-confident participants to speak up early. Just don't get stuck in any one stage, leave enough time to actually reach a decision.
4. Use plain language
If you can't explain your insight simply, one of two things is true: either you don't fully understand it yet, or you haven't found the core message hiding in the data.
Plain language isn't dumbing anything down. It's actually a sign you understand the data and the room well enough to make it land. Matt Church, the founder of the business school I’m part of, talks about explaining your thinking as if to a seven-year-old. Not because it's disrespectful, but because it forces you to clarify your own understanding to the point where it's accessible to everyone.
It echoes that quote (misattributed to half a dozen different people): "I would have written you a shorter letter, but I didn't have time." Complexity isn't credibility. With a mixed-ability team, playing only in complexity is exactly how you lose the room.
5. Reduce cognitive load
A meeting isn't the place to explore every possible angle, it's the place to make sense of what matters most. Too many charts, too many metrics, too many caveats, and people simply tap out.
Design for the brains actually in the room. If they're distracted, short on time, or walking in carrying context from three other meetings that day, adjust accordingly. That might mean pulling one key idea from each chart or choosing a single visual to carry a single idea, those are two different things. Fewer charts. More discussion. More dialogue.
If the room is working hard just to interpret the chart, they're not doing the higher-order thinking you actually need from them interpreting, weighing options, deciding and planning next steps.
6. Narrate the chart — don't just show it
A chart isn't communication on its own, it's a prompt for interpretation. Your job is to direct the room's attention to what actually matters.
When designing your visuals, you could:
Change the title to state the trend or insight you want people to see
Highlight the relevant bar or line in colour and grey out the rest
Draw arrows, boxes or circles to point at the important detail
Add annotations calling out the things you want people to notice
Then say things like:
"Here's what you're looking at…"
"Here's what I think matters…"
"Here's why I think it matters…"
This supports the people who don't read charts fluently or often, while still guiding the conversation for those who do. Good data visualisation does both at once.
7. Normalise uncertainty and limits
Nothing erodes trust faster than overconfidence, especially from the person presenting the data. A mixed-skill team needs permission to weigh in on what the data suggests, what it doesn't show, and what still needs to happen next.
In the moment, it sounds like:
"This suggests X, but it doesn't answer Y."
"Here's the assumption we're making."
"Here's what could be distorting this."
This isn't weakness, it's rigour. It invites people to think critically and consider other angles and stops the room from settling into false certainty.
8. Protect airtime so confidence doesn't equal influence
Without deliberate facilitation, a meeting will default to whoever is loudest or most fluent. Pat Lencioni calls this the HIPPO the highest paid person's opinion tends to be the one everyone hears. That's not a character flaw. It's just how groups behave.
Treat hearing from everyone as part of the meeting design, not a nice-to-have. That might look like this:
A short silent read of the data before discussion
"We've heard from three people. Who hasn't spoken yet?"
Pair discussion before opening it up to the wider group
This isn't just about people feeling included. It improves the decision itself with context, more challenge and fewer blind spots.
9. Offer options, not a single "right answer"
Data is rarely a verdict. It's more often a prompt that gets people wondering what to do next. Mixed-skill teams stall when data is presented as "the answer" because disagreeing then feels like arguing with the truth itself.
A better move is to invite perspective. What you see in the data isn't necessarily the most important thing, so ask the room.
In the moment, it sounds like:
"I see this but what feels more urgent from where you sit?"
"What haven't we considered?"
"What are the benefits and risks of this option?"
This invites real participation, rather than everyone simply listening to the person who supposedly has all the answers.
10. Make the decision explicit and testable
A "good conversation" about the data isn't the goal. Before the meeting ends, lock in:
What was decided
Who owns the next steps
What you'll measure afterward
How you'll know if it worked
This is where data storytelling actually earns its keep, it doesn't stop at the insight or a polished presentation. It drives action and learning. The meeting isn't the finish line; it's one step in a longer journey towards data-informed, meaningful change.
FAQ
What is data storytelling, and why does it matter in meetings?
Data storytelling is the practice of turning numbers and analysis into a narrative people can actually act on. In a meeting, it matters more than the analysis itself. A technically brilliant chart is wasted if the room can't follow what it means or why it matters to the decision at hand.
Why do some people struggle to follow a chart even when the data is solid?
Most rooms have a wide spread of data fluency. Some people read metrics naturally, others think in stories or examples, and some simply haven't had much exposure to interpreting charts. Without deliberate data visualisation choices, a clear title, a highlighted trend and a short narration, the less fluent members of the room quietly disengage rather than ask for help.
What's the difference between data visualisation and data storytelling?
Data visualisation is the chart or graphic itself the tool. Data storytelling is what you do with it: giving it purpose, narrating it, and connecting it to a decision. You can have excellent visualisation and still fail at storytelling if you just display the chart and let the room interpret it alone.
How do you keep a data-informed meeting from being dominated by the most confident voice?
Building airtime protection into the meeting design rather than leaving it to chance, having a short silent read before discussion, directly inviting quieter people in or having pair conversations all help. Left unmanaged, meetings default to the loudest or most senior voice, often called the HIPPO effect (highest paid person's opinion).
Does using plain language when presenting data make you look less credible?
No, it tends to do the opposite. Being able to explain a complex insight simply is usually a sign you understand it deeply, not that you're oversimplifying it. Rooms lose trust in presenters who hide behind jargon and complexity, not ones who make the message accessible.
What should every data presentation end with?
An explicit, testable decision: what was decided, who owns the next step, what will be measured, and how success will be judged. Without this, even a well-received data story risks becoming "a good conversation" that goes nowhere.
Who can help a team build these skills for presenting data internally?
Most teams figure out that they need help building these skills, one awkward meeting at a time. But data storytelling and mixed-audience communication are learnable skills and work worth doing deliberately as people won’t typically pick up these skills on their own. Whether it’s through a data strategy keynote that reshapes how people think about data storytelling, structured training or building a data-informed culture into your organisation, the investment will always pay off.
Bringing it all together
A mixed-skill meeting doesn't need everyone to become a data expert to engage, it needs everyone to be able to participate in making meaning together.
If you're the one running the meeting, these principles help you hold both the technical integrity of your analysis and the accessibility a real team decision requires. And when different minds come together around data visualisation, data strategy and honest dialogue, genuinely good things happen.
