Software designed at a desk fails at 60 mph in the dark.
Robert Grand · Battalion Chief who still runs calls
Two nights ago I caught a run out on the south end of the district. Warm night, open roads, the kind of drive where the training takes the wheel and you settle into the seat. The buggy knows the way. I know the way. Twenty-four years builds that into you, and there’s a quiet confidence in it that never gets old.
Then the iPad lit the whole cab like a road flare.
Code 3, dark two-lane, and the brightest thing in the truck was the screen that’s supposed to help me. Nothing dramatic about the run. It was a normal nighttime call, the kind we make all the time. That’s exactly the point. I can dim it. Of course I can dim it. Buried a couple taps deep, eyes off the road, at the moment my attention belongs on the windshield. So I drove with a spotlight in my peripheral, because the software gave me no fast way to tell it that it was nighttime and I was moving.
And it does that every single night. Not on the dramatic call, the ordinary one. That’s the moment I stopped being annoyed and started being certain about what to build.
The Screen Owns Your Eyes, Or The Road Does
Here’s the thing nobody in an office has to think about. In the cab, the screen is competing with the road for the one resource I cannot split: my eyes. And this isn’t the rare bad night. It’s every night shift, every dark run, the plain routine of the job.
A day and night mode should be one tap. Not a settings menu. Not a brightness slider I have to hunt for while the truck is doing sixty. One tap, or better yet, the tool should already know. It knows the time. It knows the truck is rolling. It knows I hit the lights and siren. Every one of those signals says the same thing: dim down, calm the colors, give the driver back the windshield.
That’s not a feature request. That’s an admission of who the user actually is. The office lens assumes the screen owns your attention because in an office, it does. In the cab, the road owns your eyes, and any tool that forgets that is fighting you for the windshield on the most ordinary run of the week.
The Dead Zone Is Where You Need It Most
It got better. Or worse, depending on how you look at it.
Out past the edge of the district, the cell coverage went to almost nothing. Anyone who runs calls in a big or rural response area knows the map: whole pockets where the bars drop and the little spinner just turns. And right there, furthest from the station, furthest from backup, deepest into the part of the district I know least, the software started to stall.
No offline mode. The tool that’s supposed to carry the address, the hazards, the preplan, the history, quietly becomes a blank screen exactly where I need it to be sharpest.
Think about what that means. The software is most reliable parked in the bay on strong Wi-Fi, and least reliable at the far edge of a bad night with no coverage. It has the confidence backward. It works best where the stakes are lowest and folds where the stakes are highest. That’s the signature of a tool designed by people who have never watched the bars disappear on the way to a working call.
The fix is not exotic. Cache what matters. Sync when you can, run when you can’t, and never make the crew’s access to critical information depend on a tower that was never built out here. Offline is not an edge case in this service. Offline is Tuesday.
The Office Lens
I kept coming back to the same conclusion the rest of the drive. The people who built what I was fighting with are good at their jobs. They’re just doing their jobs in a completely different world than the one I do mine in.
They design at a desk, on a stable connection, in good light, sitting still, with two free hands and their full attention on the screen. So the software they build assumes a user who is stationary, connected, well-lit, and staring right at it. Every default quietly encodes those four assumptions.
Now put that software in my cab. Moving. No signal. Dark. One hand, gloves on, half my attention on a scene I’m about to walk into. Every single one of those assumptions is false at the same time, on the exact call the tool exists to support.
That’s the office lens. It’s not incompetence and it’s not laziness. It’s distance. You cannot design for a seat you’ve never sat in, on a night you’ve never worked, in a district you’ve never gotten lost in. The gap between the desk and the fireground is not a gap in effort. It’s a gap in experience, and no amount of user research survey closes it.
The Seat Is The Spec
So the standard is the other thing. Software designed from the seat out, not the desk in.
The starting question isn’t “what features do we want.” It’s “what is true on the worst night of the job, and what does the tool owe the crew in that moment.” That single question reorders everything. Day and night mode stops being a checkbox and becomes a reflex the software has, because the worst night is dark and moving. Offline stops being a roadmap item for next year and becomes the foundation, because the worst night has no signal. Glanceable, one-handed, gloved, because the worst night gives you one hand and two seconds.
That standard doesn’t come from a survey. That’s the tell with most of this software: it was researched, not lived. I was driving to the call. I’m the medic in the parking lot and the officer in the right seat and the one who signs off on the tool and then has to use it at three in the morning. The seat is not my research. It’s my job.
It’s simple enough to test against any screen a first responder is handed. Does this help the crew on the worst night, or only impress somebody on the best day? If it only works in the demo, in the bay, on strong Wi-Fi, sitting still, it isn’t done. It’s just pretty.
The fire service has spent a long time adapting itself to software built for someone else’s world. Dimming the screen by hand at code 3. Working around the dead zone. Learning the tool’s assumptions instead of the tool learning ours. That era is ending, and it’s ending because a few of us who actually run the calls stopped waiting for permission and started building.
The desk will always build for the desk. The seat has to build for the seat. I know which one I’m sitting in.
Robert Grand is a Battalion Chief at Eugene Springfield Fire with 24 years of service. He writes Frontline Intelligence, a newsletter on operational doctrine, technology, and leadership in Fire & EMS.
If this landed, share it with someone in Fire & EMS who needs to hear it.
Subscribe
From the floor, not the vendor booth. Two times a week.