This is a failure of diagnosis.
Assuming incompetence implies the system itself is sound. The reality is that the manager is acting rationally inside an incentive structure that severely punishes the correct decision and quietly rewards the wrong one. They are optimizing for survival, not for the project's outcome.
⸻
The Cost of Friction
Making a hard decision requires spending political capital upward. It requires telling leadership something that contradicts their projections. In a healthy organization, this friction is expected. In a brittle organization, the messenger is punished.
Consider a failing vendor. Firing them means admitting the initial selection was wrong. Delaying the attached launch creates a visible gap in the quarterly roadmap that a vice president will immediately scrutinize. The manager looks at this math.
Doing nothing avoids all immediate friction. The project continues to drift, but the erosion is slow and deniable. The manager trades a fast, identifiable explosion for a slow, distributed failure. This is not weakness. This is a calculated survival vector.
⸻
Diffusion of Responsibility
A bold decision isolates the decision maker. If the decision fails, there is exactly one person to hold accountable. A weak decision diffuses that accountability across the entire system.
Instead of making the call, the manager forms a committee. They defer the choice to "further study" or escalate it to an architecture board that meets once a month. This is engineered risk distribution.
If the status quo eventually collapses, the failure is absorbed by the bureaucracy. No single person made the call, so no single person can be blamed. The manager who defers the problem into oblivion gets to keep their job, while the one who takes a bold risk is fired.
⸻
The Illusion of Progress
Organizations demand motion. A project that is "in progress" is considered safe, regardless of its actual trajectory.
So the manager adds a heavy weekly synchronization meeting instead of firing the failing vendor. They commission a deep look analysis instead of addressing the structural flaw you pointed out. None of these actions solve the underlying problem. But they produce the correct signals for the system above them. There is a new recurring meeting on the calendar. There is a slide deck being circulated.
The system reads this as governance. The problem reads this as stalling.
⸻
Operating Without a Shield
When the management layer optimizes for survival over outcomes, the shield is gone. The system is protecting itself, not you.
Waiting for a manager to suddenly find courage is a failure of your own judgment. The orientation is to see the terrain for what it is. Do not present problems that require political courage to solve. Repackage your solutions beautifully in terms of the manager's incentives. If they heavily fear upward friction, find a technical path that eliminates the threat silently.
When judgment above is compromised, the paper trail becomes your only defense. Log the data and log your recommendations. You cannot repair a compromised decision layer from below. But you can navigate it, provided you treat it as physics rather than a character flaw.
⸻
End.