Nobody Changed the Master Data

Every week, the planner changed the same field.

Every week.

“Why?”

“The system value is wrong.”

“Why don't we change it?”

“We've always corrected it manually.”

Nobody knew who owned the master data.

So the workaround continued.

For three years.

The Problem

Bad master data often survives because good employees compensate for it.

They know the supplier lead time is wrong.

They know the machine rate is unrealistic.

They know the customer address changed.

They know which account code should actually be used.

So they correct it manually.

Again.

And again.

The Explanation

A workaround can hide a data problem.

Operations still functions.

Management sees no major failure.

The underlying record remains wrong.

That means every new employee, system or automated process encounters the same bad information.

Humans learned to ignore it.

Machines won't necessarily know they should.

Practical Example

A machine's standard production rate is recorded as 120 units per hour.

Operators know the realistic rate is 90.

Planners manually compensate when scheduling.

Then a new scheduling engine uses the master data directly.

Suddenly every plan assumes 120.

Cause → incorrect master data was never corrected because experienced employees worked around it.

Consequence → automation exposes and amplifies the hidden error.

Lesson → recurring manual correction is evidence of a broken foundation.

AxTrace Perspective

Repeated overrides are useful signals.

What value keeps getting changed?

Who changes it?

How often?

Why?

Instead of treating each override as an isolated event, traceability can reveal the pattern.

Sometimes the best process improvement isn't another automation.

It's fixing the source.

Key Takeaway

If people keep correcting the same thing, stop improving the workaround.

Fix the thing.

FAQ

1. What is master data?

Master data is relatively stable information used repeatedly across operations, such as products, suppliers, machines, customers or account codes.

2. Why does incorrect master data survive?

Experienced employees often learn to compensate for errors manually, preventing the underlying problem from becoming obvious.

3. Why is bad master data especially risky for automation?

Automated systems may use the recorded value directly without knowing the informal corrections employees normally make.

4. How can organisations identify master data problems?

Look for repeated overrides, corrections and exceptions involving the same fields or records.