How to Run a Post-Event Debrief That Actually Changes What You Do Next Year

I have run post-event debriefs for 11 years and I have attended many that produced nothing more than a summary of what went right. Those meetings are enjoyable. They change nothing.

The problem is the question structure. “What went well, what could be improved” produces balanced feedback and social comfort. It doesn’t produce decisions. A debrief that changes what you do next year asks three different questions, in a specific order, and captures answers in a document that forces specificity.

The three questions that produce actionable outputs

Question 1: What cost money it shouldn’t have?

Not “what was expensive,” but specifically what spending produced no meaningful return. This is different from identifying line items that ran over budget. It’s asking which expenditures, in retrospect, had no effect on attendee experience, program quality, or organizational outcome.

Common answers I’ve collected over the years:

• “The printed program. We had 400 printed. 60 were picked up. The rest were recycled.”
• “The cocktail-hour entertainment. Attendees were in conversation and nobody watched the performance.”
• “The hotel room block on Thursday night. Most people arrived Friday morning. We paid attrition on 40 rooms.”
• “The AV production package for the breakout sessions. Those rooms had 30 people and a presenter with slides. We had a full AV technician stationed in each one for 8 hours.”

These answers directly reduce next year’s budget without reducing experience quality. The debrief that produces this question produces real savings.

Question 2: What did attendees miss that we didn’t provide?

This is the gap question. Not “what complaints did we receive,” but what did attendees try to do or access that didn’t exist? The answers usually come from informal feedback during the event, from post-event survey free text, or from observation.

Examples:

• “Three people asked where the quiet room was. We didn’t have one.”
• “Attendees were looking for a place to take calls between sessions. The lobby had nowhere to sit privately.”
• “The Friday night dinner had no agenda. People weren’t sure when they could leave.”
• “Nobody knew the shuttle schedule. We had it in the event app but people kept asking staff.”

This question produces additions to next year’s event that cost relatively little to implement: a reserved room for calls, a printed shuttle schedule at the venue entrance, a brief agenda note in the dinner program.

Question 3: What broke, and what is the systemic fix?

Not a list of complaints, but a root-cause analysis for each failure. The question forces the debrief to move past “the audio cut out in the general session” to “the audio cut out because the AV vendor didn’t conduct a soundcheck after the room reset from breakfast, and we didn’t have a soundcheck requirement in the run-of-show.”

The systemic fix is a process change, not a complaint about a vendor. The difference is important: firing an AV vendor and hiring a new one produces the same failure next year if the run-of-show doesn’t include a soundcheck requirement. Fixing the run-of-show prevents the failure regardless of which vendor you use.

Facilitation format

Run the debrief within 10 business days of the event. After 10 days, the specific details that inform the systemic analysis start to fade.

Participants: the core planning team (2-4 people), the venue coordinator if you have an ongoing relationship, and one or two stakeholders who were present for the full event. Not the full steering committee; not every vendor.

Duration: 75 minutes.

Structure:

• Minutes 0-10: brief recap of the event metrics (headcount, budget vs actual, any significant deviations)
• Minutes 10-35: Question 1 (what cost money it shouldn’t have)
• Minutes 35-60: Question 2 (what did attendees miss)
• Minutes 60-70: Question 3 (what broke, and what is the systemic fix)
• Minutes 70-75: document owners and deadlines

One person facilitates. One person captures the output document in real time, projected for the room. Both people see the same record being built, which prevents disagreement later about what was decided.

The output document

The debrief output is not a meeting notes document. It’s a decision log with four columns:

Category	Finding	Decision	Owner
Spending	Printed programs (340 unused)	Eliminate printed programs; use QR code at entry	Event coordinator
Gap	No quiet room for calls	Book 1 breakout room as quiet zone from 9am-5pm	Venue contact
Break/fix	Soundcheck gap after room reset	Add soundcheck to ROS after every room change	AV lead

Findings without a corresponding decision and owner don’t belong in the document. If the room agrees that something was a problem but nobody commits to fixing it and nobody owns the fix, it won’t change next year. Strike it from the table and address it separately or not at all.

The decision log travels into next year’s planning file. When you start planning the next event, open this document first.

What to ask attendees before the debrief

A post-event survey sent within 48 hours of the event provides raw material for Questions 2 and 3. Keep it to 5 questions:

1. Overall rating (1-5 scale)
2. Which session or moment was most valuable to you?
3. What did you try to do during the event that wasn’t easy or available?
4. If one thing changed for next year, what should it be?
5. Would you recommend this event to a colleague?

Questions 3 and 4 are your gap and failure data. Aggregate the answers before the debrief and bring them to the room as input.

Conference centers and hotels and resorts often offer post-event account reviews where the venue coordinator walks through what worked and what didn’t from their operational perspective. Ask for it. The venue sees things during an event that the planner doesn’t: load-in conflicts, kitchen timing issues, parking backups. That input feeds directly into Questions 1 and 3.

University venues frequently have event services staff who will provide a written post-event report as part of the rental agreement. Request it and bring it to the debrief. It often surfaces systemic issues that planners missed because they were managing a different part of the event.

The one thing the debrief cannot do

It can’t fix organizational decisions that weren’t planning failures. If the CEO changed the program format 10 days before the event and that change caused confusion, the debrief can document it, but the systemic fix is an organizational process change, not a planning process change. Be clear about the distinction. Planners who absorb blame for leadership decisions in post-event reviews burn out faster and change nothing.

The debrief output feeds directly into next year’s planning. When you rebuild the run-of-show based on this year’s findings, read how to build a run-of-show document for the column structure that makes the fixes visible to vendors. And if the debrief surfaces a budget issue, the event budget approval process that works above $100K gives you the framing to request an adjustment without starting from scratch.

What event are you debriefing, and which of the three questions do you expect to produce the most material?