6 ms·
Wait, so all of the hand wringing over the crappy UI was pointless because it was actually a case of miscommunication?
by jandrese 9y ago
Wait, so all of the hand wringing over the crappy UI was pointless because it was actually a case of miscommunication?
- blueish 9y agoI wouldn't call it hand wringing, as I think all the points were valid, but yes, the employee sent out the message he intended to (the real alert over the test alert).
- krapp 9y agoNo, according to the end of the posted article, poor UI and a lack of necessary safeguards were part of the problem, just not the entire problem.
- rhino369 9y agoI don't really understand how it is part of the problem. If the worker really believed an attack was incoming, confirmation screens wouldn't help at all.
- bearcobra 9y agoI guess it would depend on how that confirmation screen worked. If the design asked for a confirmation from a second user, then a single user's confusion wouldn't have resulted in the error.
- jeddawson 9y agoNot only that, but once they realized the message was sent in error they didn't have a simple way to correct course so there was a big delay between the realization and informing the terrified public. Your suggestion of having multiple user confirmations coupled with a simple way to "cancel and correct" the notice would have likely meant this never became news worthy.
- paulddraper 9y agoSure, but that's a lot different from "move these buttons around and have the user double click to be sure."
- jsjohnst 9y agoThe extra confirmation shouldn’t have been on the same user. The “two man rule” exists for emergency protocols for a reason.
- krapp 9y agoConfirmation screens might have given the operator a moment's pause to consider whether or not they were certain. A UI that makes it easy to make a mistake, even when the mistake is intended, and makes it almost impossible to correct that mistake, is a badly designed UI.
- dragonwriter 9y ago> Confirmation screens might have given the operator a moment's pause to consider whether or not they were certain. There was a confirmation screen. I have seen no suggestion how a different confirmation than actually existed would have helped, and I don't think we want to introduce more delay in the critical path of a live alert without clear and massive benefit. > A UI that makes it easy to make a mistake, even when the mistake is intended, and makes it almost impossible to correct that mistake, is a badly designed UI. The problem with correcting the mistake is not a UI problem, but a deeper planning and procedure problem.
- krapp 9y ago> and I don't think we want to introduce more delay in the critical path of a live alert without clear and massive benefit. If that delay reduces false alarms, when false alarms erode public trust in and concern about the alert system, then the massive benefit is clear. With such a system, drills and tests are going to be massively more common than actual events. Designing the UI so that the one-in-a-million option is as easy to invoke as the once-every-week option is a UI problem. Notwithstanding it not being a primary issue in this particular case, I believe it's still an issue worth discussing. Also, bear in mind that correcting the "deeper planning and procedural problems" would introduce delays as well. Anything but a purely automated system, or a big red button would introduce some delay.
- dragonwriter 9y ago> Also, bear in mind that correcting the "deeper planning and procedural problems" would introduce delays as well No, it wouldn't, because those are problems that impact after an alert is issued, and whose existence caused delays in sending an all-clear. Resolving them won't effect the path prior to an alert, and would eliminate rather than introduce delays.
- lsaferite 9y agoHow would a UI change have made the outcome different if the employee actually wanted to send a real alert?
- hinkley 9y agoWhen you're doing a post-mortem you're supposed to think about how to prevent the next one, not how to prevent the one that already happened (someone needs to tell the State Dept this). So you look at all of the contributing factors and you come up with a plan for all the ones you can reasonably address. It's been identified that a reasonable person could accidentally send a real alert even when they intended to send a fake one. So you fix that too because why the hell would you leave it once you've found it? Or to put it another way, they're already in the middle of a PR disaster. You get a second one if the press gets wind of the idea that you're cutting stupid simple corners on the remediation. And make no mistake: Fixing a UI issue with the benefit of hindsight is a stupid simple fix (avoiding it to begin with is much harder).
- Johnny555 9y agoThis is a solved problem -- the UI could require confirmation from a second employee.
- askvictor 9y agoYou have minutes before the missiles hit. Waiting around for Steve to get back from the toilet could cost a lot of lives.
- Johnny555 9y agoLike I said, the 2-man rule is a solved problem. https://en.wikipedia.org/wiki/Two-man_rule https://en.wikipedia.org/wiki/Two-man_rule What does Bob do when he goes to the toilet? He asks Steve to cover him. So if you need 2 people to send an alert, when Bob is at the console, and Steve is secondary, when Steve has to go to the toilet, he asks Jill to cover him. Alternatively a backup authorization method could be used. It does mean having 3 people available at all times, but since there are life-safety implications of real alerts as well as false alerts, it seems like a reasonable safeguard to have.
- nkoren 9y agoActually, it's even more crappy UI, just not in the visual domain. Including the phrase "this is not a drill" in something that actually is a drill could be considered a design flaw in the auditory user interface.
- ollerac 9y agoPedants, all of you.
- Cyberdog 9y agoHello. Welcome to Hacker News. Enjoy your visit!
- deleted 9y ago[deleted]
- Cyberdog 9y agoWas that addressed to me? I certainly wasn't attempting to diss the community at large. Yes, sometimes the pedantry and "um actually" nature of this place bugs me, but that's just what happens in gatherings of nerds.
- dang 9y agoOK, I overinterpreted you and will delete my comment. Sorry! (It was still an unsubstantive post though... please don't post those, even when someone else is setting a bad example.)
- deleted 9y ago[deleted]
- dang 9y agoI know how annoying it can be to run across internet comments that seem insufferably pedantic. But would you please not post unsubstantive comments to Hacker News? As much of a problem as pedantry is, empty, name-calling comments are much worse. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- jeddawson 9y agoSure sounds like it! What is confusing is that the article still points to the UI as being a part of the problem though while they're now saying the employee intentionally sent the live message. Looks like the PR campaign is still trying to deflect blame or perhaps keep things just ambiguous enough that they'll be able to rush through some extra spending to "fix" the UI issue. Hopefully more details will continue being shared and they deal with the organizational flaws instead of pouring blame on scape goats (software and individuals).
- rossdavidh 9y agoOr, there were a bunch of potential land-mines set in this process, and eventually the employee stepped on one. Which one he stepped on is maybe less interesting to me, than the fact of the organizational culture producing multiple ones to step on.
- turc1656 9y agoYup. I called bullshit on the story we were being fed at the time (https://news.ycombinator.com/item?id=16161584 https://news.ycombinator.com/item?id=16161584) and said it seemed obvious when you think about it that they really believed they were under attack, and I'm glad to see the truth finally come out. The bad UI argument could still be valid, but it definitely was not the cause of this.
- MicroBerto 9y agoSame here, and I was called a reptilian flat eaether or something to that effect. I'll never be shamed out of questioning clear nonsense.
- davesque 9y agoWell, we've seen the UI and it is crappy and it's not hard imagine someone making a mistake that way. But yeah you're kinda right. They should still fix the UI though :/.
- emodendroket 9y agoYou can't blame people for making inferences based on the news that was reported.
- make3 9y agoI mean, I fully suspect that both suck
- MicroBerto 9y agoNo. They are getting tripped up in their numerous lies. Last time this happened, the story simply disappeared from the media altogether. Expect that to happen here too.