The Layers – MRO

There’s a moment in every long project when you realize you’ve stopped building what you set out to build.
We started helping companies clean their MRO data. Duplicate part numbers. Inconsistent descriptions. The usual mess that accumulates when procurement systems grow organically across decades and acquisitions.
We were good at it. We built tools. We refined processes. We delivered clean data.
And then we watched it get dirty again.

“We tried the governance route. It didn’t stick.”
I’ve heard this from more MRO leaders than I can count.
They invested in MDM. Built taxonomies. Defined standards. Trained users. Hired data stewards. Stood up governance councils.
Two years later, the data is dirty again.
So they conclude: maybe clean data isn’t realistic for operations. Maybe “good enough” means living with a certain level of mess.
That conclusion is understandable. It’s also wrong.

The builder who asks “why” isn’t a new invention.
Leonardo was one. The cathedral masters were. The architects of Uber’s orchestration layer are.
What’s new is the stakes.
When platforms become infrastructure for entire economies — when your architecture determines what’s possible for millions of people you’ll never meet — the “why” extends beyond anything you can see.
This is building at a different scale. Not just products. Not just platforms. Possibility infrastructure.