Groupware Task Analysis
Groupware task analysis (GTA) is used to study teams in order to analyze their tasks and activities. The information collected is then used when designing or analyzing comparable team systems. The method focuses on two task models.
Task model 1: Describes the situation as it currently exists.
Task model 2: Involves a redesign of the current system or the situation described in task model 1, including solutions to problems demonstrated and requirements specified in task model 1. Task model 2 is intended to provide a model of what the future system will be when the change is implemented.
To study team activity so similar team-based systems can be more easily designed and analyzed.
To demonstrate what the future task world will be once a change is implemented.
To identify problems and propose technological solutions.
1. DEFINE SYSTEM UNDER ANALYSIS.
2. DATA COLLECTION PHASE. Prior to the construction of task model 1, collect data about the current system under analysis. The more comprehensive the data, the better (include information on tasks, personnel, and environment).
3. CONSTRUCT TASK MODEL 1. This task model should provide a comprehensive description of the current situation.
4. CONSTRUCT TASK MODEL 2. The construction of this task model involves a redesign of the system described in task model 1.
5. REDESIGN THE SYSTEM. After task model 2 is constructed, begin redesigning the system.
GTA allows the design team to gain detailed insight into the current situation in question and its corresponding issues.
GTA output allows you to define system requirements and illustrates which issues must be remedied in a new design.
Task model 2 can demonstrate which technologies are needed and how readily available those technologies are.
Can require significant time and resources.
There is limited evidence of use.
Stanton N, Salmon P, Walker G, et al. Team assessment methods. Human factors methods: a practical guide for engineering and design. Great Britain: Ashgate; 2005. p. 365-429.
