The Data Doesn’t Speak. People Do.

The Data Doesn’t Speak. People Do.

An exploration into the human element often lost in “data-driven” decision-making.

The air in the room was cold enough to make your teeth ache. Marcus, our VP of Expansion, stood before a projection screen that glowed with a single, triumphant bar chart. The bar was royal blue, and it climbed so aggressively toward the top-right corner it felt less like data and more like a declaration of war. “The numbers are clear,” he said, his voice echoing slightly in the over-chilled space. “Q2 is the time to launch in the European market. The data shows an undeniable opportunity.”

The “Clear” Opportunity vs. The Quiet Truth

Marcus’s Vision

Big Opportunity!

Chen’s Data

42% Churn

A stark contrast between projected success and real-world challenges.

In the third row, a junior analyst named Chen cleared his throat. It was a small sound, but in the reverent silence, it sounded like a firecracker. “Marcus,” he started, his voice thin, “I was looking at the churn data for our beta cohort in Germany, and it seems to be about 42% higher than the domestic equivalent. If we factor that in…”

Marcus didn’t turn. He just tilted his head, a gesture of magnanimous patience that wasn’t patient at all. “Chen, we need to see the bigger picture here. We can’t get bogged down in the weeds.” The screen switched to a slide with a giant checkmark on it. The meeting was over. Chen’s data, the contradictory data, was now just a ghost in the machine, an inconvenient whisper that had been expertly silenced.

“This is not a search for truth. This is a ceremony of justification.”

The Corporate Splinter: Misused Data

We love to talk about being “data-driven.” It sounds so rigorous, so objective. It’s a concept scrubbed clean of human messiness, of ego, of fear. We imagine data as a pure, guiding light, a flashlight cutting through the fog of opinion. But it rarely is. More often than not, it’s a hammer. We don’t follow it; we wield it. The decision is made first, born from gut feeling, political maneuvering, or a desperate need to show momentum. Then, the hunt begins. We send our teams on a quest, not for truth, but for supporting evidence. Find me the chart that proves my point. Isolate the statistic that makes my idea sound inevitable.

Ignoring the Splinter: A Corporate Bandage

Ignoring critical issues often leads to covering them up, rather than solving them.

I just spent ten minutes removing a splinter from my thumb. A tiny, almost invisible sliver of wood that had managed to turn a whole section of my hand into a throbbing, sensitive mess. It required a sharp needle, a steady hand, and a refusal to pretend it wasn’t there. Ignoring it would only lead to infection. Pushing it deeper would be madness. You have to see the problem for what it is, in all its frustrating specificity, and carefully, precisely, remove it. Bad data, or more accurately, misused data, is a corporate splinter. The single cherry-picked chart is the executive deciding to just put a bandage over it and pretend the problem will go away. Chen was trying to be the needle, and he was told to stop poking.

I’ll admit, I was once Marcus. A few years ago, I was convinced we needed to kill a legacy feature in our software. It was clunky, built on old code, and in my mind, it was holding us back. I assembled a deck of 22 slides, each one a masterpiece of confirmation bias. I highlighted the low engagement numbers. I showcased the high rate of support tickets. I presented my case with the unwavering conviction of a zealot. My boss, thankfully wiser than I was, asked the one question I hadn’t prepared for: “Show me the data on the users who *do* use it.” I didn’t have it. Because I hadn’t looked for it. Turns out, the feature was used by only 2% of our user base, but that 2% represented nearly a third of our revenue. They were our power users, the ones who had been with us for a decade. Killing the feature would have been an act of catastrophic self-harm. My beautiful, data-supported decision was completely, utterly wrong.

The Real Cost of Confirmation Bias

Users

2%

of Total User Base

=

Revenue

1/3

of Total Revenue

A small segment of users can hold disproportionate value, a truth easily missed by biased data hunting.

It’s a peculiar form of intellectual dishonesty, made worse because it cloaks itself in the language of science. We use numbers to short-circuit debate, to create an artificial sense of objectivity that bullies dissent into silence. An opinion is debatable. A spreadsheet, however, feels like fact. And if you question the spreadsheet, you’re not a team player. You’re not seeing the big picture. You are, like Chen, stuck in the weeds.

I spoke about this once with Astrid L.-A., a body language coach who works with executives. I expected her to talk about spreadsheets, but she immediately talked about posture. “Forget the slides,” she told me. “Watch their bodies. The ‘data-driven’ leader who has already made up their mind presents numbers as a shield. They stand rigid, they use pointed gestures, and they lean away from anyone who asks a difficult question.” She said the real data in the room is often somatic. It’s the tense shoulders of the team who knows the numbers are skewed. It’s the analyst who physically shrinks after their point is dismissed. “People,” she said, “are broadcasting a constant stream of high-fidelity, analog data. Most leaders are trained to ignore it entirely in favor of a single, low-resolution chart that tells them what they want to hear.”

Taste the Meal, Don’t Just Smell the Data

This whole charade is about avoiding the hard, empirical work of finding out what’s true. It’s the opposite of how you’d perfect something real, something tangible. You can’t build a truly great potato dish, for example, by insisting that the data shows paprika is the most popular spice globally. You have to cook the potato. You have to taste it. You adjust, you test, you taste again. The result isn’t a theory; it’s right there on the plate. The process is one of discovery, not justification. The truth is found in the direct experience of the thing itself. It raises fundamental questions that have real, testable answers, not abstract ones that can be endlessly debated. You quickly learn to answer things like muss man kartoffeln schälen based on the recipe’s desired outcome, not on a pre-existing belief about peels.

The Recipe for Truth: Discovery, Not Justification

True understanding comes from direct interaction, not just abstract analysis.

One approach is an honest search for the best result; the other is a political campaign to legitimize a conclusion. It’s baffling how we accept this behavior in a billion-dollar enterprise when we would never accept it in a kitchen. No chef would last a week if they only used ingredients that confirmed their biases while ignoring the ones that didn’t.

And yet, I find myself thinking that sometimes, the only way to fight fire is with fire. I know that sounds like a contradiction. I just spent a thousand words decrying the weaponization of data, and now I’m suggesting we pick up arms. But in a culture where numbers are the only accepted language of authority, sometimes the only way to disarm a bad argument is with a better, sharper, more undeniable piece of data. Maybe Chen’s mistake wasn’t speaking up; maybe it was that he only brought a single data point to a gunfight. Perhaps he needed 12 more slides, a bigger chart, and a more aggressive shade of red to counter Marcus’s blue.

The Hidden Cost

232

Hours Wasted Annually Per Team

On defensive analytics and pre-justifying decisions.

It’s a deeply cynical thought, and I don’t like it. It feels like accepting the disease as the cure. It suggests that the path forward isn’t to abandon the ceremony of justification, but simply to become better performers in it. It requires an absurd level of energy, defending against incoming statistical attacks while launching your own, all in the service of getting closer to a truth that should have been the starting point for everyone. The cost of this internal arms race is staggering-232 hours a year per team, by one estimate I saw, are wasted on creating defensive analytics and pre-justifying decisions. The real work gets lost in the crossfire.

Maybe the answer isn’t better weapons. Maybe it’s remembering that data is just the scent of the meal, not the meal itself. It can tell you something is cooking, but it can’t tell you how it tastes. The only way to know is to sit down at the table, pick up a fork, and take a bite. Marcus had his nose in the air, smelling the distant aroma of market share, while Chen was on the ground, tasting the actual dish and warning everyone that it might be burned.

Data: The Scent vs. The Meal

The Scent

💨

The Meal

🍽️

Don’t mistake the promise for the experience.