Fishbone Diagram

Define the problem and scope

Define the effect in one sentence at the fish head, including the period, audience, and conditions. Keep proposed solutions out of the problem statement so the team studies the same event. Bring observations and reliable data to the session, and label unsupported claims as hypotheses.

Build categories and cause branches

People, methods, equipment, materials, environment, and measurement are starting categories rather than mandatory labels. Replace them with journey, policy, tools, or channels when those fit the subject. Put one category on each major branch and one specific possible cause on each smaller branch, merging duplicates.

Use it in a workshop

Ask participants to write causes independently, cluster similar notes, and review evidence before voting. Repeat why questions without blaming individuals; describe processes and operating conditions. Rank causes by impact and testability, then record an owner and a validation date outside the diagram.

Apply visual and access rules

Keep branch angles, line weights, label sizes, and spacing consistent. Do not rely on color alone to distinguish categories. Shorten long sentences into precise phrases, leave room for editing, and test small branches in screen sharing and print. Add verified text as editable layers instead of generating it inside the image.

Validate before sharing

Connect the completed diagram to a validation plan. Track the data source, test method, owner, and status for each priority cause in a separate table. Review whether correlation has been mistaken for causation, invite missing stakeholders, preserve version history, and share only after the team agrees on the next test.

Related prompts

• process-diagram
• diagram-design
• workflow-diagram