Posts Tagged 'fishbone diagram'

Recommended Technique: Root Cause Analysis

Project managers, business analysts and project team members often find themselves performing root case analysis to determine the underlying source of a problem. This structured technique is used to examine a situation in order to establish the root causes and resulting effects of a particular problem. On my projects, I have found that brainstorming is a great starting point for the project team to generate insights and options to kick off their root cause analysis efforts.  Brainstorming complements root cause analysis efforts by allowing the group to consider a full set of possibilities.  There are two common methods project teams use to perform root cause analysis: the fishbone diagram and the five whys.

Fishbone Diagram. A fishbone diagram allows you to show the causes of a problem or an effect. Fishbone diagrams are also called Ishikawa or cause-and-effect diagrams. This diagram allows you to see all possible causes of a result in a structured way and to make sure that everyone understands the problem or cause that is being addressed. Fishbone diagrams are usually constructed in a group setting, where key players brainstorm the categories and the possible causes in each category. Typical categories include things like people, methods, machines, materials, measurements, and environment. After the diagram is built, the team will analyze the results and hopefully determine the actual cause of what is taking place.

Five Whys. The five whys is a questioning technique that asks “why” repeatedly in order to get to the root cause of a problem. This technique can be used alone or used with the fishbone diagram technique. This is a very simple and effective facilitation tool. Many project teams customize their use of this tool by asking how instead of why or alternating between the two terms. Often the root cause is identified before the five questions are asked.

Be careful when you use the Five Whys technique! I was in a meeting once where the meeting facilitator really annoyed the senior user by repeatedly asking “why?” in order to determine if automating an existing process would improve customer service. The senior user ended up throwing a powdered sugar doughnut at the facilitator, making a big white spot right on the front of the facilitator’s black suit jacket.   It was one of those classic moments in project meeting history, I will never forget it.

Are there other techniques that you find successful when identifying, defining and solving problems on your projects?  Please share them with us here and tell us why they worked for you.

Happy problem solving!

Susan Weese

Facing a Bottleneck? Try the Fishbone Diagram

The fishbone diagram, also referred to as an Ishikawa or cause and effect diagram, is a method of diagramming that allows the project leader to facilitate a project team session to efficiently determine causes of a particular problem affecting the project. Once root causes are identified, appropriate actions toward resolution are more easily identified.

This tool helps to focus on the cause of the problem versus the solution and organizes ideas for further analysis. The diagram serves as a map depicting possible cause and effect relationships.

fishbone diagram


Steps to develop a fishbone diagram:

1.  Capture the issue or problem under discussion in a box at the right  of the diagram. It should be precisely stated and clear to everyone on the project team.

2.  Start with a flip chart (sideways, or landscape orientation).

3.  Draw a line from the box across the paper or white board (forming the spine of the fishbone).

4.  Draw diagonal lines from the spine to represent categories of potential causes of the problem. Determine the cause categories, choosing among:

  • Man, machine, methods, materials
  • Place, procedure, people, policies
  • Some other categories that apply to the problem

5.  Add as many causes as possible, connected to a line in each category. Draw smaller lines to represent deeper causes.

6.  Brainstorm categories and potential causes of the problem and capture them under the appropriate category.

7.  Once responses have been exhausted, evaluate the diagram for “root causes,” which are the initial problems that create others on the diagram.

8.  To facilitate the team toward root causes, keep asking “Why does this happen?” until the project team gets to the root cause.

9.  Analyze the results. Remember that the project team has identified only potential causes of the problem. Further analysis is needed to validate the actual cause, ideally with data.

10.  Brainstorm potential solutions once the actual cause has been identified. Assign next steps, which usually include:

  • Verification that the root causes have been correctly identified
  • Identification of appropriate actions to eliminate are mitigate root causes

See how using a fishbone diagram to analyze root causes can help your team. I would love to hear your comments, so try it out and let me know how it goes.

James L. Haner

Learning Tree logo

Project Management Training

Learning Tree offers over 210 IT and Management courses, including Project Management training and Business Analysis training.

Enter your e-mail address to subscribe to this blog and receive notifications of new posts by e-mail.

Join 283 other followers

Follow Learning Tree on Twitter


Do you need a customized Project Management training solution delivered at your facility?

Last year Learning Tree held nearly 2,500 on-site training events worldwide. To find out more about hosting one at your location, click here for a free consultation.
AnyWare live, online training

*PRINCE2® is a registered trade mark of the Cabinet Office.


Get every new post delivered to your Inbox.

Join 283 other followers

%d bloggers like this: