Ask five people in the same plant what value an MES should deliver, and you’ll often get five different answers. None of them are wrong. But when nobody agrees on what “delivering” looks like, the system can never clearly deliver it.
One System, Many Definitions
For some plant managers, value means OEE moving up by five points. For others, it’s a quality escape that never reached a customer. For others still, it’s answering a traceability query in three minutes instead of three days.
The problem starts when the customer success team, IT, operations, and plant leadership each carry a different definition into the project. IT measures uptime and integration health. Operations measures throughput. Leadership measures payback. Each group can point to evidence that the system is, or isn’t, working, and the debate never resolves because the scoreboard was never agreed.
The Question That Comes First
One of the first things we do with a new customer is sit down with the people who matter and ask a simple question: what would have to be true for you to say this system is working?
Not features. Not dashboards. Not uptime. What would have to change on the shop floor, in the numbers, and in the weekly meeting? The answers are usually more concrete than people expect: fewer hours spent assembling reports, faster containment when a defect appears, schedule adherence that a customer can actually feel.
Making the Definition Stick
Once value is defined, it needs to be written down, owned, and reviewed. A shared definition turns into a baseline, a target, and a date to check progress. It also gives everyone a common language when priorities shift, which they always do.
Define value before you measure it. Otherwise, you’ll spend the next 18 months arguing about whether you got it.




