They have data. They have systems. But they don't have a model of how their operations actually work. Not how systems are configured, but how processes connect, how decisions cascade, and how outcomes are produced.
Ask any supply chain leader whether their organisation is "data-driven" and the answer will almost always be yes. They have ERPs, WMS platforms, TMS tools, BI suites, and analytics teams. Data flows through every corner of the operation.
Now ask a different question: "Do you have a model, a structured, shared representation, of how your operations actually work?"
The answer, in most cases, is no.
The difference between having data and having a data model. Between recording what happened and understanding the structure of how things work. Between tables in a database and a representation of operational reality.
Most organisations have digitised their operations without actually modeling them. They've captured the symptoms of how work happens without understanding the system that produces those symptoms.
In the absence of a real operational model, organisations default to KPIs as their primary lens on performance. KPIs are summary statistics. They compress complex, multi-variable processes into single numbers: on-time delivery, cost per unit, fill rate, throughput per labour hour.
These numbers are useful for reporting and benchmarking. They are terrible at understanding what's actually happening.
When organisations manage by KPIs alone, they end up optimising the metric rather than the process. A pattern that reliably produces gaming, misalignment, and unintended consequences.
Most organisations I've worked with have spent millions digitising their operations. They have dashboards, data lakes, BI teams. What they don't have is a shared, structural understanding of how those operations actually produce outcomes. That's the gap. And it's the most expensive gap they're not measuring.
An operational data model is not an entity-relationship diagram. It's not a data dictionary. It's a structured representation of how an operation works: its processes, its constraints, its dependencies, and its decision points.
At its core, an operational model captures three things:
Process structure: How work flows through the operation. Not just what steps exist, but how they connect, what triggers them, what constrains them, and how they interact across functional boundaries.
Operational context: The constraints, policies, and conditions that shape how processes behave. Carrier cutoff times. Labor availability by shift. Storage capacity limits. Seasonal demand patterns.
Causal relationships: How events in one part of the operation affect outcomes in another. An inbound delay doesn't just affect receiving. It affects putaway, pick path availability, outbound staging, carrier loading, and delivery.
