Truth Is Believing. Accuracy Is Knowing. Outcome Is Proof.™
The words were never the problem. The mental model they smuggle in has been — for almost thirty years.
I have used the term “supply chain” for my entire career. I have also, quietly, never quite trusted it. It took me a long time to work out why, and the reason has nothing to do with the words themselves. It has to do with the picture the words put in your head.
Say “chain,” and you have already been told how to think.
What a chain tells you to believe
A chain is linear. A → B → C → D → E. One thing leads to the next, in sequence, in a single direction. It has a first link and a last link, and everything in between passes the load along in order.
That picture carries two assumptions most people never examine. The first: a chain is only as strong as its weakest link — so the work is to find the weak link. The second: when something goes wrong, there is a place it went wrong, a link that broke, and the job is to locate it. Where did the chain break?
Both assumptions feel like common sense. Both are, in my experience, the reason so many operational problems get diagnosed correctly and solved anyway to no effect. Because the world does not run as a single chain.
What actually happens
Nothing important in an organization moves in one line. Suppliers, customers, finance, manufacturing, procurement, logistics, technology, regulation — every one of them influences several of the others at the same time, in both directions. Add AI agents, human judgment, external partners, weather, and geopolitics, and the picture is not a longer chain. It is a weave: many strands running at once, crossing, pulling on each other, producing an outcome together that no single strand could produce alone.
Ask the chain question of that system — where did it break? — and you will get an answer that is technically true and practically useless. You will find a broken link and miss the pattern of interactions that broke it.
The question that broke the chain
When I went into the Department of National Defence in 1998, deliveries were late, and everyone already knew where the chain had “broken”: procurement. The instruction was to automate procurement and make it faster.
The first question I asked was not about procurement. It was: what time of day do orders come in?
It sounded irrelevant. It was the whole thing. Orders were being sandbagged to the end of the day, because the service technicians who placed them were measured on how many service calls they could respond to with an onsite visit — a different function, a different incentive, a different strand entirely. Late ordering pushed buying into the window where MRO prices ran up and cross-border customs slowed down. The “procurement failure” was not in procurement. It was an emergent property of technician incentives, measurement, dispatch, time-of-day pricing, and customs paperwork — several strands intersecting, none of them the broken link, all of them the cause.
No chain model would ever have found that. You cannot find an intersection by walking a line.
Strand Commonality — the principle underneath
What I was doing had a name, and it came before the engagement, not out of it. Strand Commonality™ is the observational principle that seemingly separate operational strands — contracts, supplier performance, inventory, sourcing, the data sitting in the ERP — are frequently different expressions of the same underlying operating reality, and that the recurring relationships between them explain outcomes no single strand can.
It is the reason the Government of Canada’s Scientific Research and Experimental Development program funded my research in the first place. Not to build the Metaprise — that came later. The funding followed the theory; it did not produce it. What the DND engagement gave me was the chance to test the principle against a real operating production environment, and the principle held.
I have found the clearest way to convey it is not the mathematics of physics but the image of music. A violin played alone tells you something. So does a cello, a flute. But no one mistakes an instrument for the symphony. The music is not in any one player — it emerges from timing, interaction, and structure among all of them. An individual procurement metric, a supplier scorecard, a contract — each tells you something. Organizational performance emerges from how they interact, not from any one of them alone.
If you want the physicist’s version: string theory makes the same intellectual move — that the particles we think are fundamental are really different expressions of a deeper structure. I would not claim my organizational work is string theory; one is an unconfirmed mathematical theory of the universe and the other is a discipline drawn from practice. But the instinct is identical. The visible object is not the fundamental reality. Look beneath it for the relationships that generate what you see.
Metaprise — the architecture that follows
Once you accept that those cross-cutting relationships are real, a chain stops being an adequate description of what you are managing — and so does the word “enterprise.” What you are actually operating is an interacting ecosystem of human and non-human agents working across multiple overlapping structures at once, inside and beyond the organization’s boundaries. That is what I mean by the Metaprise™. A chain has one dimension. A Metaprise has many.
The chronology matters here, because people tend to get it backwards. Strand Commonality is the observational principle — the epistemology, the way of discovering what is actually happening. The Metaprise is the architectural conclusion that grew out of it, once I realized those relationships extended past anything “supply chain,” or even “enterprise,” could hold. The principle came first. The architecture followed. Both sit alongside the two constants I have written about elsewhere — Invariant Physics™, which describes what does not change across technology eras, and Implementation Physics™, which describes how change survives contact with reality.
What the term costs you
“Supply chain” is a fine operational label. I will keep using it, because everyone knows what it means. But I want to be clear about what it costs when it becomes the mental model rather than just the label. It teaches you to hunt for a broken link when you should be reading a pattern of interactions. It asks where did it break when the useful question is what relationships produced this outcome. It trains attention on objects when the answer is almost always in the relationships between them.
The system I have spent nearly three decades first creating and then studying was never a chain. It was always a weave. And the strength — or the failure — was never in any single thread. It was in the pattern.
So the question I would leave you with is the one I have been asking, in one form or another, since 1998:
When something in your organization goes wrong, are you still looking for the broken link — or are you finally ready to look at the weave?
This reflection draws on the Procurement Insights archive — an independent record I have published openly since 2007, consolidating documented client work, lectures, and writing reaching back to 1998, and carrying no vendor sponsorships across the past decade. Every claim is held to the Provenance Ledger™, a verify-before-publish discipline that traces each assertion to a primary source and reconciles the record forward rather than editing it in place. Strand Commonality™, Metaprise™, Invariant Physics™, and Implementation Physics™ are proprietary frameworks of Hansen Models™. Getting it right, rather than being right.
-30-
The Same Drawing, a Generation Apart
The synchronized model above I first set out in the late 1990s, publicized in early 2000 in a Metaprise™ brochure — participants coordinating through a shared center rather than handing off down a line. The version beneath it I drew now.
Lay one over the other and they register. The participants sit in the same ring. The many-to-many connections trace the same crossings. The coordinating center holds in the same place. Two drawings made a generation apart — across a complete turnover of the technologies beneath them, from a world with no cloud and no agents to one built on both — and when you superimpose them, they are the same drawing.
That is the argument of this entire post in a single frame. The label was “supply chain.” The technology was ERP, then the internet, then cloud, now AI. All of it changed. The shape of how organizations actually coordinate did not. And this is a claim you can falsify on sight: if the operating reality of 2026 were genuinely a different shape — a chain, or something new — the overlay would not line up. It lines up.
That is the difference between a demonstrated constant and a lucky guess. That earlier model was not predicting 2026. It was a correct description of how organizations coordinate, and 2026 has the same shape because the shape is the invariant — not the technology wrapped around it.
This is what Invariant Physics™ looks like visually: not a forecast that came true, but a description that was accurate when it was drawn and has not been contradicted since — across every era, every platform, and every renaming of the thing itself.
-30-
Related
Why I Have Never Quite Been Satisfied with the Term “Supply Chain”
Posted on July 25, 2026
0
Truth Is Believing. Accuracy Is Knowing. Outcome Is Proof.™
The words were never the problem. The mental model they smuggle in has been — for almost thirty years.
I have used the term “supply chain” for my entire career. I have also, quietly, never quite trusted it. It took me a long time to work out why, and the reason has nothing to do with the words themselves. It has to do with the picture the words put in your head.
Say “chain,” and you have already been told how to think.
What a chain tells you to believe
A chain is linear. A → B → C → D → E. One thing leads to the next, in sequence, in a single direction. It has a first link and a last link, and everything in between passes the load along in order.
That picture carries two assumptions most people never examine. The first: a chain is only as strong as its weakest link — so the work is to find the weak link. The second: when something goes wrong, there is a place it went wrong, a link that broke, and the job is to locate it. Where did the chain break?
Both assumptions feel like common sense. Both are, in my experience, the reason so many operational problems get diagnosed correctly and solved anyway to no effect. Because the world does not run as a single chain.
What actually happens
Nothing important in an organization moves in one line. Suppliers, customers, finance, manufacturing, procurement, logistics, technology, regulation — every one of them influences several of the others at the same time, in both directions. Add AI agents, human judgment, external partners, weather, and geopolitics, and the picture is not a longer chain. It is a weave: many strands running at once, crossing, pulling on each other, producing an outcome together that no single strand could produce alone.
Ask the chain question of that system — where did it break? — and you will get an answer that is technically true and practically useless. You will find a broken link and miss the pattern of interactions that broke it.
The question that broke the chain
When I went into the Department of National Defence in 1998, deliveries were late, and everyone already knew where the chain had “broken”: procurement. The instruction was to automate procurement and make it faster.
The first question I asked was not about procurement. It was: what time of day do orders come in?
It sounded irrelevant. It was the whole thing. Orders were being sandbagged to the end of the day, because the service technicians who placed them were measured on how many service calls they could respond to with an onsite visit — a different function, a different incentive, a different strand entirely. Late ordering pushed buying into the window where MRO prices ran up and cross-border customs slowed down. The “procurement failure” was not in procurement. It was an emergent property of technician incentives, measurement, dispatch, time-of-day pricing, and customs paperwork — several strands intersecting, none of them the broken link, all of them the cause.
No chain model would ever have found that. You cannot find an intersection by walking a line.
Strand Commonality — the principle underneath
What I was doing had a name, and it came before the engagement, not out of it. Strand Commonality™ is the observational principle that seemingly separate operational strands — contracts, supplier performance, inventory, sourcing, the data sitting in the ERP — are frequently different expressions of the same underlying operating reality, and that the recurring relationships between them explain outcomes no single strand can.
It is the reason the Government of Canada’s Scientific Research and Experimental Development program funded my research in the first place. Not to build the Metaprise — that came later. The funding followed the theory; it did not produce it. What the DND engagement gave me was the chance to test the principle against a real operating production environment, and the principle held.
I have found the clearest way to convey it is not the mathematics of physics but the image of music. A violin played alone tells you something. So does a cello, a flute. But no one mistakes an instrument for the symphony. The music is not in any one player — it emerges from timing, interaction, and structure among all of them. An individual procurement metric, a supplier scorecard, a contract — each tells you something. Organizational performance emerges from how they interact, not from any one of them alone.
If you want the physicist’s version: string theory makes the same intellectual move — that the particles we think are fundamental are really different expressions of a deeper structure. I would not claim my organizational work is string theory; one is an unconfirmed mathematical theory of the universe and the other is a discipline drawn from practice. But the instinct is identical. The visible object is not the fundamental reality. Look beneath it for the relationships that generate what you see.
Metaprise — the architecture that follows
Once you accept that those cross-cutting relationships are real, a chain stops being an adequate description of what you are managing — and so does the word “enterprise.” What you are actually operating is an interacting ecosystem of human and non-human agents working across multiple overlapping structures at once, inside and beyond the organization’s boundaries. That is what I mean by the Metaprise™. A chain has one dimension. A Metaprise has many.
The chronology matters here, because people tend to get it backwards. Strand Commonality is the observational principle — the epistemology, the way of discovering what is actually happening. The Metaprise is the architectural conclusion that grew out of it, once I realized those relationships extended past anything “supply chain,” or even “enterprise,” could hold. The principle came first. The architecture followed. Both sit alongside the two constants I have written about elsewhere — Invariant Physics™, which describes what does not change across technology eras, and Implementation Physics™, which describes how change survives contact with reality.
What the term costs you
“Supply chain” is a fine operational label. I will keep using it, because everyone knows what it means. But I want to be clear about what it costs when it becomes the mental model rather than just the label. It teaches you to hunt for a broken link when you should be reading a pattern of interactions. It asks where did it break when the useful question is what relationships produced this outcome. It trains attention on objects when the answer is almost always in the relationships between them.
The system I have spent nearly three decades first creating and then studying was never a chain. It was always a weave. And the strength — or the failure — was never in any single thread. It was in the pattern.
So the question I would leave you with is the one I have been asking, in one form or another, since 1998:
When something in your organization goes wrong, are you still looking for the broken link — or are you finally ready to look at the weave?
This reflection draws on the Procurement Insights archive — an independent record I have published openly since 2007, consolidating documented client work, lectures, and writing reaching back to 1998, and carrying no vendor sponsorships across the past decade. Every claim is held to the Provenance Ledger™, a verify-before-publish discipline that traces each assertion to a primary source and reconciles the record forward rather than editing it in place. Strand Commonality™, Metaprise™, Invariant Physics™, and Implementation Physics™ are proprietary frameworks of Hansen Models™. Getting it right, rather than being right.
-30-
The Same Drawing, a Generation Apart
The synchronized model above I first set out in the late 1990s, publicized in early 2000 in a Metaprise™ brochure — participants coordinating through a shared center rather than handing off down a line. The version beneath it I drew now.
Lay one over the other and they register. The participants sit in the same ring. The many-to-many connections trace the same crossings. The coordinating center holds in the same place. Two drawings made a generation apart — across a complete turnover of the technologies beneath them, from a world with no cloud and no agents to one built on both — and when you superimpose them, they are the same drawing.
That is the argument of this entire post in a single frame. The label was “supply chain.” The technology was ERP, then the internet, then cloud, now AI. All of it changed. The shape of how organizations actually coordinate did not. And this is a claim you can falsify on sight: if the operating reality of 2026 were genuinely a different shape — a chain, or something new — the overlay would not line up. It lines up.
That is the difference between a demonstrated constant and a lucky guess. That earlier model was not predicting 2026. It was a correct description of how organizations coordinate, and 2026 has the same shape because the shape is the invariant — not the technology wrapped around it.
This is what Invariant Physics™ looks like visually: not a forecast that came true, but a description that was accurate when it was drawn and has not been contradicted since — across every era, every platform, and every renaming of the thing itself.
-30-
Share this:
Like this:
Related