The Distance From The Pizza

Every organization starts close to the pizza.

In a small business, the person making the decisions is often close to the customer, the employee, the product and the consequences of those decisions. As the organization grows, that proximity begins to disappear.

More locations, more management layers, more specialized functions, more systems, more reporting and more technology can create increasing distance between the people making decisions and the people experiencing the outcomes.

That distance is not necessarily bad. Scale creates enormous advantages. Centralization can eliminate duplication. Standardization can improve consistency. Technology can increase speed and visibility. Mergers and acquisitions can create real operating and financial value.

But distance can also create organizational friction. The central idea of this paper is simple:

The Distance From The Pizza is the distance between the person experiencing an outcome and the person truly empowered to change it.

As that distance grows, information may travel farther and become more sophisticated, while context, ownership and immediacy can diminish. The organization may know more about what is happening without necessarily being closer to why it is happening.

This matters enormously during transformation. Business cases routinely model cost savings, productivity, synergies, revenue growth and technology benefits. They are generally much less precise about the organizational consequences required to achieve those benefits: employee disruption, customer frustration, management distraction, lost institutional knowledge, productivity dips, turnover, workarounds and delayed execution.

Those consequences can create a second, less visible bill: Recovery Cost — the money, time and opportunity required to repair problems created or amplified by the transformation itself.

The question for leaders is therefore not whether transformation creates friction. It inevitably does. The question is whether the organization understands where the friction will occur, what it will cost, and whether the value being pursued is large enough to absorb it.

1. The $100 Million Question

Imagine a transformation with a headline value of $100 million.

The business case is compelling. There are identified synergies, productivity improvements, technology savings and opportunities for growth. But what if the organization spends $12 million dealing with the consequences of getting there?

Extra consulting. Retraining. Recruitment. Severance. System remediation. Customer recovery. Management distraction. Delayed projects. Lost productivity. Lost relationships.

And what if another $8 million of value simply never appears because key employees leave, customers become less satisfied, or institutional knowledge disappears?

The transformation may still have created value. But the value realized is not the value promised.

This is why organizational friction deserves to be treated as an economic variable, not simply a change-management issue.

2. Every Organization Starts Close to the Pizza

Imagine you own a neighbourhood pizza restaurant.

You know your customers. You know your employees. You can see the pizzas coming out of the oven. You hear the complaints. You notice when an employee is struggling. You know when the Saturday night rush goes badly. If a customer complains, you can often hear the complaint yourself. If an employee needs help, you can intervene immediately. If quality falls, you can see it.

There isn't much distance between the person making the decisions and the reality of the business.

Then the restaurant grows. One location becomes five. Five becomes fifty. Regional management appears. Then corporate functions. Procurement. HR. Finance. IT. Operations. Analytics. Customer service. Enterprise systems.

At some point, you're no longer managing pizza. You're managing reports about pizza.

3. The Distance From The Pizza

That is the metaphor.

The Distance From The Pizza is not physical distance. It is organizational distance. It is the distance between:

·       the customer and the person accountable for customer experience;

·       the employee doing the work and the person deciding how the work should be done;

·       the problem and the person empowered to fix it;

·       the data and the context behind the data;

·       the consequence and the decision that created it.

The greater the distance, the more likely it is that information will be filtered, translated, aggregated and eventually converted into a number on a dashboard. The number may be accurate. What can disappear is the story.

4. Distance Isn't The Enemy

This is not an argument against scale.

Large organizations can do things small organizations cannot. They can negotiate better prices, invest in sophisticated technology, develop specialized expertise, spread risk, standardize critical processes and build capabilities that would otherwise be impossible.

Centralization can remove duplication. Standardization can remove unnecessary variation.

But not all variation is waste.

Sometimes what looks like variation is local knowledge. Sometimes a workaround exists because the standardized process doesn't fit the customer. Sometimes an employee knows something the dashboard cannot see.

The challenge is distinguishing necessary distance from avoidable distance.

5. Distance Creates Organizational Friction

Organizational friction is what happens when the organization has to work harder than it should to turn a decision into an outcome. It can appear as:

·       slow decisions;

·       repeated approvals;

·       conflicting priorities;

·       workarounds;

·       employee frustration;

·       customer complaints;

·       duplicate work;

·       systems that do not reflect how work is actually performed;

·       leaders receiving information too late to act on it;

·       projects that technically launch but struggle to deliver the expected value.

Friction is not automatically bad. Some friction is necessary. Controls exist for reasons. Governance exists for reasons. Quality checks exist for reasons.

The objective is not zero friction. It is to understand which friction creates value and which friction consumes it.

6. We've Been Increasing Organizational Distance for More Than 40 Years

The story of modern business can also be read as a story of increasing organizational distance.

1980s–early 1990s: Physical consolidation. Organizations centralized management, closed facilities, consolidated operations and removed duplicated structures.

1990s: Process consolidation. ERP and centralized functions increasingly standardized how information and work moved through the organization.

2000s–2010s: Scale and financial engineering. Shared services, outsourcing, private-equity buy-and-build strategies and larger organizational footprints increased the importance of centralized decision-making.

2010s–2020s: Digital consolidation. Cloud systems, platforms, automation and analytics made it possible to manage larger and more distributed organizations from farther away.

Now: AI. AI may accelerate the trend further by allowing decisions to be made faster, at greater scale and potentially farther from the underlying work.

The question is not whether distance is increasing. The question is what happens when distance becomes disconnection.

7. The Transformation Business Case

Most transformation business cases are built around things that are relatively easy to model:

·       cost reduction;

·       productivity improvement;

·       revenue growth;

·       technology savings;

·       headcount reduction;

