Please enable JavaScript.
Coggle requires JavaScript to display documents.
Human Error? No, Bad Design
Norman Chapter 5 (Main Ideas (Design for…
Human Error? No, Bad Design
Norman Chapter 5
Main Ideas
Why errors occur
-
-
attitude of people toward errors: blame&punish, blame&train
-
-
-
-
Quotes
In this paragraph Norman is speaking about the automation of tasks, but that people are then required to sit back and watch. Design should instead take advantage of those things that humans do really well and have the systems support those things that they do not.
"Difficulties arise when we do not think of people and machines as collaborative systems, but assign whatever tasks can be automated to the machines and leave the rest to people." (Norman p 215)
Reflection
Even though this is very 'widget' based, as an Application Designer, this chapter really hit home for me
Often the designer is obtaining requirements from management and not being able to consult the people who actually do the job.
Norman speaks about competing requirements, but I think he glosses over it too quickly.
It is amazing the extent and level of 'creativity' that people will employ in order to get around a system constraint.
Totally agree with the quote from the standpoint that we are often asked to automate a broken business process - and all you get is a slightly faster broken process.
Analysis
Norman categorizes errors, types of errors and the subcategories of slips and mistakes. He then offers design guidelines to mitigate errors from occuring