At first glance, these appear to be unrelated articles.
Different years.
Different technologies.
Different market conditions.
Different protagonists.
Different industry conversations.
In reality, they represent a nineteen-year record of the same recurring observation expressed through different technologies, organizational contexts, and business conditions.
The Traffic Pattern Is the Story
People are not reading eight articles from eight different years on eight different subjects.
They are discovering that the same underlying observation kept resurfacing regardless of:
Technology generation
Procurement trend
Methodology
Framework
Platform
Market cycle
The observation itself is surprisingly simple:
Organizations rarely struggle because technology is incapable.
They struggle when operating assumptions, incentives, governance structures, decision rights, process integrity, and organizational readiness fail to align with reality.
The technology changes.
The underlying challenge does not.
Prediction Is Speculative. Observation Is Evidence.
One of the reasons I find this traffic pattern so interesting is that it reveals something important about the archive itself.
The value of the archive is not that it contains predictions.
The value is that it contains observations.
At the time each article was written, I was not attempting to forecast the future.
I was documenting what I was seeing at that moment in time.
What organizations were doing.
What was working.
What was failing.
Which assumptions were proving valid.
Which assumptions were collapsing under real-world conditions.
Those observations accumulated over years and then decades.
Viewed individually, they are articles.
Viewed collectively, they become evidence.
That distinction matters.
Prediction is speculative.
Observation is evidence.
The Discipline Behind the Archive
Every major framework I have developed emerged from the same discipline:
Observe reality.
Document reality.
Compare reality across time.
Identify recurring patterns.
Test whether those patterns remain valid under new conditions.
That process ultimately led to:
Phase 0™
Hansen Fit Score™ (HFS™)
Strand Commonality™
AGR™
Implementation Physics™
ARA™ RAM 2025™
None of these concepts appeared fully formed.
Each emerged from repeated encounters with the same underlying failure mechanics documented across hundreds of organizations, initiatives, technology deployments, and transformation efforts.
For example, Phase 0™ emerged from a recurring observation: organizations were often selecting capable technologies while overlooking whether the surrounding enterprise was prepared to absorb the outcomes those technologies would produce.
The technology selection was frequently correct.
The organizational readiness was not.
The resulting failure patterns repeated often enough that they ceased being isolated events and became observable laws.
Why This Matters in the AI Era
Many readers assume today’s discussions around AI readiness, governance survivability, verification, organizational absorption, and decision architecture represent entirely new challenges.
They are not.
The technologies are new.
The underlying questions are not.
For nearly three decades, the same pattern has appeared repeatedly:
Organizations become excited about a new capability.
Attention shifts toward what the technology can do.
Far less attention is given to whether the surrounding organization can absorb what the technology produces.
Eventually reality intervenes.
Not because the technology failed.
Because the operating environment was not prepared for its consequences.
The current AI era is not exempt from this pattern.
If anything, AI accelerates it.
Why the Archive Matters
The archive does not matter because it is old.
It does not matter because it is large.
It matters because it provides a longitudinal record of observed reality.
It allows us to compare today’s assumptions against yesterday’s outcomes.
It allows us to separate recurring patterns from temporary trends.
It allows us to stress-test current thinking against conditions that have already played out.
When you read across years rather than individual articles, you are not revisiting old topics.
You are examining how the same structural dynamics reappear under different names, different technologies, and different market conditions.
Most importantly, it allows us to see that the current AI discussion is not an isolated event.
It is part of a much longer story.
A story that began long before AI.
A story that has remained remarkably consistent across multiple technology eras.
And a story that continues to unfold today.
The real question is not whether AI will change the enterprise.
The real question is whether enterprises have changed enough to absorb what AI will produce.
That is the story the archive has been documenting for nearly three decades.
-30-
We don’t predict failure. We identify the conditions that produce it.
Technology Changes. The Story Doesn’t.
Posted on May 29, 2026
0
The Archive Is Not Telling Eight Different Stories. It Is Telling One Story Across Nineteen Years.
Over the past few days, I noticed something interesting in the Procurement Insights™ analytics.
Readers were not simply viewing recent articles. They were moving through the archive, reading posts written years—and in some cases decades—apart.
Among them were:
At first glance, these appear to be unrelated articles.
Different years.
Different technologies.
Different market conditions.
Different protagonists.
Different industry conversations.
In reality, they represent a nineteen-year record of the same recurring observation expressed through different technologies, organizational contexts, and business conditions.
The Traffic Pattern Is the Story
People are not reading eight articles from eight different years on eight different subjects.
They are discovering that the same underlying observation kept resurfacing regardless of:
The observation itself is surprisingly simple:
Organizations rarely struggle because technology is incapable.
They struggle when operating assumptions, incentives, governance structures, decision rights, process integrity, and organizational readiness fail to align with reality.
The technology changes.
The underlying challenge does not.
Prediction Is Speculative. Observation Is Evidence.
One of the reasons I find this traffic pattern so interesting is that it reveals something important about the archive itself.
The value of the archive is not that it contains predictions.
The value is that it contains observations.
At the time each article was written, I was not attempting to forecast the future.
I was documenting what I was seeing at that moment in time.
What organizations were doing.
What was working.
What was failing.
Which assumptions were proving valid.
Which assumptions were collapsing under real-world conditions.
Those observations accumulated over years and then decades.
Viewed individually, they are articles.
Viewed collectively, they become evidence.
That distinction matters.
Prediction is speculative.
Observation is evidence.
The Discipline Behind the Archive
Every major framework I have developed emerged from the same discipline:
That process ultimately led to:
None of these concepts appeared fully formed.
Each emerged from repeated encounters with the same underlying failure mechanics documented across hundreds of organizations, initiatives, technology deployments, and transformation efforts.
For example, Phase 0™ emerged from a recurring observation: organizations were often selecting capable technologies while overlooking whether the surrounding enterprise was prepared to absorb the outcomes those technologies would produce.
The technology selection was frequently correct.
The organizational readiness was not.
The resulting failure patterns repeated often enough that they ceased being isolated events and became observable laws.
Why This Matters in the AI Era
Many readers assume today’s discussions around AI readiness, governance survivability, verification, organizational absorption, and decision architecture represent entirely new challenges.
They are not.
The technologies are new.
The underlying questions are not.
For nearly three decades, the same pattern has appeared repeatedly:
Organizations become excited about a new capability.
Attention shifts toward what the technology can do.
Far less attention is given to whether the surrounding organization can absorb what the technology produces.
Eventually reality intervenes.
Not because the technology failed.
Because the operating environment was not prepared for its consequences.
The current AI era is not exempt from this pattern.
If anything, AI accelerates it.
Why the Archive Matters
The archive does not matter because it is old.
It does not matter because it is large.
It matters because it provides a longitudinal record of observed reality.
It allows us to compare today’s assumptions against yesterday’s outcomes.
It allows us to separate recurring patterns from temporary trends.
It allows us to stress-test current thinking against conditions that have already played out.
When you read across years rather than individual articles, you are not revisiting old topics.
You are examining how the same structural dynamics reappear under different names, different technologies, and different market conditions.
Most importantly, it allows us to see that the current AI discussion is not an isolated event.
It is part of a much longer story.
A story that began long before AI.
A story that has remained remarkably consistent across multiple technology eras.
And a story that continues to unfold today.
The real question is not whether AI will change the enterprise.
The real question is whether enterprises have changed enough to absorb what AI will produce.
That is the story the archive has been documenting for nearly three decades.
-30-
We don’t predict failure. We identify the conditions that produce it.
Share this:
Like this:
Related