Why data doesn't create learning. Curiosity does
There's a strange thing that happens in a lot of workplaces. The dashboard is built. The report goes out. The meeting agenda even has a line item that says - discuss the findings and yet, somehow, almost nothing is actually learned.
People glance at the numbers. Someone points out that something went up or down. Another person offers a quick explanation, usually the first one that comes to mind and before long, the room is already moving towards action. On the surface, it looks like a conversation that’s grounded in data. Data was in the room, after all. But being present isn't the same as being understood.
Curiosity isn't just a personality trait
We tend to think of curious people as a certain type, the ones who ask a lot of questions, read widely and never settle for the first answer. And sure, some people are naturally wired that way.
But in the workplace, curiosity isn't only personal. It's cultural. And leaders play a huge role in whether that culture grows or gets quietly shut down.
What leaders are really teaching, without saying a word
Every time a leader looks at a number and reacts, they're teaching people something. Whether they realise it or not, they're showing the team whether data is something to defend, to comply with, to prove a point with or to actually learn from.
Here's a small example that says a lot: imagine a disappointing result lands on the table.
One leader asks, "Who's responsible for this?"
Another asks, "What might be contributing to this, and what do we still need to understand?"
Same result. Two completely different conversations.
The first question creates urgency sure but it also shrinks the room. People get careful. They start explaining themselves instead of exploring the problem. They reach for whatever answer feels safest to say out loud.
The second question does something different. It doesn't let anyone off the hook but it puts accountability next to understanding, not in place of it. It says, 'I care about the result, but I also care about what led to it.'
Numbers don't explain themselves
Data rarely hands us the full picture. A number can drop without telling us why. A dashboard can show variation without giving us context. A survey can capture how people feel without capturing the story behind it. A target can be hit while something important quietly breaks in the process.
Data gives us signals, not answers. Curiosity is what turns a signal into something we can actually trust.
Without it, data becomes a performance. It gets collected because it's supposed to be. It gets reported because it's expected. It gets "discussed" because the agenda says so, but the real work of questioning, testing, and digging deeper never really happens.
That's activity. It's not maturity.
What curious leaders actually do differently
Curious leaders don't treat their first read of the data as the final word. They resist the urge to make messy numbers look tidy. They ask what else could be true. They wonder who might see the same data differently. They stay aware of what the numbers simply can't tell them.
None of this means every meeting turns into a philosophy seminar. Decisions still need to get made. But when curiosity is missing, teams tend to act too early in solving the obvious version of a problem instead of the real one. They treat the symptom and never touch the actual pattern underneath it.
People are always watching how leaders handle discomfort
This is really where it counts. People notice what a leader does when data is uncomfortable. Do they get defensive? Do they only seem to welcome numbers that back up the plan already in motion? Or are they willing to sit with something messy long enough to actually understand it?
"We're data-informed" can mean two very different things:
"Bring me numbers that support what I've already decided,"
or
"Help me see reality clearly, even when it's inconvenient."
Employees can tell the difference. And here's the thing, curiosity spreads. So does defensiveness.
If leaders won't ask genuine questions their teams won't either. If uncertainty gets treated like weakness, people will learn to hide it. If pushback gets treated like disrespect, people will stop pushing back. And if polished certainty keeps getting rewarded over honest, careful thinking, that's exactly what a team will start producing, even when the situation calls for something far more thoughtful.
Building a culture where questions are actually safe
Encouraging people to "ask more questions" isn't enough on its own. Leaders have to build an environment where asking is genuinely safe, useful and expected.
That means making room for interpretation, not just reporting. It means treating a simple, honest question as a real contribution, not a sign that someone's behind. It means letting the people closest to the work explain what the data might be missing. And it means keeping "What are we seeing?" is separate from "What should we do about it?" because when those two questions blur together too fast, teams skip understanding entirely just to look decisive.
It also means protecting the people who say the hard thing out loud. The person who slows the meeting down with a tough question. The person who points out a flaw in the data. The person who notices a downside to something everyone's celebrating. If those contributions keep getting brushed aside, people learn fast that curiosity is only welcome when it's convenient.
The questions worth asking out loud
If we actually want people to use data well, they need to feel safe wondering out loud. That means being able to:
Notice a pattern without immediately getting defensive
Question an assumption without feeling like they're being disloyal
Say something like, "This is interesting, but I don't think we fully understand it yet."
Ask things like, "Who's missing from this data?", "What might this number be hiding?", or "What would we expect to see if we're wrong about this?"
These are the questions that stop teams from mistaking movement for progress. They're what helps people understand not just what changed, but why it changed, for whom, and at what cost.
Curiosity doesn't weaken accountability — It strengthens it
A curious leader isn't dodging responsibility by asking more questions. They're taking responsibility seriously enough to actually understand the situation before acting on it. Fast decisions built on thin understanding might feel efficient but they're not always the smart ones.
So here's the real question worth sitting with: it's not whether leaders say they value curiosity. Most probably do. The real test is whether their behaviour, especially when it's inconvenient and especially when people are watching, actually makes curiosity possible for everyone else.
The real difference
Data can tell a team that something changed. Only curiosity can tell them why it matters. Leaders who protect space for honest questions, even the uncomfortable ones, end up with teams that understand reality instead of just reporting on it. That difference shows up in every decision that follows.
FAQ
1. What does it mean to be "data-informed" as a leader?
It means using data to genuinely understand what's happening, not just to justify decisions already made. It’s the difference between ‘show me the numbers to back up what I’ve already decided’ and ‘help me see what’s actually happening here.’
2. Why doesn't having a dashboard automatically mean data is being used well?
A dashboard shows information but doesn't guarantee anyone's actually thinking about it. Teams can review reports weekly and still avoid asking hard questions. Without curiosity behind it, data ends up present but not truly understood or acted on.
3. How can leaders encourage curiosity instead of shutting it down?
It starts with the questions asked first. Choosing "what's contributing to this?" over "who's responsible?" invites honest exploration instead of defensiveness. Leaders also need to protect people who raise inconvenient points instead of letting them get dismissed.
4. Doesn't encouraging more questions slow down decisions?
Not when done well. Curiosity separates "what are we seeing?" from "what should we do?" so teams don't jump to the first obvious answer. That small pause for understanding usually leads to sharper decisions, not slower ones.
5. What's the risk if leaders don't model curiosity?
Curiosity spreads through teams, but so does defensiveness. If uncertainty is treated as weakness, people learn to hide problems instead of surfacing them, leading to polished, "safe" reporting instead of honest insight.
