Browsing All posts tagged under »Hansen Fit Score«

Nine Months Later, the Iran War Shows Why Black Swans Rarely Arrive Without Signals

March 9, 2026

0

The best way to respond to the Iran war is not to expand your AI footprint, but the aperture of your procurement and supply chain lens.

When Five AI Models Analyze the Same Data Three Months Apart — and Reach the Same Conclusion

March 8, 2026

0

Five AI models. Three verification layers. Two graphs. Thirty years of data. One conclusion the industry has overlooked for multiple tech generations.

The Krishna Paradox — IBM watsonx Orchestrate | Hansen Fit Score™ Preliminary Assessment

March 3, 2026

0

First greenwashing, then AI washing, and now Phase 0 washing?

How the Hansen Fit Score™ Works — In 7 Minutes

March 1, 2026

0

What is the Hansen Fit Score™? You asked — here's the answer.

I Am a Lousy Salesperson

February 28, 2026

0

Your success with ProcureTech, including AI, starts by asking questions nobody is asking.

The C-Suite Sweep — Part 1 of 4: A Memo for the CIO

February 25, 2026

0

In 2010, I sat at a roundtable with the former CIO of the United States Government discussing transparency in procurement. In 2011, I taught procurement professionals to "act like a CIO." In 2025, the CIO's view of procurement evolved. The 80% failure rate didn't. Here is the question no vendor demo will answer.

When One Model Says Yes and Five Say Wait: Why Multimodel Validation Matters

February 24, 2026

0

Six models. One question. Five said "probable." One said "certain." The difference is where the credibility lives.

The Kraljic Paradox: When the Diagnosis Is Right but the Instrument Is Wrong

February 23, 2026

2

Kraljic described the world we model. We have built the instrument that his diagnosis deserved.

James, About That 75% Number

February 22, 2026

0

What makes the Procurement Insights Archives unique and why it can't be duplicated?

When the Dominant Advisory Firm Starts Asking Your Question

February 22, 2026

0

We published the measurement on February 14th. Eight days later, Gartner published the observation.