The projector fan is a low, industrial wheeze, the kind of sound that fills the gaps where confidence should be. I’m staring at slide 21, which is a timeline that I spent 31 hours meticulously crafting with a team of leads who actually know how to code. It says twenty-one months. It says that because we’ve accounted for the 11 edge cases in the legacy database, the migration of 1001 user accounts, and the inevitable churn of at least 1 senior architect who will realize they’d rather bake bread in Vermont than deal with our tech debt. It’s an honest estimate. It’s a death sentence.

Opposite me, the CEO’s phone vibrates against the mahogany table-a sharp, jarring rattle that sounds like a warning. He doesn’t look at me. He looks at his screen. A deck has just arrived from a competitor. I know what’s in it because I’ve seen this play 11 times in the last decade. They’re promising 11 months. They’re promising a total cost of $500,001. They’re promising the moon, and I’m standing here offering a realistic flight plan to the upper atmosphere with a 21 percent chance of turbulence. My honesty isn’t a virtue in this room; it’s a friction point. It’s an obstacle to the collective delusion required to get a project funded.

I’m thinking about that wave earlier today. I was walking into the lobby and someone waved. I waved back, a big, enthusiastic motion, only to realize they were looking at the person 1 step behind me. That stinging, localized heat in your cheeks? That’s what this meeting feels like. I’m waving at a reality that doesn’t want to see me. I’m offering a hand to a process that would much rather high-five a lie.

We’ve built an entire industry on the back of the “Optimism Bias,” but it’s more insidious than just being hopeful. It’s a structural incentive to lie. If I tell the truth and say 21 months, the project gets canceled, or worse, given to the guy who says 11. If the guy who says 11 months gets the job, he gets the funding, he hires the staff, and then, at the 11-month mark, he simply says, “Oh, we hit some unforeseen blockers.” He asks for more money. He gets it, because by then, the company is too deep to quit. Sunk cost is the best friend of a confident liar. I’m the idiot who tried to be honest up front, which meant I never even got the chance to fail. I was killed by the estimate before the first line of code was ever written.

The Inspector Analogy

Hayden K.-H. knows this feeling better than anyone. Hayden is a carnival ride inspector I met during a layover in 31-degree weather. He spends his days looking at the guts of things that are designed to look fun but are actually just physics trying to kill you. He told me once that people hate the guy who finds the crack in the Ferris wheel axle. They don’t see a hero saving lives; they see a guy who’s closing the ride and ruining the Saturday. “The inspector who says ‘Everything looks great’ gets a cup of coffee and a smile,” Hayden told me. “The guy who says ‘This bolt is 1 millimeter off’ gets a headache and a stack of paperwork.” We’ve turned software development into a carnival. The executives are the kids who want to go fast, and the honest engineers are the inspectors trying to explain that the centrifugal force is going to launch the passenger car into the parking lot.

But the kid doesn’t want to hear about G-force. The kid wants to hear about the loop-de-loop.

There is a specific kind of violence in a spreadsheet. When you see a row that says “Testing: 1 week,” and you know for a fact that it takes 41 days just to get the staging environment to stop crashing on boot, you feel a physical ache. You want to speak up. You want to be the person who says the king is naked, but the king is paying for your health insurance and your 401k. So you sit there. You watch the CEO nod at the 11-month proposal. You see the light in his eyes-the light of a man who thinks he’s found a shortcut. There are no shortcuts in systems of high complexity. There are only deferred costs.

I remember one project where we tried to be “agile” by ignoring the 11-month estimate altogether and just working in 2-week sprints. It was like trying to build a bridge by throwing stones into a river and hoping they’d stack themselves up before the tide came in. We had 111 developers on that project. Every single one of them knew we were sinking, but because the “official” timeline said we were 71 percent done, nobody wanted to be the one to mention the water in the engine room. It’s a psychological safety issue, sure, but it’s also a survival strategy. In many organizations, being the bearer of bad news is functionally equivalent to being the cause of the bad news. If I tell you the project will take 21 months, I am the reason it takes 21 months. If you believe the guy who says 11, and it ends up taking 31, well, that’s just “unforeseen circumstances.”

