Procurement Insights | Jon W. Hansen | March 20, 2026
This individual — whom I promised I would never name — gave me permission to share our discussion. What follows is that conversation, as close to verbatim as the coffee cup between us allowed.
CPO: Jon, I’ll be honest with you. Your documents create unwanted accountability versus providing a positive validation of action — in which said action does not have to be right, it just has to be moving. And because people make the latter decision before receiving your information, they are inspired into self-examination, but defend their decision.
Hansen: Am I hearing you correctly? By the time someone encounters my work, they have already committed emotionally to a direction. My documents don’t validate that direction — they interrogate it. So the reader experiences a conflict: the content resonates intellectually, but accepting its implications means admitting the decision they already made may be wrong. So they defend the decision instead of examining it.
CPO: Exactly. The market rewards motion. Gartner rewards motion. Consultants reward motion. You are the only voice in the room saying wait. And by the time I find your work, I’ve already told my board which direction we’re going.
Hansen: Which means the problem isn’t messaging. It’s timing. The only moment my documents convert is before the emotional commitment is made. Before the vendor is shortlisted. Before the consultant is engaged.
But here’s what’s changing — and this is what should worry you personally, not just organizationally.
In the ERP era, the consequences of a bad selection took three to five years to surface. Long enough for the decision-maker to have moved on. In the SaaS era, eighteen months to two years. Still survivable for a career.
CPO: And in the AI era?
Hansen: Months. Possibly weeks.
Agentic AI deployed into a workflow without governance redesign doesn’t fail slowly — it fails at the speed of the workflow it was embedded in.
For the first time, the person making the decision and the person experiencing the consequences may be the same person, in the same role, within the same budget cycle.
CPO: (sets down the coffee cup)
So you’re telling me I no longer have the runway to be wrong and recover.
Hansen: I’m telling you the accountability gap that let you survive the last three technology cycles is closing. The defense mechanism that let you buy Gartner’s validation and move forward is about to stop working — not because you got less capable, but because the timeline compressed to the point where the consequences arrive before your next performance review.
CPO: That’s not a comfortable thing to hear over coffee.
Hansen: No. But it’s the right conversation to have before the SOW gets signed.
What This Conversation Actually Revealed
The CPO in that exchange was not telling me something I didn’t know intellectually.
I have documented the accountability gap across seven technology eras. I have watched decision-makers survive bad selections by outrunning the consequences — promoted before the failure surfaced, moved on before the post-mortem was written.
What the CPO told me — and what I had not fully named — is this:
My work arrives after the emotional decision has already closed.
The reader resonates. The reader reflects. And then the reader defends the direction they already committed to — because reversing course means admitting something uncomfortable to people who are watching.
That is not a content problem. It is not a pricing problem. It is a timing problem.
What Is Changing Now
Because the AI era is compressing the accountability gap to the point where the consequences arrive before the escape route opens.
- ERP era — 3 to 5 years
- SaaS era — 18 to 24 months
- AI era — failure at the speed of the workflow
There is no longer enough time between the decision and the consequence to build a narrative that protects you.
Which means the conversation I have been trying to have for 28 years is about to become unavoidable. Not because the market became wiser. Because the timeline removed the option not to be.
What To Do Before You Decide Anything
You don’t need to change direction today. But before you move forward, do this:
1. Write down what you believe will happen after deployment. Not the vendor version — your internal expectation.
2. Identify what could break in the first 30 to 60 days. Not technically — operationally.
3. Ask who owns that outcome. Not the system. Not the consultant. A name.
If those answers are unclear, you are not making a technology decision. You are accepting a risk you cannot yet see.
That is where Phase 0™ starts.
The Question Worth Asking Before the SOW Gets Signed
Does your organization have the governance structure, the change management capacity, and the decision-making clarity to absorb what you are about to deploy — before it deploys at a speed you cannot reverse?
That is the Phase 0™ question. It has always been the Phase 0™ question. The difference now is that the cost of skipping it arrives on your desk while you are still sitting in it.
If you are about to approve an AI initiative, an ERP migration, or any technology commitment in 2026 — and you have not pressure-tested that question with independent evidence — the assessment exists.
It is not comfortable reading. But it is the right conversation to have before the signature happens.
→ Epicor HFS™ Consolidated Assessment + Phase 0™ Migration Readiness Check: https://payhip.com/b/adsXi
$1,750 USD. Instant download. PDF format.
Before your next decision is finalized, run the assessment. After that point, it becomes post-mortem analysis.
Jon W. Hansen is the Founder of Hansen Models™ and Procurement Insights, an 18-year independent research and advisory platform built on a living archive of 3,300+ published documents.
Hansen Models™ | Independent. Longitudinal. Unconflicted. hpt@hansenprocurement.com | procureinsights.com
Jon W. Hansen is the Founder of Hansen Models™ and Procurement Insights, an 18-year independent research and advisory platform built on a living archive of 3,300+ published documents.
Hansen Models™ | Independent. Longitudinal. Unconflicted. hpt@hansenprocurement.com | procureinsights.com
-30-
Procurement Insights
A Veteran CPO Finally Tells Me What I Am Not Seeing
Posted on March 20, 2026
0
Procurement Insights | Jon W. Hansen | March 20, 2026
This individual — whom I promised I would never name — gave me permission to share our discussion. What follows is that conversation, as close to verbatim as the coffee cup between us allowed.
CPO: Jon, I’ll be honest with you. Your documents create unwanted accountability versus providing a positive validation of action — in which said action does not have to be right, it just has to be moving. And because people make the latter decision before receiving your information, they are inspired into self-examination, but defend their decision.
Hansen: Am I hearing you correctly? By the time someone encounters my work, they have already committed emotionally to a direction. My documents don’t validate that direction — they interrogate it. So the reader experiences a conflict: the content resonates intellectually, but accepting its implications means admitting the decision they already made may be wrong. So they defend the decision instead of examining it.
CPO: Exactly. The market rewards motion. Gartner rewards motion. Consultants reward motion. You are the only voice in the room saying wait. And by the time I find your work, I’ve already told my board which direction we’re going.
Hansen: Which means the problem isn’t messaging. It’s timing. The only moment my documents convert is before the emotional commitment is made. Before the vendor is shortlisted. Before the consultant is engaged.
But here’s what’s changing — and this is what should worry you personally, not just organizationally.
In the ERP era, the consequences of a bad selection took three to five years to surface. Long enough for the decision-maker to have moved on. In the SaaS era, eighteen months to two years. Still survivable for a career.
CPO: And in the AI era?
Hansen: Months. Possibly weeks.
Agentic AI deployed into a workflow without governance redesign doesn’t fail slowly — it fails at the speed of the workflow it was embedded in.
For the first time, the person making the decision and the person experiencing the consequences may be the same person, in the same role, within the same budget cycle.
CPO: (sets down the coffee cup)
So you’re telling me I no longer have the runway to be wrong and recover.
Hansen: I’m telling you the accountability gap that let you survive the last three technology cycles is closing. The defense mechanism that let you buy Gartner’s validation and move forward is about to stop working — not because you got less capable, but because the timeline compressed to the point where the consequences arrive before your next performance review.
CPO: That’s not a comfortable thing to hear over coffee.
Hansen: No. But it’s the right conversation to have before the SOW gets signed.
What This Conversation Actually Revealed
The CPO in that exchange was not telling me something I didn’t know intellectually.
I have documented the accountability gap across seven technology eras. I have watched decision-makers survive bad selections by outrunning the consequences — promoted before the failure surfaced, moved on before the post-mortem was written.
What the CPO told me — and what I had not fully named — is this:
The reader resonates. The reader reflects. And then the reader defends the direction they already committed to — because reversing course means admitting something uncomfortable to people who are watching.
That is not a content problem. It is not a pricing problem. It is a timing problem.
What Is Changing Now
Because the AI era is compressing the accountability gap to the point where the consequences arrive before the escape route opens.
There is no longer enough time between the decision and the consequence to build a narrative that protects you.
Which means the conversation I have been trying to have for 28 years is about to become unavoidable. Not because the market became wiser. Because the timeline removed the option not to be.
What To Do Before You Decide Anything
You don’t need to change direction today. But before you move forward, do this:
1. Write down what you believe will happen after deployment. Not the vendor version — your internal expectation.
2. Identify what could break in the first 30 to 60 days. Not technically — operationally.
3. Ask who owns that outcome. Not the system. Not the consultant. A name.
If those answers are unclear, you are not making a technology decision. You are accepting a risk you cannot yet see.
That is where Phase 0™ starts.
The Question Worth Asking Before the SOW Gets Signed
Does your organization have the governance structure, the change management capacity, and the decision-making clarity to absorb what you are about to deploy — before it deploys at a speed you cannot reverse?
That is the Phase 0™ question. It has always been the Phase 0™ question. The difference now is that the cost of skipping it arrives on your desk while you are still sitting in it.
If you are about to approve an AI initiative, an ERP migration, or any technology commitment in 2026 — and you have not pressure-tested that question with independent evidence — the assessment exists.
It is not comfortable reading. But it is the right conversation to have before the signature happens.
→ Epicor HFS™ Consolidated Assessment + Phase 0™ Migration Readiness Check: https://payhip.com/b/adsXi
$1,750 USD. Instant download. PDF format.
Before your next decision is finalized, run the assessment. After that point, it becomes post-mortem analysis.
Jon W. Hansen is the Founder of Hansen Models™ and Procurement Insights, an 18-year independent research and advisory platform built on a living archive of 3,300+ published documents.
Hansen Models™ | Independent. Longitudinal. Unconflicted. hpt@hansenprocurement.com | procureinsights.com
Jon W. Hansen is the Founder of Hansen Models™ and Procurement Insights, an 18-year independent research and advisory platform built on a living archive of 3,300+ published documents.
Hansen Models™ | Independent. Longitudinal. Unconflicted. hpt@hansenprocurement.com | procureinsights.com
-30-
Share this:
Related