How to run a post-event debrief after a team outing

To debrief a team outing, ask a handful of people what worked and what they'd change within a few days of the event, then spend 15 minutes with whoever organized it going over the logistics, and write down one change for next time. That's the whole method. It works because most event problems (a room too loud to talk in, an activity that ran long, a menu with nothing for vegetarians) are obvious the day after and forgotten a month later.

This guide covers who to ask, the questions, how to run the organizers' review, and a template for keeping the notes.

Why a short debrief is worth the time

Debriefs are one of the better-studied habits in teamwork research. A 2013 meta-analysis in Human Factors pooled 46 samples (2,136 participants) and found that teams and individuals who held debriefs outperformed comparison groups by about 25% on average. The authors also found that debriefs worked better when they were aligned with a specific goal and had some structure, rather than being an open chat.

Those studies measured work performance, in medical and non-medical settings, real and simulated, not team dinners. The lesson that carries over is the structure: a few fixed questions, asked soon after, with the answers written down.

Ask attendees by hand, within a week

Pick four to six people and ask them directly, in person or by direct message. A group message asking for feedback mostly gets silence or "it was great!"

Choose people who will give you a range:

• someone new to the team
• someone who rarely comes to events
• someone who said no to this one (their reason is useful too)
• someone outside the usual social group

Our guidance is to ask within three to five days. After a week, people remember whether they had a good time but not why.

The four questions

1. What was the best part?
2. What would you change?
3. Was the time and place easy for you? If not, what would have been?
4. Would you come to something like this again?

Keep the questions open. A scale from one to ten mostly tells you that people are polite.

The 15-minute organizers' review

Within a week, sit down with everyone who helped plan the event. One person takes notes in a doc that will still exist next year, not a chat thread.

Go through it in this order:

1. What did we set out to do? Welcome new hires, celebrate a launch, get two teams talking. If there was no goal, write down what it turned out to be.
2. What went to plan? Start here on purpose. In a 2005 field study in the Journal of Applied Psychology, soldiers on navigation exercises who reviewed both their successes and their failures after each day improved more than those who reviewed only failures. Knowing what worked is how you repeat it.
3. What went wrong logistically? The venue was hard to find, the booking was for 20 and 26 came, the bill took 40 minutes to split. Facts only, no blame.
4. What did attendees tell us? Read out the answers to the four questions, without names.
5. What's the one change? Pick a single change for next time and put it at the top of the notes. A list of twelve improvements gets read once.

A template for the notes

Copy this into a doc and fill one in after every event. Over a few months it becomes your team's event playbook, which matters most when the person who usually plans everything moves on.

Event: [Name, type, date]

Goal: [One sentence]

Who came: [Number said yes / number attended / team size]

Cost: [Total and per person]

Worked: [Two or three things to repeat]

Didn't work: [Two or three things, factual]

What people said: [Short paraphrases, no names]

One change for next time: [Single item]

Venue notes: [Noise, private room size, accessibility, how to book, contact]

Group the entries by event type (dinners, outdoor activities, celebrations). After three or four of each, patterns show up: which venues work for groups over 15, how long an activity can run before people drift, which nights your team turns up for.

Use the answers on the next event

The debrief only pays off if the next planner reads it. Link the notes from wherever you keep the year's dates (the team event calendar guide has a setup for that) and open them before booking anything.

If attendance itself is the problem, the debrief tells you why people came; why people skip team events covers the reasons they don't. And to track whether events are improving over a longer stretch, see how to measure if your team events are working.

Where TeamOutings fits

TeamOutings keeps a record of each outing that helps when you fill in the template: the date, place and cost per person, the yes, no and maybe replies with any notes people left, the outing's chat, and the photo album. You can also poll the team on the activity, date or place for the next one.

It doesn't have surveys, feedback forms, reports or export, so the questions above are asked by hand and the notes live in your own doc. Attendance on the day is also yours to count: the headcount shows who said yes, not who turned up.