The Difference Between Operational Truth and System Truth | Observations from the Shop Floor
Michael Gardner, COO
Few business conversations begin with someone questioning reality – most begin with someone insisting they are right.
“The order shipped.”
“No, it didn’t.”
“The inventory is available.”
“No, it isn’t.”
“The invoice matches.”
“Then why is everyone upset?”
I’ve heard versions of these conversations for most of my career; what makes them interesting is that both sides are often telling the truth. They’re simply describing different versions of reality.
Over the years, I’ve noticed something that exists in almost every business I’ve worked with: there are two forms of truth operating inside the organization at the same time. The first is what is actually happening; the second is what the system says is happening.
Most days those two realities remain reasonably close together… some days they do not. When they drift apart, the consequences can range from inconvenient to expensive. A customer calls asking where an order is. The system says it shipped. The warehouse manager says it is still sitting on a dock waiting for a carrier. Which one is true?
The answer is usually both.
The system is reporting what someone recorded, and operations is reporting what someone observed. Neither answer is necessarily wrong, but the challenge is that businesses do not operate solely on recorded events. They operate within the reality that exists between those events.
This is the difference between Operational Truth and System Truth.
System Truth is what has been recorded. Operational Truth is what people know.
Years ago, I experienced a situation that perfectly illustrated the difference. A customer placed an order for a specific product that we showed in stock. The customer was about two hours away from our warehouse, and we had a scheduled delivery heading into their market. We committed to delivering the product on that truck.
At the time, everything looked good. We had inventory on hand, and we also had additional inventory scheduled to arrive before the delivery date. Even though we backordered part of the request, we felt confident in making the commitment.
Then reality intervened.
The inventory count was accurate, but the material sitting in the warehouse had been damaged. It had already been moved to a damaged inventory area, but the process for removing it from available inventory had not yet been completed.
Meanwhile, the replenishment shipment arrived exactly as expected. The receiving transaction was entered into the system, so the inventory showed as received. There was only one problem: the material was still sitting in the receiving area. It had not been put away and was not yet available to pick. When the warehouse team went to fill the order, the product wasn’t there.
The customer didn’t receive the shipment.
The customer service representative was frustrated. The salesperson was frustrated. The warehouse team was frustrated. Most importantly, the customer was frustrated because the commitment we had made was not fulfilled.
To fulfill that commitment, another employee ended up loading the material into a personal vehicle the next day and driving it directly to the customer because all of our delivery trucks and drivers were already committed elsewhere.
It was expensive.
It was inconvenient.
And it wasn’t an ERP problem.
The system had done exactly what it was supposed to do. The inventory reflected what had been recorded, while operations understood what was actually happening. The two truths had simply drifted apart.
That experience changed our processes. Damaged inventory was identified and removed from available inventory faster. Incoming inventory was no longer considered available when it crossed the dock door. It became available when it was put away and ready to be picked.
We didn’t change software.
We changed the process.
Two Versions of Reality
Once you begin looking for this pattern, you see it everywhere.
- A purchase order says material will arrive Friday, but the truck breaks down on Thursday. Operationally, everyone knows the material will not arrive on time. The system still says Friday.
- A customer order shows complete, but the final component needed to assemble the product is damaged during production. Operations knows the order cannot ship. The system still shows complete.
- An invoice matches the purchase order, but the receiving team knows half the material was rejected during inspection. The accounting system sees a match while operations sees a problem.
Neither side is wrong – they are simply looking at different versions of reality.
Why the Gap Matters
One of the most common mistakes organizations make is assuming that these two truths should always be identical. In reality, businesses are dynamic while systems are transactional. People closest to the work usually recognize change long before a transaction is entered into a database.
The customer service representative already knows the shipment will be late, the scheduler already knows production will miss the target date, and the receiving department already knows the material has quality issues. The system simply has not caught up yet.
What I’ve learned over the years is that Operational Truth almost always arrives first. The system catches up later. Sometimes minutes later, sometimes days later… occasionally, much longer.
The Goal Is Not Perfection
Many organizations respond to this reality by trying to eliminate the gap, yet that is rarely possible. The goal is not to create a world where Operational Truth and System Truth are always identical, but to understand where the gaps exist – reducing the time between what people observe and what the system reflects.
The most effective organizations understand both realities. They respect the value of the system while remaining connected to the people closest to the work. The least effective organizations spend their time arguing about which version is correct.
The best organizations recognize that these truths are partners. Operational Truth explains what is happening, while System Truth preserves what happened.
You need both.
What Technology Should Really Do
This observation has shaped much of how I think about software. Good software records reality, but great software helps people understand reality. There is a difference.
A transaction may be accurate and still fail to communicate what matters. A dashboard may be technically correct and still miss the operational problem everyone on the shop floor already sees.
The opportunity is not simply to capture more data, but to reduce the distance between what people know and what systems know. The closer those two realities become, the better decisions an organization can make.
That is true for ERP systems, accounting systems, inventory systems, and even artificial intelligence.
AI may process information faster than any employee, but it still depends on the information it can see. If Operational Truth never reaches the system, AI inherits the same blind spots as every technology that came before it.
Final Observation
After all these years, I’ve found that the most valuable conversations rarely begin by asking what the system says. They begin by asking the people closest to the work what they know. The strongest organizations understand the difference between Operational Truth and System Truth and work every day to bring the two closer together.