If You Keep Doing What You Have Always Done, You Will Always Get the Same Outcome. Seven Technology Eras Prove It.

Posted on April 8, 2026

0


If you resign yourself to doing what you have always done, you will always get the same outcome.

That is how you go through seven different technology eras and never improve outcomes.

For nearly three decades, the enterprise technology industry has cycled through transformation after transformation. Each era arrived with new platforms, new promises, and new analyst frameworks telling organizations what to buy and how to deploy it.

The failure rate never moved.

The Seven Eras. The Same Result.

ERP. eProcurement. SRM. P2P. Analytics. Cloud. AI.

Seven distinct technology cycles. Seven rounds of vendor selections, implementation roadmaps, Gartner Magic Quadrants, McKinsey transformation frameworks, and Big Four advisory engagements.

And across all seven — a consistent 55–80% implementation failure rate documented independently by RAND, MIT Sloan, McKinsey, Deloitte, and Gartner itself.

The technology changed. The outcomes did not.

There is only one explanation for that consistency: the variable that determines success was never addressed. Not in the first era. Not in the seventh. Not in any of the five between them.

That variable is organizational readiness — the pre-commitment conditions that determine whether a technology deployment can succeed before the decision is made.

“Nobody Ever Got Fired for Buying Gartner”

There is a saying in enterprise technology that has protected incumbent advisory firms for decades: nobody ever got fired for buying IBM. The modern equivalent is nobody ever got fired for buying Gartner.

It has been the perfect organizational shield. When an initiative fails — and across seven technology eras, most of them do — the decision-maker points to the Magic Quadrant, the analyst briefing, the McKinsey framework. The process was followed. Due diligence was done. The right firms were engaged.

And the failure rate held at 55–80% across every cycle.

If the same model has delivered the same outcome across seven eras, the question isn’t who followed it — it’s whether it was the right model to begin with.

Not because Gartner lacks intelligence. They have enormous amounts of it. But because the intelligence they sell is the wrong instrument for the problem organizations are actually trying to solve. Gartner tells you which vendor is capable. It does not tell you whether your organization is capable of absorbing that vendor’s capability. Those are different questions — and only one of them determines whether the implementation succeeds.

The organizations that kept buying the same advisory model, following the same frameworks, and selecting from the same Magic Quadrant got exactly what they paid for. Point-in-time vendor assessments. Post-commitment implementation support. And the same failure rate, cycle after cycle, era after era.

The Variable That Was Always Missing

At the Department of National Defence in 1998, the instinct was to chase the train — automate the process, make it faster, deploy the technology. Instead, I stopped and asked a question nobody had thought to ask: what time of day do orders come in?

That question — not the technology — moved delivery performance from 51% to 97.3% in 90 days. Before a single piece of technology was introduced.

If we had accepted the situation as the boss and kept running for the train, we would have automated a broken process faster. We would never have arrived at 97.3%.

The diagnostic question was not in Gartner’s framework. It was not in McKinsey’s transformation playbook. It was not in any of the advisory models that have guided seven technology cycles of enterprise transformation.

It is in Phase 0™. It has been since 1998.

The Break in the Pattern

The 27-year Procurement Insights archive has documented this pattern across every technology cycle since the late 1990s. Zero vendor sponsorships. Zero paid analyst relationships. The conclusion has been consistent from the first entry to the last: organizations do not fail because the technology does not work. They fail because they deploy it into conditions that cannot sustain the outcome.

MIT, McKinsey, Stanford HAI, and BCG have now independently arrived at the same finding — without coordination, without access to the archive, and without knowing each other’s conclusions. The convergence is documented.

The advisory model that guided seven eras of failure is not going to diagnose the conditions that caused it. It was not designed to. Its commercial architecture depends on the post-commitment engagement model that arrives after the conditions are already set.

Phase 0™ operates in the only window where those conditions can be changed — before the commitment is made. And the commitment should never be made until the right outcome — the real outcome — is achieved.

Seven eras. Same failure rate. Same advisory model. Same missing diagnostic.

The eighth era does not have to repeat the pattern.

But it will — for every organization that resigns itself to doing what has always been done.


One Final Thought

Based on our own real-world experience with RAM 2025™ multimodel validation, autonomous AI will not reliably achieve strategic outcomes in complex environments without human oversight. The models provide analytical depth, pattern recognition, and adversarial scrutiny. The human provides judgment, timing, relationship intelligence, and the capacity to ask the question the system did not know it needed. Remove the human from that equation and you do not get better decisions. You get faster ones — pointed in the wrong direction.


The Procurement Insights archive contains 3,300+ independently produced documents spanning 18 years. Zero vendor sponsorships. Zero paid analyst relationships. RAM 2025™ multimodel validation confirms findings across five independent models.

Phase 0™ is the pre-commitment organizational readiness diagnostic. It exists in the only window where the outcome is still changeable — before the commitment is made.

Book a 30-Minute Readiness Conversation


-30-

Posted in: Commentary