Product team retrospectivesacross discovery and delivery
Review discovery, decisions, handoffs, delivery, launch, and customer learning as one connected product system.
A product team retrospective inspects how discovery, decisions, delivery, and customer learning worked together. Invite product, design, engineering, and each partner who took part in the decisions or carried the work into the world. Keep ticket completion in context as one part of the product story.
Questions across the product loop
- Which customer evidence changed the plan?
- Which assumption outlasted the evidence behind it?
- Which decision arrived late or missed an important participant?
- Where did design, engineering, or go-to-market context break down?
- Which lesson appeared only after launch?
- Which outcome matters for the next experiment?
Run the conversation across the whole loop
- Name the product period, decision, release, or experiment under review.
- Put known evidence and team interpretations in separate groups.
- Give every function quiet time to add observations.
- Group patterns across discovery, decisions, delivery, and adoption.
- Prioritize the condition with the greatest effect on learning or outcomes.
- Choose one change and decide how the team will check it.
Formats for product teams
ROBIN covers Risks, Opportunities, Bright Spots, Improvements, and Next Steps. WRAP maps Wishes, Risks, Appreciations, and Puzzles. Sailboat gives a cross-functional group one picture of momentum, drag, risk, and destination.
Connect output to customer evidence
Completed tickets tell you something about flow. Customer value needs evidence from user behavior, support conversations, research, quality, and the decisions that shaped the work.