When UI Design Flaws Can Be Fatal

On June 1, 2009, Air France flight 447 fell into the Atlantic Ocean, killing all 228 people on board. The proximate cause was pilot error: the co-pilot pulled back on the sidestick at exactly the wrong moment, stalling the aircraft at high altitude. But the deeper cause — the one that the official investigation struggled to name clearly — was a design failure.

The Airbus A330's fly-by-wire system uses a sidestick design in which the pilot's and co-pilot's inputs are independent: they do not move together, and there is no tactile feedback when one pilot is overriding the other. When the captain arrived on the flight deck and took hold of his sidestick, he could not tell that the co-pilot was simultaneously pulling back on his. Two inputs. One aircraft. No awareness. The plane stalled. Nobody understood why until it was too late.

The First Law of UI Design

I have proposed that there is a single overriding principle of good interface design: the Principle of Least Action. A good interface minimizes the cognitive and physical work required to accomplish any task. It presents information when it is needed, not before; hides it when it is not needed; and never requires the user to infer something that the system could simply tell them.

The sidestick design violated this principle catastrophically. It required pilots to infer what the other pilot was doing — something the system knew perfectly well and could have communicated instantly. The information existed. The design did not surface it.

Bad Design Is Everywhere

Most bad UI design doesn't kill people. But it costs money, frustrates users, and erodes trust in products that could otherwise be excellent. The pattern is the same whether you are looking at a cockpit or a smartphone app: the system knows something the user needs to know and fails to tell them; or it forces the user to take an action in order to find out something the system already has; or it presents choices in a way that makes the wrong choice easy and the right choice hard.

Google has made this mistake repeatedly. Microsoft has built a twenty-year empire of software that violates the Principle of Least Action at nearly every turn. These are not small failures. They represent billions of hours of lost human productivity, collective.

What Good Design Looks Like

Good design makes the user feel that the system is on their side. It anticipates what they need before they ask. It never punishes an innocent mistake with irreversible consequences. It surfaces the most important information prominently, and it makes the most dangerous actions the hardest to perform.

The lesson of AF447 is not just for aerospace engineers. Every designer who puts a destructive action one click away from a creative one, every developer who buries critical information in a menu, every product manager who approves a flow that could cause user error — they are all, in a small way, designing the conditions for a stall.