5 Guidelines for Ergonomic Observation

In my work in medical product ergonomics (as well as other areas of product design), I frequently encounter product teams who are applying field observation in their product development processes.  This is great, but much of the time, the teams lack the skills for conducting effective observations.  Actually, not so much the lack of skills, but a lack of structure to guide what to observe and how to document observations.  This lack of structure typically results in two types of patterns of observation notes:

1. Write everything - In this case observers write down every event in an ultimately futile effort to document the entire task flow, procedure, etc. This is the professional version of those students from high school who write down everything the teacher writes, even if they don't know what it means. I always loved it when the teacher would write something on the blackboard and then quickly erase it, leaving these human Xerox machines bewildered.
2. Write what's interesting- The more common approach is to document events or ideas that are out of the ordinary or unusual as they contribute above and beyond the observer's current knowledge base. This is certainly a more manageable approach, but is highly variable due individual observer's thresholds for what is "interesting".

How do you overcome these note-taking habits?  When I provide training on "Minimally Invasive User Research", I emphasize a team-based approach where multiple observers take on distinct, but overlapping roles.  For example, one observer may track high-level task flows while another focuses on the detail interactions between a user and a medical instrument.  But even when attention is focused to a particular set of user interactions, one can fall back in the write everything/write what's interesting habit.

An effective way to break away from those observational note-taking traps is to use guidelines.  Guidelines fall between having no structure and an overly-constrained template, by giving a set of elements to pay attention to, but the flexibility to document them as the observer sees fit. 

For example, in the case of observing a medical instrument interaction, I created the guideline of FoRCePS.  Forceps are a common medical instrument, making the term a memorable acronym for medical product designers.  The acronym represents five ergonomic areas to consider during observations, and is a loosely-based expansion of Stephen Pheasant's cardinal rules of anthropometrics.   The guidelines are:

• Feedback - Identify where the user's access to sensory feedback (e.g. visual, tactile) is compromised
• Reach - Identify situations where the user's major limbs (arms, legs) and minor limbs (fingers) must over-extend in order to carry-out a task
• Clearance - Identify situations where the user's major limbs (arms, legs) and minor limbs (fingers) must function within a limited space, such as finger holes or a handle
• Posture - Identify situations where the user's overall body posture is deviated from neutral position, as well as deviations at key joints (e.g. shoulder, wrist)
• Strength - Identify situations where the user must apply excessive or prolonged force for movement or stability, relative to their strength capabilities

Observers are encouraged to consider each of these guidelines individually for both macro and mico ergonomic issues, but also to understand how they interact with each other. For example, if there is limited visual access, compromising feedback, then a user may change his or her body and limb postures to accommodatean improved field-of-view, but in doing so, increase the extent of reach and reduce the effective  transfer strength.  I recommend watching a brief segment of a medical procedure (or other task where ergonomic compromises are common) to practice paying attention to these 5 issues.

So even with a set of five key principles, there's a lot to pay attention to during live observations and in follow-up video review.  Fortunately, FoRCePS and similar mental "tools" give an observer guidance and provide a consistent way to track issues that can be shared with other observers who are focusing on different aspects of the observed task.