Six weeks late, and no single point of failure
How the real reason gets filtered out before it reaches the top.
Your status report says: complex analysis underway. Your programme is six weeks late. Both are true. Neither tells you why.
A cross-border programme. Three locations on three continents. The question: which analyses to run before the next phase.
The team that will perform the analyses consults the senior technical group at the head office. The group recommends three. The team does not hear a recommendation. They hear a directive.
The work begins. Some of the data does not exist locally. Some of the analysis requires capability the team does not have. Nobody escalates, because nobody believes the original recommendation is renegotiable. What was offered as guidance is now treated as constraint.
A third location is waiting for the output. Their own deliverable depends on it. They push. They get deflection or silence. They read the silence as stalling, incompetence, or low priority.
The team that is stuck will not name the head office as the source of the problem. Tension grows between people who used to trust each other.
Senior leadership sees a delayed project. They do not see the mechanism. The actual reason was filtered out three times before it reached the top: nobody negotiated the original recommendation. Each layer stripped out part of the reason.
Six weeks. Sometimes twelve. Not one decision. A repeating pattern.
Repeated across workstreams and decision cycles, this is how programmes lose months, then years, without a single visible point of failure.
The visible cost: penalties, slipped revenue, resources burning on stalled work. The hidden cost: trust between the locations, which is rarely named.
This pattern is not one programme. It recurs across many, in different industries.
Programmes do not fail in a single moment. They drift between people who believe they are aligned.