Identifying potential use errors
When working with usability engineering and interface design, a very effective and systematic way to help you identify potential use errors is to use the ‘PCA analysis’. The PCA analysis breaks down each use step into three components: Perception, Cognition, and Action, hence the name PCA.
Breaking each task step of the users interaction with the devise down to these three components help you understand what each task requires from the user.
A use error or difficulty is likely to occur if the user is unable to meet one of these task requirements related to perception, cognition and action. In this way, the PCA analysis, can be a very usefull tool to help you identify use errors related to hazardous situations.
User-device interaction model
We have now looked at how steps in user tasks can be broken down to Perception, Cognition, and Action. The PCA analysis is derived from the above model of user-device interaction. The model illustrates a user interacting with a device through a user interface. The user gives input to the device (e.g. presses a button), which the device processes to provide an output back to the user through the device user interface.
The user shall be able to perceive this output from the device, understand what to do with the output and act accordingly. This model can be applied to consider sources of potential use errors or hazardous situations caused by the device output. Note that we differentiate between:
- hazardous situations caused by a response of the medical device and
- hazardous situations caused by a user action or lack of action based on information obtained from the medical device.
PCA analysis provides valuable input to the user interface design
We have introduced the PCA analysis and the user-device interaction model. Let’s consider a simple example of how to apply the PCA analysis in order to both (1) identify potential use errors and (2) identify design input requirements:
|Task step||P/C/A component||Use error||Consequence||Design input requirement|
|Power on device||Perception – detect ON/OFF button||The user cannot detect the button||Device is not powered on.||ON/OFF button shall be backlit|
|Cognition – understand that pressing the ON/OFF button powers on the device||The user does not understand that pressing the ON/OFF button powers on the device||ON/OFF button shall use standard icon according to IEC 60417-5009|
|Action – apply pressure to depress the ON/OFF button||The user is unable to apply enough pressure to depress the button||The force required to activate the ON/OFF button shall be between 3.1 – 22.2 N (0.7 – 5 pounds) .|
Jon Storm Madsen
Partner / Head of Usability Engineering