Your team finished the project. Or the launch. Or the quarter. Or the offsite. Someone scheduled a debrief. Someone asked you for the team debrief template.
You can find one in five seconds. They're all variations of the same form. What went well. What didn't. What would we do differently. Lessons learned. Owners and dates.
You'll fill it in. The team will fill in their parts. You'll come out with a clean document. Three months later, the same problems will show up on the next project.
The team debrief template is not the problem. The problem is that a debrief template is a form, and a form only produces honest answers if the team has practiced the behaviors the form requires. Without those behaviors, a debrief becomes theater. Everyone knows the script. Nobody learns anything new. The form gets filed.
This page is both — a workable template you can run today, and the four behaviors that decide whether the template generates insight or recycled politeness.
The Team Debrief Template
The template below is intentionally short. A debrief that takes longer than 90 minutes loses its honesty curve. People relax their candor as fatigue sets in. Schedule 75 minutes, end by 90 hard, and put the harder questions earlier in the agenda.
Section 1: What Did the Team Actually Set Out to Do?
(5 minutes — write before discussing.) Each team member writes — silently — what they understood the goal of the work to be. Not the official goal on the kickoff slide. Their actual operating goal as they did the work. Reveal the silent answers at the same time.
If the answers diverge, that's the most important data the debrief will produce. It tells you the team was working on different things and didn't notice. The rest of the debrief is informed by that finding.
Section 2: What Worked? (Three Concrete Examples)
(10 minutes.) Not vague praise. Three specific moments, decisions, or behaviors that worked, and why they worked. Naming concrete examples lets the team replicate them. "Communication was good" doesn't replicate. "When Priya called the customer directly on day three instead of routing through account management, we got the requirements clarified in 20 minutes instead of two days" replicates.
Section 3: What Didn't Work? (Three Concrete Examples)
(15 minutes.) Same rule. Three specific moments where the work stalled, the wrong decision was made, or the team dynamic got in the way. Same specificity. "We had communication problems" doesn't help. "When the spec changed in week four, the engineering team didn't know for nine days, and we built two features that got cut" helps.
This is the question the form asks but the team rarely answers honestly. The four behaviors below are what determines whether you get specifics or generalities here.
Section 4: What Did We Avoid Saying? (5-Minute Silent Write)
(5 minutes — silent write, then go around.) Each team member writes one thing they thought during the project but didn't say. Could be a doubt about the strategy. Could be a frustration with a teammate. Could be a question they didn't ask because they thought they should already know.
The team reads. The room can ask clarifying questions but cannot debate or judge. The point isn't to relitigate the project. The point is to surface what got buried so the team knows whether silence is a pattern.
Section 5: What Will We Do Differently — Specifically?
(15 minutes.) For each "didn't work" item, name one specific behavior change for the next project. Not a principle. A behavior. "Improve communication" is not a behavior change. "Standing 15-minute spec-change call within 24 hours of any change" is.
Each behavior change gets a single owner and a check-in date — usually two weeks into the next project, when the new behavior either holds or quietly slips.
Section 6: What Did We Learn About Each Other?
(10 minutes.) The relational learning, not the operational learning. What did each member of the team see in someone else that they hadn't seen before? Strengths surfaced. Surprises about how a teammate handled pressure. The five-minute version of this question is often the one the team remembers a year later.
Section 7: Wrap
(5 minutes.) The facilitator names the three behavior changes, the owners, and the check-in dates. The document gets sent out within 24 hours. No editorializing. Just the record.
Total: 65 minutes if the team is sharp, 90 if it's a complex project. End on time even if you didn't get to everything. Discipline on time pressure protects future debriefs from getting cancelled because "the last one ran long."
The Four Behaviors That Decide Whether the Template Works
The template is designed to surface honest material. It does that only if the team can do four things. If they can't, the form will get filled with safe answers, and the debrief will produce no learning. Worse, the team will start to dread debriefs because they feel performative.
Behavior 1: Treat Bad News as Information, Not Indictment
When a teammate says "this didn't work because of X," the room cannot interpret X as an attack. The default interpretation has to be: this is information about how we work, not a complaint about a person. Most teams haven't practiced this. The first hard answer becomes a defended position, and the rest of the debrief turns into a series of defensive responses.
If your team can't separate the data from the person who delivered it, your debrief template needs an upstream intervention before it'll work. That intervention isn't "tell people to be more open." It's lived practice — situations where the team has to surface bad information together and watch the consequences land neutrally. The capability is buildable. It usually isn't built in a meeting room.
Behavior 2: Suspend Hierarchy for the Duration of the Conversation
A debrief works only if the most junior person in the room can name a problem the most senior person caused without political risk. Most debriefs fail this test silently. The junior person learns to read the room and softens what they say. The leader doesn't notice because the answers sound clean.
The fix isn't a rule about "all opinions matter." The fix is the leader actively asking: "What did I do during this project that made your work harder?" — and then receiving the answer without explaining or defending. Once the team sees that question land cleanly, future debriefs get more honest. Until they see it, the form will keep producing safe answers.
For more on what happens to teams that haven't built this capability, The Psychological Safety Test Most Leaders Fail maps the gap between thinking your team has psychological safety and being able to test it.
Behavior 3: Stay With the Specific, Avoid the Abstract
When the team starts trading principles, the debrief is over. "We need better communication" is not data. "Communication was an issue at week three when the spec changed and we found out three days later" is data. Principles can't be acted on. Specific moments can.
The facilitator's job is to interrupt every abstract claim with a specific request: "When did that happen? Who was there? What was said?" If the team can't produce specifics, that means either (a) the issue isn't real and they're inventing one to look like they're learning, or (b) the issue is real but uncomfortable enough that they're hiding it behind generalities. Either case is worth surfacing.
How to Capture Ideas Before They Disappear gets at the meta-skill: most useful insight is specific and easily lost. The debrief is one of the few moments when the team has the chance to capture it.
Behavior 4: Treat the Output as a Working Document, Not a Memorial
The biggest signal that a debrief produced no learning is that the document gets sent out, filed, and never read again. The output of a real debrief should sit on the next project's kickoff agenda. The three behavior changes named at the end of the debrief should appear at week-two stand-up of the new project, with a 30-second review of whether each one held.
If the document doesn't reappear in the next project, the debrief was theater. Honest debrief output looks like a punch list of behavior changes that the team is actually implementing, not a polished narrative summarizing the last project for the file.
Why Most Debriefs Don't Produce Learning
Three patterns recur across debriefs that fill in the form but produce no change:
The team mistakes politeness for safety. A debrief where everyone agrees about what went wrong and nobody surfaces a real disagreement isn't a safe debrief. It's a managed one. Real debriefs include constructive disagreement and recovered honesty. If yours doesn't, the absence of conflict is a signal, not a credit.
The leader speaks first. When the most senior person in the room sets the framing for "what worked" and "what didn't," the rest of the team calibrates to that framing. The data gets compressed into the leader's view of the project. The fix is a simple structural change: the leader speaks last in every section. They listen to four perspectives before adding their own.
The team doesn't decompress before debriefing. A debrief held the day after a difficult launch usually gets the wrong material. Either the team is still in adrenaline and overstates the wins, or they're depleted and overstate the losses. Wait two business days. Hold the debrief on a calm morning. The signal-to-noise improves dramatically.
For the deeper version of why teams under pressure say one thing and do another, Groupthink Examples Teams Should Recognize Before They Become One maps the same dynamic in real time.
How a Debrief Connects to After-Action Review
If your team runs after-action reviews already, the team debrief template above is the same instrument with a different name. The terminology comes from the military tradition; many product and operations teams have adopted it. The mechanics are the same: structured questions, honest answers, behavior changes named for the next cycle.
For the AAR-tradition view of the same work, After Action Review Template walks through the structure with the four AAR-specific questions and how to make the next round of work different from the last one.
What a Real Debrief Produces
Most debriefs produce a document. A real debrief produces three things:
Specific behavior changes the team will implement on the next project. Not principles. Not aspirations. Behaviors. With owners. Reviewed at the two-week mark of the next project to see if they held.
A more honest team. Each successful debrief makes the next debrief easier. Each performative debrief makes the next one harder. The trajectory either compounds toward useful learning or compounds toward filed paperwork. There's no neutral.
Confidence in the team's collective intelligence. Teams that can see themselves clearly trust their own decision-making more. They stop relying on the leader to tell them what they did wrong. They develop the capability to course-correct in real time, not just in retrospect. That capability is the actual point of running debriefs at all.
For the structural intervention that builds the capability — putting a team into pressurized conditions where they have to debrief in real time, not retroactively — the Save the Titanic experience was designed to compress a year of debrief skill into 3.5 hours. The simulation surfaces decision patterns. The structured debrief that follows turns those patterns into specific behavior changes the team can use the next week.
How to Run This Template Tomorrow
If you have a debrief on the calendar in the next two weeks, replace whatever template you were planning to use with the seven sections above. Schedule 75 minutes. Print one copy of the questions for each person.
Have the leader speak last in every section. Don't allow the conversation to drift into principles. When it does, ask "when did that specifically happen?" and bring it back to the moment.
End with three behavior changes, three owners, three check-in dates. Send the record within 24 hours. Put the three changes on the agenda of the next project's kickoff.
If the debrief was honest, you'll know within ten minutes — by the second answer to "what didn't work," the team is producing material the leader hadn't already seen. If the debrief was theater, the leader will be the only person speaking in detail by section three. That's diagnostic, not failure. It tells you the team needs upstream work on the behaviors before any future debrief will surface anything useful.
Watch how the Save the Titanic experience works — it shows what the upstream work looks like when the goal is to install team-level honesty before the project that needs it.
Read next: After Action Review Template