Post Completion Errors and How to Avoid Them
A followup to our prior post…
Excerpt (via System Concept.com)
Post completion errors are a specific type of human error that is completely preventable, in most cases, if the product has been designed properly. For example, a simple, well timed beep from the photocopier reminding you to take the original out of the machine (once it had printed out the last copy), would save you the hassle of having to remember to take the original out of the copier. Post completion errors are systematic in nature and only occur sometimes. They tend to occur when tasks follow a sequence of actions in order to achieve their goal and when users have to perform a sub-task after the main goal has been achieved (i.e. when the goal achieving step is not the final step in the sequence).
In the above example, no catastrophes occurred, however post completion errors can occur anywhere and cannot be trained out. They also tend to be hard to predict, a nuisance and can make the entire experience of using a product negative. Therefore it is important that designers and evaluators of products make an effort to eliminate the occurrence of post completion errors as early in the design and evaluation cycle as possible.
It is possible to attempt to eliminate post completion errors. One strategy is for designers and evaluators to watch out for tasks that consist of a sequence of sub-tasks and ensure that the goal achieving step is the final task in the sequence. For example, obtaining copies from a photocopier can be divided into the following sub-tasks: place original in the copier, provide details of number of copies, properties of copies etc, press copy button, take original out of the copier and collect copies. The goal achieving task in this example is the ‘collect copies’ task. Therefore ensuring that this goal is achieved as the last task in the sequence eliminates the post completion error.