The screen was flashing that ugly, aggressive shade of red, the kind that usually means the database has decided to take an unscheduled vacation or you’ve just committed an act of digital hubris. But here, in the Q3 status update for ‘Project Nightingale,’ the red was just the landscape. It wasn’t a warning; it was decor.
I’ve been trying to force-quit the background processes in my own head for days. That feeling of hitting the Escape key seventeen times, knowing the core application is frozen, but refusing to acknowledge that the power button is the only answer? That’s what this meeting felt like. Seventeen people, all professionally dressed for a funeral they insisted was a launch party, methodically narrating their piece of the failure. The Gantt chart was a massacre of dependencies, yet every single person ended their segment with the same synthesized confidence: “We anticipate a positive course correction pending Q4 resource allocation.”
It’s a lie, of course. Everyone knows it. The Product Owner, bless her heart, was tracking a metric we internally call the ‘M-score’-Mortality Score. It had been holding steady at a decisive 95 for two months. But she reported the ‘Velocity Index’ was up 5 points because we had technically closed five tickets, even though those five tickets were just renaming previous failed deliverables. The system is designed to reward activity, not outcome. Activity is visible. Outcome is risky.
The Shift in Objective
I used to think this phenomenon-the Zombie Project-was a failure of simple management. A catastrophic oversight rooted in the sunk cost fallacy. You put $4,000,000 into a venture, so you must put in $400,000 more just to justify the first mistake. Simple, sad math. But that analysis, while neat, is deeply insufficient. It assumes irrationality when, in fact, the behavior is perfectly rational if you adjust the objective function.
The Rational Custodianship of Failure
Think about it. Killing ‘Nightingale’ requires courage, but more importantly, it means admitting that the last 18 months, $15,000,000, and the collective focus of 45 high-salaried professionals were a waste. Who gets fired when a project is successfully killed? The Project Manager, the Director, sometimes the VP who greenlit it. They lose their budget, their headcount, and their authority. But what happens if the project merely fails slowly?
Risk of Accountability Mitigation
95% Progress
If it fails slowly, over the course of 2 to 3 years, everyone involved is shielded. The budget remains. The team remains. You have a plausible, constantly updated narrative of ‘challenging market conditions,’ ‘unexpected technical debt,’ or ‘strategic pivots.’ The manager has successfully preserved their domain, their relevance, and their $125k salary for another fiscal year. They become essential custodians of a problem that must, by definition, never be solved. The continuation of the zombie project is their KPI.
The Silence vs. The Tilling
❝
I saw this logic perfected by a former colleague, a woman who specialized in large-scale government integration projects. She had one project that ran for five years, delivered nothing tangible, but secured her team of 305 engineers continuous funding. When they finally pulled the plug, she was promoted for her ‘resilience and comprehensive risk mitigation.’ She hadn’t mitigated the risk of failure; she had mitigated the risk of accountability.
– Observation on Career Preservation
It makes me think of Luca R.-M., a soil conservationist I met deep in Appalachia. He wasn’t talking about Gantt charts, but about topsoil-the stuff that actually feeds us. Luca wasn’t obsessed with maximizing the harvest this year; he was obsessed with ensuring the land could produce anything 45 years from now. He spent his time rotating crops and letting fields lie fallow, allowing the ecosystem to repair itself. He called it ‘investing in the silence.’ Our organizations hate silence. They hate fallow periods. They demand continuous tilling of projects that yield dust, fearing that if the team doesn’t have a burning objective, their purpose-and their budget-will vanish.
Long-term viability. Ecosystem repair. Sustainable yield.
Short-term visibility. Immediate resource consumption. Dust yield.
Value Density vs. Volume of Effort
I remember arguing with a CFO once about a competing project. It was smaller, focused, and genuinely transformative, but it required redirecting $575k from a bloated legacy system revamp (a zombie). He couldn’t grasp the value of the focused, smaller win. He kept saying, “But the zombie gives us political weight. It proves we’re tackling the big problems, even if we’re failing.” The perception of effort became more valuable than the reality of success. This is why we cling to the colossal failure over the humble, achievable win.
There is a deep, almost spiritual difference between maintaining something that holds genuine, enduring worth and propping up a wasteful structure simply because it employs people. If you look at something truly crafted for permanence, something built with an understanding of lasting value, the contrast is sharp. For certain high-end clients, particularly those concerned with the heritage of craftsmanship and detailed luxury, resources are only allocated to things that endure. They understand the difference between high-value density and low-value volume. A highly detailed, exquisite piece, perhaps something you might acquire from a place like the
Limoges Box Boutique, is an object where every dollar spent contributed to lasting beauty and utility. The zombie project, conversely, is a massive edifice where 95% of the spending goes into maintaining the scaffolding and painting over the rot.
The Personal Cost
I’ve been on both sides. Early in my career, I was the enthusiastic champion of ‘Project Cerberus,’ a beautiful, multi-headed monster that promised everything and delivered endless meetings. My mistake wasn’t technical; it was political. I tied my identity to the project’s ambition. When my own data showed the M-score had hit 85, I argued against the data, criticizing the testing parameters, arguing that the failure was temporary-exactly the pattern I now despise. I did it because admitting Cerberus was dead meant admitting I had failed publicly, spectacularly, and had to give up my shiny budget. I spent 1,585 hours nursing a corpse because my ego was inside its thoracic cavity.
Metabolic Failure and Moral Leaching
This is the secret comfort of the Zombie Project: it removes the necessity of difficult decisions. It replaces the agonizing clarity of amputation with the soothing routine of maintenance. We are professional janitors of failure, and the organization pays us well to keep the floors shiny around the festering corpse.
The Cost of Compliance
But the cost isn’t just financial. It’s moral and emotional. Every time you redirect a brilliant, capable engineer to a pointless task, you leach a little bit of their soul. You teach them that competence is secondary to compliance. You train them to embrace the rhetoric of perpetual, slow failure. Eventually, the best people, the ones who crave actual impact, burn out and leave. The ones who remain are the ones who have mastered the art of the 95 M-score report.
We talk about organizational health, but health requires metabolism-the ability to process resources and discard waste quickly. When an organization cannot kill a project, it signals metabolic failure. It signals that the risk of truth is greater than the risk of waste. We are prioritizing the internal political comfort of 45 people over the external, real-world success of the company. It’s a tragedy dressed up as corporate governance.
The Courage to Declare Death
What would happen if, in that Q3 meeting, someone simply said: “I have failed. This project is dead. We have saved the company $5,000,000 by stopping it today, and we are redirecting 95% of this team to the project that actually has life in it”? That person would be treated like a lunatic. They would be seen as dangerous. But they would be the only one telling the truth. The real measure of organizational courage isn’t launching a new initiative; it’s burying an old one.
