By Jon W. Hansen | Procurement Insights | March 2026
A supply chain event invitation arrived in my inbox this morning with the following line:
“Stop buying new tech to patch a broken foundation.”
It is the right instinct.
And it raises a question more important than the invitation was designed to answer:
What exactly is the foundation — and how do you know it is broken?
Where Most Conversations Stop
When organizations diagnose a broken foundation, the answer usually comes quickly:
Disconnected systems. Lack of visibility. Inconsistent data. Poor integration between functions.
From there, the conclusion feels logical — the problem is architectural. And the solution follows: better integration, more advanced platforms, AI-driven orchestration, end-to-end visibility layers.
All of that is genuinely valuable work. And it addresses a real category of problem.
The gap is in the assumption underneath it: that once the systems are connected and the data is clean, the process will hold.
That assumption is almost never tested. And it is almost always wrong.
Where the Foundation Actually Breaks
The Procurement Insights archive has been documenting enterprise technology implementation across seven consecutive technology eras — from ERP through eSourcing, P2P, SRM, CLM, and now AI. The pattern across all of them is consistent:
The failure is rarely in what the technology can do. It is in what the process can sustain.
More specifically — incentives that drive behavior away from the intended process. Timing pressures that force workarounds. Exception pathways that become the norm rather than the edge case. External dependencies that reshape outcomes in ways the system never modeled.
These are not architectural failures. They are process structural integrity failures.
And the distinction matters, because the solution to an architectural failure is a better architecture. The solution to a process structural integrity failure is a readiness diagnostic that verifies whether the behavioral conditions of the process are aligned with what the technology is expected to produce — before the technology is deployed.
The Proof Case
In the late 1990s, the Department of National Defence engaged our team to address a procurement performance failure. Delivery performance had collapsed to 51%. The systems were connected. The data was available. The governance framework was documented and largely intact.
The foundation looked sound.
We asked one question.
What time of day do orders come in?
The answer exposed a behavioral misalignment that no architectural assessment had found. Service technicians were batching orders at 4pm — driven by their own incentive structure, not by the process design. Late-day orders triggered premium pricing, missed customs windows, and collapsed delivery performance. The process said one thing. The actual behavior said something entirely different.
The fix was not a new system. It was a readiness diagnostic that identified the behavioral misalignment before the technology intervention began. Delivery performance went to 97.3% in three months and held for seven years.
That is not an architectural story. It is a process structural integrity story.
And it is the story most transformation initiatives never tell — because the question was never asked.
The AI Acceleration Effect
In warehouse and fulfillment environments — exactly the context the Softeon invitation was addressing — the stakes are even higher in the current moment.
AI does not just automate tasks. It learns from existing conditions, reinforces them, and scales them consistently. What once showed up as friction, delay, or inconsistency in a human-operated process becomes smooth, repeatable, and harder to question when an AI system inherits it.
The process does not improve. It becomes normalized — at the speed and scale of AI.
Great technology will never overcome a lack of process integrity, resulting in poor governance.
This is why “stop buying new tech to patch a broken foundation” is exactly the right starting point — but the conversation has to go one layer deeper before the technology decision is made.
The Distinction the Industry Needs
Governance architecture describes how the system is intended to work. It documents decision rights, integration flows, escalation paths, and accountability structures.
Process structural integrity determines whether the system actually holds when real-world conditions arrive — when incentives conflict, timing pressures mount, exceptions accumulate, and the behavioral reality of the organization diverges from its documented design.
Connecting systems closes the architectural gap.
Diagnosing process structural integrity closes the behavioral gap.
Both are necessary. The sequence matters.
Process Integrity → Governance → Technology
Most organizations build it in reverse. They deploy the technology, implement the governance, and discover the process integrity gap in the post-mortem. By which time the technology has already inherited — and scaled — whatever behavioral conditions it found.
The Bridge
The supply chain and procurement community has been saying versions of “stop patching a broken foundation” for as long as implementations have been failing. That instinct is correct, and every vendor, consultant, and practitioner who has ever said it was pointing at something real.
The bridge this archive has been building for 18 years is the instrument that answers the question the slogan raises: how do you know the foundation is broken, and what kind of break is it?
Not a system break. Not an integration gap. A behavioral break — the gap between how the process is designed to work and how people actually behave within it under real-world pressure.
That is the break that technology cannot fix. It has to be diagnosed before the technology arrives.
The Archive Behind the Argument
The distinction between architectural and behavioral breaks is not a theory. It is the pattern the Procurement Insights archive has been documenting since 2007 across seven consecutive technology eras, 23 crisis events, and 3,300+ independently published documents. These four graphics show what 18 years of independent, unconflicted, contemporaneous evidence looks like.
Archive documented above the line. Market arrivals below. Two parallel tracks converging at 2026 — the moment the market arrived at the question the archive has been answering since 2007.
Five concepts the archive documented alongside the years it took the market to arrive at the same conclusion. The gap between teal and orange is the commercial case for zero vendor sponsorships.
Every major supply chain shock from 2007 to 2026 — each one a data point in the reversion dataset. The Iran War / Hormuz closure at the far right: all five vectors archive-predicted before February 28.
The growth curve from 80 documents in 2007 to 3,300+ in 2026. The zero vendor sponsorships baseline runs flat underneath it throughout. “Still recording” is not a tagline. It is the status of the record right now.
This post was prompted by a supply chain event invitation. The instinct behind the marketing line is sound — and it opens a conversation the archive has been having since 2007. If your organization is navigating a similar question before a major technology investment, the diagnostic is below.
Are You Phase 0™ Ready?
Most AI and transformation initiatives don’t fail because of capability. They fail because the process they operate within cannot sustain what is being asked of it under real-world conditions.
Your Readiness Check
Identify: Name the AI initiative or technology deployment your organization is currently scoping or evaluating.
Check: Before that deployment was scoped — was there a verified answer to this question: are the behavioral conditions of the process aligned with the outcome the AI is expected to produce?
Decide: If the answer is no — or was never asked — the AI will not correct those conditions. It will scale them.
Act: Ask the one equivalent question the data layer cannot answer: “What time do our orders come in?” The answer will tell you more about your readiness than any platform capability assessment.
One next step: Book a 30-minute readiness conversation. 📅 calendly.com/jon-toq/30min
The full diagnostic framework: The Hansen Fit Score™ — What It Does, Who It’s For, and Why It Matters Now
Jon W. Hansen is the founder of Hansen Models™ and Procurement Insights — 18 years, 3,300+ published documents, zero vendor sponsorships. The HFS™, Phase 0™, and RAM 2025™ are proprietary frameworks developed independently.
© 2026 Jon W. Hansen | Procurement Insights | hansenprocurement.com | hpt@hansenprocurement.com
-30-
Procurement Insights 
Stop Buying New Tech to Patch a Broken Foundation — But First, How Do You Know It’s Broken?
Posted on March 26, 2026
0
By Jon W. Hansen | Procurement Insights | March 2026
A supply chain event invitation arrived in my inbox this morning with the following line:
“Stop buying new tech to patch a broken foundation.”
It is the right instinct.
And it raises a question more important than the invitation was designed to answer:
What exactly is the foundation — and how do you know it is broken?
Where Most Conversations Stop
When organizations diagnose a broken foundation, the answer usually comes quickly:
Disconnected systems. Lack of visibility. Inconsistent data. Poor integration between functions.
From there, the conclusion feels logical — the problem is architectural. And the solution follows: better integration, more advanced platforms, AI-driven orchestration, end-to-end visibility layers.
All of that is genuinely valuable work. And it addresses a real category of problem.
The gap is in the assumption underneath it: that once the systems are connected and the data is clean, the process will hold.
That assumption is almost never tested. And it is almost always wrong.
Where the Foundation Actually Breaks
The Procurement Insights archive has been documenting enterprise technology implementation across seven consecutive technology eras — from ERP through eSourcing, P2P, SRM, CLM, and now AI. The pattern across all of them is consistent:
The failure is rarely in what the technology can do. It is in what the process can sustain.
More specifically — incentives that drive behavior away from the intended process. Timing pressures that force workarounds. Exception pathways that become the norm rather than the edge case. External dependencies that reshape outcomes in ways the system never modeled.
These are not architectural failures. They are process structural integrity failures.
And the distinction matters, because the solution to an architectural failure is a better architecture. The solution to a process structural integrity failure is a readiness diagnostic that verifies whether the behavioral conditions of the process are aligned with what the technology is expected to produce — before the technology is deployed.
The Proof Case
In the late 1990s, the Department of National Defence engaged our team to address a procurement performance failure. Delivery performance had collapsed to 51%. The systems were connected. The data was available. The governance framework was documented and largely intact.
The foundation looked sound.
We asked one question.
What time of day do orders come in?
The answer exposed a behavioral misalignment that no architectural assessment had found. Service technicians were batching orders at 4pm — driven by their own incentive structure, not by the process design. Late-day orders triggered premium pricing, missed customs windows, and collapsed delivery performance. The process said one thing. The actual behavior said something entirely different.
The fix was not a new system. It was a readiness diagnostic that identified the behavioral misalignment before the technology intervention began. Delivery performance went to 97.3% in three months and held for seven years.
That is not an architectural story. It is a process structural integrity story.
And it is the story most transformation initiatives never tell — because the question was never asked.
The AI Acceleration Effect
In warehouse and fulfillment environments — exactly the context the Softeon invitation was addressing — the stakes are even higher in the current moment.
AI does not just automate tasks. It learns from existing conditions, reinforces them, and scales them consistently. What once showed up as friction, delay, or inconsistency in a human-operated process becomes smooth, repeatable, and harder to question when an AI system inherits it.
The process does not improve. It becomes normalized — at the speed and scale of AI.
Great technology will never overcome a lack of process integrity, resulting in poor governance.
This is why “stop buying new tech to patch a broken foundation” is exactly the right starting point — but the conversation has to go one layer deeper before the technology decision is made.
The Distinction the Industry Needs
Governance architecture describes how the system is intended to work. It documents decision rights, integration flows, escalation paths, and accountability structures.
Process structural integrity determines whether the system actually holds when real-world conditions arrive — when incentives conflict, timing pressures mount, exceptions accumulate, and the behavioral reality of the organization diverges from its documented design.
Connecting systems closes the architectural gap.
Diagnosing process structural integrity closes the behavioral gap.
Both are necessary. The sequence matters.
Process Integrity → Governance → Technology
Most organizations build it in reverse. They deploy the technology, implement the governance, and discover the process integrity gap in the post-mortem. By which time the technology has already inherited — and scaled — whatever behavioral conditions it found.
The Bridge
The supply chain and procurement community has been saying versions of “stop patching a broken foundation” for as long as implementations have been failing. That instinct is correct, and every vendor, consultant, and practitioner who has ever said it was pointing at something real.
The bridge this archive has been building for 18 years is the instrument that answers the question the slogan raises: how do you know the foundation is broken, and what kind of break is it?
Not a system break. Not an integration gap. A behavioral break — the gap between how the process is designed to work and how people actually behave within it under real-world pressure.
That is the break that technology cannot fix. It has to be diagnosed before the technology arrives.
The Archive Behind the Argument
The distinction between architectural and behavioral breaks is not a theory. It is the pattern the Procurement Insights archive has been documenting since 2007 across seven consecutive technology eras, 23 crisis events, and 3,300+ independently published documents. These four graphics show what 18 years of independent, unconflicted, contemporaneous evidence looks like.
Archive documented above the line. Market arrivals below. Two parallel tracks converging at 2026 — the moment the market arrived at the question the archive has been answering since 2007.
Five concepts the archive documented alongside the years it took the market to arrive at the same conclusion. The gap between teal and orange is the commercial case for zero vendor sponsorships.
Every major supply chain shock from 2007 to 2026 — each one a data point in the reversion dataset. The Iran War / Hormuz closure at the far right: all five vectors archive-predicted before February 28.
The growth curve from 80 documents in 2007 to 3,300+ in 2026. The zero vendor sponsorships baseline runs flat underneath it throughout. “Still recording” is not a tagline. It is the status of the record right now.
This post was prompted by a supply chain event invitation. The instinct behind the marketing line is sound — and it opens a conversation the archive has been having since 2007. If your organization is navigating a similar question before a major technology investment, the diagnostic is below.
Are You Phase 0™ Ready?
Most AI and transformation initiatives don’t fail because of capability. They fail because the process they operate within cannot sustain what is being asked of it under real-world conditions.
Your Readiness Check
Identify: Name the AI initiative or technology deployment your organization is currently scoping or evaluating.
Check: Before that deployment was scoped — was there a verified answer to this question: are the behavioral conditions of the process aligned with the outcome the AI is expected to produce?
Decide: If the answer is no — or was never asked — the AI will not correct those conditions. It will scale them.
Act: Ask the one equivalent question the data layer cannot answer: “What time do our orders come in?” The answer will tell you more about your readiness than any platform capability assessment.
One next step: Book a 30-minute readiness conversation. 📅 calendly.com/jon-toq/30min
The full diagnostic framework: The Hansen Fit Score™ — What It Does, Who It’s For, and Why It Matters Now
Jon W. Hansen is the founder of Hansen Models™ and Procurement Insights — 18 years, 3,300+ published documents, zero vendor sponsorships. The HFS™, Phase 0™, and RAM 2025™ are proprietary frameworks developed independently.
© 2026 Jon W. Hansen | Procurement Insights | hansenprocurement.com | hpt@hansenprocurement.com
-30-
Share this:
Related