The goal of a retro is for a cross-functional team to write a crisp narrative of an issue, identify improvements, and an action plan. It’s one team having a candid conversation with a growth mindset. Typically the product manager writes it and shares it in advance of a retrospective meeting to seek input. 

Here’s my Retro Template, which contains the following sections: 

1. Issue Summary and Status
2. Details
3. Root Cause
4. Learnings
5. Action Plan

A similar format could also be used for sprint retrospective meetings. 

The issue summary must be written in words that a customer would understand. It must state the impact on the customer or the business. Then, use 5 whys till you get to the root cause. 

The key outcome of a retro is learnings that inform an action plan with assigned owners. The actions should resolve the current issue and also prevent this issue from occurring again.  

PS: Typically I write about building products. I write to pay it forward and to clarify my thinking.