Session Brief: Fishbone Diagram

Goal

Artifact: Fishbone Diagram

Working Question

Which possible causes across all relevant categories deserve data-driven deep validation as the next action?

Context

Problem sentence with time, frequency, and impact; known prior hypotheses; access to data (logs, KPIs, incident reports); list of people who worked close to the problem in the last four weeks.

Setup

• Format: Method session
• Duration: 30-60 min
• Mode: Workshop
• Participants: One facilitator, who separates categories from severity judgment; two to eight participants with direct process involvement (Operations, Engineering, Quality, Support); one scribe for clean transcription.
• Owner: One facilitator, who separates categories from severity judgment
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Fishbone Diagram. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with a pre-drawn Fishbone (head on the right, spine horizontal, 4-6 ribs); stickies; markers; timer; link to logs, tickets, or data that can support causes.

Preparation

Write problem in Fishbone head. Choose categories (classically 6Ms: Methods, Machines, Materials, Manpower, Measurement, Milieu; alternatively 4Ps for services). Set timer for first collection phase.

Agenda

1. Phase 1: Clarify the problem (5 min) Owner: Facilitator Action: Read and test the problem sentence, checking whether it is an observable symptom with time and impact. If not, rewrite it. Hint: "Performance is poor" is not a symptom. "P95 API latency on /orders > 800 ms since 2026-05-10" is. Without a symptom there is no Fishbone. Output: Fishbone Diagram

2. Phase 2: Choose categories (5 min) Owner: Facilitator Action: Define 4-6 categories as ribs. Use classic 6Ms for production, 4Ps (People, Process, Policy, Place) for services, or custom categories for context. Hint: More than six categories overloads participants. If a category stays empty, it is likely irrelevant for this problem and should be removed. Output: Cause Categories

3. Phase 3: Collect causes (20-30 min) Owner: Facilitator Action: Collect causes for each category for 5 minutes each, then share in sequence. Add causes as stickies on each rib. For each main cause, add 2-3 sub-causes (Why). Hint: If all causes land in one category, the group is one-sided or has a preformed model. Explicitly probe other categories. Output: Investigation Backlog

4. Phase 4: Prioritize (10 min) Owner: Facilitator Action: Mark causes by (a) likelihood and (b) data availability for verification. Label top 3-5 causes with owner and investigation method. Hint: Prioritize by likelihood, not favorite hypothesis. If no data is available, treat the cause as an investigation task, not an action. Output: Fishbone Diagram

5. Phase 5: Follow-up (5-10 min) Owner: Owner Action: Create investigation backlog: one concrete check action (log query, experiment, interview) per top cause with due date. Store the clean diagram as artifact. Hint: A Fishbone without investigation backlog stays a nice sketch. At least three investigation actions with dates are required for diagnostic value. Output: Cause Categories

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Fishbone Diagram

Closeout

• Update result artifact: Fishbone Diagram
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Fishbone Diagram: Fishbone Diagram

Working Question

Which possible causes across all relevant categories deserve data-driven deep validation as the next action?

Context

Problem sentence with time, frequency, and impact; known prior hypotheses; access to data (logs, KPIs, incident reports); list of people who worked close to the problem in the last four weeks.

Participants

• Owner: One facilitator, who separates categories from severity judgment
• Participants: One facilitator, who separates categories from severity judgment; two to eight participants with direct process involvement (Operations, Engineering, Quality, Support); one scribe for clean transcription.

Input

Whiteboard or Miro board with a pre-drawn Fishbone (head on the right, spine horizontal, 4-6 ribs); stickies; markers; timer; link to logs, tickets, or data that can support causes.

Template

Fishbone Diagram Working Template

Goal

Surface possible cause categories and likely root causes for a problem.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Working area

• Problem statement:
• Cause categories:
• Possible causes:
• Evidence:
• Likely causes:

Output artifacts

• Fishbone diagram:
• Cause list:
• Investigation backlog:

Open questions

• ...

Next step

Owner, date, and success signal.

Completion Check

• Fishbone Diagram is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision