Quarterly review. The retention chart is on screen, and the line is going up. The room nods. The CHRO mentions the new onboarding program launched last quarter as a likely driver. Someone writes it into the slide deck for the board.
Nobody asks about the denominator. Survey response rate dropped from 82% to 41% that quarter. The people most likely to have left already stopped responding. The number on screen is real. What it claims about retention is not.
This happens in conference rooms every week, to managers and individual contributors alike. Reading data in a live meeting, under time pressure, with a room full of people who’ve already started nodding, is a behavioral challenge that has almost nothing to do with statistical skill. The result is bad decisions that look like good ones until the real numbers surface months later.
This post is about three behavioral habits that make smart people read data wrong, and a simple check (three questions, no formulas) that catches most of the errors before they become decisions.
The real reason “not a numbers person” is a trap
Math anxiety is real. Research suggests it affects roughly 6 in 10 university students, and the effects carry into the workplace. But there’s a wide gap between “I struggle with regression analysis” and “I should not be the one reading this chart.” The first is a reasonable skill boundary. The second is abdication dressed as humility.
The job isn’t producing the analysis. Somebody else already did that. Your job, whether you manage a team or contribute as an individual, is being the last reader before a decision gets made. You’re the person who knows the business context, the stakeholder dynamics, the history of what was tried before. The analyst knows the data. You know what the data is supposed to be about.
That’s a different job entirely, and it doesn’t require a statistics degree.
What data interpretation actually means at work
Three things. Reading what a number claims. Asking whether that claim holds up. Knowing when to press before acting.
That’s it. You don’t need to build the model. You don’t need to clean the dataset. You need to be a skeptical, informed reader who brings context the data team doesn’t have. This applies equally whether you’re a manager reviewing a team’s results or an IC evaluating a vendor proposal, analyzing a competitive landscape, or presenting findings to leadership.
If you want a baseline on where your critical thinking skills stand today, Risely’s free assessment is a good place to start.
The three moves that quietly wreck data-informed decisions
These aren’t character flaws. They’re habits formed under workplace pressure: tight meeting windows, social dynamics that reward confidence over caution, and organizational cultures that treat questioning data as slowing things down. They show up in managers reviewing team metrics and in ICs building business cases or analyzing project data. Coaching surfaces these patterns constantly. Naming them is the first step toward changing them.
Move 1: Mistaking correlation for proof
The coaching pattern: “The Confident Misreader.”
The scenario looks like this. “We launched the mentorship initiative in Q2. Engagement went up 8 points. It worked.” The room agrees. The initiative gets expanded. Nobody asks what else changed that quarter: a new VP joined, the company announced a hiring freeze (which paradoxically increases short-term engagement scores), and the survey questions were reworded.
This is post hoc reasoning, the assumption that because B followed A, A caused B. Daniel Kahneman’s work on System 1 thinking explains why it’s so persistent. Fast, pattern-based cognition looks for the simplest causal story. One visible variable (the initiative) gets credit for a multi-variable outcome. It feels like insight. It’s pattern recognition misfiring.
The coaching question that breaks the pattern: “What else changed that quarter?”
Not “are you sure?” Not “prove it.” Just: what else changed? That single question reintroduces the complexity that post hoc reasoning flattens. It doesn’t require you to run a controlled experiment. It just requires you to acknowledge that the world didn’t hold still while your initiative ran.
Move 2: Cherry-picking without knowing it
The coaching pattern: “The Selective Presenter.”
This one is rarely conscious dishonesty. A team lead is preparing a case for expanding a program. They pull the metrics that support continuation. They find them quickly because they’re looking for them. They stop looking. The contradictory data isn’t suppressed. It’s never encountered, because the search ended once confirmation arrived.
The behavioral tell: the person can’t articulate why contradictory data was excluded. Not won’t. Can’t. They didn’t see it. Confirmation bias works invisibly. You don’t experience the moment of choosing to ignore inconvenient numbers. You experience the relief of finding numbers that match your direction.
The coaching prompt that works here: “What would a skeptic point to?”
This reframes the task. Instead of asking someone to argue against themselves (which people resist), you’re asking them to predict an opponent’s argument. That’s a much easier cognitive move, and it almost always surfaces the data they unconsciously skipped.
If this pattern feels familiar, a decision-making assessment can help you see where the gaps are.
Move 3: Opting out when the stakes are highest
The coaching pattern: “The Identity Opt-Out.”
“I’ll let the data team handle the numbers.” Sometimes that’s appropriate delegation. Often it’s abdication. The difference: delegation means you stay in the conversation and ask questions. Abdication means the analysis gets accepted without interrogation from the person who understands the business context best.
The cost is real. When a non-analyst manager defers completely, the data team’s assumptions about what matters go unexamined. An analyst might flag a statistically significant result that has zero practical significance. Or miss a contextual factor (a team reorganization, a product launch, a seasonal pattern) that the manager would have caught immediately.
The numbers here are striking. Forrester found that 75% of executives self-rate as having advanced data literacy. DataCamp’s 2026 State of Data and AI Literacy report found that 88% of organizations report data skills gaps. Both can be true at the same time. The gap isn’t knowledge. It’s behavior. People know more about data than they’re willing to act on.
If the opt-out pattern resonates, your strategic thinking skills are worth examining. Strategic thinking and data interpretation share a core requirement: the willingness to sit with complexity instead of simplifying prematurely.
The 3-Question Check
This isn’t a checklist to print and laminate. These are three questions to internalize, the kind that become reflexive after you’ve asked them enough times. They work in meetings, vendor reviews, board prep, and any moment where a number is about to become a decision.
Question 1: What’s missing from this picture?
Every dataset has a frame, and the frame determines what you see. The question to start with is always about what’s outside that frame.
Engagement score goes up. Was attrition measured in the same period? Did the survey response rate change? Are the people who left (and therefore aren’t in the engagement data) the same ones who would have scored lowest?
Revenue per customer increases. Did the customer count shrink? Is the growth coming from one whale account that masks a broader decline?
The absence question is the most powerful single habit in data interpretation. It costs nothing, requires no technical skill, and catches errors that sophisticated analysis sometimes misses because the analyst was working inside the same frame.
If you want to sharpen this instinct, problem-solving skills are the foundation. Seeing what’s missing is a problem-solving behavior.
Question 2: Who built this, and what were they trying to show?
Not an accusation. A calibration.
A vendor presenting renewal data has an incentive to show engagement in the best light. An internal advocate building a business case has already decided what they want. A neutral analyst producing an exploratory report has different incentives than either.
None of these people are lying. All of them are framing. The choices they made (which time period, which metric, which comparison group, which visualization) reflect what they were trying to communicate. Knowing the source tells you where the frame probably sits.
Michael Luca and Amy Edmondson wrote about this in Harvard Business Review. Their argument: data-driven decision-making fails most often not because the data is wrong, but because the question the data was built to answer isn’t the question you’re trying to answer.
Question 3: If the number were 20% different, would we still decide the same thing?
This is a sensitivity test, and it’s the most clarifying question you can ask about any number that’s influencing a decision.
If your engagement score is 72% and you’d make the same call whether it was 58% or 86%, the number isn’t load-bearing. The decision is based on something else (strategy, intuition, pressure from above), and the number is decoration. That’s fine, but you should know it.
If the number being 20% different would change everything, you need tighter data. You need to know the margin of error, the sample size, the measurement method. A load-bearing number deserves load-bearing scrutiny.
This question also reveals when a decision has already been made emotionally and data is being recruited to confirm it. If no version of the number would change the outcome, the decision isn’t data-informed. It’s data-decorated.
For more on separating emotional decisions from evidence-based ones, this piece on decision-making as a core skill is worth reading.
If you want to practice these questions with a coach who won’t judge the asking, try a conversation with Merlin. Merlin can walk you through real data scenarios and help you build the habit of questioning before deciding.
What changes when you actually use this
Two scenarios. Neither is triumphant. Both are mundane. That’s the point.
A team lead starts asking Question 1 during vendor reviews. During a software renewal meeting, the vendor shows a slide: “User engagement up 34% year over year.” The team lead asks, “What’s the denominator on that usage stat?” Turns out active users dropped 30% over the same period. The per-user engagement metric looked great because the casual users had all churned. The remaining users were power users who’d be engaged regardless of the platform. That single question changes a six-figure renewal conversation from “let’s continue” to “let’s renegotiate.”
An IC in a cross-functional planning meeting uses Question 2 on a competitor analysis slide. She asks who built the analysis and what data sources it used. The answer: the sales team, using only closed-lost deal data. The product team had a different dataset (support tickets, feature requests, win-rate by segment) that told a different story. The competitor wasn’t stronger across the board. They were stronger in one segment the sales team happened to be losing. The conversation shifts from “we need to match their features” to “we need to understand why we’re losing in enterprise.”
Neither person did anything heroic. They asked a plain question at the right moment. The questions worked because they came from people who understood the business context and were willing to slow the room down for 30 seconds. One was a team lead, one was an IC. The skill is the same regardless of title.
These are leadership behaviors in practice. Not grand vision. Not strategy decks. The willingness to ask a question that might make the room uncomfortable for a moment. If your organization is working on building this capacity at scale, Risely’s leadership development solutions are designed for exactly this kind of behavioral change.
Back to the conference room from the opening. The retention chart is on screen. The line goes up. The room starts to nod.
What if that manager had asked one question? Any of the three. “What’s missing from this picture?” would have surfaced the response rate drop. “Who built this?” would have revealed it was pulled by the team that launched the onboarding program and had a stake in showing results. “If retention were 20% lower, would we change anything?” would have forced the room to reckon with whether they were even making a decision, or just confirming one that had already been made.
One question. No statistical modeling. No pivot tables. Just the willingness to be the person in the room who asks before everyone agrees.
That’s data interpretation. Not a technical skill. A behavioral one.
Try a coaching session with Merlin and practice asking the questions that change the conversation. Or explore more core management skills and where data literacy fits in.
Frequently asked questions
Do I need a statistics background to interpret data at work?
No. Data interpretation for managers is about reading what a number claims, asking whether that claim holds up, and knowing when to press before acting. Most data mistakes in business aren’t statistical errors. They’re failures to ask basic questions about context, framing, and what’s missing from the picture.
What are the most common data interpretation mistakes managers make?
Three patterns show up consistently: mistaking correlation for proof (assuming an initiative caused a result just because the timing lined up), cherry-picking data without realizing it (stopping the search once you find numbers that confirm your direction), and opting out of data conversations entirely by deferring to analysts without providing business context. All three are behavioral habits, not knowledge gaps.
How can I get better at reading data if I’m not a numbers person?
Start with three questions you can ask about any dataset: What’s missing from this picture? Who built this, and what were they trying to show? If the number were 20% different, would we still make the same decision? These questions don’t require math. They require the willingness to slow down before accepting a number at face value.
What is the difference between correlation and causation in business decisions?
Correlation means two things moved together. Causation means one thing made the other happen. In business, this distinction matters because initiatives, market shifts, seasonal patterns, and team changes all happen simultaneously. When engagement goes up the same quarter you launched a new program, correlation is present. Proof that the program caused the change requires isolating that variable from everything else that shifted.
How does cognitive bias affect data-driven decision making?
Cognitive biases shape which data you notice, which data you ignore, and how you interpret what you see. Confirmation bias leads people to stop searching once they find supporting evidence. Anchoring bias makes the first number you see disproportionately influence your judgment. System 1 thinking (fast, pattern-based) assigns credit to the most visible variable in a multi-variable outcome. Awareness helps, but structured questions help more.