Fishbone Diagram Template 23
Fishbone Diagram Template 23
Fishbone Diagram
Also Called: Cause and Effect Diagram.
Contents
What is a Fishbone Diagram? What is a Fishbone Diagram?
How to Construct a Fishbone
A fishbone diagram helps team members visually diagram a problem or condition's root causes, Diagram
allowing them to truly diagnose the problem rather than focusing on symptoms. It allows team
Example Fishbone Diagram
members to separate a problem's content from its history, and allows for team consensus
around the problem and its causes. Examples, Resources, Courses,
and Training
2. Categorization
Brainstorm major categories of your process or procedure (QI Toolbox: Brainstorming). Connect them to the backbone, in "ribs."
There is no specific number of steps or categories you might need to describe the problem; some common categories are listed
below.
WWW .HE AL TH .S T A TE . M N. U S/ QI
MIN N E SO T A DE P AR T ME N T OF HE A L TH PU BL IC HE A L TH & QI T O OL BO X | F IS HB ONE DI AG RA M
3. Contributing Factors
Brainstorm possible problem causes, and attach each to the appropriate rib. Your team might find it helpful to place ideas on
category ribs as they are generated, or to brainstorm an entire list of ideas and then place them on ribs all at once.
Ideally, each contributing factor would fit neatly into a single category, but some causes may seem to fit into multiple categories. If
you have a contributing factor that fits into more than one category, place it in each location, and see whether, in the end,
considering that factor from multiple points of view has made a difference.
4. Ask: Why?
As you list a factor, repeatedly ask your team why that factor is present:
Why does staff lack expertise? (Because we don't attend training.)
Why don't we attend training? (Because we don't have the funding.)
Why don't we have the funding? (Because we haven't applied for grants.)
Why don't we apply for grants? (Because we're unaware of sources.)
Etc.
Sometimes this asking process is called the "Five Whys," as five is often a manageable number to reach a suitable root cause. Your
team may need more or less than five whys. (More Information: Wikipedia: Five Whys.)
Continue to push deeper for a clear understanding. While you could likely brainstorm all day, however, it is important to know when
to stop to avoid frustration. A good rule of thumb: When a cause is controlled by more than one level of management, remove it
from the group.