19.07.2013 Views

BY ORDER OF THE AIR FORCE PAMPHLET 91-215 SECRETARY ...

BY ORDER OF THE AIR FORCE PAMPHLET 91-215 SECRETARY ...

BY ORDER OF THE AIR FORCE PAMPHLET 91-215 SECRETARY ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

A2.A.9. <strong>THE</strong> CAUSE AND EFFECT TOOL<br />

A2.A.9.1. FORMAL NAME. The cause and effect tool<br />

A2.A.9.2. ALTERNATIVE NAMES. The cause and effect diagram, The fishbone tool, the Ishikawa<br />

Diagram<br />

A2.A.9.3. PURPOSE. The cause and effect tool is a variation of the logic tree tool and is used in the<br />

same hazard ID role as the general logic diagram (i.e. a more rigorous, detailed tool). The special<br />

advantage of the cause and effect tool is its origin in the quality management process and the thousands of<br />

personnel who have been trained in the tool. Because it is widely used, thousands of personnel are familiar<br />

with it and therefore require little or no training to apply it to the problem of detecting risk.<br />

A2.A.9.4. APPLICATION. The cause and effect tool will be effective in organizations that have had<br />

some success with the quality initiative. As pointed out above, the tool is among the most commonly<br />

applied quality procedures and significant numbers of personnel are very comfortable using it. It should be<br />

used in the same manner as the logic diagram previously covered and can be applied in both a positive and<br />

negative variation.<br />

A2.A.9.5. METHOD. The cause and effect diagram is essentially a logic diagram but with a significant<br />

variation. The cause and effect diagram is provides more structure than the ordinary logic diagram through<br />

the branches that give it one of its alternate names, the fishbone diagram. Figure A2.19 illustrates this<br />

structure. Note that there are two basic variations, one for tactical type operations (the 4 “M”) and<br />

another for administrative processes (the 4 “P”). Of course the user can tailor the basic “bones” based on<br />

special characteristics of the operation or mission that is being analyzed. As in the case of the logic<br />

diagram, either a positive or negative outcome block is designated at the right side of the diagram. Then,<br />

using the structure of the diagram, the user or team of users completes the diagram by adding causal<br />

factors in either the “M” or “P” structure. By using branches off the basic entries, additional hazards can<br />

be added to the diagram. The examples provided illustrate this process. The cause and effect diagram is a<br />

very effective team hazard ID tool and should be used in a team setting whenever possible.<br />

A2.A.9.6. RESOURCES. There are many publications describing in great detail how to use cause and<br />

effect diagrams.<br />

A2.A.9.7. COMMENTS. This procedure has proven very effective and has established the cause and<br />

effect diagram as a powerful hazard ID tool.<br />

A2.A.9.8. EXAMPLES. An example of cause and effect tool in action is illustrated at Figure A2.19.<br />

56

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!