Field Evidence · Fort Leavenworth
Eight years of attempts. Delivered in 45 days.
On the first day of a new contract, the customer walked into the office and asked for something they had been trying to get built for eight years. They had tried internally. They had tried other contractors. Nobody had delivered it.
8 years
Prior attempts, internal and contracted, none delivered
45 days
Developed, tested, verified and delivered into production
Day one
The request arrived on the first day of the contract
A new team
People who had not worked together before
The Situation
An eight-year problem, handed over in ten minutes.
It arrived without ceremony. Day one of the contract, and the request came across the desk almost as an aside, with a suggested timeline of ten days. That casualness is worth sitting with. A requirement that had resisted eight years of effort was being described as a week and a half of work by the person asking for it.
The obvious reading is that the customer was being unrealistic. The more useful reading is that nobody involved, on either side, had a clear picture of what the work actually was. Eight years of failed attempts had produced a great deal of material, and that material had become a substitute for understanding. Each new team inherited it, treated it as the definition of the problem, and began work from there.
When something has failed for eight years, the accumulated work is not an asset. It is a record of a misunderstanding, repeated.
The Turn
Throwing away everything we were given.
The first real work was not building. It was reading the intent. Not the specification, and not the pile of prior attempts, but the question of what this thing needed to do and how its parts actually related to one another once you looked past how they had been described.
Once those relationships were clear, so was the verdict on the inherited material. It was built on a reading of the requirement that did not hold. Keeping any of it would have meant carrying the original error forward one more time, which is precisely what the previous eight years consisted of. So it went in the bin, all of it, and the work restarted from intent.
It is worth being plain about what that decision costs. Discarding eight years of accumulated effort in the opening days of a contract is not a comfortable thing to propose to a customer, and on most programmes it is not a decision a delivery team is permitted to make at all. It is also the entire reason this case has a different ending from the eight that preceded it.
The Diagnostic
Reading the conditions, not the backlog
Nothing about this was a capability problem. The people who had tried before were not less able, and the technology was not the obstacle. What separated this attempt from the previous ones was the conditions the work was done under.
Attention
Aimed at the artifact
Eight years of effort had been directed at the material that had accumulated around the request rather than at what the customer needed the result to do. Each attempt inherited the previous attempt’s assumptions and worked harder inside them. Attention was never scarce here. It was pointed at the wrong object.
Alignment
Never established
The clearest evidence was the ask itself. The request arrived with a suggested timeline of ten days, offered casually. A ten day estimate on an eight year problem is not an unreasonable deadline so much as a signal that no shared understanding of the work existed, on either side of the table.
Authority
Primary enabler
The decision that unlocked this was the decision to discard everything that had been handed over. That call had to be made early and made locally. On a team without the authority to reject inherited work, it travels up a chain, meets the people who commissioned that work, and quietly dies. Here it was made in days.
Adaptability
Present from the start
A team formed that month had no established way of doing things to defend. That is usually treated as a disadvantage. In this case it meant the team could organise around what it found rather than around what it had always done, which is exactly the flexibility the previous attempts lacked.
Delivery
Forty-five days, by a team that had never worked together
From the decision to restart, the work ran forty-five days through development, testing and verification, and into production. The customer got the working product they had been asking for.
The part that deserves emphasis is who did it. This was a newly formed team. These were people who had not worked together before, with no shared history, no established rhythm, and none of the accumulated familiarity that is usually offered as the explanation for why a group performs well. They had the Four A's applied deliberately from the first week, and that turned out to be enough.
A team with no history outperformed eight years of institutional effort. Not because the people were exceptional, but because the conditions were built on purpose rather than inherited.
What This Case Teaches
Three things worth taking from it
A long-running failure is usually a definition problem
When capable people fail at something repeatedly over years, the odds that the ninth attempt needs more effort are low. The odds that all eight attempts were solving a misstated problem are high. The first move on inherited work is to establish what the result actually needs to do, before deciding whether any of the existing material deserves to survive.
Sunk work is the hardest thing to put down, and often the most important
Eight years of artifacts carry enormous gravity. They represent budgets defended and reputations attached. That gravity is exactly why each successive team kept building on a foundation that could not hold. Someone has to be able to say the material is wrong, early, and be permitted to act on it.
Team history is not the variable people think it is
The team here had none. No shared shorthand, no established trust, no prior wins together. It still delivered what eight years of established teams had not. Familiarity is pleasant and it is not the thing producing the result. The conditions are.
Related Reading
OPM Data Warehouse Recovery
Twenty failing daily processes to more than 1,600 reliable ones, with the client named and the figures stated.
The Knowledge-Authority Gap
Why placing decisions at the wrong level is the hidden cause of most organizational slowdowns.
That Won't Work Here
Four words that end meetings, bury ideas, and explain entire organizational cultures.
Work With Us
Sitting on something that has stalled for years?
Long-running failures are rarely capability problems. Mission Intelligence Systems diagnoses what the conditions are actually producing, and what has to change before the next attempt.