Team & Operations
Retrospective Template
Add this template to your Jamie account or sign up and try it.
Use template
A retrospective template is a structured format for documenting sprint, project, or period retrospectives. It defines what to capture from each session: what the team did well with specific examples, what did not go well or caused frustration, the key insights and learnings from the period, concrete improvement actions with owners and deadlines, and a review of action items from the previous retro. The goal is to produce notes that make retrospectives actionable rather than cathartic - so each retro produces a small number of specific changes the team will actually make, rather than a list of feelings that gets forgotten by the next sprint.
About this template
This template has five sections. Each one tells Jamie what to capture during a retrospective and how to structure the output.
Section 1: What Went Well
Lists what the team should keep doing - processes, practices, and behaviors that worked. With specific examples rather than vague statements.
Section 2: What Didn't Go Well
Lists what broke down, caused friction, or fell short - without blame. Captures the issue and the context, not the person.
Section 3: What We Learned
Captures the key insights and takeaways: what surprised the team, what assumptions turned out to be wrong, and what they would do differently.
Section 4: Action Items for Improvement
Lists concrete changes the team will make, limited to 2 to 3 with the highest impact. Each action has an owner, a deadline, and a way to know if it worked.
Section 5: Carried-Over Actions from Last Retro
Reviews the action items from the previous retrospective: what was completed, what is still in progress, and what was dropped and why.
Why Teams Use This Template
Retrospectives without action items are just complaints with an agenda
The purpose of a retro is not to vent - it is to produce a small number of specific changes that will make the next sprint better. A structured template that forces the conversation from observation to ownership to deadline is what makes that happen.
Previous retro actions that get dropped erode team trust
When the team commits to changing something in a retro and it never happens, the retro stops feeling worthwhile. A carried-over actions section that reviews previous commitments at the start of every retro creates accountability and makes the process feel real.
Specific examples are what make retro feedback useful
"Communication was bad" is not useful. "Requirements changed three times after development started because stakeholders weren't aligned before kickoff" is. A structured what-went-wrong section that encourages specificity produces feedback that can actually be acted on.
Retro notes shared with the broader team create organizational learning
When retro notes are structured and shareable, the learnings from one team's sprint can benefit other teams working on similar problems. Jamie produces structured notes automatically within minutes of the retro ending.
How to Use This Template in Jamie
Jamie works natively on your device. No bot joins your call, no meeting link needed. Use it across every online platform, capture in-person meetings via your laptop or phone, and get structured notes in 100+ languages - and your data stays on EU servers, fully encrypted, GDPR compliant.
Step 1: Add the Retrospective template in Jamie under Settings > Templates - or click Use this template to load it automatically.
Step 2: Start your retro on any platform: Zoom, Teams, Google Meet, or in person.
Step 3: Within minutes of the retro ending, your notes appear structured in five sections.
Step 4: Switch templates after the fact if needed. Jamie regenerates the summary in the new format.
Built for agile and product teams
Jamie processes and stores your data only within the EU. All data is encrypted with AES-256 in transit and at rest. No third-party bot sits in your call. Audio is streamed for transcription and never stored. The template works with any meeting platform and handles meetings in 100+ languages.
FAQS
A retrospective template should include five sections: what went well with specific examples, what did not go well with context rather than blame, key learnings and insights, 2 to 3 concrete improvement actions with owners and deadlines, and a review of carried-over actions from the previous retro.
The single biggest lever is limiting improvement actions to 2 to 3 items with a specific owner and deadline - rather than a long list that no one owns. A structured template that moves from observation to ownership forces that discipline. Teams use Jamie to apply the retrospective template automatically, so structured notes are ready within minutes of the retro ending.
Retro documentation needs to capture both the observations and the commitments. When every retro produces notes in the same five-section format, the team can track whether previous improvements were implemented and whether they worked. Jamie applies the template automatically after every retrospective.
The most reliable method is starting every retro with a review of the previous retro's actions - what was completed, what is in progress, and what was dropped. The Jamie Retrospective template has a dedicated carried-over actions section that makes this review the first item on every retro agenda.
Yes. Jamie works natively on your device with no bot joining the call. This is particularly relevant for retrospectives, where honest reflection about what went wrong requires a psychologically safe environment - and a visible recording bot can inhibit that.
