Fishbone diagram - Revision history

Tkokotas at 19:05, 17 November 2018

2018-11-17T19:05:26Z

← Older revision		Revision as of 19:05, 17 November 2018
Line 1:		Line 1:
			''Developed by Karoline Holm Hansen''


	[[File:step3.png\|right\|500px]]		[[File:step3.png\|right\|500px]]
	The Fishbone diagram is named for its resemblance to a fishbone. The investigated problem is placed of the "head" and the identified root causes comes out of the "spine" like ribs, see the illustration. It is also called an Ishikawa diagram after its creator Kaoru Ishikawa, or a Cause-and-Effect diagram. Ishikawa created it as a tool in a toolkit for quality control. Its use has since turned towards identification of root causes for problems. This has made it a valuable tool for risk identification, and in a wider sense in Risk Management as it can help a team figure out how best to handle the risks with ARTA<ref name="How" />. The Fishbone diagram has the benefits of being a systematic and organised way of finding potential causes to a problem and of encouraging the team using it to talk about both the problem and its causes. Part of this talk will have the outcome of having ranked the root causes according to their likelihood of happening and how easy they are to fix or control. This allows the team to prioritise and better manage their risks.		The Fishbone diagram is named for its resemblance to a fishbone. The investigated problem is placed of the "head" and the identified root causes comes out of the "spine" like ribs, see the illustration. It is also called an Ishikawa diagram after its creator Kaoru Ishikawa, or a Cause-and-Effect diagram. Ishikawa created it as a tool in a toolkit for quality control. Its use has since turned towards identification of root causes for problems. This has made it a valuable tool for risk identification, and in a wider sense in Risk Management as it can help a team figure out how best to handle the risks with ARTA<ref name="How" />. The Fishbone diagram has the benefits of being a systematic and organised way of finding potential causes to a problem and of encouraging the team using it to talk about both the problem and its causes. Part of this talk will have the outcome of having ranked the root causes according to their likelihood of happening and how easy they are to fix or control. This allows the team to prioritise and better manage their risks.

Karoline: /* Common ways it is used */

2017-09-27T13:11:30Z

Common ways it is used

← Older revision		Revision as of 13:11, 27 September 2017
Line 84:		Line 84:
	#*Performance		#*Performance
	#*Place		#*Place
	#:[[File:8Ps.png\|left\|400px]] ~~<br /><br />~~<br /><br /><br /><br /><br /><br /><br /><br /><br /><br />		#:[[File:8Ps.png\|left\|400px]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br />

	==Limitations of the Fishbone Diagram==		==Limitations of the Fishbone Diagram==

Karoline: /* Common ways it is used */

2017-09-27T13:11:11Z

Common ways it is used

← Older revision		Revision as of 13:11, 27 September 2017
Line 84:		Line 84:
	#*Performance		#*Performance
	#*Place		#*Place
	#:[[File:8Ps.png\|left\|400px]]		#:[[File:8Ps.png\|left\|400px]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />

	==Limitations of the Fishbone Diagram==		==Limitations of the Fishbone Diagram==

Karoline: /* Common ways it is used */

2017-09-27T13:10:46Z

Common ways it is used

← Older revision		Revision as of 13:10, 27 September 2017
Line 44:		Line 44:
	#*Man (which covers both physical and knowledge work)		#*Man (which covers both physical and knowledge work)
	#*Measurement (which covers inspection and environment)		#*Measurement (which covers inspection and environment)
	#:<~~!--Insert picture--~~>		#:[[File:5Ms.png\|left\|400px]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
	#:Sometimes it is relevant to include three extra Ms, these are:		#:Sometimes it is relevant to include three extra Ms, these are:
	#*Mission (which covers the purpose and the environment)		#*Mission (which covers the purpose and the environment)
	#*Management		#*Management
	#*Maintenance		#*Maintenance
	#:<~~!--Insert picture--~~>		#:[[File:8Ms.png\|left\|400px]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
	# The second one considers these causes<ref name="City" />		# The second one considers these causes<ref name="City" />
	#*People		#*People
Line 57:		Line 57:
	#*Environment		#*Environment
	#*Measurement		#*Measurement
	#:<~~!--Insert picture--~~>		#:[[File:Manufacturing.png\|left\|400px]] <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />

	For '''Services''' another two standards exist:		For '''Services''' another two standards exist:
