// description
A cause-and-effect diagram that maps potential causes of a problem into categories (often: People, Process, Equipment, Materials, Environment, Management) branching off a central "spine" — like the skeleton of a fish.
// history
Created by Japanese quality control pioneer Kaoru Ishikawa in the 1960s, the diagram was first used at Kawasaki shipyards to manage manufacturing quality. It became one of the seven basic tools of quality control and spread globally through the Total Quality Management movement of the 1970s–90s. Its visual structure makes it effective for team-based problem analysis because everyone can see and contribute to the cause map simultaneously.
// example
Problem: your Gumroad product has low conversion despite good traffic. Fishbone branches: People (buyers don't trust a new seller), Process (checkout is clunky, no clear CTA), Materials (product description is vague), Environment (competing products have more reviews), Management (no email follow-up sequence). Mapping this reveals multiple contributing causes rather than a single fix.
// katharyne's take
The fishbone is brilliant for problems that seem to have multiple causes at once — which is most real-world problems. When my KDP sales are weird, I map it out: listing quality, keyword targeting, cover design, category selection, external factors like algorithm changes. It stops me blaming one thing and genuinely examines the whole picture. I do mine on paper with a Sharpie, not in fancy software.
// creative uses
- Map a low-converting Etsy shop with a fishbone: branches for Listing Photos, Keywords/SEO, Product Description, Price, Trust Signals (reviews, shop history), and Traffic Source. Filling in each branch often reveals that the problem isn't where you assumed — low conversion is frequently a trust problem, not a product problem.
- Use a fishbone before launching a new digital product: map every possible reason a buyer might not purchase (no awareness, unclear value prop, no social proof, price objection, no urgency, technical friction at checkout). Each branch becomes a pre-launch checklist item.
- Apply the fishbone to an underperforming email sequence: branches for Subject Lines, Send Frequency, Content Relevance, List Quality, CTA Clarity, and Offer Strength. Visual mapping stops you from defaulting to "I'll just write better emails" when the actual issue might be a degraded list from an old giveaway.
// quick actions
- Take your most persistent, unresolved business problem and draw a fishbone on paper right now — spine pointing right, problem statement at the head, 4–6 category branches on the left. Fill in at least two causes under each branch before deciding which to address first.
- Use the fishbone categories People, Process, Materials, and Environment to audit your Etsy listing: People (who's your target buyer — is it clear from the listing?), Process (is the purchase flow smooth?), Materials (are your photos and description strong?), Environment (what are your competitors doing that you're not?).
- After any failed product launch, write the problem at the head of a fishbone and work backwards through every contributing factor. Share the diagram with a trusted peer or community for a second pair of eyes on causes you might have missed.
// prompt ideas
Run a fishbone diagram analysis on this problem: [describe your problem — e.g. my Etsy shop traffic is high but conversion is low / my KDP title ranked well but sales stopped after week 2]. Identify the most likely causes across these branches: Listing Quality, Keywords/Traffic Source, Trust Signals, Product-Market Fit, Price, and External Factors. For each branch, give me 2–3 specific causes to investigate.
My [course / digital product / Etsy shop] launch underperformed. Before I assume I know why, help me build a fishbone diagram to map all possible contributing causes. Use branches for: Audience Readiness, Offer Clarity, Marketing Touchpoints, Timing, Price, and Product Quality. Then help me rank which branches are most likely responsible based on what I can tell you about the launch: [describe what happened].
I've been getting a specific pattern of negative feedback on [my product / course / service]: [describe the feedback]. Use a fishbone diagram to help me trace this back to root causes — don't just accept the surface-level complaint. Identify which branches (people, process, materials, environment) are most likely contributing, and give me one concrete fix for the highest-priority cause.