Determination of Orientation and Practice Requirements When Using an Obstacle Course for Mobility Performance Assessment

Abstract

Objective: Determine effect of orientation (introduction and familiarization) and practice (repeated performance) on human performance under various load conditions as assessed by an obstacle course. Background: Obstacle courses are commonly used as screening tools by military, police, and firefighters or to assess human capabilities and the effect of wearing personal protective equipment (PPE) and other occupationally necessary equipment on mobility task performance. Unfortunately, little is formally documented about the effect of orientation and practice on performance outcomes of obstacle or mobility courses being used. Method: Forty-eight participants were recruited from the Canadian Army Infantry and Combat Engineer population. Participants either received regular or extensive orientation of the course before completing it. Following orientation, participants completed the course five consecutive times while wearing their PPE with full fighting order (FFO) and five consecutive times while wearing no PPE and non-FFO across a five-day period (maximum two runs per day), with ensemble presentation order counterbalanced. Total course completion time and individual obstacle completion times were measured for each run of the course. Results: While wearing FFO, participants continued to decrease the time required for completing the course; however, while wearing non-FFO, time to course completion did not significantly change over the five runs. There were no differences in course completion times for the regular and extensive course orientation groups. Conclusions: Considerations required to mitigate orientation and practicing effects can differ depending on type or complexity of load condition. While wearing FFO, practicing effects can introduce undesired confounding factors into data collection. Application: Any practice runs on an obstacle course prior to its use as an assessment tool should focus on the loaded (e.g., FFO) condition because improvement on loaded runs is likely transferred to unloaded, but this does not apply in the reverse.