By Jon Hansen | Procurement Insights | March 2026
For 30 years, we have increased C-suite involvement in enterprise transformation. Failure rates did not improve.
That is not a technology problem. It is not a change management problem. It is not a vendor problem.
It is a structural failure built into how decisions are made.
The people who choose the solution are not the people who have the authority to make it work.
That single sentence explains 30 years of consistent failure across seven technology eras, $30 billion in ProcureTech investment, and every post-mortem that concluded with recommendations nobody implemented. It is the root cause that industry studies reflected but never named — and it is what we now formally identify as the Authority Gap.
What the Data Shows
The graphic accompanying this post tracks two measurements across the CIO, CFO, and CPO roles: their active involvement in the selection phase of enterprise initiatives, and their actual authority during the implementation phase — plotted against the documented failure rate for initiatives where each role held primary leadership.
The pattern is consistent and telling.
CPOs hold the highest selection involvement of any C-suite role — approximately 92 percent of enterprise procurement technology decisions involve CPO-level leadership in vendor evaluation and selection. Their implementation authority drops to roughly 32 percent. That 60-point gap is not a measurement anomaly. It is the structural explanation for why ProcureTech failure rates run at 75 to 80 percent. CPOs select the vendor. They cannot compel finance to restructure incentives, force IT to prioritize data governance, or require operations to modify workflows. The moment the contract is signed, authority migrates to functions the CPO does not control.
CIOs present the inverse profile. Their selection involvement is the lowest of the three roles — approximately 60 percent — but their implementation authority is the highest at 87 percent. They inherit deployment mandates for platforms they did not fully evaluate against organizational readiness conditions. The result: technically competent deployment into organizationally unprepared environments. Failure rate: 65 to 70 percent.
CFOs occupy the middle position in both dimensions. At 75 percent selection involvement — primarily through capital approval authority — and 48 percent implementation authority, their failure profile is slightly lower at 55 to 60 percent. But CFO-driven failures tend to be the most financially catastrophic, because capital pressure compresses implementation timelines past the point where course correction is possible.
Thirty Years of Evidence: The Failure Landscape
The table below maps the empirical evidence across four distinct eras. The single most important finding: failure rates did not improve as executive ownership expanded.
More C-suite involvement did not close the gap. It distributed it.
The Clean Summary Statement
“Over the past 30 years, roughly 70% of enterprise initiatives and 75–80% of ProcureTech initiatives have failed or underdelivered. While early failures were primarily attributed to CIO-led programs, today’s failures are the result of shared CIO–CFO–CPO accountability — confirming that transformation breakdowns are no longer functional, but systemic.”
The Coupa Illustration
In my 2011 Changing Face of Procurement presentation, I cited Coupa’s 156 percent year-over-year MRR growth as evidence of the SaaS transformation wave reshaping procurement. The citation was accurate. What neither I nor anyone else in the industry said clearly enough at the time was this: the organizations driving that growth were CPO-led selections with minimal readiness assessment.
The Hansen Fit Score™ (HFS™) assessment of Coupa documents the largest capability-to-outcome gap of any vendor in the series: 4.8 points. That gap did not emerge from product failure. It emerged from the same authority gap the graphic illustrates. CPOs selected Coupa. They did not have the organizational authority to enforce the readiness conditions that would have made the selection perform.
Industry studies reflected this pattern in aggregate failure rates. They did not name the structural cause.
I wrote the industry’s first formal independent white paper on Coupa in 2009 — predating all major analyst coverage. I was watching this arc develop before the Series C closed.
Three Baseline Cases: What Closing the Gap Actually Looks Like
Theory explains the failure. Evidence closes the argument. The archive contains documented cases across both public and private sector organizations — separated by jurisdiction, governance structure, and procurement mandate — that establish what success looks like when the authority gap is closed before capital is committed. Three of the most comprehensively documented are presented here. They are drawn from both sectors deliberately: the public sector cases provide the most rigorous, auditable, and publicly verifiable outcome data available; the private sector case demonstrates that the methodology is not a government procurement instrument — it is an organizational readiness principle that holds regardless of industry.
✅ Baseline Case #1 | Canada Department of National Defence (DND) — 1998
SR&ED-funded Relational Acquisition Model (RAM) deployment | Ottawa, Canada
- Delivery performance: 51% → 97.3% — achieved in three months, sustained for seven years
- Administrative overhead: 23 FTEs → 3 FTEs — sustained reduction without service degradation
- Procurement cost savings: sustained at 23% annually across the engagement period
- Why it worked: Readiness was assessed and addressed before technology was deployed. The authority gap was closed structurally — not by title, but by design. The engagement led directly to a company sale and the foundational SR&ED documentation that underpins all Hansen Models™ methodology.
✅ Baseline Case #2 | Commonwealth of Virginia — eVA eProcurement Program — 2001
Statewide eProcurement platform | Commonwealth of Virginia, USA
- Scope: Statewide eProcurement platform deployed across all Commonwealth agencies — one of the earliest and most comprehensively documented government SaaS procurement successes in North America.
- Governance-first approach: Governance architecture preceded platform selection. Accountability structures, workflow alignment, and stakeholder adoption frameworks were established before the technology contract was awarded.
- Outcomes: Transaction volume and adoption rates consistently exceeded projections — documented in Procurement Insights as a longitudinal counter-case to the 70–80% failure pattern.
- Why it worked: The authority gap was closed by design. The Commonwealth assigned cross-functional implementation authority to the same team that led selection — eliminating the handoff failure mode that defines the majority of enterprise technology deployments.
✅ Baseline Case #3 | Colgate-Palmolive — Process-First Procurement Transformation — Early 2000s
Global consumer goods manufacturer | Private sector | Fortune 500
- Track record: Gartner Supply Chain Top 25 for over 20 consecutive years — one of the longest sustained performance records in the ranking’s history. Reached #1 in 2019.
- Methodology: Colgate-Palmolive implemented a process-first approach to procurement and supply chain transformation — establishing governance, incentive alignment, and cross-functional accountability structures before technology deployment, not after. The “Funding the Growth” continuous improvement program built organizational readiness as a permanent operating principle rather than a pre-launch checklist.
- Resilience pattern: The same external disruptions that produced boomerang cycles across the broader Consumer Products and CPG industry — 9/11, the 2008 financial crisis, activist investor cost-cutting pressure, COVID supply chain chaos — produced stability at Colgate-Palmolive. Same industry. Same shocks. Different organizational architecture.
- Why it worked: Readiness was not treated as a project phase. It was treated as a structural condition. The authority gap between who designed the transformation and who operated it was closed at the governance level — and held across two decades of market disruption.
Three cases. Two sectors. Three different governance structures and procurement mandates. One shared condition: readiness preceded deployment, and implementation authority was held by the same function that owned the transformation design.
The Procurement Insights archive documented all three as sharing what it identified as the “timeless formula for digital procurement success” — the groundwork for what was accomplished occurred before the technology was introduced. That is not a government procurement principle. That is an organizational readiness principle. Colgate-Palmolive proves it holds in the private sector under sustained commercial pressure across two full decades.gap produces.
The Only Place This Gets Fixed — Before or During
Phase 0™ does not improve implementation. It determines whether implementation is possible.
That statement applies before the contract is signed. It also applies at 11pm on a Tuesday, six months into a deployment that is quietly going sideways.
The Hansen Method™ and the Phase 0™ Organizational Readiness Diagnostic were not built solely for organizations at the beginning of a technology decision. They were built in response to the authority gap — and that gap can be surfaced and addressed at any point where the outcome can still be shaped.
For organizations that have not yet committed: Phase 0™ operates before vendor selection, establishing the organizational readiness conditions that determine whether any vendor can succeed. It surfaces governance gaps, incentive misalignments, data architecture deficiencies, and accountability structure failures that neither the CIO’s technical assessment nor the CFO’s ROI model nor the CPO’s vendor evaluation captures. This is the ideal entry point — the moment where the cost of intervention is lowest and the range of available choices is widest.
For organizations already mid-implementation: The authority gap does not require a failed initiative to be addressed. If the signs are present — adoption resistance, scope creep, misaligned incentives, governance disputes between functions, a growing distance between what was promised and what is being delivered — Phase 0™ can function as a mid-course diagnostic. It identifies which specific readiness conditions are absent, which functions need to close the authority gap retroactively, and whether the initiative can be restructured to reach its intended outcomes without starting over.
The honest answer to “Do we have to wait for complete failure?” is no. Complete failure is simply the most expensive way to confirm what a readiness diagnostic would have found in the first week.
The DND engagement, the Virginia eVA program, and the Colgate-Palmolive transformation succeeded because the gap was closed before deployment. But the methodology that closed it does not expire at go-live. It applies wherever an organization is willing to ask the question honestly — and act on the answer before the next decision gate, not after the final post-mortem.
The gap has always been closable. The question is only when.
The Question for 2026
The changed face of procurement is not a better platform. It is not more C-suite involvement. It is not more advanced AI.
It is closing the authority gap before the decision is made.
The organizations that understand that will exit the 70–80 percent. The ones that don’t will continue to fund it.
⚡ 5-Minute Application
You don’t need a consultant to know if you have an Authority Gap. You need four questions and five minutes.
If you are a CPO, do this right now — before your next initiative moves forward:
1. Identify: Who selected your last major ProcureTech solution?
2. Check: Who actually owns implementation authority today — budget, workflow changes, data governance, and user adoption?
3. Compare: Are those the same person or the same function?
4. Decide:
- If yes → you have structural alignment. Proceed with confidence.
- If no → you have an Authority Gap. Do not proceed with your next initiative until it is resolved.
If those answers span more than one function, you are not starting an implementation. You are starting a failure cycle.
The one immediate next move: Before your next vendor briefing, map the four decision rights above on a single page — who owns selection, who owns implementation, who controls incentives, who controls data governance. If the answer is four different functions, you have just diagnosed the root cause of your last failed initiative. And your next one, if nothing changes.
This is what Phase 0™ does formally — and systematically — before capital is committed. Thirty minutes with the diagnostic will tell you more about your readiness than any vendor demo. → procureinsights.com
Jon Hansen is the Founder of Hansen Models™ and the author of the Procurement Insights research archive, spanning 18 years and 3,300+ published documents. He has 42 years of experience in high-tech and procurement. The Hansen Fit Score™ (HFS™), Phase 0™ Organizational Readiness Diagnostic, and RAM 2025™ Multimodel Validation Framework are proprietary methodologies of Hansen Models™. Assessment services and organizational readiness diagnostics: procureinsights.com
Hansen Fit Score™ Vendor Assessment Series | Hansen Models™ (1001279896 Ontario Inc.) | © 2026
-30-
Procurement Insights
Selected to Fail: The Authority Gap That 30 Years of C-Suite Involvement Could Not Close
Posted on March 18, 2026
0
By Jon Hansen | Procurement Insights | March 2026
For 30 years, we have increased C-suite involvement in enterprise transformation. Failure rates did not improve.
That is not a technology problem. It is not a change management problem. It is not a vendor problem.
It is a structural failure built into how decisions are made.
The people who choose the solution are not the people who have the authority to make it work.
That single sentence explains 30 years of consistent failure across seven technology eras, $30 billion in ProcureTech investment, and every post-mortem that concluded with recommendations nobody implemented. It is the root cause that industry studies reflected but never named — and it is what we now formally identify as the Authority Gap.
What the Data Shows
The graphic accompanying this post tracks two measurements across the CIO, CFO, and CPO roles: their active involvement in the selection phase of enterprise initiatives, and their actual authority during the implementation phase — plotted against the documented failure rate for initiatives where each role held primary leadership.
The pattern is consistent and telling.
CPOs hold the highest selection involvement of any C-suite role — approximately 92 percent of enterprise procurement technology decisions involve CPO-level leadership in vendor evaluation and selection. Their implementation authority drops to roughly 32 percent. That 60-point gap is not a measurement anomaly. It is the structural explanation for why ProcureTech failure rates run at 75 to 80 percent. CPOs select the vendor. They cannot compel finance to restructure incentives, force IT to prioritize data governance, or require operations to modify workflows. The moment the contract is signed, authority migrates to functions the CPO does not control.
CIOs present the inverse profile. Their selection involvement is the lowest of the three roles — approximately 60 percent — but their implementation authority is the highest at 87 percent. They inherit deployment mandates for platforms they did not fully evaluate against organizational readiness conditions. The result: technically competent deployment into organizationally unprepared environments. Failure rate: 65 to 70 percent.
CFOs occupy the middle position in both dimensions. At 75 percent selection involvement — primarily through capital approval authority — and 48 percent implementation authority, their failure profile is slightly lower at 55 to 60 percent. But CFO-driven failures tend to be the most financially catastrophic, because capital pressure compresses implementation timelines past the point where course correction is possible.
Thirty Years of Evidence: The Failure Landscape
The table below maps the empirical evidence across four distinct eras. The single most important finding: failure rates did not improve as executive ownership expanded.
More C-suite involvement did not close the gap. It distributed it.
The Coupa Illustration
In my 2011 Changing Face of Procurement presentation, I cited Coupa’s 156 percent year-over-year MRR growth as evidence of the SaaS transformation wave reshaping procurement. The citation was accurate. What neither I nor anyone else in the industry said clearly enough at the time was this: the organizations driving that growth were CPO-led selections with minimal readiness assessment.
The Hansen Fit Score™ (HFS™) assessment of Coupa documents the largest capability-to-outcome gap of any vendor in the series: 4.8 points. That gap did not emerge from product failure. It emerged from the same authority gap the graphic illustrates. CPOs selected Coupa. They did not have the organizational authority to enforce the readiness conditions that would have made the selection perform.
Industry studies reflected this pattern in aggregate failure rates. They did not name the structural cause.
I wrote the industry’s first formal independent white paper on Coupa in 2009 — predating all major analyst coverage. I was watching this arc develop before the Series C closed.
Three Baseline Cases: What Closing the Gap Actually Looks Like
Theory explains the failure. Evidence closes the argument. The archive contains documented cases across both public and private sector organizations — separated by jurisdiction, governance structure, and procurement mandate — that establish what success looks like when the authority gap is closed before capital is committed. Three of the most comprehensively documented are presented here. They are drawn from both sectors deliberately: the public sector cases provide the most rigorous, auditable, and publicly verifiable outcome data available; the private sector case demonstrates that the methodology is not a government procurement instrument — it is an organizational readiness principle that holds regardless of industry.
✅ Baseline Case #1 | Canada Department of National Defence (DND) — 1998
SR&ED-funded Relational Acquisition Model (RAM) deployment | Ottawa, Canada
✅ Baseline Case #2 | Commonwealth of Virginia — eVA eProcurement Program — 2001
Statewide eProcurement platform | Commonwealth of Virginia, USA
✅ Baseline Case #3 | Colgate-Palmolive — Process-First Procurement Transformation — Early 2000s
Global consumer goods manufacturer | Private sector | Fortune 500
Three cases. Two sectors. Three different governance structures and procurement mandates. One shared condition: readiness preceded deployment, and implementation authority was held by the same function that owned the transformation design.
The Procurement Insights archive documented all three as sharing what it identified as the “timeless formula for digital procurement success” — the groundwork for what was accomplished occurred before the technology was introduced. That is not a government procurement principle. That is an organizational readiness principle. Colgate-Palmolive proves it holds in the private sector under sustained commercial pressure across two full decades.gap produces.
The Only Place This Gets Fixed — Before or During
Phase 0™ does not improve implementation. It determines whether implementation is possible.
That statement applies before the contract is signed. It also applies at 11pm on a Tuesday, six months into a deployment that is quietly going sideways.
The Hansen Method™ and the Phase 0™ Organizational Readiness Diagnostic were not built solely for organizations at the beginning of a technology decision. They were built in response to the authority gap — and that gap can be surfaced and addressed at any point where the outcome can still be shaped.
For organizations that have not yet committed: Phase 0™ operates before vendor selection, establishing the organizational readiness conditions that determine whether any vendor can succeed. It surfaces governance gaps, incentive misalignments, data architecture deficiencies, and accountability structure failures that neither the CIO’s technical assessment nor the CFO’s ROI model nor the CPO’s vendor evaluation captures. This is the ideal entry point — the moment where the cost of intervention is lowest and the range of available choices is widest.
For organizations already mid-implementation: The authority gap does not require a failed initiative to be addressed. If the signs are present — adoption resistance, scope creep, misaligned incentives, governance disputes between functions, a growing distance between what was promised and what is being delivered — Phase 0™ can function as a mid-course diagnostic. It identifies which specific readiness conditions are absent, which functions need to close the authority gap retroactively, and whether the initiative can be restructured to reach its intended outcomes without starting over.
The honest answer to “Do we have to wait for complete failure?” is no. Complete failure is simply the most expensive way to confirm what a readiness diagnostic would have found in the first week.
The DND engagement, the Virginia eVA program, and the Colgate-Palmolive transformation succeeded because the gap was closed before deployment. But the methodology that closed it does not expire at go-live. It applies wherever an organization is willing to ask the question honestly — and act on the answer before the next decision gate, not after the final post-mortem.
The gap has always been closable. The question is only when.
The Question for 2026
The changed face of procurement is not a better platform. It is not more C-suite involvement. It is not more advanced AI.
It is closing the authority gap before the decision is made.
The organizations that understand that will exit the 70–80 percent. The ones that don’t will continue to fund it.
⚡ 5-Minute Application
You don’t need a consultant to know if you have an Authority Gap. You need four questions and five minutes.
If you are a CPO, do this right now — before your next initiative moves forward:
1. Identify: Who selected your last major ProcureTech solution?
2. Check: Who actually owns implementation authority today — budget, workflow changes, data governance, and user adoption?
3. Compare: Are those the same person or the same function?
4. Decide:
The one immediate next move: Before your next vendor briefing, map the four decision rights above on a single page — who owns selection, who owns implementation, who controls incentives, who controls data governance. If the answer is four different functions, you have just diagnosed the root cause of your last failed initiative. And your next one, if nothing changes.
This is what Phase 0™ does formally — and systematically — before capital is committed. Thirty minutes with the diagnostic will tell you more about your readiness than any vendor demo. → procureinsights.com
Jon Hansen is the Founder of Hansen Models™ and the author of the Procurement Insights research archive, spanning 18 years and 3,300+ published documents. He has 42 years of experience in high-tech and procurement. The Hansen Fit Score™ (HFS™), Phase 0™ Organizational Readiness Diagnostic, and RAM 2025™ Multimodel Validation Framework are proprietary methodologies of Hansen Models™. Assessment services and organizational readiness diagnostics: procureinsights.com
Hansen Fit Score™ Vendor Assessment Series | Hansen Models™ (1001279896 Ontario Inc.) | © 2026
-30-
Share this:
Related