After six years of running the same interface, we shipped a significant UI refresh to production. The engineering went smoothly. Clean diff, all tests passed, signed-in sessions carried over correctly. We were confident.
Within five hours, the reviews started coming in. Within an hour of that, we had reverted.
What the Operators Found
Small things, by our measure. A button that used to be in one place was now in another. A menu label had changed. The flow to log downtime was technically simpler, but different from what six years of muscle memory had trained.
For us, the interface was cleaner. For operators who had run the same workflow 500 times a day for years, the same interface was suddenly unfamiliar. In a factory environment, unfamiliar means slow, and slow means production at risk.
This is the part we didn't account for.
What We Got Right
The engineering was solid. Sessions persisted correctly. The new skeleton loading made the interface feel faster. The date filter gave operators a faster path to yesterday's data. Error states were handled more gracefully.
On paper, it was an improvement. In practice, familiarity is its own kind of reliability.
What We'd Do Differently
Get operators in the room before the first line of code. We had a clear mental model of what the new interface should look like. We didn't validate that model with the people who would actually use it every day. That's the single biggest gap.
Change fewer things at once. We refreshed the entire dashboard in one release. A phased rollout would have let us catch the friction earlier and adapt before the full fleet was exposed.
Acknowledge the cost of familiarity. Engineers think in terms of capability: does this do what it needs to do? Operators think in terms of fluency: can I do it without thinking? Both matter. We optimized for the wrong one.
The Engineering Wasn't the Problem
The refresh itself was technically sound. The real lesson is that in B2B software serving operators on a factory floor, the people who build the product and the people who use it every day have very different relationships with the interface. A button that takes 300ms to render is an engineering metric. A button that's in the wrong place is a daily frustration repeated hundreds of times per shift.
We reverted within an hour of the first reports. The next refresh will be staged, validated with operators, and trained before it ships.