Use of Cause and Effect Diagram for Risk Management
Copyright Procept Associates Ltd. 2005
Aryana Project Management Conference
Tehran, Iran
March 2005
Use of Cause and Effect Diagram for Risk Management
Michael Stefanovic, P.Eng., PMP, MBA
Procept Associates Ltd.
www.procept.ca
www.procept.com
Use of Cause and Effect Diagram for Risk Management
Copyright Procept Associates Ltd. 2005
1. Introduction
It was November 8, 2004 when I attended a dinner meeting that was organized by the
local PMI chapter. The guest speaker was Dr. David Hillson, of “Risk Doctor and
Partners.” The topic was “Use a Risk Breakdown Structure to Understand Your Risks”
(http://www.risk-doctor.com/). I have listened to David before; he is an excellent speaker
and he knows Risk Management. Again, his presentation was excellent and received a
standing ovation from the capacity crowd.
During the question and answer period, I was prompted to ask David: “Has anyone tried
to use a Cause and Effect Diagram for the same purpose of identifying project risks?” I
do not remember David’s answer, but it was enough to encourage me to explore this idea
further. I cannot pretend that this is an original idea; the PMBOK 2004 edition identifies
Cause and Effect Diagram as a tool for Risk Identification process (ref. #1).
I entered “Cause and Effect Diagram, Risk Management” on Google and got 421,000
hits! Unfortunately, almost all talked about one or the other, but not both (at least the first
50 did not). Rather than spend hours fishing for the right article, I concluded that the
purpose of the Cause and Effect Diagram is risk identification, even if this is not
expressly stated by an article. Therefore, I decided to simply make this link (between the
Cause and Effect Diagram, and Risk Management) more explicit. This, in conclusion, is
the purpose of this presentation.
2. Risk Management Basics
Figure 1 summarizes the 6 Risk Management processes, according to the PMI’s Guide to
the Project Management Body of Knowledge (ref. #1). For the purpose of this
presentation, I think that this is adequate. However, if more information is required, I
recommend reading Chapter 11 of the referenced book.
How to
approach and
conduct risk
management
on a project.
Determining
which risks
might affect
the project
and
documenting
their
characteristics
Prioritizing
risks for
subsequent
further analysis
or action
Numerically
analysing the
effect of
identified risks
on overall
project
objectives
Developing
options and
actions to
enhance
opportunities
and to reduce
threats to
project
objectives
Tracking
identified risks,
monitoring
residual risks,
identifying new
risks, executing
risk response
plans and
evaluating their
effectiveness.
Figure 1 – Risk Management Processes
Risk
Monitoring
And Control
Risk
Response
Planning
Quantitative
Risk
Analysis
Qualitative
Risk
Analysis
Risk
Identificat.
Risk
Management
Planning
www.procept.com
Use of Cause and Effect Diagram for Risk Management
Copyright Procept Associates Ltd. 2005
3. What is Cause and Effect Diagram?
The Cause and Effect Diagram (CAED) organizes and graphically represents the causes
of a particular problem. It is also referred to as the Ishikawa Diagram, or Fishbone
Diagram. Another definition is: “A graphic tool used to explore and display opinion
about sources of variation in a process” (ref. #2).
CAED benefits are that it:
Defines sources that contribute most to the problem;
Defines interrelationships between these sources;
Provides a basis for corrective, or preventive action.
3.1 History
In the 1960 s, Dr. Kaoru Ishikawa developed and started using the concept.
3.2 What Does it Look Like?
Figure 2 shows one example of a CAED.
Late for
Work
Clothing
Alarm Clock
Bathroom Breakfast
Kids Spouse
Snow storm
Train late
Road
accident
Car does not
start
Transportation
Power failure
Alarm set for PM
Alarm set for
wrong time
Alarm not loud
enough
No clean shirts
Dog hid one shoe
Pants wrinkled
Hole in the soc
Kid sick
Kid missed
school bus
Kid lost his
homework
Does not want
to go to school
Town turns
water off
Light bulb burnt
Daughter taking shower
Toilet clogged
Wants to “converse”
Is sick
Forgot her birthday
Can not start her car
Out of eggs
Out of coffee
No clean cups
Toaster smoking
Figure 2 – Cause and Effect Diagram
www.procept.com
Use of Cause and Effect Diagram for Risk Management
Copyright Procept Associates Ltd. 2005
3.3 How is CAED Used?
1. Start with the problem that is being analyzed on the right side of the diagram (e.g.
“Late For Work”);
2. List the possible causes of that problem at the end of each primary branch (e.g.
“Breakfast”). These are given conditions about which there is nothing we can do
(i.e. breakfast is taken before leaving for work);
3. Add secondary branches with risk events within the cause area (e.g. “toaster
smoking”);
4. Add tertiary branches: more detailed risk events that have as effect the risk event
on the secondary branch (e.g. full of crumbs, or wiring insulation too old);
5. Continue developing new, more detailed risk events until you have reached the
level of detail where risk events are specific, measurable and controllable.
This process can be performed by project team brainstorming, by using affinity diagrams,
or other facilitative risk identification tools.
Once completed, this process will provide a list of risk events that need to be addressed if
the probability of the problem occurrence is to be mitigated.
4. Use For Risk Management
4.1 Risk Identification
The process outlined under 3.3 above illustrates how a CAED can be used for risk event
identification.
4.2 Another Form of Risk breakdown Structure
CAED has all the advantages of a Risk Breakdown Structure, which are that it:
Facilitates risk identification;
Provides project risk categories;
Provides a template from past projects for the risk identification process;
Provides a structure for risk assessment;
Facilitates evaluation of the alternatives;
Figure 3 shows an example of a Risk breakdown Structure (ref. #5).
www.procept.com
Use of Cause and Effect Diagram for Risk Management
Copyright Procept Associates Ltd. 2005
4.3 Provides a Hierarchy of Risks
As explained in 3.3, risk events are organized hierarchically. A risk event at one level of
detail becomes an effect (impact) of a more detailed risk event. For instance, the three top
level risk events of any project are:
Project ends late;
Project budget is overrun;
The product that the project delivered does not work.
Everyone knows that for any decently sized project, these risk events are not adequately
specific, measurable, or controllable to be practical. However, they are an example of the
first level of detail below an even higher level: “Project Fails.”
Using CAED as a risk hierarchical structure would lead us to define causes (e.g.
“Breakfast”) as the first level of risk event detail. In such case, we should give it a risk
event characteristic (e.g. “Breakfast Late”).
4.4 Evaluate Competing Proposals
The process for using CAED for evaluating competing proposals can be summarized as
follows:
1. Construct Risk Cause and Effect Diagram for each proposal;
2. Assess probability and impact for risk events at the ends of branches;
3. Multiply probability with impact for each risk event (Expected Monetary Value);
Figure 3 – Example of a Risk Breakdown Structure (Ref. #5)
www.procept.com
Use of Cause and Effect Diagram for Risk Management
Copyright Procept Associates Ltd. 2005
4. Add all expected monetary values for each proposal;
5. Rank proposals in order of risk expected monetary values.
4.5 Prioritize Competing Projects
A very similar process to the one explained in 4.4 can be used for prioritizing between
competing projects:
1. Construct Risk Cause and Effect Diagram for each project;
2. Assess probability and impact for risk events at the ends of branches;
3. Multiply probability with impact for each risk event (Expected Monetary Value);
4. Add all expected monetary values for each project;
5. Rank projects in order of risk expected monetary values.
4.6 Organize Risk Historical Database
CAED can be used effectively for organizing a risk historical database storage and
retrieval system. It can:
1. Group projects by type;
2. Create risk causes categories;
3. Store risk factors information by cause;
4. Retrieve risk information only from applicable causes for a new project.
4.7 Risk Management Reporting
Similar to any other reporting strategy, risk management reports are structured to provide
summary reports to senior management and detailed reports to middle management. The
CAED hierarchy of risks can be used to summarize, or detail risk management reports.
5. Conclusion
A Cause and Effect Diagram can be effective in:
• Risk identification;
• Replacing Risk Breakdown Structure where advantageous;
• Hierarchically organizing risk events;
• Evaluating competing proposals on the basis of their risk levels;
• Prioritizing competing projects on the basis of their risk levels;
• Organizing a risk historical data base;
• Risk management reporting.
www.procept.com
Use of Cause and Effect Diagram for Risk Management
Copyright Procept Associates Ltd. 2005
References:
1. A Guide to the Project Management Body of Knowledge, Project Management
Institute, 3rd
edition, 2004
2. http://mot.vuse.vanderbilt.edu/mt322/Ishikawa.htm
3. http://www.jiscinfonet.ac.uk/InfoKits/risk-management/ishikawa
4. http://www.westfallteam.com/Cause&Effect_Diagrams.pdf
5. http://www.risk-doctor.com/
www.procept.com

More Related Content

PPTX
MPHASIS
PPTX
Kirch media scandal
PPTX
Marketing Strategy - TCS
PPTX
Presentation on nokia overall started
DOCX
4 P's of Vodafone company
PPT
How to manage stress at workplace
PDF
Stress At Work (Tips to Reduce and Manage Job and Workplace Stress)
PPT
Cause and-effect diagram
MPHASIS
Kirch media scandal
Marketing Strategy - TCS
Presentation on nokia overall started
4 P's of Vodafone company
How to manage stress at workplace
Stress At Work (Tips to Reduce and Manage Job and Workplace Stress)
Cause and-effect diagram

Similar to Use of Causeand Effect Diagrams for Risk Management (20)

PPT
Cause and effect diagram
PPTX
Cause and effect diagram
PPTX
Root cause analysis training
PPTX
Root cause analysis
PPTX
K10972 vinit opc
PPTX
Root cause analysis
PDF
Causeeffect
PDF
Project Management Practitioner: Problem Solving and Decision Making
PPTX
Visual tools for Risk Management Process
PPTX
Project Risk Management (10)
PPTX
Deviation management new (1)
DOCX
1.  Patient Safety is a health care professionals’ duty. A sur.docx
PDF
Cause And Effect Analysis For Quality Management Powerpoint Presentation Slides
PDF
Don't Overthink Risk Management by Suzanne Hartin
PPTX
Cause effect diagram
PPTX
Root cause analysis
PPT
Project Risk Management-Pankaj K Sinha
PPT
Qcl 14-v3 [cause-effect diagram]-[banasthali university]_[shreya gupta]
PDF
Risk Management Perspectives Conference 2014
DOC
Risk impact
Cause and effect diagram
Cause and effect diagram
Root cause analysis training
Root cause analysis
K10972 vinit opc
Root cause analysis
Causeeffect
Project Management Practitioner: Problem Solving and Decision Making
Visual tools for Risk Management Process
Project Risk Management (10)
Deviation management new (1)
1.  Patient Safety is a health care professionals’ duty. A sur.docx
Cause And Effect Analysis For Quality Management Powerpoint Presentation Slides
Don't Overthink Risk Management by Suzanne Hartin
Cause effect diagram
Root cause analysis
Project Risk Management-Pankaj K Sinha
Qcl 14-v3 [cause-effect diagram]-[banasthali university]_[shreya gupta]
Risk Management Perspectives Conference 2014
Risk impact
Ad

More from Procept Associates (8)

PDF
Project Scheduling & Controls
PDF
Ba Certificate Info 2009-09-28
PDF
Decisions Decisions
PDF
ITILv3 Service Design
PDF
Essential Business Analysis Skills
PDF
Procept Whirlwind Workshop 2007
PDF
Procept Risk Workshop 2007
PDF
White Paper:Project Management And Business Analysis Maturity
Project Scheduling & Controls
Ba Certificate Info 2009-09-28
Decisions Decisions
ITILv3 Service Design
Essential Business Analysis Skills
Procept Whirlwind Workshop 2007
Procept Risk Workshop 2007
White Paper:Project Management And Business Analysis Maturity
Ad

Recently uploaded (20)

PPT
Retail Management and Retail Markets and Concepts
PDF
the role of manager in strategic alliances
DOCX
ola and uber project work (Recovered).docx
PDF
Cross-Cultural Leadership Practices in Education (www.kiu.ac.ug)
PDF
Clouds that Assimilate the Build Parts I&II .pdf
PPTX
basic introduction to research chapter 1.pptx
PDF
How to run a consulting project from scratch
PDF
HQ #118 / 'Building Resilience While Climbing the Event Mountain
PPTX
Understanding Procurement Strategies.pptx Your score increases as you pick a ...
PDF
IFRS Green Book_Part B for professional pdf
PDF
Handouts for Housekeeping.pdfbababvsvvNnnh
PPTX
Market and Demand Analysis.pptx for Management students
PDF
Sustainable Digital Finance in Asia_FINAL_22.pdf
PPTX
Week2: Market and Marketing Aspect of Feasibility Study.pptx
DOCX
80 DE ÔN VÀO 10 NĂM 2023vhkkkjjhhhhjjjj
PDF
Comments on Clouds that Assimilate Parts I&II.pdf
PDF
dataZense for Data Analytics unleashed features
PDF
Communication Tactics in Legal Contexts: Historical Case Studies (www.kiu.ac...
PDF
Tortilla Mexican Grill 发射点犯得上发射点发生发射点犯得上发生
PPTX
chapter 2 entrepreneurship full lecture ppt
Retail Management and Retail Markets and Concepts
the role of manager in strategic alliances
ola and uber project work (Recovered).docx
Cross-Cultural Leadership Practices in Education (www.kiu.ac.ug)
Clouds that Assimilate the Build Parts I&II .pdf
basic introduction to research chapter 1.pptx
How to run a consulting project from scratch
HQ #118 / 'Building Resilience While Climbing the Event Mountain
Understanding Procurement Strategies.pptx Your score increases as you pick a ...
IFRS Green Book_Part B for professional pdf
Handouts for Housekeeping.pdfbababvsvvNnnh
Market and Demand Analysis.pptx for Management students
Sustainable Digital Finance in Asia_FINAL_22.pdf
Week2: Market and Marketing Aspect of Feasibility Study.pptx
80 DE ÔN VÀO 10 NĂM 2023vhkkkjjhhhhjjjj
Comments on Clouds that Assimilate Parts I&II.pdf
dataZense for Data Analytics unleashed features
Communication Tactics in Legal Contexts: Historical Case Studies (www.kiu.ac...
Tortilla Mexican Grill 发射点犯得上发射点发生发射点犯得上发生
chapter 2 entrepreneurship full lecture ppt

Use of Causeand Effect Diagrams for Risk Management

  • 1. Use of Cause and Effect Diagram for Risk Management Copyright Procept Associates Ltd. 2005 Aryana Project Management Conference Tehran, Iran March 2005 Use of Cause and Effect Diagram for Risk Management Michael Stefanovic, P.Eng., PMP, MBA Procept Associates Ltd. www.procept.ca www.procept.com
  • 2. Use of Cause and Effect Diagram for Risk Management Copyright Procept Associates Ltd. 2005 1. Introduction It was November 8, 2004 when I attended a dinner meeting that was organized by the local PMI chapter. The guest speaker was Dr. David Hillson, of “Risk Doctor and Partners.” The topic was “Use a Risk Breakdown Structure to Understand Your Risks” (http://www.risk-doctor.com/). I have listened to David before; he is an excellent speaker and he knows Risk Management. Again, his presentation was excellent and received a standing ovation from the capacity crowd. During the question and answer period, I was prompted to ask David: “Has anyone tried to use a Cause and Effect Diagram for the same purpose of identifying project risks?” I do not remember David’s answer, but it was enough to encourage me to explore this idea further. I cannot pretend that this is an original idea; the PMBOK 2004 edition identifies Cause and Effect Diagram as a tool for Risk Identification process (ref. #1). I entered “Cause and Effect Diagram, Risk Management” on Google and got 421,000 hits! Unfortunately, almost all talked about one or the other, but not both (at least the first 50 did not). Rather than spend hours fishing for the right article, I concluded that the purpose of the Cause and Effect Diagram is risk identification, even if this is not expressly stated by an article. Therefore, I decided to simply make this link (between the Cause and Effect Diagram, and Risk Management) more explicit. This, in conclusion, is the purpose of this presentation. 2. Risk Management Basics Figure 1 summarizes the 6 Risk Management processes, according to the PMI’s Guide to the Project Management Body of Knowledge (ref. #1). For the purpose of this presentation, I think that this is adequate. However, if more information is required, I recommend reading Chapter 11 of the referenced book. How to approach and conduct risk management on a project. Determining which risks might affect the project and documenting their characteristics Prioritizing risks for subsequent further analysis or action Numerically analysing the effect of identified risks on overall project objectives Developing options and actions to enhance opportunities and to reduce threats to project objectives Tracking identified risks, monitoring residual risks, identifying new risks, executing risk response plans and evaluating their effectiveness. Figure 1 – Risk Management Processes Risk Monitoring And Control Risk Response Planning Quantitative Risk Analysis Qualitative Risk Analysis Risk Identificat. Risk Management Planning www.procept.com
  • 3. Use of Cause and Effect Diagram for Risk Management Copyright Procept Associates Ltd. 2005 3. What is Cause and Effect Diagram? The Cause and Effect Diagram (CAED) organizes and graphically represents the causes of a particular problem. It is also referred to as the Ishikawa Diagram, or Fishbone Diagram. Another definition is: “A graphic tool used to explore and display opinion about sources of variation in a process” (ref. #2). CAED benefits are that it: Defines sources that contribute most to the problem; Defines interrelationships between these sources; Provides a basis for corrective, or preventive action. 3.1 History In the 1960 s, Dr. Kaoru Ishikawa developed and started using the concept. 3.2 What Does it Look Like? Figure 2 shows one example of a CAED. Late for Work Clothing Alarm Clock Bathroom Breakfast Kids Spouse Snow storm Train late Road accident Car does not start Transportation Power failure Alarm set for PM Alarm set for wrong time Alarm not loud enough No clean shirts Dog hid one shoe Pants wrinkled Hole in the soc Kid sick Kid missed school bus Kid lost his homework Does not want to go to school Town turns water off Light bulb burnt Daughter taking shower Toilet clogged Wants to “converse” Is sick Forgot her birthday Can not start her car Out of eggs Out of coffee No clean cups Toaster smoking Figure 2 – Cause and Effect Diagram www.procept.com
  • 4. Use of Cause and Effect Diagram for Risk Management Copyright Procept Associates Ltd. 2005 3.3 How is CAED Used? 1. Start with the problem that is being analyzed on the right side of the diagram (e.g. “Late For Work”); 2. List the possible causes of that problem at the end of each primary branch (e.g. “Breakfast”). These are given conditions about which there is nothing we can do (i.e. breakfast is taken before leaving for work); 3. Add secondary branches with risk events within the cause area (e.g. “toaster smoking”); 4. Add tertiary branches: more detailed risk events that have as effect the risk event on the secondary branch (e.g. full of crumbs, or wiring insulation too old); 5. Continue developing new, more detailed risk events until you have reached the level of detail where risk events are specific, measurable and controllable. This process can be performed by project team brainstorming, by using affinity diagrams, or other facilitative risk identification tools. Once completed, this process will provide a list of risk events that need to be addressed if the probability of the problem occurrence is to be mitigated. 4. Use For Risk Management 4.1 Risk Identification The process outlined under 3.3 above illustrates how a CAED can be used for risk event identification. 4.2 Another Form of Risk breakdown Structure CAED has all the advantages of a Risk Breakdown Structure, which are that it: Facilitates risk identification; Provides project risk categories; Provides a template from past projects for the risk identification process; Provides a structure for risk assessment; Facilitates evaluation of the alternatives; Figure 3 shows an example of a Risk breakdown Structure (ref. #5). www.procept.com
  • 5. Use of Cause and Effect Diagram for Risk Management Copyright Procept Associates Ltd. 2005 4.3 Provides a Hierarchy of Risks As explained in 3.3, risk events are organized hierarchically. A risk event at one level of detail becomes an effect (impact) of a more detailed risk event. For instance, the three top level risk events of any project are: Project ends late; Project budget is overrun; The product that the project delivered does not work. Everyone knows that for any decently sized project, these risk events are not adequately specific, measurable, or controllable to be practical. However, they are an example of the first level of detail below an even higher level: “Project Fails.” Using CAED as a risk hierarchical structure would lead us to define causes (e.g. “Breakfast”) as the first level of risk event detail. In such case, we should give it a risk event characteristic (e.g. “Breakfast Late”). 4.4 Evaluate Competing Proposals The process for using CAED for evaluating competing proposals can be summarized as follows: 1. Construct Risk Cause and Effect Diagram for each proposal; 2. Assess probability and impact for risk events at the ends of branches; 3. Multiply probability with impact for each risk event (Expected Monetary Value); Figure 3 – Example of a Risk Breakdown Structure (Ref. #5) www.procept.com
  • 6. Use of Cause and Effect Diagram for Risk Management Copyright Procept Associates Ltd. 2005 4. Add all expected monetary values for each proposal; 5. Rank proposals in order of risk expected monetary values. 4.5 Prioritize Competing Projects A very similar process to the one explained in 4.4 can be used for prioritizing between competing projects: 1. Construct Risk Cause and Effect Diagram for each project; 2. Assess probability and impact for risk events at the ends of branches; 3. Multiply probability with impact for each risk event (Expected Monetary Value); 4. Add all expected monetary values for each project; 5. Rank projects in order of risk expected monetary values. 4.6 Organize Risk Historical Database CAED can be used effectively for organizing a risk historical database storage and retrieval system. It can: 1. Group projects by type; 2. Create risk causes categories; 3. Store risk factors information by cause; 4. Retrieve risk information only from applicable causes for a new project. 4.7 Risk Management Reporting Similar to any other reporting strategy, risk management reports are structured to provide summary reports to senior management and detailed reports to middle management. The CAED hierarchy of risks can be used to summarize, or detail risk management reports. 5. Conclusion A Cause and Effect Diagram can be effective in: • Risk identification; • Replacing Risk Breakdown Structure where advantageous; • Hierarchically organizing risk events; • Evaluating competing proposals on the basis of their risk levels; • Prioritizing competing projects on the basis of their risk levels; • Organizing a risk historical data base; • Risk management reporting. www.procept.com
  • 7. Use of Cause and Effect Diagram for Risk Management Copyright Procept Associates Ltd. 2005 References: 1. A Guide to the Project Management Body of Knowledge, Project Management Institute, 3rd edition, 2004 2. http://mot.vuse.vanderbilt.edu/mt322/Ishikawa.htm 3. http://www.jiscinfonet.ac.uk/InfoKits/risk-management/ishikawa 4. http://www.westfallteam.com/Cause&Effect_Diagrams.pdf 5. http://www.risk-doctor.com/ www.procept.com