Braum’s bounded itself to a circle roughly 300 miles wide, and the market reads it as caution — a company that left growth on the table. Read the same decision through Implementation Physics and it is one of the most disciplined growth strategies in American retail. It is also the same discipline that governed a cotton exchange in 1931 and a defence supply chain in 1998. The technology changes. The law doesn’t.
Whenever Braum’s comes up, the reflex is immediate and almost unanimous. Look what they gave up. A family dairy in Oklahoma, founded in 1968, that still owns its own herd, its own feed mill, its own processing plant, its own bakery, its own trucks — and roughly 300 stores it refuses to expand beyond a fixed radius of the farm. The analyst’s instinct, the investor’s instinct, the consultant’s instinct, all land in the same place: they could have been so much bigger. They didn’t become McDonald’s. They didn’t become Walmart. They capped their own footprint.
The what did they give up question is the wrong question, and it is the wrong question in a way that should interest anyone trying to make sense of why technology initiatives fail. Because “what did they give up?” is the scaling-era version of a reflex I have spent decades watching wreck transformation programs: the assumption that growth is always good, that more footprint is always progress, and that any boundary on expansion is a cost rather than a choice. The right question — the one almost no one asks — is the opposite. What were they protecting?
What the Radius Actually Protects
Start with the facts, because they are unusual and they are verifiable. Braum’s is the only major ice cream maker in the country that still milks its own cows — a private herd of roughly ten thousand, one of the largest dairy operations in the world. Milk moves from cow to store shelf in under thirty-six hours. But it is not only the milk. Braum’s also raises and processes its own beef — the burgers are 100% beef, never frozen, ground from the company’s own herd, in stores within thirty-six to forty-eight hours, and cooked to order. The sesame-seed buns are baked daily in Braum’s own bakery. The trucks run nearly every day of the year. And every store sits within roughly 300 miles of the Tuttle, Oklahoma farm.
The market reads that radius as a ceiling. It is not a ceiling. It is the boundary inside which the promise stays true.
And notice that it is not one promise but several, which is the part that should end the argument before it starts. The easy dismissal of Braum’s is that dairy is a special case — milk is uniquely perishable, so of course freshness needs proximity. The beef and the bakery close that escape hatch. Fresh-ground never-frozen beef cooked to order, buns baked the same day, milk on the shelf within a day and a half — these are three distinct immobile conditions, and the radius protects all of them at once. This is not a quirk of one perishable product. It is an entire vertically integrated operation whose every promise depends on the same boundary holding. Braum’s owns the feed mill, the herd, the processing plant, the bakery, the beef, the trucks, and the stores — and it owns all of it precisely because every link has to stay inside the radius for the promise to survive. The ownership and the radius are the same decision seen from two angles.
The core promise is freshness — milk on the shelf a day and a half after the cow was milked, beef that never sees a freezer, bread baked that morning. That promise is not portable. It depends on physical proximity, on time, on owned distribution, on control of every link from feed to freezer. Stretch the radius and the promise breaks — not gradually, but at the exact distance where the product can no longer make the trip fresh. The 300 miles is not how far Braum’s was able to grow. It is how far it could grow while the thing that makes it Braum’s remained intact.
And the radius protects more than the milk. By Braum’s own account, the boundary is also what lets every delivery driver be home with their family each night. The condition being protected is not a single variable. It is freshness and the human reality of the operation — two conditions held by one boundary. Cross it, and you don’t lose one of them. You lose both, and you become a different company that happens to share a name.
Robinson Saw This in 1931
Here is where the archive does the work that no single observation could, because the principle underneath Braum’s is not new. It is ninety-five years old, and it has been sitting in the procurement literature the whole time.
In 1931, the economist E.G. Robinson drew a distinction that almost no one outside economic history remembers, and that explains Braum’s completely. He separated external economies into two kinds. Mobile external economies are benefits a firm can capture from well beyond the territory where they are produced — they travel. Immobile external economies require proximity; they only exist if the firm is physically close enough to realize them. His example of a mobile economy was the Liverpool cotton exchange, which firms could use locally or globally to everyone’s benefit. His conclusion, remarkable for an era with no internet and no global logistics, was that the advantages of concentrating large-scale industry in one place were declining as mobile economies rose.
That single distinction is the law the whole Braum’s story turns on. Before you scale, you have to know whether your value lives in a mobile economy or an immobile one — because scaling destroys value precisely when you treat an immobile condition as though it were mobile.
Braum’s value is an immobile economy. Freshness-in-thirty-six-hours cannot travel; it requires proximity by its physical nature. So Braum’s did the only disciplined thing available: it governed the boundary to the radius where the immobile condition holds, and refused to cross it. Wall Street’s “what did they give up?” is not a neutral question. It is the specific error of assuming all value is mobile — that footprint can always expand without cost. For an immobile economy, that assumption is fatal. The companies that make it scale the footprint and then spend years and fortunes trying to rebuild the condition they destroyed in the expansion. Braum’s simply declined to destroy it in the first place.
There is a tempting third option, and it is worth pausing on because it proves the rule rather than breaking it: instead of respecting the boundary or ignoring it, you can try to engineer it away — to convert an immobile economy into a mobile one. Years ago I wrote about exactly such an attempt: Made-in-Transit packaging, a concept by the designer Agata Jaworska in which food keeps growing inside its package during shipping, so that it arrives at the store at peak freshness rather than decaying toward a “best before” date. It was genuinely inventive — TIME named it a best invention of 2008, and it was exhibited at MoMA — and it was a real effort to make freshness travel. And it worked, for mushrooms, because the warmth of a freight truck is exactly what a growing mushroom needs. It did not work for bananas, where, as I noted at the time, you would have to ship the tree with the fruit. The concept became celebrated design thinking; it never became the supermarket system it set out to be. The lesson is not that the attempt failed — it is that engineering can sometimes move the immobile-versus-mobile line, but only where the physics happens to cooperate, and never by wishing it away. The boundary does not vanish. It relocates to wherever the physics actually stops you. Braum’s milk, beef, and bread are the banana case, not the mushroom case — which is precisely why Braum’s bounds the radius instead of trying to package its way out of it.
The Same Law, Three More Times
This is the part the archive makes visible in a way a single post never could. The Braum’s principle is not a dairy principle. It shows up, identically, across domains and across a century — and I have it on the record in three places that were never written to prove a single law, but do.
In August 2007, writing on public-sector procurement, external economies, and the global value chain, I worked through Humphrey and Schmitz’s governance framework — the recognition that the value in a chain comes from governing the relationships among the actors: coordinating decisions not only on what is produced and how, but on when, how much, and at what price. The value was never in compressing suppliers or centralizing spend. It was in governing the coordination. Same law: the footprint is not the point; the governance of the boundary is.
In July 2024, looking at AstraZeneca’s “two supply chain” strategy — one for the East, one for the West, with R&D kept global — I argued the move was neither retreat nor innovation. It was adaptive governance, and my advice was four words: don’t throw out the umbrella; use it differently. AstraZeneca had read its own economies correctly. Manufacturing is regional and benefits from proximity — an immobile economy, governed by region. R&D is a mobile economy, governed globally. They did not pick a footprint. They governed each economy according to its nature. Exactly what Braum’s did, in reverse proportion.
And in January 2026, tracing the line from the Liverpool cotton exchange of 1930 to DP World’s 2026 resilience report, the through-line was unmistakable: resilience is not bought with proximity alone, and it cannot be automated into being. You cannot automate your way to resilience. You have to govern your way there. Robinson knew it in 1931. The DND agent-based work proved it in 1998. DP World is documenting it in 2026. The technology changed beyond recognition across that span. The governance question did not change at all.
Three posts — written in 2007, 2024, and this year — in public-sector procurement, pharmaceutical supply, and global port logistics. None was written to prove the others. Together they establish that the Braum’s lesson is not an anecdote about ice cream. It is a law about scale, and Braum’s is simply the cleanest place to see it, because the condition it protects — freshness — is so physical that the boundary is visible on a map.
What Implementation Physics Actually Is
This is the discipline underneath all of it. Implementation Physics is not a slogan about doing things in the right order. It is the practice of identifying the operating condition on which the promise depends — and determining whether that condition is mobile or immobile — before you scale, before you deploy, before you expand. Because the failure mode is always the same: an organization maximizes the footprint, discovers too late that it has crossed the boundary where its real value lived, and then spends years trying to recreate the condition it destroyed in the name of growth.
It is the same finding as the Department of National Defence engagement in 1998. Delivery was failing, and every instinct in the room said to process more orders, add more systems, scale the operation. The breakthrough was not more of anything. It was a single question that exposed the hidden condition: what time of day do orders come in? Order timing silently governed customs, courier, inventory, and pricing — an immobile condition that no amount of added scale would fix, and that the right governance fixed completely. Fixing the condition, with no new technology in the building, drove delivery performance from 51% to 97.3%.
Only then did the technology enter — and this is the part that matters, because it is the whole law in sequence. Three months later, once the substrate was aligned and a pilot had proven it out, the agent-based modeling system (RAM, 1998) was introduced. Running on conditions that now actually supported it, the technology delivered what it never could have delivered on the broken substrate: it reduced the collective buyer FTE count from twenty-three to three, and it sustained the result across seven consecutive years. The condition fix recovered the performance. The technology, applied to an aligned substrate, harvested the efficiency and made it durable. Reverse that order — technology first, onto the broken condition — and you get the generational failure from the ERP to the present-day AI eras.
That is what Braum’s did with its radius, what AstraZeneca did with its two chains, what the Liverpool exchange did through governance, and what the DND work did by asking the unglamorous question first. The names differ. The discipline is identical.
So the next time a company holds off on selecting the technology to ask the better question first, don’t read it as a threat to technology adoption. Read it as the deliberate sequencing — the critical delay that aligns the seams between the functions before the technology lands on them, exactly as it happened at DND. That is not caution. It is the difference between technology that harvests value and technology that fails on a substrate that was never ready for it.
The radius was never the limit. It was the condition — the whole business — and the discipline was refusing to confuse the two.
-30-
Note: Braum’s does not, to my knowledge, describe its decisions in these terms. The operational facts above are a matter of public record; the reading of them through mobile and immobile economies is mine. What the company intended is its own; what the decision reveals, when you hold it up to a ninety-five-year-old economic distinction, is the subject of this piece.
Truth Is Believing. Accuracy Is Knowing.
Jon Hansen is the creator of Implementation Physics™, a research-based framework developed over nearly three decades to explain why technology and operating initiatives succeed or fail regardless of the technology being deployed. His research forms the foundation for the Hansen Method™, Hansen Fit Score™ (HFS™), Phase 0™ Readiness Assessment, and the ARA™ RAM 2025™ multimodel verification architecture. He currently serves as a Board Member of the CIPS Americas Chapter.
Related reading from the archive: Public Sector Procurement Practice and the Principles of External Economies, Clustering and the Global Value Chain (August 2007) · Made-in-Transit Packaging: Innovative, But Is It Practical? (December 2010) · AstraZeneca — Don’t Throw Out the Umbrella (July 2024) · From Liverpool 1930 to DP World 2026: The Supply Chain Governance Question That Never Changes (January 2026)
Related
The Radius Was Never the Limit. It Was the Condition.
Posted on June 13, 2026
0
Braum’s bounded itself to a circle roughly 300 miles wide, and the market reads it as caution — a company that left growth on the table. Read the same decision through Implementation Physics and it is one of the most disciplined growth strategies in American retail. It is also the same discipline that governed a cotton exchange in 1931 and a defence supply chain in 1998. The technology changes. The law doesn’t.
Whenever Braum’s comes up, the reflex is immediate and almost unanimous. Look what they gave up. A family dairy in Oklahoma, founded in 1968, that still owns its own herd, its own feed mill, its own processing plant, its own bakery, its own trucks — and roughly 300 stores it refuses to expand beyond a fixed radius of the farm. The analyst’s instinct, the investor’s instinct, the consultant’s instinct, all land in the same place: they could have been so much bigger. They didn’t become McDonald’s. They didn’t become Walmart. They capped their own footprint.
The what did they give up question is the wrong question, and it is the wrong question in a way that should interest anyone trying to make sense of why technology initiatives fail. Because “what did they give up?” is the scaling-era version of a reflex I have spent decades watching wreck transformation programs: the assumption that growth is always good, that more footprint is always progress, and that any boundary on expansion is a cost rather than a choice. The right question — the one almost no one asks — is the opposite. What were they protecting?
What the Radius Actually Protects
Start with the facts, because they are unusual and they are verifiable. Braum’s is the only major ice cream maker in the country that still milks its own cows — a private herd of roughly ten thousand, one of the largest dairy operations in the world. Milk moves from cow to store shelf in under thirty-six hours. But it is not only the milk. Braum’s also raises and processes its own beef — the burgers are 100% beef, never frozen, ground from the company’s own herd, in stores within thirty-six to forty-eight hours, and cooked to order. The sesame-seed buns are baked daily in Braum’s own bakery. The trucks run nearly every day of the year. And every store sits within roughly 300 miles of the Tuttle, Oklahoma farm.
The market reads that radius as a ceiling. It is not a ceiling. It is the boundary inside which the promise stays true.
And notice that it is not one promise but several, which is the part that should end the argument before it starts. The easy dismissal of Braum’s is that dairy is a special case — milk is uniquely perishable, so of course freshness needs proximity. The beef and the bakery close that escape hatch. Fresh-ground never-frozen beef cooked to order, buns baked the same day, milk on the shelf within a day and a half — these are three distinct immobile conditions, and the radius protects all of them at once. This is not a quirk of one perishable product. It is an entire vertically integrated operation whose every promise depends on the same boundary holding. Braum’s owns the feed mill, the herd, the processing plant, the bakery, the beef, the trucks, and the stores — and it owns all of it precisely because every link has to stay inside the radius for the promise to survive. The ownership and the radius are the same decision seen from two angles.
The core promise is freshness — milk on the shelf a day and a half after the cow was milked, beef that never sees a freezer, bread baked that morning. That promise is not portable. It depends on physical proximity, on time, on owned distribution, on control of every link from feed to freezer. Stretch the radius and the promise breaks — not gradually, but at the exact distance where the product can no longer make the trip fresh. The 300 miles is not how far Braum’s was able to grow. It is how far it could grow while the thing that makes it Braum’s remained intact.
And the radius protects more than the milk. By Braum’s own account, the boundary is also what lets every delivery driver be home with their family each night. The condition being protected is not a single variable. It is freshness and the human reality of the operation — two conditions held by one boundary. Cross it, and you don’t lose one of them. You lose both, and you become a different company that happens to share a name.
Robinson Saw This in 1931
Here is where the archive does the work that no single observation could, because the principle underneath Braum’s is not new. It is ninety-five years old, and it has been sitting in the procurement literature the whole time.
In 1931, the economist E.G. Robinson drew a distinction that almost no one outside economic history remembers, and that explains Braum’s completely. He separated external economies into two kinds. Mobile external economies are benefits a firm can capture from well beyond the territory where they are produced — they travel. Immobile external economies require proximity; they only exist if the firm is physically close enough to realize them. His example of a mobile economy was the Liverpool cotton exchange, which firms could use locally or globally to everyone’s benefit. His conclusion, remarkable for an era with no internet and no global logistics, was that the advantages of concentrating large-scale industry in one place were declining as mobile economies rose.
That single distinction is the law the whole Braum’s story turns on. Before you scale, you have to know whether your value lives in a mobile economy or an immobile one — because scaling destroys value precisely when you treat an immobile condition as though it were mobile.
Braum’s value is an immobile economy. Freshness-in-thirty-six-hours cannot travel; it requires proximity by its physical nature. So Braum’s did the only disciplined thing available: it governed the boundary to the radius where the immobile condition holds, and refused to cross it. Wall Street’s “what did they give up?” is not a neutral question. It is the specific error of assuming all value is mobile — that footprint can always expand without cost. For an immobile economy, that assumption is fatal. The companies that make it scale the footprint and then spend years and fortunes trying to rebuild the condition they destroyed in the expansion. Braum’s simply declined to destroy it in the first place.
There is a tempting third option, and it is worth pausing on because it proves the rule rather than breaking it: instead of respecting the boundary or ignoring it, you can try to engineer it away — to convert an immobile economy into a mobile one. Years ago I wrote about exactly such an attempt: Made-in-Transit packaging, a concept by the designer Agata Jaworska in which food keeps growing inside its package during shipping, so that it arrives at the store at peak freshness rather than decaying toward a “best before” date. It was genuinely inventive — TIME named it a best invention of 2008, and it was exhibited at MoMA — and it was a real effort to make freshness travel. And it worked, for mushrooms, because the warmth of a freight truck is exactly what a growing mushroom needs. It did not work for bananas, where, as I noted at the time, you would have to ship the tree with the fruit. The concept became celebrated design thinking; it never became the supermarket system it set out to be. The lesson is not that the attempt failed — it is that engineering can sometimes move the immobile-versus-mobile line, but only where the physics happens to cooperate, and never by wishing it away. The boundary does not vanish. It relocates to wherever the physics actually stops you. Braum’s milk, beef, and bread are the banana case, not the mushroom case — which is precisely why Braum’s bounds the radius instead of trying to package its way out of it.
The Same Law, Three More Times
This is the part the archive makes visible in a way a single post never could. The Braum’s principle is not a dairy principle. It shows up, identically, across domains and across a century — and I have it on the record in three places that were never written to prove a single law, but do.
In August 2007, writing on public-sector procurement, external economies, and the global value chain, I worked through Humphrey and Schmitz’s governance framework — the recognition that the value in a chain comes from governing the relationships among the actors: coordinating decisions not only on what is produced and how, but on when, how much, and at what price. The value was never in compressing suppliers or centralizing spend. It was in governing the coordination. Same law: the footprint is not the point; the governance of the boundary is.
In July 2024, looking at AstraZeneca’s “two supply chain” strategy — one for the East, one for the West, with R&D kept global — I argued the move was neither retreat nor innovation. It was adaptive governance, and my advice was four words: don’t throw out the umbrella; use it differently. AstraZeneca had read its own economies correctly. Manufacturing is regional and benefits from proximity — an immobile economy, governed by region. R&D is a mobile economy, governed globally. They did not pick a footprint. They governed each economy according to its nature. Exactly what Braum’s did, in reverse proportion.
And in January 2026, tracing the line from the Liverpool cotton exchange of 1930 to DP World’s 2026 resilience report, the through-line was unmistakable: resilience is not bought with proximity alone, and it cannot be automated into being. You cannot automate your way to resilience. You have to govern your way there. Robinson knew it in 1931. The DND agent-based work proved it in 1998. DP World is documenting it in 2026. The technology changed beyond recognition across that span. The governance question did not change at all.
Three posts — written in 2007, 2024, and this year — in public-sector procurement, pharmaceutical supply, and global port logistics. None was written to prove the others. Together they establish that the Braum’s lesson is not an anecdote about ice cream. It is a law about scale, and Braum’s is simply the cleanest place to see it, because the condition it protects — freshness — is so physical that the boundary is visible on a map.
What Implementation Physics Actually Is
This is the discipline underneath all of it. Implementation Physics is not a slogan about doing things in the right order. It is the practice of identifying the operating condition on which the promise depends — and determining whether that condition is mobile or immobile — before you scale, before you deploy, before you expand. Because the failure mode is always the same: an organization maximizes the footprint, discovers too late that it has crossed the boundary where its real value lived, and then spends years trying to recreate the condition it destroyed in the name of growth.
It is the same finding as the Department of National Defence engagement in 1998. Delivery was failing, and every instinct in the room said to process more orders, add more systems, scale the operation. The breakthrough was not more of anything. It was a single question that exposed the hidden condition: what time of day do orders come in? Order timing silently governed customs, courier, inventory, and pricing — an immobile condition that no amount of added scale would fix, and that the right governance fixed completely. Fixing the condition, with no new technology in the building, drove delivery performance from 51% to 97.3%.
Only then did the technology enter — and this is the part that matters, because it is the whole law in sequence. Three months later, once the substrate was aligned and a pilot had proven it out, the agent-based modeling system (RAM, 1998) was introduced. Running on conditions that now actually supported it, the technology delivered what it never could have delivered on the broken substrate: it reduced the collective buyer FTE count from twenty-three to three, and it sustained the result across seven consecutive years. The condition fix recovered the performance. The technology, applied to an aligned substrate, harvested the efficiency and made it durable. Reverse that order — technology first, onto the broken condition — and you get the generational failure from the ERP to the present-day AI eras.
That is what Braum’s did with its radius, what AstraZeneca did with its two chains, what the Liverpool exchange did through governance, and what the DND work did by asking the unglamorous question first. The names differ. The discipline is identical.
So the next time a company holds off on selecting the technology to ask the better question first, don’t read it as a threat to technology adoption. Read it as the deliberate sequencing — the critical delay that aligns the seams between the functions before the technology lands on them, exactly as it happened at DND. That is not caution. It is the difference between technology that harvests value and technology that fails on a substrate that was never ready for it.
The radius was never the limit. It was the condition — the whole business — and the discipline was refusing to confuse the two.
-30-
Note: Braum’s does not, to my knowledge, describe its decisions in these terms. The operational facts above are a matter of public record; the reading of them through mobile and immobile economies is mine. What the company intended is its own; what the decision reveals, when you hold it up to a ninety-five-year-old economic distinction, is the subject of this piece.
Truth Is Believing. Accuracy Is Knowing.
Jon Hansen is the creator of Implementation Physics™, a research-based framework developed over nearly three decades to explain why technology and operating initiatives succeed or fail regardless of the technology being deployed. His research forms the foundation for the Hansen Method™, Hansen Fit Score™ (HFS™), Phase 0™ Readiness Assessment, and the ARA™ RAM 2025™ multimodel verification architecture. He currently serves as a Board Member of the CIPS Americas Chapter.
Related reading from the archive: Public Sector Procurement Practice and the Principles of External Economies, Clustering and the Global Value Chain (August 2007) · Made-in-Transit Packaging: Innovative, But Is It Practical? (December 2010) · AstraZeneca — Don’t Throw Out the Umbrella (July 2024) · From Liverpool 1930 to DP World 2026: The Supply Chain Governance Question That Never Changes (January 2026)
Share this:
Like this:
Related