The Cost of Lies

This is why I’ve started to look at specialized firms that actually handle the mess. When you’re dealing with something like financial technology, where a single decimal point error can trigger a $1,000,001 loss in a millisecond, you can’t afford the “6-month miracle” promise. People who work in high-stakes environments alongside a trading platform development team, usually understand that the cost of a lie is compounded by interest. You either pay for the truth now, or you pay for the catastrophe later. There is no third option where the software just magically assembles itself because a Sales VP promised it would.

The Ferris Wheel Incident

I think back to Hayden K.-H. and his Ferris wheels. He once found a structural flaw in a ride that had been running for 21 years. The owner was livid. He called Hayden every name in the book. He tried to get Hayden fired. He said Hayden was “stalling progress” and “costing the local economy.” Two weeks later, another inspector-one who was a bit more ‘optimistic’-cleared the ride. It ran for 41 days before a support beam buckled. Nobody died, luckily, but the ride was scrapped. The owner didn’t call Hayden to apologize. He just complained that the new ride was more expensive.

We punish the accurate because accuracy is boring and expensive. We reward the optimistic because optimism feels like leadership. If I stand up in this meeting and say, “Sir, the 11-month estimate is a fabrication designed to win the contract, and if we sign it, we are committing to a failure that will manifest in exactly 311 days,” I am the buzzkill. I am the reason the mood in the room shifted. I am the one who isn’t a “team player.”

The Data Lie

It’s a strange contradiction. We claim to value data-driven decision-making, yet we ignore any data that doesn’t fit the narrative of rapid growth. We have 51 different Jira dashboards, 11 different communication channels, and 1 central lie that we all agree to protect. The lie is that we can control the timeline of discovery. Software isn’t manufacturing; it’s a series of discoveries. You don’t know how long it takes to find a needle in a haystack until you start moving the hay. But the CEO wants me to give him a schedule for the needle-finding. And if I say I don’t know, he’ll find someone who says they can find 11 needles by Friday.

I’ve spent 11 years in this cycle. I’ve seen projects that were “71 percent complete” for 21 months. I’ve seen $1,000,001 budgets turn into $5,000,001 budgets because nobody had the courage to say “no” at the beginning. And yet, here I am, waving back at the wrong person again. I’m hoping that this time, if I explain the 21-month roadmap with enough clarity, they’ll see the wisdom in it. I’m hoping they’ll choose the inspector over the carnival barker.

The Illusion of Magic

But as the CEO closes my deck and opens the competitor’s, I see the look on his face. It’s the look of a man who wants to believe in magic. He doesn’t want the 21-month reality. He wants the 11-month fantasy. And he’ll get it. He’ll get the fantasy for the first 11 months, and then he’ll get a very expensive reality for the next 21.

I realize now that the estimate didn’t kill the project. The project was already dead. It was killed by the requirement that it be easy. It was killed by the refusal to accept that complexity has a fixed price, and you can either pay it in time or pay it in blood. I’m just the guy holding the bill, standing at the edge of the ride, watching the first passengers climb into a car that I know isn’t bolted down quite right. I’ll keep my notes. I’ll keep my 21-month plan in a folder labeled “I Told You So,” though I’ll never actually open it. There’s no joy in being right about a disaster.

The Inspector’s Sleep

Maybe I should have just lied. It would have been easier. I would have been the hero for at least 11 months. I could have bought a boat. But then I think about Hayden, standing in the rain with his flashlight, looking at a rusted bolt. He sleeps well at night. I want to sleep well too, even if I have to do it in a house I can only afford because I’m the only one who knows the roof is going to leak in 31 days.

The CEO looks up. “Can we do it in 11?”

I look at the 21 on my slide. I look at the 11 on his. I think about the guy waving in the lobby.

“No,” I say.

And just like that, I’m invisible again.