How to Facilitate Key Performance Indicators (KPI) Using an Ishakawa Diagram (ie, Fishbone Analysis)
October 4, 2012 3 Comments
Jack Welsh, CEO Emeritus for the General Electric Company, instilled his organization with an understanding that “If you can’t measure it, you can’t manage it.” With enough effort, almost every “fuzzy factor” can be converted to SMART criteria (ie, Specific, Measurable, Adjustable, Relevant, and Time-Based). Prioritized criteria form the foundation for major initiatives around Balanced Scorecard, dashboard techniques, portfolio decisions, and other essential corporate processes such as idea management.
Key Performance Indicators (KPI) can be identified during meetings by using root-cause analysis. Also referred to as Ishikawa or “fishbone” diagrams, the method generates a visual mind map listing possible causes. Named after Professor Kaoru Ishakawa at the University of Tokyo, he developed the process in 1945 to resolve steel production problems. Fishbone diagrams can be used to support analysis, identify gaps, provide insight about possible SMART criteria, and make assignments for follow-up activities and proactive change designs.
Here are the workshop steps to build a simple cause and effect diagram:
- In advance, prepare the following drawing (devoid of content) using either multiple sheets of paper, or some professional drawing tool.
- Use the objectives of the project to identify the “primary effect” or end result that needs to be changed. Decide on a trigger or a one-word label that captures the meaning of the full definition. In the example above, the term “CHANGE” captures the effect being analyzed. Based on importance and time constraints you will want to manage the total number of “causes”, typically between eight and twelve total. As a practical activity, you may also focus on fewer, even one or two primary effects, or four as illustrated.
- Options to explore potential root causes are now considered within each causal area. You may launch a brainstorming activity of all possible causes, and then assign codes to help the team categorize them. Most approaches to cause and effect diagrams begin with four likely categories of causes. Although you can experiment with the labels (and in practice you will notice similar, albeit different labels being used by others), four categories frequently used for potential causes include:
- Tools: Traditionally seen as the technology or equipment that leads to error, but could also reflect tangible resources that provide possible causes
- Method: Isolates the activities or tasks that might be the source of concern or the opportunity for improvement
- People: Intends to capture the group relationships and quality of decisions made
- Data: Traditionally seen as the information required to support the cause
You might also use breakout teams and assign one or more causal categories. Ideally, determine in a large group setting the most important category of causes and develop as a large group. Then consider assigning the less important categories to sub-teams or work offline for additional development.
- During a break, lunch, or evening illustrate your diagram and provide your workshop participants with full narrative definitions for each of the labels you will use in your fishbone diagram.
- Depending on time constraints, lead your analysis activity either by beginning with the most important causes, taking all of the causes within a category, or perhaps grab the easiest to manage, the “low-hanging” fruit. Determine clear and simple questions in advance to lead the analysis and know what you intend to do with the analysis — what type of documentation is required to satisfy the deliverables. For example, if you are leading up to a RASI (ie, roles and responsibilities) chart, then articulate the next steps or activities that need to be assigned.
One of the benefits to building a fishbone diagram includes the consensus that gets built around the assumptions. Once your participants understand the question, agree on the cause and effect behind the potential answers, you will find it is much easier to build consensus around the priorities and next steps required to either remediate a problem or design for change.
Let us know what you think by commenting below. For additional methodology and team-based meeting support for your change initiative, refer to “Change or Die, a Business Process Improvement Manual” for much of the support you might need.
Become Part of the Solution, Improve Your Facilitation Skills
The FAST curriculum on Professional Facilitation Skills details the responsibilities and dynamics mentioned above. Remember, nobody is smarter than everybody, so consult your FAST Facilitator Reference Manual or attend a FAST professional facilitative leadership training workshop offered around the world (see MG Rush for a current schedule — an excellent way to earn 40 PDUs from PMI, CDUs from IIBA, or CEUs).
Do not forget to order Change or Die if you working on a business process improvement project. It provides detailed workshop agendas and detailed tools to make your role easier and your team’s performance a lot more effective—daring you to embrace the will, wisdom, and activities that amplify a facilitative leader.
- How to set Key Performance Indicators for your business (premierlinedirect.co.uk)
- Facilitators are More Popular than Dictators: Google Ngram Viewer (facilitativeleadership.wordpress.com)
- Key Performance Indicators (kpi) (competencydevelopment.wordpress.com)