Implementation Physics™: The Discipline That Turns Friction Cost Into a Measurable Business Problem

Posted on April 17, 2026

0


“Do you know what your real friction cost is?”


Most organizations don’t. Not because they haven’t tried — but because friction cost doesn’t appear as a single number. It is distributed, absorbed, and invisible in aggregate, even when it is painfully visible in the parts.

That invisibility is not an accident. It is the natural consequence of a market that has spent 25 years measuring the cost of failure while systematically ignoring the cost of success.

CDW and Grainger are successful companies. Combined, they generate more than $40 billion in annual revenue. Both companies succeeded. But they succeeded while absorbing friction cost the market never learned to measure. CDW because it evolved into managing complexity that shouldn’t have compounded in the first place. Grainger because even the most structurally aligned model accumulates friction without continuous revalidation.

The market did not solve friction. It learned to live with it. And then it learned to build entire business models around managing it.

In the AI era, that is no longer a viable strategy.


The Three Executives Who Don’t Measure Friction

This is really the AI black box — only it applies to all technology.

The CFO measures visible friction — implementation budgets, change management programs, system replacements, productivity losses during transitions. What the CFO does not measure is invisible friction: the accumulated cost of workarounds, shadow processes, spreadsheets running alongside platforms, rework cycles, and decisions made on incomplete data. That cost is real. It is large. And it is distributed across so many budget lines that it never appears as a single number anywhere in the financial statements. The CFO knows exactly what the platform cost. The CFO has no idea what the platform is costing in friction absorbed every year since it was deployed.

The CIO measures system performance — uptime, integration costs, user adoption rates, ticket volumes. What the CIO does not measure is the friction cost of deploying technology into an environment whose model was never validated before the deployment began. Every ticket raised, every workaround built, every integration requiring custom development — these are friction costs. They are logged as operational expenses. They are never connected back to the root cause: the model was incomplete before the technology was introduced.

The CEO measures outcomes — revenue, margin, market share, customer satisfaction. What the CEO does not see is the gap between the outcomes being achieved and the outcomes that would be achievable if the friction cost were eliminated at source rather than managed at scale. That gap is not in the technology. It is not in the people. It is in the model the technology was deployed into — and whether that model was correctly defined and validated before the commitment was made.

The friction is real in every case. The measurement is absent in every case. And the absence of measurement is what allows friction to compound, undisturbed, for years — or in the cases of CDW and Grainger, for decades.


What Friction Actually Costs

In 2006, a paper published in Summit Magazine titled “Technology’s Diminishing Role in an Emerging Process-Driven World” argued that process understanding — not technology capability — was the determining variable in transformation outcomes. The market ignored it. The incentive structure at the time rewarded technology investment, not process validation. And because friction costs arrived slowly — compounding over two to four years rather than two to four weeks — organizations had enough time and margin to absorb them, reframe them, and move on to the next technology cycle.

That pattern repeated across seven technology cycles between 2001 and 2020.

The 80% failure rate isn’t a technology problem. It is a measurement problem. Organizations are measuring the wrong thing. Not failure in the conventional sense — but failure to deliver the outcome the investment was designed to produce. Which means that in most organizations, 80% of the friction cost absorbed over the last 25 years was, in most cases, preventable — not by choosing better technology, but by validating the model the technology was deployed into before the deployment began.

That is the number no CFO has ever put on an income statement. That is the cost no CIO has ever connected back to root cause. That is the gap no CEO has ever seen as a single, isolated, measurable problem.

It has a name now. It is called friction cost. And measuring it — and preventing it at source — is what Implementation Physics™ is designed to do.


Why AI Changes the Measurement Problem

Until 2020, the invisible nature of friction cost was tolerable because the recovery window was open. Organizations had time to discover misalignment, absorb the cost, and adapt before the damage became irreversible.

AI closes that window entirely.

When AI is deployed into an environment where the model has not been validated, it does not gradually reveal the misalignment. It scales it — at a pace that outstrips the organization’s capacity to recognize, measure, and respond to what is going wrong. Friction that previously cost two to four years of absorbed budget now costs weeks.

This is not a technology risk. It is a measurement risk. Organizations that cannot measure their friction cost cannot manage it. And organizations that cannot manage it will discover, at AI speed, exactly how expensive it has always been.


Friction cost is not what you pay when things fail. It is what you keep paying when things appear to work.


The Measurement Framework

Implementation Physics™ provides a pre-commitment framework for measuring and preventing friction cost before it is incurred. It rests on three disciplines that operate in sequence:

Strand Commonality™ — identifying the cross-silo connections that determine whether the model reflects operational reality. Every connection that exists but hasn’t been mapped is a potential source of friction. Every variable that sits outside the model’s current boundary is a friction cost waiting to be incurred. Strand Commonality™ maps those connections before the technology deployment creates the conditions that make them expensive to discover.

Strand Stability™ — validating that the corrections hold under real operational conditions before scaling begins. A model that appears sound in a design environment and fails under operational pressure generates friction at the exact moment the organization is least equipped to absorb it. Strand Stability™ confirms the model before that moment arrives.

Phase 0™ — the pre-commitment diagnostic that applies both disciplines before the investment is made, before the technology is selected, and before the efficiency gains are locked into an environment that was never correctly defined. Phase 0™ does not assess the technology. It assesses the environment the technology will be deployed into — and produces a measurable answer to the question every CFO, CIO, and CEO should be asking before any major commitment:

What is our current friction cost — and what will it cost us if we scale it?


The Proof That the Physics Work

The 1998 Department of National Defence engagement is the earliest documented application of Implementation Physics™. Delivery performance was 51%. The environment was functioning exactly as designed. Technology was being considered as the solution. A single diagnostic question — “What time of day do orders come in?” — surfaced the behavioral strand generating friction across five agents simultaneously, invisibly, in ways that no domain metric had been designed to observe. The strand was mapped. The corrections were validated. Performance moved to 97.3% in 90 days and held for seven years. The technology came last — introduced to sustain a model that reality had already confirmed.

The Commonwealth of Virginia’s eVA initiative followed the same sequence in 2000. A structural strand of agency-by-agency fragmentation was generating friction across every stakeholder simultaneously — again, invisibly. Process understanding and stakeholder alignment corrected it before the technology was deployed. The result was $338 million in savings over 24 years.

Two cases. Two decades. Two entirely different sectors and technologies. The same physics. The same sequence. The same result.


The Question That Changes the Conversation

For 25 years, the C-suite conversation about transformation has been organized around two questions: did this succeed, and did this fail? Those questions direct attention backward — to outcomes already delivered, costs already absorbed, and decisions already made.

Implementation Physics™ reorganizes the conversation around a different question — one that belongs at the beginning of every major commitment, not at the end:

What is our current friction cost — and what will it cost us if we scale it?

That is a CFO question. It is a CIO question. It is a CEO question. And it is the question that Phase 0™ is designed to answer — before the investment is made, before the technology is introduced, and before the friction cost that has been invisible for 25 years is locked in at AI speed.

The physics were always there. The measurement framework now exists. The only question is when you choose to see the cost.


[Graphic: Acute vs. Chronic Friction Cost — 2001 to 2026]

Acute friction cost is visible. Chronic friction cost is the one that compounds silently — across every initiative that succeeded just enough to survive.


Jon W. Hansen is the Founder of Hansen Models™ and Procurement Insights — 27 years, 3,300+ documents, zero vendor sponsorships. Implementation Physics™ is the founding discipline of Hansen Models™. For Phase 0™ Diagnostic information visit hansenprocurement.com.

-30-

Posted in: Commentary