The laser pointer is trembling. It is not because Dave is nervous-though he should be-but because the heavy industrial air conditioner in the boardroom is humming at a frequency that matches his caffeine-induced tremor. He is pointing at a thin, sapphire-colored bar on the screen labeled ‘Phase 2: Integration and Stress Testing.’ According to the slide, this phase will take 12 days. In the physical world, the one where gravity and human error exist, it will take at least 82 days. But right now, in this room, nobody says a word. We all stare at the chart like it’s a religious icon, a sacred text that promises salvation if only we believe hard enough. I can feel the collective weight of 22 people holding their breath, all of us participating in the same polite, institutionalized lie.

I’m a prison librarian by trade, and I’ve learned that the only place where time is actually honest is behind a 12-foot fence. There, if you have 3622 days left on your sentence, you will serve 3622 days. There are no ‘agile sprints’ to shave off a year. There is no executive who can pivot your release date to Q3 because the stakeholders are restless. Time is the only thing we have in abundance, and it is the only thing that never lies to us.

In this boardroom, however, time is a malleable clay. We use it to sculpt fantasies that satisfy the ego of the person with the highest salary. The project timeline is not a roadmap; it’s a tool for psychological management. If the leadership team admitted that the software wouldn’t be ready for 202 days, the stock price might dip, or the VP of Sales might lose her $52,000 bonus. So, we all agree that it will take 92 days. We agree to the lie because the truth is too expensive to acknowledge in the present moment. We would rather pay for the truth in six months, with interest, in the form of employee burnout and catastrophic technical debt.

I’ve seen this happen at least 42 times in my career. It starts with the ‘Aggressive Goal.’ This is a euphemism for a deadline that ignores the laws of physics. The project manager, who has likely spent 112 hours that month adjusting the color-coding on his spreadsheets, presents a plan that assumes everything will go perfectly. It assumes no one will get sick, no server will crash, and no client will change their mind. It is a plan built on the assumption that the world is a sterile laboratory. But the world is more like my library after a lockdown-chaotic, unpredictable, and full of people trying to sneak things past the sensors.

The Lie is a Warm Blanket

They are the ones who stay until 10:02 PM on a Tuesday, trying to fix a bug that was inevitable the moment the timeline was shortened to appease a director who hasn’t written a line of code in 12 years.

The Honesty of Physical Engineering

There is a profound disconnect between digital planning and physical reality. In the digital world, you can move a block of time with a mouse click. In the real world, you cannot make concrete dry faster or steel bend easier just because you changed the font on a slide. This is why I appreciate the approach of Sola Spaces. When you are dealing with glass, aluminum, and the structural integrity of a building, the fantasy of the ‘accelerated timeline’ disappears. You can’t negotiate with the load-bearing capacity of a beam. Engineering requires an honesty that corporate software development has largely abandoned. If an engineer tells you a sunroom will take 32 days to install, they aren’t trying to sell you a vision; they are telling you how long it takes for the materials to exist and the bolts to be tightened. There is a grounding effect in physical construction that exposes the absurdity of our digital daydreams.

Why do we keep doing it? Because the corporate ecosystem punishes the truth. If you are the one person in the meeting who raises their hand and says, ‘This will actually take 152 days, not 62,’ you are labeled as a cynic. You are told you lack ‘vision’ or that you aren’t ‘aligned with the mission.’ We have created a culture where the person who lies the most convincingly is the one who gets the most resources. It’s a race to the bottom of reality. We reward the person who promises the impossible, and then we act shocked when the project fails, costing the company $822,000 in lost revenue and emergency consulting fees.

Truth is a Structural Necessity

If we treated our project timelines with the same respect we treat architectural drawings, we wouldn’t be in this mess. You don’t see architects ‘sprinting’ to finish a foundation. They know that if the foundation is rushed, the whole structure will eventually develop cracks that no amount of paint can hide. But in the world of ‘deliverables’ and ‘milestones,’ we are obsessed with the paint. we want the project to look finished on the dashboard, even if the underlying logic is a crumbling mess of patches and workarounds. This is the pernicious nature of our optimism: it’s not actually about hope; it’s about the avoidance of immediate conflict.

I’ve watched 12 different managers come and go through the prison library system. The ones who succeeded weren’t the ones who promised to reorganize the entire 22,000-book collection in a weekend. They were the ones who looked at the dust, looked at the broken shelves, and said, ‘This is going to take 132 days of hard work.’ They were the ones who didn’t care about the blue glow of a chart. They cared about the physical weight of the books. They understood that the only way to build anything of value is to respect the time it actually takes to do it.