Step 1 — The Effect
What problem are you analyzing?
Define the effect that sits at the head of the fishbone. Be specific and measurable.
✓
Be specificDescribe a measurable fact, not a vague impression.
✗
Don't assign blameFocus on the process, not on individuals.
✗
Don't suggest a solutionDescribe the symptom, not the remedy.
How to write a good problem statement?
A good problem statement is the foundation of the entire diagram. If you define it poorly, your categories and causes will go in the wrong direction.
Try to include:
- What exactly is happening (observable symptom)
- When it started or when it occurs
- Where — in which process, product, or team
- How often — one-time, recurring, constant
- What is the impact — on customers, revenue, team
Good examples:
- "Since March, customer support response time has increased from 2h to 8h."
- "In the last quarter, 15% of orders are shipped with a delay exceeding 48h."
- "Bounce rate on the pricing page jumped to 78% after the latest redesign."
Avoid: "We have a quality problem" (too vague), "John doesn't do his job" (blame), "We need to hire more people" (solution).
Step 2 — Categories
Choose your category framework
Categories form the major branches of your fishbone. Pick a preset or create your own.
Step 3 — Causes
Add causes to each category
Click a category tab, then add causes. Click a cause to expand sub-causes.
Step 4 — Review
Review your fishbone diagram
Check that all major causes are captured before exporting.
Diagram complete
Your fishbone diagram
Problem / Effect