A Review of the Event Analysis of Systemic Teamwork Methodology

HFIDTC/WP1.1.3/10
Version 2/ 31 October 2005
3.2 Observation
Background and applications
Observational techniques are used to gather data regarding the physical and verbal
aspects of a particular task or scenario. Observational techniques are used to collect data
regarding various aspects of system and task performance, such as data regarding the
tasks catered for by the system, the individuals performing the tasks, the tasks themselves
(task steps and sequence), errors made, communications between individuals, the
technology used by the system in conducting the tasks (controls, displays, communication
technology etc), the system environment and the organisational environment.
Observation has been extensively used in the HF community, and typically forms the
beginning of an analysis effort.
Domain of application
Generic.
Procedure and advice
Step 1: Define the objective of the analysis
The first step in observational analysis involves defining the aims and objectives of the
observation. This should include determining which product or system is under analysis,
which environment the observation will take place, which user groups will be observed,
what type of scenario’s will be observed and what data is required. Each point should be
clearly defined and stated before the process continues.
Step 2: Define the scenario(s)
Once the aims and objectives of the analysis are clearly defined, the scenario(s) to be
observed should be defined and described further. For example, when conducting an
observational analysis of control room operation, which type of scenario is required
should be clearly defined. Is normal operation under scrutiny or is the analysis focussed
upon operator interaction and performance under emergency situations. The exact nature
of the required scenario(s) should be clearly defined by the observation team. It is
recommended that a HTA is conducted for the task or scenario under analysis.
Step 3: Observation plan
Once the aim of the analysis is defined and also the type of scenario to be observed is
determined, the analysis team should proceed to plan the observation. The team should
consider what they are hoping to observe, what they are observing, and how they are
going to observe it. Depending upon the nature of the observation, access to the system
in question should be gained first. This may involve holding meetings with the
establishment in question, and is typically a lengthy process. Any recording tools should
be defined and also the length of observations should be determined. Placement of video
and audio recording equipment should also be considered. To make things easier, a
walkthrough of the system/environment/scenario under analysis is recommended. This
26