Retrospective Template
Retrospective template for our quarterly product team review
No card required
What this brief specifies
Who's in the room
Product and engineering together, 14 people, mixed tenure, high trust but real tension between the two functions.
The quarter being reviewed
Q3: three major features shipped, one failed launch, only 60% of OKRs hit.
What has to come out of it
An honest, systemic, not blame-driven, diagnosis of the failed launch, plus three to four specific commitments for Q4.
What makes this hard
The bind here is that the retro is explicitly asked to stay systemic, not personal, in a room that already has real tension between product and engineering. Reaching an honest diagnosis of one failed launch, inside a quarter that also shipped three successful features and hit 60% of OKRs, means resisting two easy failure modes: relitigating existing friction under the banner of 'systemic' feedback, or playing it safe with vague commitments that dodge naming what actually broke. All of that has to happen in a fixed three-hour, in-person window, with 14 people in the room, not much space to both diagnose honestly and land specific, ownable commitments for Q4 if the conversation drifts.
Related use cases
See how Flaibo works for Founder.
Frequently asked questions
Carrying forward who's in the room, exactly what this quarter did and didn't deliver, and the outcome actually needed, a systemic diagnosis plus concrete commitments, not a blame session, means the template an AI assistant helps build can structure the three hours around that specific risk instead of a generic 'what went well' format. The next retro that has to turn a mixed quarter into honest, ownable next steps starts from that same structure instead of a blank agenda.