The Theater of Objectivity: Why the 47-Slide Deck Never Mattered
The Whine of Precision (47 Decibels)
The fan in the overhead projector has this specific, oscillating whine that hits exactly 47 decibels, I’m sure of it. I am sitting in Conference Room B, watching Sarah navigate the 27th slide of a presentation that has already consumed 37 days of our lives. On the screen, a heat map shows that Vendor A out-performs Vendor C in latency by exactly 17 percent. The colors are crisp. The axes are labeled with a precision that suggests we are doing something noble, something scientific. We stayed late 7 nights in a row for this, eating lukewarm pizza that tasted like cardboard and corporate penance. We were seeking the ‘Truth’ with a capital T, or so we told ourselves.
Then the CTO, a man who wears a watch that costs more than my first two cars combined-let’s say $7,777-leans back in his ergonomic chair. He doesn’t look at the screen. He doesn’t even look at Sarah. He looks at his own reflection in the polished mahogany table, adjusts his cufflink, and clears his throat. ‘Great work, Sarah,’ he says, and you can hear the ‘but’ vibrating in the air from 17 offices away. ‘I played golf with the CEO of Vendor C last week. Good guy. Salt of the earth. He told me about their roadmap, and I think they’re the right fit for our culture. Let’s move forward with them.’
(The First Verdict)
I felt something snap in my chest. It wasn’t anger, not exactly. It was more like the feeling I had last Tuesday when I cried during a commercial for a local bank-the one where the old man finally buys his granddaughter a bicycle. I’m becoming emotionally porous, I think. Everything feels too heavy or too hollow. In that conference room, the hollowness was deafening. We weren’t there to find the best vendor. We were there to provide the narrative scaffolding for a decision he had already made over a gin and tonic on the 17th hole.
🎭
We call this ‘being data-driven.’ It’s a beautiful lie we tell ourselves to keep from admitting that we are mostly just apes in expensive suits following our guts and our social hierarchies.
The Rhetorical Shield (37 Fissures)
Take Paul G., for example. Paul is a safety compliance auditor I worked with back in my 27th year. Paul is the kind of guy who carries 7 different types of measuring tape and has a 107-point checklist for every hallway he walks down. He once showed me a report where a warehouse floor was graded as ‘Critical Risk’ because of 37 separate structural micro-fissures. He had the data. He had the photos. He had the 17-page addendum from the structural engineer.
But the site manager didn’t want to shut down for repairs. So, he hired a consultant who looked at the same 37 fissures and categorized them as ‘Settling Anomalies.’ The site manager used the second set of data to justify the decision he’d made before Paul even opened his clipboard. The data didn’t change the reality of the floor; it just changed the story the company told its insurance provider. Paul G. eventually quit and started a 7-acre lavender farm, which is probably the only logical response to realizing your life’s work is being used as a rhetorical shield.
The Ghost in the Machine (77 Variables)
This is the frustration that sits at the heart of modern engineering. We are trained to believe in the sovereignty of the metric. We think that if we can just gather 77 variables and run them through a sufficiently complex model, the right answer will emerge like a ghost from a machine. But in the boardroom, that ghost is usually just the VP’s intuition wearing a sheet made of Excel spreadsheets.
[The data is the costume, not the actor.]
The Observation
There is a specific kind of exhaustion that comes from being the person who builds that costume. You spend 477 hours cleaning a dataset, removing outliers, and ensuring that the p-value is significant. You present it with the hope that the truth will be self-evident. And then you watch it get discarded because someone ‘has a feeling.’ It makes you want to stop looking at the numbers entirely. Why bother with 107 rows of analysis when the final result is dictated by who someone went to prep school with 37 years ago?
The Blame Offload (The Data Fall Guy)
We pretend it’s about the 17 percent latency improvement when it’s actually about the comfort of a familiar relationship. To admit that decisions are emotional is to admit that the system is fallible. So we maintain the theater. We produce the 47-slide decks. we hire the auditors like Paul G. to give us the ‘all clear’ even when the floor is literally cracking under our feet. It’s a ritual. It’s a way of offloading the blame.
If Vendor C fails, the CTO won’t say, ‘I made a bad call at the golf course.’ He’ll say, ‘The data we had at the time, as evidenced by Sarah’s 107-page report, suggested they were the optimal choice.’ The data is the fall guy.
The Architect’s Fear
I remember a project where we had to choose a database architecture. We did a 7-week study… The clear winner was a distributed SQL solution. But the Lead Architect had spent 7 years working with a specific NoSQL document store, and he simply didn’t want to learn something new. He spent the next 17 days finding 7 fringe edge cases where the SQL solution might-might-fail under a load we would never actually see. He used data to murder the better option because he was afraid of being a novice again.
The Human Glitch (107 Million Years Old)
We all do it, to some extent. I do it. I’ll decide I want a new phone, and then I’ll spend 47 minutes looking for the one review that says the battery life is actually okay, ignoring the 17 others that say it’s a disaster. I find the data that makes me feel safe in my desires. It’s a human glitch, a bug in our 107-million-year-old operating system.
I’m tired of the performance. I’m tired of the 47-slide decks that act as tombstones for 37 days of lost labor. Maybe the next time I’m in a meeting like that, I’ll just pull up that bank commercial. I’ll let everyone cry for 17 seconds, and then we can finally talk about the fact that the CTO just really likes the guy from Vendor C. It would be the most honest 17 minutes of my entire career.
The Lavender Truth
You can’t fudge the data on a lavender crop.
I think Paul G. had the right idea with the lavender. You can’t fudge the data on a lavender crop. Either the plant lives or it dies. There are no consultants to tell you the 37 withered stalks are actually just ‘dormant success stories.’ There is only the soil, the sun, and the 7-day weather forecast that doesn’t care about your golf game. There is a terrifying beauty in that kind of truth-the kind that doesn’t need a slide deck to exist.
Further Reading on Practical Integrity:
