139: Too Much/Too Little Detail
Definition/Typical Issues
Do the procedures provide too little detail to ensure proper performance of the task by the most inexperienced operator? Do the procedures have too much detail, such as design details?
Examples
Example 1
- The instructions for a computer software program just stated "change the loading preferences to user-defined values." No further directions were provided on how this could be done.
Example 2
- An engineer developed a procedure in paragraph format. About half of the information in the procedure was design information that the operators did not need.
Example 3
- An operations procedure for the shutdown of the cooling water system included specific steps on how to close manually operated valves. This information was not needed in the procedure because it was a common operator skill that did not require any task-specific knowledge.
Example 4
- An inexperienced mechanic made a mistake installing a piece of equipment. The procedure stated only to remove the old item and replace it with a similar unit. This was not detailed enough for the inexperienced mechanic.
Typical Recommendations
- Consider using an outline format with high level steps for experienced users and detailed steps for inexperienced users.
- Provide guidance on content, including what should not be included in procedures. Also include guidance on what information should be included in related documents such as training or technology manuals.
- Refrain from embedding operational steps within a long descriptive narrative that explains the unit or theoretical basis for how the unit operates.
Cross-References
| Version 10 Element(s) | |
|---|---|
| Node ID | Node Name |
| 128 | Level of Detail LTA |
| Maritime Element(s) | |
|---|---|
| Node ID | Node Name |
| 133 | Too Much/Little Detail |