The Renamed Column
The word on the screen is either the word your team already uses, or it's friction — every single time anyone looks at it.
A feature request came in a while back that was easy to underestimate. An operator wanted a single column renamed, because the label CounterCtrl used didn't match what their team called that figure internally.
It would have been reasonable to deprioritize. It's a cosmetic change, not a new capability. We shipped it that cycle anyway.
Here's the reasoning behind that call. The word on a screen is either the word a team already uses every day, or it's a small tax paid every single time someone looks at that screen — a half-second of translation between what they see and what they mean. Multiply that half-second across a few hundred views a week, across a few dozen stores, and "a small thing" stops being small. It becomes a constant, low-grade friction that never shows up in a bug report but shapes whether people trust and actually use the tool in front of them.
This is part of why "Customer First" functions as an operating principle for us rather than a slogan. It doesn't mean every request gets built exactly as asked — plenty don't, for good reasons. It means a request like a renamed column, which costs us little and removes real friction for the people using the product every day, gets treated as a real request rather than a nuisance to be triaged away.
Most of what makes software feel considered to use isn't one clever feature. It's a long accumulation of decisions like this one — small, individually unremarkable, and collectively the difference between a tool a team tolerates and one they actually trust.