DESIGN 5 min read

Designing interfaces for expert operators

Consumer software optimizes for the first five minutes: onboarding flows, tooltips, generous whitespace, big friendly buttons. Expert operational software is used for thousands of hours by the same small set of people. Optimizing for day one actively hurts day two hundred.

We design for density over discovery. Keyboard-first interaction. Fewer confirmation dialogs, because the user already knows what they're doing. Information laid out so an experienced eye can scan it in under a second, even if it looks intimidating to a first-time visitor.

This is a deliberate trade-off, and it's one reason our interfaces read as 'terminal-like' or technical. That aesthetic isn't nostalgia — it's a signal to the user that the tool respects their expertise and won't waste their time re-explaining itself on every screen, the same 'calm software' principle behind our design philosophy.

More from the Log

  • The case for calm software

    Most operational tools compete for attention. We think the opposite is the better design constraint — and it changes how you build with AI.

  • Applied AI is not a chatbot

    Chat interfaces are the easiest way to ship AI, and often the wrong one. Here's how we think about where a model belongs in a workflow.