Posted in: Procurement Insights · CIO Insights · CFO Insights
“A new report from Coupa shows that while 85% of CFOs say AI is central to their strategy, 92% worry about their ability to implement it. That’s up from 66% last year — a sharp shift that shows confidence is moving in the wrong direction.”
— SupplyChain247, April 2026
When Norman Katz shared this in our discussion stream this week, something clicked.
Not because the number was surprising. Because the cause was already in the archive. Documented twice. Before the pattern repeated.
The Constraint Was Identified Before the Pattern Repeated — Twice
In 2011, I documented that 92% of government IT leaders had reservations about moving to the cloud. Not about whether the cloud worked. About whether their organizations were ready to operate it.
Fifteen years later, 92% of CFOs are expressing the same reservation — not about whether AI works, but about whether their organizations can execute on it.
Different technology. Same structural constraint. The percentage is just the symptom.
The real question is: why did the symptom persist beyond 1998 and 2008?
The answer was already in the archive. Not once. Twice.
1998: The Question That Started Everything
At Canada’s Department of National Defence, the first question I asked was simple:
“What time of day do orders come in?”
The answer — 4 PM — revealed that the incentive structure around the service technicians was generating the wrong behavior, producing the wrong data, and destroying delivery performance. The policy said order after each service call. The system allowed something different. Technicians were sandbagging orders until end of day to hit their service call targets — at the cost of parts availability and delivery performance.
Nobody had asked the question because nobody thought it was a technology question. It wasn’t. It was a process structural question.
Delivery performance went from 51% to 97.3% in three months and sustained for seven years. No new technology. No governance framework. One diagnostic question — asked before the commitment was made.
That question is the origin of Phase 0™.
2008: The Same Question in a Different Industry
Ten years later, an IEE analysis of Oracle Packaging asked one question:
“What width are we cutting this foil?”
The answer revealed that the manufacturing process was generating unnecessary work in process (WIP), tying up capital, creating goods expiration risk, and silently widening the gap between Finance and operations.
The result: WIP reduced by 30%, working capital down $232K — without changing the manufacturing process. Lead time cut to half the industry standard. 5% reduction in raw material orders. Potential to reduce scrap by 50%.
And this line, published in the Procurement Insights archive in August 2008: “WIP represents a good opportunity to open a dialogue with your CFO.”
Two industries. Two questions. Same “process structural integrity” revelation leading to successful outcomes.
Why Were the 1998 and 2008 Successes Ignored?
Both proof cases shared one uncomfortable characteristic: the breakthrough had nothing to do with technology.
At DND in 1998, delivery performance went from 51% to 97.3% not because of a new system — but because one question about process structure revealed a behavioral misalignment that no technology could have fixed.
At Oracle Packaging in 2008, $232K in working capital was recovered and lead times were halved not because of new machinery — but because one question about process structure revealed a Finance-Operations gap that had been silently compounding.
Neither result fit the narrative the industry was selling. An answer that says ask this diagnostic question before you buy anything is not a message that serves a model built on selling, implementing, and advising on technology.
So the questions went unasked. The gap persisted. The technology advanced.
And in 2011, 92% of CIOs expressed hesitation about cloud adoption — not about the technology, but about whether their organizations were ready to operate it.
And in 2026, 92% of CFOs expressed the same hesitation about AI — for exactly the same reason.
The 92% figure didn’t appear because of the technological breakthroughs. It appeared because of how those breakthroughs were sold — without the diagnostic question that 1998 and 2008 had already proven was the only one that mattered.
By the way, in 1998, after the process structural integrity was implemented, what we now call Phase 0 today, innovative technology was introduced, significantly multiplying the return benefits in significant dollar savings and FTE reductions.
Readiness first. Then technology. In that sequence, the returns compound. In the reverse sequence, the 92% uncertainty figure is the perpetual result.
Four Eras. One Diagnosis.
The question was never whether the technology works.
It was whether the organization was structurally aligned to act on what the technology produces — before the commitment was made, not after the gap surfaced. In short, lead with technology and skip Phase 0™, and the 92% outcome is not a risk. It’s the result. For those who have been following this blog for a while, you will recognize the continuing use of the tech-led, equation-based model instead of leading with the people-process-technology, agent-based model.
What This Means for CIOs, CFOs, and CDOs
The Procurement Insights archive has 3,300+ documents spanning 18 years. It has always been described as a procurement resource.
That description is accurate but incomplete.
Procurement and manufacturing operations sit at the intersection of every enterprise function — Finance, Operations, Technology, Legal, and Supply Chain. Which means the archive isn’t documenting procurement failures. It’s documenting organizational behavior at the point where strategy meets execution under real conditions.
What the CIO reads as a technology adoption problem, the CDO reads as a data governance problem, and the CFO reads as an execution confidence problem — they are three manifestations of the same underlying constraint, seen from different seats.
The 1998 DND case is a CIO document. The 2008 Oracle Packaging case is a CFO document. The 2011 cloud hesitation data is a CDO document. The 2026 Coupa AI execution gap is all three simultaneously.
The archive was always C-Suite content. It just took the industry 28 years to arrive at the questions it was already answering.
The Constraint Has a Name
Rick Justice, EVP/CCO at Cisco, called it SMOP — the Small Matter of People. He used it to remind his teams that it was never about the technology alone. Org issues, readiness, culture — those were the real keys to scaling solutions.
That was Cisco’s internal leadership wisdom during one of the most ambitious supply chain transformations of its era.
It is still the most precise diagnosis of why AI is failing in the CFO suite today.
The technology has advanced. The constraint hasn’t.
We’ve Had the Answer Since 1998. The Market Is Just Now Catching Up.
This is not a post about an interesting pattern in the data.
It is a post about causality documented across 28 years and three completely different operational environments.
In 1998, a single diagnostic question surfaced a structural misalignment at DND that no policy, no system, and no governance framework had caught.
In 2008, the same category of question surfaced a structural misalignment at Oracle Packaging that was silently destroying working capital and widening the Finance–Operations gap.
In 2011, the failure to use the 1998 and 2008 mechanisms produced the documented large-scale symptom — 92% of CIOs were hesitant about cloud execution.
In 2026, it produced its second — 92% of CFOs uncertain about AI execution.
The diagnosis was written before either symptom appeared. That is not pattern recognition after the fact. That is a predictive framework operating across four eras and two proof cases.
Phase 0™ exists to surface that gap before it becomes a cost.
Phase 0™ — The Organizational Readiness Diagnostic
Phase 0™ was built specifically for this moment — when the pressure to move fast is highest and the cost of moving wrong is highest simultaneously.
The initial diagnostic takes under 10 minutes.
What it surfaces can take years to close after the fact — if the gap is discovered during implementation rather than before it.
Access the preliminary high-level self-diagnostic now to get a quick take on where your organization sits right now — free, immediate download: (COMING SOON)
In the meantime, you can book a 30-minute readiness conversation directly — no sales pitch, no obligation, one focused conversation about whether your organization can actually execute on its next initiative.
What the Archive Offers That No One Else Can
Governance doesn’t create outcomes. Process structural integrity determines whether governance can even function.
We see the patterns others don’t — which provides you with the insights you need to get it right at the right time.
Phase 0™ · HFS™ Hansen Fit Score™ · RAM 2025™ · Hansen Models™ · 18 years · 3,300+ documents · Zero vendor sponsorships · Zero paid analyst relationships · procureinsights.com · hpt@hansenprocurement.com · © 2026 Jon W. Hansen · All Rights Reserved
Archive References:
-30-
Procurement Insights 
1998 & 2008: Success. 2011 & 2026: The 92% Problem. What Went Wrong?
Posted on April 2, 2026
0
Posted in: Procurement Insights · CIO Insights · CFO Insights
When Norman Katz shared this in our discussion stream this week, something clicked.
Not because the number was surprising. Because the cause was already in the archive. Documented twice. Before the pattern repeated.
The Constraint Was Identified Before the Pattern Repeated — Twice
In 2011, I documented that 92% of government IT leaders had reservations about moving to the cloud. Not about whether the cloud worked. About whether their organizations were ready to operate it.
Fifteen years later, 92% of CFOs are expressing the same reservation — not about whether AI works, but about whether their organizations can execute on it.
Different technology. Same structural constraint. The percentage is just the symptom.
The real question is: why did the symptom persist beyond 1998 and 2008?
The answer was already in the archive. Not once. Twice.
1998: The Question That Started Everything
At Canada’s Department of National Defence, the first question I asked was simple:
“What time of day do orders come in?”
The answer — 4 PM — revealed that the incentive structure around the service technicians was generating the wrong behavior, producing the wrong data, and destroying delivery performance. The policy said order after each service call. The system allowed something different. Technicians were sandbagging orders until end of day to hit their service call targets — at the cost of parts availability and delivery performance.
Nobody had asked the question because nobody thought it was a technology question. It wasn’t. It was a process structural question.
Delivery performance went from 51% to 97.3% in three months and sustained for seven years. No new technology. No governance framework. One diagnostic question — asked before the commitment was made.
That question is the origin of Phase 0™.
2008: The Same Question in a Different Industry
Ten years later, an IEE analysis of Oracle Packaging asked one question:
“What width are we cutting this foil?”
The answer revealed that the manufacturing process was generating unnecessary work in process (WIP), tying up capital, creating goods expiration risk, and silently widening the gap between Finance and operations.
The result: WIP reduced by 30%, working capital down $232K — without changing the manufacturing process. Lead time cut to half the industry standard. 5% reduction in raw material orders. Potential to reduce scrap by 50%.
And this line, published in the Procurement Insights archive in August 2008: “WIP represents a good opportunity to open a dialogue with your CFO.”
Two industries. Two questions. Same “process structural integrity” revelation leading to successful outcomes.
Why Were the 1998 and 2008 Successes Ignored?
Both proof cases shared one uncomfortable characteristic: the breakthrough had nothing to do with technology.
At DND in 1998, delivery performance went from 51% to 97.3% not because of a new system — but because one question about process structure revealed a behavioral misalignment that no technology could have fixed.
At Oracle Packaging in 2008, $232K in working capital was recovered and lead times were halved not because of new machinery — but because one question about process structure revealed a Finance-Operations gap that had been silently compounding.
Neither result fit the narrative the industry was selling. An answer that says ask this diagnostic question before you buy anything is not a message that serves a model built on selling, implementing, and advising on technology.
So the questions went unasked. The gap persisted. The technology advanced.
And in 2011, 92% of CIOs expressed hesitation about cloud adoption — not about the technology, but about whether their organizations were ready to operate it.
And in 2026, 92% of CFOs expressed the same hesitation about AI — for exactly the same reason.
The 92% figure didn’t appear because of the technological breakthroughs. It appeared because of how those breakthroughs were sold — without the diagnostic question that 1998 and 2008 had already proven was the only one that mattered.
By the way, in 1998, after the process structural integrity was implemented, what we now call Phase 0 today, innovative technology was introduced, significantly multiplying the return benefits in significant dollar savings and FTE reductions.
Readiness first. Then technology. In that sequence, the returns compound. In the reverse sequence, the 92% uncertainty figure is the perpetual result.
Four Eras. One Diagnosis.
The question was never whether the technology works.
It was whether the organization was structurally aligned to act on what the technology produces — before the commitment was made, not after the gap surfaced. In short, lead with technology and skip Phase 0™, and the 92% outcome is not a risk. It’s the result. For those who have been following this blog for a while, you will recognize the continuing use of the tech-led, equation-based model instead of leading with the people-process-technology, agent-based model.
What This Means for CIOs, CFOs, and CDOs
The Procurement Insights archive has 3,300+ documents spanning 18 years. It has always been described as a procurement resource.
That description is accurate but incomplete.
Procurement and manufacturing operations sit at the intersection of every enterprise function — Finance, Operations, Technology, Legal, and Supply Chain. Which means the archive isn’t documenting procurement failures. It’s documenting organizational behavior at the point where strategy meets execution under real conditions.
What the CIO reads as a technology adoption problem, the CDO reads as a data governance problem, and the CFO reads as an execution confidence problem — they are three manifestations of the same underlying constraint, seen from different seats.
The 1998 DND case is a CIO document. The 2008 Oracle Packaging case is a CFO document. The 2011 cloud hesitation data is a CDO document. The 2026 Coupa AI execution gap is all three simultaneously.
The archive was always C-Suite content. It just took the industry 28 years to arrive at the questions it was already answering.
The Constraint Has a Name
Rick Justice, EVP/CCO at Cisco, called it SMOP — the Small Matter of People. He used it to remind his teams that it was never about the technology alone. Org issues, readiness, culture — those were the real keys to scaling solutions.
That was Cisco’s internal leadership wisdom during one of the most ambitious supply chain transformations of its era.
It is still the most precise diagnosis of why AI is failing in the CFO suite today.
The technology has advanced. The constraint hasn’t.
We’ve Had the Answer Since 1998. The Market Is Just Now Catching Up.
This is not a post about an interesting pattern in the data.
It is a post about causality documented across 28 years and three completely different operational environments.
In 1998, a single diagnostic question surfaced a structural misalignment at DND that no policy, no system, and no governance framework had caught.
In 2008, the same category of question surfaced a structural misalignment at Oracle Packaging that was silently destroying working capital and widening the Finance–Operations gap.
In 2011, the failure to use the 1998 and 2008 mechanisms produced the documented large-scale symptom — 92% of CIOs were hesitant about cloud execution.
In 2026, it produced its second — 92% of CFOs uncertain about AI execution.
The diagnosis was written before either symptom appeared. That is not pattern recognition after the fact. That is a predictive framework operating across four eras and two proof cases.
Phase 0™ exists to surface that gap before it becomes a cost.
Phase 0™ — The Organizational Readiness Diagnostic
Phase 0™ was built specifically for this moment — when the pressure to move fast is highest and the cost of moving wrong is highest simultaneously.
The initial diagnostic takes under 10 minutes.
What it surfaces can take years to close after the fact — if the gap is discovered during implementation rather than before it.
Access the preliminary high-level self-diagnostic now to get a quick take on where your organization sits right now — free, immediate download: (COMING SOON)
In the meantime, you can book a 30-minute readiness conversation directly — no sales pitch, no obligation, one focused conversation about whether your organization can actually execute on its next initiative.
What the Archive Offers That No One Else Can
Governance doesn’t create outcomes. Process structural integrity determines whether governance can even function.
We see the patterns others don’t — which provides you with the insights you need to get it right at the right time.
Phase 0™ · HFS™ Hansen Fit Score™ · RAM 2025™ · Hansen Models™ · 18 years · 3,300+ documents · Zero vendor sponsorships · Zero paid analyst relationships · procureinsights.com · hpt@hansenprocurement.com · © 2026 Jon W. Hansen · All Rights Reserved
Archive References:
-30-
Share this:
Related