PROTOTYPE Arrival Brief

～Statement of Condition Select and Prioritize: Runway conditions Low visibility procedures Hydroplaning Crosswinds/windshear Terrain/MSA Aircraft performance Convective activity GPWS/TCAS alerts Fuel status/delays
～Bottom Lines ～Backup Plan

Eliciting Instructor/Evaluator and Other User Feedback
Two forms of feedback should be collected during this prototype refinement stage. The first form is feedback from the users, both pilots and instructors. This is detailed feedback, and is generally best collected first. Once the prototype has been refined through user feedback, the second form of feedback to be collected is the more general organizational feedback discussed in the next subsection.
Prototype presentations to the users allow the development team to collect informal comments during the presentation, and more formal, quantitative feedback through a form that can be handed out or administered during the user feedback sessions. The user feedback sessions should be designed and scheduled so that the development team can collect good data in an efficient manner. Ideally, airlines would be able to perform usability testing, where the procedures are evaluated in some operational or simulated context. That is not possible in most cases, so working with small groups provides a good alternative. If possible, the sessions should be scheduled for five to ten individuals who are likely to work well together. Working with too small a group (less than five) is less efficient, and the individuals are less likely to be stimulated by a wider range of comments. Working with too large a group (substantially more than ten) is more difficult to manage, and the feedback will likely cover a broad range of topics but not in depth.
In scheduling these sessions, there are a number of additional considerations. If instructors and crews are very busy and it is difficult to schedule a meeting, consider scheduling the prototype feedback sessions as part of other planned meetings. If resistance is likely from a specific group, consider having a separate session with that group addressing their issues as soon as possible within the feedback process.
The feedback sessions should have two parts. The first part is a more general presentation of the CRM procedures and their rationale, followed by encouraging users to ask questions and make general comments. Once the group has a good understanding of the procedures and their purpose, a form can be administered to ask for comments or ratings about the different aspects of the procedures. Items may include questions about the effects of a proposed procedure on workload, ease of
understanding the procedure, how the procedure interfaces with the rest of the SOP, possible problems, and how the procedure might be improved. In most cases the development team is less interested in consensus and more interested in individual feedback, so the forms should be completed individually and not as part of the group discussion.
　
中國航空網 m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：Developing Advanced Crew Resource Management (ACRM) Training: A Training Manual(34)