Line 66:		Line 66:
	#*Location (this usually includes equipment and machinery)		#*Location (this usually includes equipment and machinery)
	#*Measurement		#*Measurement
	#:<~~!--Insert picture--~~>		#:[[File:Services.png\|left\|400px]]<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
	#The second one is called ''The 4 Ss''<ref name="Wikipedia" /> and considers these causes		#The second one is called ''The 4 Ss''<ref name="Wikipedia" /> and considers these causes
	#*Surroundings		#*Surroundings
Line 72:		Line 72:
	#*Systems		#*Systems
	#*Skills		#*Skills
	#:<~~!--Insert picture--~~>		#:[[File:4Ss.png\|left\|400px]]<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />

	For '''Product Marketing''' this standard exists		For '''Product Marketing''' this standard exists
Line 84:		Line 84:
	#*Performance		#*Performance
	#*Place		#*Place
	#:~~<!--Insert picture-->~~		#:[[File:8Ps.png\|left\|400px]]

	==Limitations of the Fishbone Diagram==		==Limitations of the Fishbone Diagram==

Karoline at 11:49, 27 September 2017

2017-09-27T11:49:11Z

Show changes

Karoline: /* References */

2017-09-27T03:57:19Z

References

← Older revision		Revision as of 03:57, 27 September 2017
Line 109:		Line 109:
	==References==		==References==
	<references />		<references />
	'''Key references'''		'''Key references''' <br />
	''4. This article gives an introduction to the Fishbone diagram and how to use it in conjunction with '''The 5 Whys'''. ''		''4. This article gives an introduction to the Fishbone diagram and how to use it in conjunction with '''The 5 Whys'''. ''<br />
	''7. Wikipedia gives a brief overview of the tool and explain common first level causes for production, marketing, and service. Lastly it describes how the tool can be used in lean.''		''7. Wikipedia gives a brief overview of the tool and explain common first level causes for production, marketing, and service. Lastly it describes how the tool can be used in lean.''<br />
	''2. This article explains more of the history of the Fishbone diagram and diagram itself. The article demonstrates how to use the tool with codification and draws relevant conclusions for the Fishbone diagram itself as well as for being used in this conjunction.''		''2. This article explains more of the history of the Fishbone diagram and diagram itself. The article demonstrates how to use the tool with codification and draws relevant conclusions for the Fishbone diagram itself as well as for being used in this conjunction.'' <br />
	''3. This article explains why teams should use the tool then give a step by step explanation on how to use it.''		''3. This article explains why teams should use the tool then give a step by step explanation on how to use it.''

Karoline at 03:56, 27 September 2017

2017-09-27T03:56:28Z

← Older revision		Revision as of 03:56, 27 September 2017
Line 108:		Line 108:

	==References==		==References==
	<references />		<references />
			'''Key references'''
			''4. This article gives an introduction to the Fishbone diagram and how to use it in conjunction with '''The 5 Whys'''. ''
			''7. Wikipedia gives a brief overview of the tool and explain common first level causes for production, marketing, and service. Lastly it describes how the tool can be used in lean.''
			''2. This article explains more of the history of the Fishbone diagram and diagram itself. The article demonstrates how to use the tool with codification and draws relevant conclusions for the Fishbone diagram itself as well as for being used in this conjunction.''
			''3. This article explains why teams should use the tool then give a step by step explanation on how to use it.''

Karoline: /* Suggested literature not covered by the DTU License */

2017-09-22T12:46:06Z

Suggested literature not covered by the DTU License

← Older revision		Revision as of 12:46, 22 September 2017
Line 107:		Line 107:
	It should be noted that these tools are only suggestions on how to take better advantage of the Fishbone diagram to reach the goal of doing proper ''Risk Management'' that would be the reason why a team would use the diagram in the first place. It should also be noted that this list is in no way exhaustive.		It should be noted that these tools are only suggestions on how to take better advantage of the Fishbone diagram to reach the goal of doing proper ''Risk Management'' that would be the reason why a team would use the diagram in the first place. It should also be noted that this list is in no way exhaustive.

	~~==Suggested literature not covered by the DTU License==~~
	~~<!-- Ishikawa original works; ...-->~~
	==References==		==References==
	<references />		<references />

Karoline at 12:44, 22 September 2017

