The Interface I'm Proudest Of Runs a Dispatch Desk. You'll Never See It in a Portfolio.
The interface I'm proudest of runs a dispatch desk.
You will never see it in a design portfolio.
It isn't beautiful. It's a dense screen a dispatcher works all day. Orders coming in, stock on hand, what's picked, what's loaded, which truck leaves when.
Every minute on that screen is money
Get it wrong and the wrong order goes on the wrong truck. Or a truck sits at the dock while everyone scrambles. Every minute of that is money, and the people using it know exactly whose.
That's the part that changes how you design. When a mistake shows up as a truck idling at a loading dock with a driver on the clock, aesthetics stop being the point. The screen has one job: help a person under pressure make the right call faster than they could without it. It's a $64 million lesson the people who built Australia's bus ticketing app learned in public. Operational software fails operationally, not visually.
It's also why founders who hire a designer to make the product look good are usually solving the wrong problem. Nobody at that dispatch desk cares whether the screen is pretty. They care whether the trucks leave on time.
Consumer apps are designed for the first five minutes
The demo. The first impression. Delight. The whole discipline of consumer product design is optimised for the moment someone opens the thing for the first time and decides whether to keep it.
That's a real skill, and it's the one the industry trains for. Sora nailed the first five minutes and had nothing underneath, so a million people downloaded it and then never came back. First impressions get you the download. They don't get you the ten-thousandth hour.
This was designed for the ten-thousandth hour
The dispatcher isn't a first-time user having a magical onboarding experience. They're an expert. Fast, under pressure, running the same task a thousand times a shift. They stopped needing hand-holding on day two. By day two hundred, every extra click is a tax they pay hundreds of times a shift.
So there's no room for decoration. Every element on that screen either helps someone make a faster decision or it's noise. And noise, on a screen like that, isn't just ugly. It slows the whole operation down. A gentler version of the same rule holds everywhere: the job is deciding what should exist and what shouldn't. On a dispatch desk, that decision gets measured in idle trucks.
Designing for the expert is the opposite instinct to designing for the demo. You strip, you tighten, you make the common path invisible-fast and the rare path merely possible. It's harder, it pays better, and it's the work most designers won't go near, which is exactly why I do it.
Our industry rewards the screenshot
The hero shot. The launch-day reveal. The portfolio grid where every project is one gorgeous still frame.
None of the work that actually matters photographs well. A dispatch desk running smoothly looks like a boring, dense screen. You can't capture "the trucks left on time for three years straight" in a 1200-pixel-wide image, so nobody puts it on Dribbble, so the whole field quietly agrees it doesn't count. The best design work rarely wins awards for exactly this reason. The award goes to the thing that looks impressive in a screenshot. The impact lives in the thing that doesn't.
The best operational design disappears
Nobody notices it, because the trucks leave on time.
That's the whole measure. Not applause, not a case study, not a screenshot. Just an operation that runs a little smoother than it did before, worked by people who will never think about the interface again because it stopped getting in their way. The design succeeded by becoming invisible.
That is the opposite of a portfolio piece. It's also the hardest thing I do. Anyone can make a screen that photographs well for the reveal. Making one a tired expert can trust at hour ten thousand, on a bad day, with money on every minute, is a different craft entirely. It just doesn't have a hero shot.
---
