Ask the Dumb Question
When data meets decisions, that “obvious” question does important work.
I ask the dumb questions in meetings. I always have.
It used to make me self-conscious. Now I consider it one of the most useful things I do.
Here’s what we’ve learned about why nobody asks, what happens when someone finally does, and the exact words I use when that someone is me.
Nobody asks because it feels risky
Last week’s post on sneaky metrics got a comment that stuck with me. Ankita wrote: “The part that matters most is getting really concrete really fast…who owns the metric, what’s in, what’s out.” She’s right. But to get concrete, someone has to start the conversation. And that’s the part nobody talks about.
So why don’t people ask? It’s not because people don’t care. It’s because asking feels scary.
It feels like admitting you should already know, but don’t. It can sound like you’re challenging the person who owns the number. And when meetings move fast - nobody wants to be the one who slows everything down for a question that might have an obvious answer.
So people stay quiet. They go back to their desks and work from numbers they don’t fully understand, or they quietly calculate things their own way. And that’s how you end up with two people presenting different revenue figures in the same meeting.
You ask the “dumb” question, and then what…?
A few years ago, we were working to automate financial reporting for a subscription business - analyst reports, multi-year contracts, revenue recognized on release. The setup seemed clean. Then someone asked: “What do we do when a report is released late?”
The room got quiet.
It turned out late releases weren’t unusual. And the harder part was that there wasn’t one clean answer waiting to be unlocked.
The question didn’t just surface the answer. It surfaced the fact that nobody had one and an important discussion was needed.
This situation happens way more than people admit. And when it does, the path forward is usually the same.
First, bring in the person closest to the data - not the person with the biggest title. They’re the ones who have been quietly making the call.
Second, run scenarios out loud: “If this report releases on the 3rd instead of the last day of the month, which period does it land in?” Concrete examples cut through abstraction faster than any definition will, and will raise decisions that need to be made. Use the examples to clarify the boundaries. Perhaps 3 days late doesn’t change anything - but 7 days does.
Third, consider any downstream effects from your decision. If you decide late reports count in the next month, what happens to monthly revenue targets? Do they shift? Do commissions change? Does finance need to adjust forecasts?
Finally, write it down before you leave the room and communicate that decision. Even a Slack message counts! The goal isn’t a perfect policy document, but making sure that information doesn’t go back to living in one person’s head.
This is why I embrace asking those “dumb” questions. Because that question - the one that felt disruptive to ask - was the one that surfaced a problem everyone needed to resolve anyway. The report automation project didn’t create it. It just made it impossible to keep absorbing in silence.
What to actually say
The question itself doesn’t have to be brilliant. It just has to be asked. Here’s what I actually say in different situations. These are not scripts, but starting points.
When I don’t understand a number:
“Can you walk me through what’s included in this?”
Simple and non-threatening. It puts the burden on understanding, not on challenging. Nine times out of ten, the person explaining it discovers something in the telling.
When something feels off:
“I want to make sure I’m not missing something - this looks different from what I expected. Can we look at it together?”
“I might be missing something” does a lot of work. It’s honest, it’s humble, and it makes it about understanding rather than accusation. But you’re still asking.
When you suspect two people are measuring differently:
“Before we go further - are we calculating this the same way? I want to make sure we’re comparing apples to apples.”
This one is especially useful when two numbers don’t match and everyone’s being polite about it. Name it directly. It’s almost always the issue.
When you’re presenting and want to get ahead of confusion:
“Quick note on this number before we dive in. Here’s exactly what’s included and what’s not.”
If you define it first, nobody has to ask. This one takes 20 seconds and saves 10 minutes.
In all of these examples, the common thread isn’t the exact phrasing, but the framing. Curiosity, not accusation. You’re not challenging anyone. You’re making sure everyone’s working from the same understanding.
You don’t have to ask it in the room
Not every question needs to be asked in the middle of a big meeting. If you’re earlier in your career, or just not in a position to break the flow, you still have options.
Listen closely. Take notes. Then follow up with someone close to the number. That’s often the analyst who built it, or the person pulling the report each week.
And use the same language:
“Can you walk me through what’s included in this?”
“I want to make sure I’m interpreting this right…”
These conversations are often easier one-on-one. People will go deeper. You’ll get a clearer answer. And if something important comes out of it, you can bring it back to the group:
“Quick follow-up on that number from earlier - here’s how it’s actually defined…”
You’re still creating clarity. You’re just doing it in a way that fits the moment.
Want more? This article by Gustavo Razzetti has great ways to “unblock” conversations with reframing - not fighting.
Asking “dumb” questions is a superpower
When one person asks, it gives everyone else permission.
Someone senior might assume everyone else already knows the answer. But from the junior person who is afraid to look inexperienced to the new team member who doesn’t want to slow things down or even the long-timer who has been pulling that same metric for years - they all need someone to go first.
The whole dynamic shifts when a group sees that clarifying a definition isn’t a challenge, it’s just good practice. Meetings will (eventually) get faster, not slower. Decisions get cleaner. People stop quietly disagreeing in their heads and start actually resolving it out loud. Real conversations can happen.
And the people who were already doing this? They tend to be the ones others describe as “easy to work with” or “really sharp on the data.” It’s not that they know more. It’s that they’re not pretending to know things they don’t.
Go on - ask those “dumb” questions.
I still ask the dumb questions. I probably always will.
Sometimes I even ask when I think I already know the answer, because I’ve seen too many times what happens when nobody does. The number that everyone nodded at turns out to mean three different things. The decision gets made on a metric nobody fully understands. The rework shows up two months later.
Asking isn’t the dumb thing. Staying quiet is.
Related articles:
