Boeing right's a wrong: The flight attendant button
reuters.com
reuters.com
Now can I have a similar button in a restaurant? So I don't have to have my conversation interrupted by people coming by to ask me how dinner is going, and do I can get issues (like running out of water) addressed promptly.
Also, in the US I always felt slightly guilty calling a waiter over as if I'm calling him out on not doing his job. Here, if they don't have the doorbell thingy it's expected that you'll shout すみません! when you're ready to order.
The other major design issue with airplanes is putting the buttons on a remote and then jamming it into the armrest next to your butt so you can accidentally hit it when you're sleeping or shifting around. It's the airplane equivalent of pocket dialing.
"turn left and pick up credit card terminal. Then go to table 32." "say: 'how was your food today sir?'
Sounds fucking awful even if it does get you 10s faster service.
Of course once I read it, I started to wonder if I could code mana.
As for buttons, why not follow Larry David's lead and put a bell on every table?
Just last week I was sitting at a terrace located a little ways away from the restaurant itself. The waitress punched in our drink orders, but we stopped her from turning around and asked her about the specials. Our beers arrived before she finished describing them.
This place had one order-taker and one or two 'runners' who delivered and bussed. Increasing latency while taking orders isn't nice... but in this case it completely obliterated message delivery time (and a whole lot of legwork).
I bet quite a few websites and softwares have similar problems.
You've seen this in many average products, but I feel I have to insist that it is not due to design in general, but more due to the average designer lacking the talent to solve the two axis equation properly.
Also, even the more stable and mature aircraft designs get relatively frequent software updates, and there is a lot of software in aircraft these days. The interesting part is where the faster iteration process of software development meets the slower process of aircraft development. The software developers are constantly iterating just like you would expect them to, and then every so often spin off a version for release on the side. That release version goes through extensive testing (mostly regression testing to make sure nothing that used to work is now broken) before it ever makes it onto an aircraft. Usually a few fixes are required as well. While all of that is happening, there are still people working on the next version.
With a firmware update, this solution can even be retro-fitted to existing planes.
Some others have call and cancel buttons separately in either remote controls or armrest built controls.
And to turn the light on you could push the light itself.