When The Pizza Gets Lost In The Spreadsheet

There is something wonderfully reassuring about a spreadsheet.

Everything has a place. Rows. Columns. Percentages. Totals. Variances. Forecasts. You can take a complicated business and make it look remarkably orderly.

And that is both the power of the spreadsheet — and sometimes its greatest danger.

Because somewhere between the pizza shop and the spreadsheet, the pizza can get lost.

The spreadsheet isn't the problem

Let's be clear. I like spreadsheets. Most executives I know do. They help us see patterns, compare performance, identify problems and make decisions. Dashboards, KPIs, forecasts and analytics do much the same thing. We need them.

The problem begins when information becomes a substitute for understanding.

Imagine a customer walks into a pizza restaurant and complains that her pizza is late. The employee knows why. The oven has been running inconsistently all evening. One of the experienced cooks called in sick. The new employee is still learning. There was an unusually large order from a local business. And the delivery driver had to make two trips because the first order was incomplete.

The customer doesn't care about any of that. She just knows her pizza is late.

Now imagine how that event travels through the organization. The employee tells the supervisor. The supervisor records the incident. The information gets captured in a customer-service system. A weekly report shows an increase in delivery complaints. The regional manager sees the number. The operations team sees a trend. Eventually, the executive team sees a slide that says: Delivery satisfaction down 4.7%.

The number may be completely accurate. But something important has happened.

The story has disappeared.

We love the number because the number feels objective

Numbers are comforting. They appear neutral. They allow us to compare one period with another, one business unit with another, one plant with another, one acquisition with another. They give us the ability to say, 'Here is what is happening.'

But a number rarely tells us why it is happening. And even when it does, it may not tell us what the person closest to the problem knows that the number doesn't.

That distinction matters.

A customer satisfaction score tells you something about the customer. It doesn't necessarily tell you what the customer experienced. An employee engagement score tells you something about employees. It doesn't necessarily tell you why an employee is frustrated. A productivity number tells you something about output. It doesn't necessarily tell you what employees are doing to achieve that output. A margin tells you something about financial performance. It doesn't necessarily tell you what had to be sacrificed to produce it.

The spreadsheet tells you what happened. The pizza tells you why.

The further away we get, the more we aggregate

This is where The Distance From The Pizza becomes interesting.

The further an organization gets from the actual work, the more information tends to be summarized. One customer complaint becomes a percentage. One hundred complaints become a trend. A trend becomes a KPI. The KPI becomes a dashboard. The dashboard becomes a board presentation. And eventually a very real experience becomes a little box on a PowerPoint slide.

There is nothing inherently wrong with that progression. Leaders cannot personally listen to every customer. They cannot watch every employee. They cannot stand beside every machine. They cannot sit in every sales meeting.

Scale requires abstraction.

But abstraction has a price.

The question is whether we know what that price is.

The spreadsheet can hide the exception

Here's another problem. Organizations are very good at measuring what happens most often. They are much less good at understanding what happens occasionally.

But sometimes the exception is where the real problem lives.

The customer who leaves after one terrible experience may be statistically insignificant. The experienced employee who quietly quits may barely move the turnover number. The production line that develops an intermittent problem may still hit its monthly target. The supplier relationship that deteriorates slowly may never trigger a red flag. The manager who spends three hours every Friday creating a workaround may still report that the process is 'working.'

The spreadsheet sees the aggregate. The person doing the work sees the exception.

And exceptions are often where organizational friction hides.

When the KPI becomes the objective

There is an even more dangerous moment. It happens when the measurement designed to help the organization becomes the thing the organization manages.

Customer service agents discover which metrics matter and optimize for them. Managers learn how their business units are evaluated and manage toward those measures. E

Employees learn what gets noticed. Soon the organization isn't necessarily improving the business. It is improving the numbers that represent the business.

