<?xml version="1.0" encoding="utf-8"?>

Contributing to retrospectives

Retrospectives turn experiences into learning opportunities. As a product owner, how you participate shapes team safety and growth. Balance leadership with being a team member by following the recommendations:

  • Join as a peer, not a boss. Retrospectives work best when everyone feels equal. Avoid dominating the conversation or defending decisions immediately. Listen carefully and acknowledge team perspectives, even difficult ones.
  • Show vulnerability by discussing your own areas for improvement. Share specific examples like "I changed priorities mid-sprint, which disrupted your work" or "I wasn't available quickly enough for questions." This honesty encourages others to speak openly, too.
  • Focus on actionable improvements, not just complaints. When issues come up, guide the conversation toward specific solutions. Ask "What process change would help prevent this problem?" Make commitments to address team concerns and follow through visibly.
  • Balance discussing problems with celebrating progress. Acknowledge team achievements and connect their work to customer impact whenever possible.

Pro Tip: Review notes from the previous retrospective before each new one to report on actions you promised to take. This shows your commitment to improvement.

Improve your UX & Product skills with interactive courses that actually work