Fishbone (Ishikawa) Retrospective

Fishbone Retrospective Format

System

What technology, software, or tools might be affecting our team's performance or outcomes?

Guide the team in examining technical infrastructure, software tools, and systems integration points. Encourage participants to think about both obvious technical issues and subtle system interactions that might impact their work.

Process

What workflows or sequences of activities are causing delays or inefficiencies in our work?

Focus on identifying bottlenecks, redundancies, or gaps in workflows. Help the team distinguish between process issues and other factors by asking about specific steps in their work procedures.

Forms

What issues with our templates or documentation could be impacting clarity or accuracy?

Examine documentation quality, accessibility, and completeness. Consider both formal and informal documentation, and how well it serves its intended purpose.

People

What factors related to individual or team skills, communication, or roles are affecting our success?

Address team dynamics and individual contributions while maintaining a blame-free environment. Focus on systemic issues rather than personal criticism.

Policies

What guidelines or rules might be misaligned with our actual practices or creating challenges?

Explore both formal and informal policies that impact work. Consider whether policies support or hinder current team needs and practices.

Place

What aspects of our physical or virtual workspace might be impacting our collaboration or productivity?

Consider both physical and virtual work environments. Include factors like tools, workspace layout, and remote collaboration capabilities.

When to use this retrospective

• When facing complex problems that may have multiple root causes or contributing factors
• After identifying a significant issue or challenge that requires systematic analysis
• When the team needs to move beyond symptoms to understand underlying causes
• During project post-mortems or incident reviews to prevent future problems

Suggested icebreaker questions

• If our team were a machine, what part would need the most maintenance right now?
• What's the most surprising solution you've discovered to a recurring problem?

Ideas and tips for your retrospective meeting

• Start with the effect or problem statement clearly defined at the 'head' of the fish
• Encourage equal participation from all team members across all categories
• Focus on identifying causes rather than jumping to solutions too quickly
• Use the 'Five Whys' technique within each category to dig deeper into root causes
• Document all insights, even if they don't initially seem significant
• Schedule enough time (90-120 minutes) to explore all categories thoroughly