Loading content
The Fishbone Diagram, also known as the Ishikawa Diagram, is a tool for root cause analysis that helps identify the most common problems in processes. It allows teams to systematically capture and categorize causes in order to develop solutions.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A fishbone diagram organizes possible causes of an observed problem in a visual structure resembling a fish skeleton.
Kaoru Ishikawa developed the diagram in Japan's quality management in the 1960s to help teams analyze causes systematically. It is therefore also called an Ishikawa or fishbone diagram.
Put the effect at the head and collect possible causes as main bones. Sub-causes branch beneath them; categories support a complete view. The diagram records hypotheses that must then be tested with data.
The clearly stated problem defines the focus of analysis.
Categories structure different areas of influence.
A deeper condition explains an observed effect more adequately.
Data tests which suspected causes actually contribute.
The diagram supports teams investigating defects, quality problems, and improvement opportunities. It generates hypotheses rather than proving causality; fact checking and prioritization remain necessary.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.