What Is Operator Experience? The UX Nobody Designs For

I have an unhealthy fixation on experience, for users, for customers, and most of all for the operators who actually run the business on top of the software we build. The first two get all the attention. The third is where companies quietly bleed out.

Operators are the support agents, the ops team, the finance analyst reconciling a report at 11pm, the implementation engineer onboarding a new client. They live inside the internal tools nobody bothered to design. And their experience compounds straight into your margins.

Why it gets ignored

Internal tools have no champion. They never show up in a demo, and the people who suffer from them rarely sit in the room where the roadmap gets decided. So the friction just builds up. People invent manual workarounds, keep a spreadsheet to bridge two systems that won't talk to each other, and hold the real process in their heads until they quit and it walks out the door with them. It's the same blindness I write about in running support as one system: internal friction never gets a ticket, so it never gets fixed.

What changes when you care

• Support resolves issues in minutes instead of escalating to engineering.
• Onboarding a new customer stops requiring a heroic effort.
• Headcount scales sub-linearly with revenue, the whole point of software.
• Key-person risk drops because the process lives in the tool, not in someone's head.

When you treat operators as first-class users, the business gets cheaper to run as it grows. When you don't, every new customer costs you a little more than the one before, and at some point the growth isn't worth what you're paying for it. Starting from the experience, including the one nobody demos, is baked into how I work. So I obsess over the operator. Someone has to. If your ops team is drowning in workarounds, let's talk →