Website traffic drop root-cause analysis
Ishikawa fishbone for a website traffic drop — six causal categories covering content, technical SEO, backlinks, UX, competition, and algorithm changes.
For the ops lead
Scenario
An ops lead runs a growth post-mortem after a 30% organic traffic drop. The Ishikawa (fishbone) diagram structures the team's brainstorm into six standard causal categories, preventing the meeting from fixating on the most vocal hypothesis while ignoring systemic causes. The completed diagram becomes the project brief for the remediation sprint.
Annotation key
effect "..."— the problem statement, placed at the fish's head (right side)category id "Label"— defines a major causal branch (a "bone"); use a shortidto assign causesid : "cause text"— assigns a cause string to the named category branch- Each category renders as a diagonal rib pointing toward the effect
- Sub-causes (second-order) can be added by nesting if the DSL supports it
How to read
The effect (traffic decline) sits at the right. Six causal ribs branch from the spine: Content, Technical, Backlinks, UX, Competition, and Algorithm. Each rib lists four specific hypotheses. In a workshop, the team votes on each cause, color-codes high-confidence ones, and converts the highest-priority items into action items. The diagram serves as both a brainstorming artifact and a living post-mortem document.