That distinction can be subtle. And it can be expensive. Because a metric is a proxy. It is not the thing itself. Customer satisfaction isn't the customer. Employee engagement isn't the employee. Productivity isn't the work. Revenue isn't the customer relationship. EBITDA isn't the business.

And the spreadsheet isn't the pizza.

This is where transformation gets interesting

Every major transformation produces more data. New systems. New dashboards. New reporting structures. New KPIs. New governance. New performance measures. New definitions of success.

Ironically, an organization can emerge from a transformation with dramatically more information — and still be farther away from the reality of the business.

That is not necessarily a technology failure. It can be an organizational design problem.

The technology may be working perfectly. The ERP may be working perfectly. The dashboard may be working perfectly. The data may be accurate. And yet the organization may still be making poor decisions because it has lost the context behind the data.

This is one reason frontline input matters so much. People closest to the work often see problems before they become metrics.

The challenge is not choosing between data and people. It's making sure the data doesn't silence the people.

The dashboard should be a window, not a wall

A good dashboard should make the organization easier to understand. Not harder.

It should cause a leader to ask, 'What's going on here?' Not, 'How do I get this number back where it belongs?'

That's a subtle difference.

Imagine a plant's on-time production rate drops from 96% to 91%. The instinct in many organizations is to ask who is accountable for the five-point decline. A better place to start might be: What changed? Who is closest to it? What do they know that we don't? What do we need to do about it?

The dashboard has done its job when it gets you to the pizza.

Not when it keeps you staring at the dashboard.

Information can reduce distance — or disguise it

This may be one of the most important distinctions in modern organizations.

Technology has the potential to reduce organizational distance enormously. Real-time operational data can give leaders visibility they never had before. Analytics can reveal patterns that would otherwise be invisible. AI can synthesize enormous volumes of information. Digital systems can connect frontline activity with executive decision-making.

All of that can bring an organization closer to the pizza.

But there is another possibility.

Technology can create the illusion of proximity.

A CEO can have 47 dashboards on a screen and still have no idea what is happening on the factory floor. A board can receive hundreds of pages of reporting and still miss the emerging issue. A manager can have access to every KPI imaginable and still be surprised by what the customer or employee is experiencing. More information does not automatically mean more understanding.

Sometimes it simply means we have built a better spreadsheet between ourselves and the pizza.

So what should leaders do?

Perhaps the answer is surprisingly simple.

Keep going to the pizza.

Not literally — although sometimes literally. Talk to customers. Talk to frontline employees. Visit the plant. Sit with the service team. Listen to the salespeople. Ask the warehouse employees what isn't working. Ask the people who actually use the new system. Ask the people who are creating the workarounds.

Then come back to the spreadsheet.

Because the spreadsheet is still incredibly valuable. But now you have context. Now you know what the number means. Now you can see the difference between a temporary fluctuation and an emerging problem. Now you can recognize when the number is telling you something important — and when it is hiding something important.

The best leaders don't choose between the spreadsheet and the pizza. They know when to look at each one.

The Pizza Test

So here's another question for the series.

When someone brings you a number, ask: Where is the pizza?

Who experienced the outcome? Who performed the work? Who saw the problem first? Who understands the exception? Who knows what the number doesn't tell you?

And perhaps the most important question: When was the last time someone from the executive team actually went looking for the story behind the number? Because if the answer is 'never,' there is a good chance the organization is managing the spreadsheet.

Not the pizza.

The Distance From The Pizza

The first article in this series asked: How far away from the pizza are we?

This one asks a slightly different question: Can we still see the pizza through the spreadsheet?

As organizations grow, abstraction is inevitable. The challenge is not to eliminate it. The challenge is to prevent abstraction from becoming disconnection.

Because eventually every number represents something real.

A customer. An employee. A product. A machine. A relationship. A decision. A consequence. A pizza.

And if we forget that, the spreadsheet may tell us everything we need to know — except what's actually going on.

James Ellis - October 2026