The sound of the champagne cork popping in the sales suite echoed through the ventilation shafts, arriving in the engineering bay as a dull, thudding omen. It was 4:08 PM on a Tuesday. I know the time exactly because that is precisely when I decided to start this ridiculous diet, and my stomach was already beginning to register its first formal protest. Across the room, Marcus, our lead architect, didn’t look up from his monitor. He didn’t need to. He knew that sound meant a contract had been signed for a project that, according to his initial 18-page technical assessment, required at least 208 days of development. He also knew, with the weary certainty of a man who has seen 88 such cycles come and go, that the sales team had just promised it would be delivered in 48.
Estimation: A Political Compromise
This is the fundamental friction of the modern workplace, a friction I watch from my literal and metaphorical lighthouse. Up here, tending to the 48 prisms that focus the beam out over the Atlantic, the world seems binary: the light is on or it is off. The rocks are there or they are not. But in the world of project management, numbers are not reflections of reality; they are chips in a high-stakes poker game where everyone is bluffing and the house-the client-always expects a royal flush on a pair-of-twos budget.
The Estimate Laundering Process
We say things like, ‘This feature will take 128 hours,’ because that 8 at the end provides a thin veneer of mathematical rigor. If we said it would take ‘about a week,’ we would be seen as amateurs. But that number isn’t a calculation. It is a political compromise… By the time the estimate reaches the client, it has been laundered through so many layers of optimism and fear that it no longer bears any resemblance to the physical reality of writing code or designing circuits. It has become a fiction.
My stomach growls again. It is now 5:28 PM. The diet is roughly 80 minutes old and I am already considering the ethical implications of raiding the emergency rations kept in the base of the tower. There is a direct parallel here. We set goals based on who we wish we were, rather than who we actually are. I wish I were a person who could survive on kale and distilled water. The sales team wishes the engineers were 38 percent faster than human biology allows.
The Unforeseen Reality
We treat these ‘human factors’ as anomalies, as ‘unforeseen circumstances.’ But they aren’t unforeseen. They are the only thing you can actually count on.
“
If you run a project for 108 days, someone will get the flu. Someone’s car will break down. Someone will have a crisis of faith in the middle of a stand-up meeting. To exclude these from an estimate isn’t being optimistic; it’s being dishonest. Yet, the politics of the office demand this dishonesty. If a lead engineer stands up and says, ‘I need 28 percent of this timeline to account for the fact that we are all fallible humans who make mistakes,’ they aren’t praised for their honesty. They are told to ‘sharpen their pencil’ and ‘be a team player.’
This is where the cycle of distrust begins. The client is promised a fantasy. When the fantasy inevitably fails to materialize-usually around the 68 percent mark of the timeline-the finger-pointing starts. But the failure didn’t happen in the middle of the project. It happened at the very beginning, the moment the first estimate was typed into a document.
The Cost of Silence
Project Trust Erodes
Project Dignity Remains
We are terrified of the silence that follows when you tell a client that their $188,000 budget is actually $288,000 short of what they need. So we say ‘Yes’ and hope for a miracle. We hope that this time, for the first time in the history of industrial civilization, the 1,008 variables of a complex project will all align perfectly. It is a form of secular prayer.
AHA #2: Ignoring The Maps
We have mountains of historical data from every project we’ve ever finished. We know, if we bother to look, that our ‘8-hour’ tasks actually take an average of 18 hours. We have the maps; we just refuse to look at them because the maps show a much longer, much more expensive route than the one we want to take. Using a tool like PlanArty allows a team to actually look at that historical data, turning those past failures into a realistic roadmap for the future, rather than just repeating the same optimistic errors.
The Dignity of Truth
This failure is now data. We can plan around it.
As I crunch on them, I feel a strange sense of relief. The lie of the ‘perfectly disciplined João’ has been exposed. I am a man who eats crackers at 6:00 PM. It is a fact. It is data. And once you have data, you can actually plan. If I know I will get hungry at 6:00 PM, I can bring a healthy snack instead of raiding the emergency supply. Projects are the same.
I’ve spent 18 years in this lighthouse, and if there’s one thing the sea teaches you, it’s that it doesn’t care about your schedule. The tide comes in when it comes in. Technical debt doesn’t care about your quarterly goals. It accumulates with the steady, crushing weight of the rising tide. You can ignore it for a while, but eventually, you’re underwater.
The Lighthouse Standard: Predictable Rhythm
The beam rotates every 18 seconds. It doesn’t try to go faster to please the ships. It just does the work, at the speed the work requires.
There is a profound dignity in that. Perhaps tomorrow, Marcus will walk into the sales office and tell them that the 48-day timeline is a beautiful fiction, and that if they want the job done right, they need to settle in for the full 208 days. He probably won’t. The champagne has already been drunk, and the $888 commission checks are already being calculated. But a man can dream, even on a stomach full of crackers and unfulfilled promises.
