In today’s post, Aza Raskin explicates on the Poka-Yoke and how it can be effectively applied to user interfaces.
Be sure to read our other interviews in our leadership series.
We lean fans spend a lot of time explaining how great Toyota is. And great they are. See what I mean? We can’t help ourselves. Anyhow, I am interested in your thoughts related to the way Toyota deals with interfaces, etc. I personally have two Toyota vehicles in my driveway and love them. But I was recently in my brother in laws new Camry and noticed they made some rather big changes to the way things looked and felt inside. I dare say things looked a little un-Toyota-like.
A simple and effective concept from Toyota is Poka-Yoke, or mistake-proofing. Products and Interfaces are context-sensitive ” that is, products and interface features have a particular purpose , but I’m curious if you can share any generic context-agnostic approaches to mistake-proofing, or Poka-Yoke? Principles of Poka-Yoke you can apply to anything; to any product or interface?
An interface is humane if it is responsive to human needs and considerate of human frailties. We make mistakes. No matter how hard we try to concentrate and prevent errors, errors will happen when our concentration wanes or when we are forced to do something that is beyond our cognitive abilities like multi-tasking: the act of consciously thinking about two things at once — and, with the use of Queueing Theory & Little’s Law, we learn that multi-tasking leads to lower productivity.
Poka-Yoke is an excellent method of making a process more efficient and humane by being considerate of human frailties: we won’t always be thinking about which way a part fits in, so design the part in a antisymmetric way so that it can only be installed correctly.
Shigeo Shingo wrote “Defects arise because errors are made; the two have a cause-and-effect relationship…yet errors will not turn into defects if feedback and action take place at the error stage”. In other words, users make mistakes, but those mistakes are detrimental only if they aren’t corrected immediately. One context-agnostic principle of humane interface design is summed up in the mantra “Never Use a Warning When You Mean Undo”. If you make a mistake, no big deal. Just undo it.
For example, a common Poka-Yoke style method is to cover an important switch so that it cannot be bumped accidentally. But, what happens if you use that switch all the time? You’ll either leave the cover open or flick-the-cover-open-and-flip-the-switch as a single gesture. In the computer world, we often have the advantage over the real-world in being able to undo. So that even though you just ran the smash-the-car-into-the-wall safety test while the technician was inside, you can just go back to the way it was before.
If Poka-Yoke was practiced more in interface design our lives on the computer would be a lot less stressful.
Other articles in the “Ask Aza Raskin” Series:
- Aza Raskin discusses the infinite scroll approach to Google search results.
- Aza Raskin shares his thoughts on Feature Bloat (aka, Featuritis)
- Aza Raskin describes the concept of Quasimodal Design.
- Aza Raskin explains the role of Poka Yoke in the User Experience