2017-09-22T12:44:27Z

← Older revision		Revision as of 12:44, 22 September 2017
Line 1:		Line 1:
	[[File:step3.png\|right\|500px]]		[[File:step3.png\|right\|500px]]
	The Fishbone diagram is named for its resemblance to a fishbone with the investigated problem being in the place of the head and the identified root causes coming out of the spine (see picture). It is also called an Ishikawa diagram after its creator Kaoru Ishikawa or a Cause-and-Effect diagram. Ishikawa created it as a tool in a toolkit for quality control. Its use has since turned towards identification of root causes for problems. This has made it a valuable tool for risk identification, and in a wider sense in Risk Management as it can help a team figuring out how best to handle the risks with ARTA<ref name="How" />. The Fishbone diagram has the benefits of being a systematic and organised way of finding potential causes to a problem and encouraging the team using it to talk about both the problem and its causes.		The Fishbone diagram is named for its resemblance to a fishbone with the investigated problem being in the place of the head and the identified root causes coming out of the spine (see picture). It is also called an Ishikawa diagram after its creator Kaoru Ishikawa or a Cause-and-Effect diagram. Ishikawa created it as a tool in a toolkit for quality control. Its use has since turned towards identification of root causes for problems. This has made it a valuable tool for risk identification, and in a wider sense in Risk Management as it can help a team figuring out how best to handle the risks with ARTA<ref name="How" />. The Fishbone diagram has the benefits of being a systematic and organised way of finding potential causes to a problem and encouraging the team using it to talk about both the problem and its causes. Part of this talk will have the outcome of having ranked the root causes according to their likelihood of happening and how easy they are to fix or control. This allows the team to prioritise their and better manage risks.

	This article will focus on the Fishbone diagram. It will consider how the diagram is appropriately used in Risk Management as well as its purpose ans limitations. It will also touch upon tools that can be used in conjunction with the diagram to strengthen a project's management of risks. The article will be based on previous literature on the subject<!-- as well as the author's personal experiences with the tool-->.		This article will focus on the Fishbone diagram. It will consider how the diagram is appropriately used in Risk Management as well as its purpose ans limitations. It will also touch upon tools that can be used in conjunction with the diagram to strengthen a project's management of risks. The article will be based on previous literature on the subject<!-- as well as the author's personal experiences with the tool-->.

Karoline at 12:40, 22 September 2017

2017-09-22T12:40:35Z

← Older revision		Revision as of 12:40, 22 September 2017
Line 1:		Line 1:
	[[File:step3.png\|right\|500px]]		[[File:step3.png\|right\|500px]]
	The Fishbone diagram is named for its resemblance to a fishbone with the investigated problem being in the place of the head and the identified root causes coming out of the spine (see picture). It is also called an Ishikawa diagram after its creator Kaoru Ishikawa or a Cause-and-Effect diagram.		The Fishbone diagram is named for its resemblance to a fishbone with the investigated problem being in the place of the head and the identified root causes coming out of the spine (see picture). It is also called an Ishikawa diagram after its creator Kaoru Ishikawa or a Cause-and-Effect diagram. Ishikawa created it as a tool in a toolkit for quality control. Its use has since turned towards identification of root causes for problems. This has made it a valuable tool for risk identification, and in a wider sense in Risk Management as it can help a team figuring out how best to handle the risks with ARTA<ref name="How" />. The Fishbone diagram has the benefits of being a systematic and organised way of finding potential causes to a problem and encouraging the team using it to talk about both the problem and its causes.
	~~Identifying the~~ root causes ~~of a problem makes~~ it a valuable tool in Risk Management, as it can help ~~the~~ team figuring out how best to handle ~~this~~ with ARTA.

	This article will focus on the ~~fishbone~~ diagram. It will consider how the diagram is appropriately used in Risk Management as well as its purpose ans limitations. It will also touch upon tools that can be used in conjunction with the diagram to strengthen a project's management of risks. The article will be based on previous literature on the subject<!-- as well as the author's personal experiences with the tool-->.		This article will focus on the Fishbone diagram. It will consider how the diagram is appropriately used in Risk Management as well as its purpose ans limitations. It will also touch upon tools that can be used in conjunction with the diagram to strengthen a project's management of risks. The article will be based on previous literature on the subject<!-- as well as the author's personal experiences with the tool-->.