·       procurement savings;

·       merger synergies.

What is harder to model is the organizational absorption required to achieve those benefits.

·       How many experienced employees will leave?

·       How much productivity will be lost during the transition?

·       How much management capacity will be consumed?

·       How many customers will experience disruption?

·       How much institutional knowledge will disappear?

·       How many workarounds will employees create?

·       How long will it take for the new organization to perform as well as the old one?

The transformation business case often models the destination. It models the journey much less precisely.

8. The Evidence: Disruption Is Measurable

There is growing evidence that organizational disruption is not simply a subjective experience.

A 2017 meta-analysis covering 24 independent samples and 5,496 acquisitions found a consistently negative and statistically significant relationship between organizational cultural differences and acquisition performance.

A 2024 study of major U.S. airline mergers found that organizational consolidation produced meaningful deterioration in operational quality. Carrier-caused delays increased by roughly 20% of the industry average after operations were combined, with disruption generally fading over approximately one to two years. The authors estimated roughly $870 million in losses from organizational inefficiencies across the mergers studied, using a conservative back-of-the-envelope calculation.

Research on U.S. private-equity buyouts also illustrates the other side of the equation. A large study of approximately 3,200 target firms and 150,000 establishments found modest net employment effects alongside substantial increases in gross job creation and destruction, as well as productivity gains.

Transformation can create value and disruption at the same time. The question is whether we are measuring both.

9. Recovery Cost

One of the most useful ways to think about organizational friction is through Recovery Cost.

Recovery Cost is the cost of getting the organization back to the performance level required to realize the original business case.

Direct recovery cost. Additional consultants, retraining, recruitment, restructuring, system remediation and customer recovery.

Opportunity cost. Lost productivity, delayed projects, management distraction, missed sales and slower execution.

Permanent value leakage. Customers who leave, employees who do not return, relationships that deteriorate and institutional knowledge that disappears.

Eventually recovered does not necessarily mean economically recovered.

An organization may eventually return to stable headcount, service levels and operating performance. That does not mean it recovered the customers, relationships, knowledge, time and opportunities that were lost along the way.

10. The Pizza Test

Before launching a major transformation, ask a deceptively simple set of questions:

·       Where is the pizza?

·       Where does the customer experience the organization?

·       Where does the employee actually perform the work?

·       Where is the product or service created?

·       Where do problems first become visible?

·       How far away are the people making the important decisions?

·       Which distance is necessary?

·       Which distance is avoidable?

·       Does technology reduce the distance — or simply give management better information about what is happening at the other end?

The Pizza Test is not intended to produce a score. It is intended to force a conversation about proximity, context and accountability before the organization gets too far away from the work.

11. The Consultant That Is Six Degrees From The Pizza

There is another layer to the distance problem.

Large transformations often bring in consultants, systems integrators, program offices and external experts. They can provide valuable capabilities and objectivity. But every additional layer creates another opportunity for reality to be translated before it reaches the people making decisions.

A frontline problem becomes a workstream. A workstream becomes a status report. A status report becomes a steering-committee issue. A steering-committee issue becomes an executive decision.

By the time the decision reaches the executive table, everyone may be looking at the same problem — but nobody is necessarily looking at the pizza.

The answer is not to eliminate consultants. It is to make sure the transformation team maintains enough proximity to the work that abstraction does not replace understanding.

12. The Private Equity Pizza

Private equity provides a particularly interesting test of the concept.

Buy-and-build strategies can create genuine value through purchasing scale, operational improvement, management capability, technology and capital discipline. But as portfolios grow, the distance between the investment decision and the operating reality can also grow. A portfolio company can become a set of KPIs. A plant can become an EBITDA bridge. A customer relationship can become a retention percentage.

The numbers matter. But the numbers are not the pizza.

The challenge for owners and boards is to maintain enough operating proximity to know what the numbers are actually telling them.

13. The ERP Paradox

Enterprise systems were supposed to help organizations get better information. They did.

But better information is not the same as greater proximity. An ERP system can tell a senior executive that a process is taking 14% longer than expected. It may not tell them that a workaround exists because the standardized process does not fit a customer's requirement.

The system sees the transaction. The employee sees the exception.

The ERP paradox is that an organization can become better informed about the business while becoming more distant from the business.

14. The AI Pizza

AI creates the most interesting version of the question.

AI can summarize thousands of customer comments. It can identify patterns in employee data. It can predict demand. It can flag operational anomalies. It can accelerate decisions.

That could reduce organizational distance. But there is another possibility.

AI could simply allow us to make decisions farther away from the pizza — faster.

The technology itself will not determine the answer. Leadership choices will. The question should therefore be asked explicitly:

Can AI actually bring us closer to the pizza — or are we simply going to make decisions farther away from it, faster?

15. Transformation Is Not Complete When Implementation Is Complete

A system can go live. A merger can close. A new organization chart can be published. A shared-services model can be implemented. None of those things necessarily mean the transformation is complete.

The real test is whether the organization is producing the value the transformation was designed to produce. That is Value Realization.

And Value Realization depends on more than implementation. It depends on whether the organization can absorb the change without allowing organizational friction to consume the value being pursued.

Transformation Strategy → Organizational Friction → Execution → Value Realization

Conclusion: How Far Away From The Pizza Are We?

The most important question may not be how big an organization has become.

It may be how far away from the work its decision-makers have become.

Scale creates capability. Distance creates potential friction.

The challenge for leaders is to know when the distance is creating value and when it is beginning to consume it.

How far away from the pizza are we?

And what are we doing to make sure the people making the decisions can still see, hear and understand what is happening there? That is the question behind The Distance From The Pizza.

James Ellis - October 2026