Holy dreck this fuigetry.
After letting Captain Deladier know what’s up with the giant asteroid looming spinning ever closer, Barcalow’s attention is grabbed by a screen immediately before him. It’s the collision alarm.
Prepare your eyes.
This is the interface equivalent of running around screaming in an Ed Wynn voice while flailing your arms over your head. Sure, it’s clear something’s wrong, but other than that, it’s not helping.
Sure, there’s the buzzing and the giant yellow, all-caps text that blinks COLLISION ALARM. There’s a pea green bar that seems to be indicating steadily decreasing distance or time or something that is running out. Those two are helpful. The rest of this information is a pile of nonsense.
- Blinking? If the pilot has seconds to act, isn’t there a risk that when he glances at the screen for a split second, that he’ll miss something?
- What’s with the blue waves rippling out from the representation of the ship? If it’s a collision, wouldn’t you expect something to be represented as coming toward the ship, and maybe a line describing its path, and a point illustrating point of impact?
- Why do all of the NV need to be labeled as such? Why do they need to blink randomly? How is that useful information?
- How do those numbers link to those labels? Isn’t that asking the navigator to do a lot of visual work in a crisis?
- What does it mean for the ESTIMATED MASS to be changing to zero and suddenly jump again? Because that would better fit a Cthulu alarm, as the physics of the Old World no longer applied. Stell’bsna n’ghft. Y’hah.
- What does it mean for the APPROXIMATE SPEED to start so low, rise to nearly 1000, and fall again? What outside force is acting on this mass? (Or is it a function of the mass changing? Anyone care to do the speculative math?)
- The DISTANCE TO OBJECT does in fact decrease like you might expect it to at the beginning. But then it drops to zero. Shouldn’t they be dieing instead? Oh, but then it jumps again.
- Why is time contained in a single number? Does the Federation use some Metric version of time?
- How can OBJECT TRAJECTORY be a single digit? It’s a multivariate concept.
- Why are there no units? As in, anywhere?
- How could OBJECT BEARING change to zero and then jump back up again just like ESTIMATED…
- …Are you kidding me?
And that’s when I went, frame by frame, and captured the data points. Here they are, visualized as a graph over time. Notice anything?
OK, let me just line those up for you.
I know sci-fi interfaces are often made under time pressure, but it really lets me down when they just copy and paste numbers. Like we won’t, many years later, analyze it frame-by-frame for a blog. Sheesh.
Urgency requires focus
Of course this is a narrative interface, meant to communicate to an audience in about a second that things are very very bad for the Rodger Young. Of course it’s rooted in a mechanical metaphor where dumb, fixed sensors with thresholds would go all calamity when things went pear-shaped.
We don’t live in that world anymore. Urgency requires focus, and when circumstances are dire, yes, the pilot needs to know the direness of the problem, but then they also need to focus on fixing that problem. Urgency interfaces should…
- Get attention, and once they have it ease up on the attention getting, since it becomes a distraction.
- Illustrate the problem, including time-until-anticipated.
- Illustrate what the computer is doing about it (if it’s agentive, which the Rodger Young is clearly not.)
- Illustrate the best options available and provide a means to enact those.
Note that the COLLISION ALERT does two and a half of those. It gets Barcalow’s attention, shows the problem with a label, and a green bar shows time remaining. That’s maybe a tenth of the screen. Then it tries its very, very best to distract the user from that useful information with blinking, semi-random nonsense. Was this thing designed by the bugs?