← All signals
2026.04 · Essay·Design·6 min read

Why operator tools should feel like instruments, not SaaS.

A pilot doesn't want a dashboard. A pilot wants an altimeter. Most software for operators has confused those two things for fifteen years.

I spent a long time watching field operators use software before I realized what they actually want it to be. They don't want a dashboard. They want an altimeter.

Dashboards assume you have the time to look around. An altimeter assumes you need one number, now, and that number had better be right. Almost all operator software is built as the former. Almost all operators would pay more for the latter.

What instruments actually are.

An instrument has three properties that almost no SaaS product has. The primary number is exactly where your eye lands first. The secondary numbers are available but never in front. And the whole thing reads correctly when you're distracted, tired, or out of context.

None of that is a design preference. It's a consequence of the environment. A cockpit has finite attention. A control room has finite attention. A Friday night at a busy hotel front desk has finite attention. The software that survives those environments is the software designed around attention scarcity, not feature richness.

The test I run.

Can the operator pull the one number they need in three seconds, on bad lighting, while someone is talking to them? If not, it's not an instrument yet.

Every product I've shipped for operators runs that test before anything else. Voltafy. Performance Tracker. Philly. If you can't pass the three-second rule, every other design decision is downstream of the wrong priority.

Why this matters commercially.

SaaS has trained an entire generation of builders to optimize for feature velocity. That's the right optimization for the tools people choose to use. It's the wrong optimization for the tools people are forced to use. Operators are forced to use their software. That changes what good means.

The business outcome, in my experience: when you stop trying to be a dashboard and start trying to be an instrument, adoption goes up and support tickets drop. Operators stop fighting the tool and start leaning on it. That's when revenue starts compounding from retained attention instead of churned trials.

— Juan Stefan Diaz
Work together
Next →
Every business is a construction project. Here's the five-phase build plan.
◉ Book a call
LiveAMS Grid stable2027 · dv1.0
◐ Sound off⌘K