Retrospective

What it does

This skill facilitates running a Product Retrospective, helping teams reflect on their work and identify areas for improvement. It guides the process through distinct phases like "What Went Well," "What Could Be Improved," and "Action Items." The retrospective focuses on outcomes rather than individual blame, fostering a culture of continuous learning within product teams.

When to use it

• After completing a significant sprint or project milestone to assess progress and identify adjustments.
• When team morale is low or productivity has stalled, to uncover underlying issues and rebuild momentum.
• To proactively surface process inefficiencies before they become major roadblocks.
• During regular cadence (e.g., monthly) to ensure consistent reflection and adaptation.

Key capabilities

• Guides users through the "What Went Well," "What Could Be Improved," and "Action Items" phases of a retrospective.
• Facilitates structured discussion around outcomes, not individual performance.
• Helps teams identify actionable steps for future improvement.
• Provides a framework for consistent retrospective practice.

Example prompts

• “Let’s run a product retrospective on the last sprint.”
• "Guide us through a retrospective focusing on our recent feature launch."
• "Facilitate a retrospective to understand why we missed our deadline."

Tips & gotchas

This skill is most effective when used with a team committed to open and honest feedback. Ensure all participants understand the focus on outcomes and continuous improvement, not individual accountability.