What Did the Last Event Teach You?
A post-show review held within days, with every team in the room, turns one event's mistakes into the next one's plan.
Most event debriefs are a thank-you email and a survey. This guide borrows the after-action review and its four questions to turn one event's mistakes into the next one's plan. It shows who to invite, including the venue and the builder, how to keep facts apart from blame, and how to write each change into the next brief and floor plan.
A post-event review is a short meeting held within days of an event. Every team that ran the event compares what was meant to happen with what did. Most firms skip it. They send a thank-you email and a survey, and the same mistakes come back a year later. This guide gives a method borrowed from the army, with four questions, rules and a register that carries each fix forward.
Thank-you emails teach nothing
Most lessons from an event are small and concrete. Take two common ones. The first sign could not be seen from the main entrance. The follow-up email went out a week late. Neither needs a big fix. Each needs someone to write it down.
Both lessons are cheap to learn once and costly to learn every year. A survey asks guests how they felt. It cannot say why the signs failed or who should fix them. That takes the people who ran the event, together in one room.
The four questions of the after-action review
The US Army made the after-action review a standard habit. Its 1993 guide, A Leader's Guide to After-Action Reviews, describes a talk among the people who did the work. They find out for themselves what happened and why. It runs on four questions.
- What was meant to happen?. What it asks for: The plan. The event version: The brief, the floor plan, the run of show.
- What happened?. What it asks for: The facts. The event version: Times, counts, photos, the radio and decision log.
- Why was there a difference?. What it asks for: Causes. The event version: The late decision, the missing input, the check nobody ran.
- What will we change?. What it asks for: Actions. The event version: A change, an owner and the document it goes into.
The order matters. Agree on the plan first, then the facts, and only then the causes. Teams that jump to causes end up arguing about opinions.
Hold it within days, with every team
Hold the review within a week, while memories are fresh. But give the team a day off first, as the case against event burnout argues.
Invite every team that touched the event, not only your own. The venue's event manager saw the doors and the dock. The builder saw the load-in. The AV lead saw the cues, and the caterer saw the queues. The client lead knows what the client heard afterwards.
Ask each team to send three facts in writing before the meeting. A fact has a time and a place. "The coat check queue reached the front door at 7 pm" is a fact. "Arrival was chaotic" is not.
Keep facts apart from blame
A review fails when people start to defend themselves. Talk about what happened, not who did it. Ask someone other than the most senior person to run the meeting, so juniors speak freely. Let the crew speak before the producer does.
Treat a near miss as good news, because someone caught it. A near-miss log kept during the show gives the review its best facts. The job nobody sees explains how to keep one and why clients should see it.
Run the post-event review in one hour
- Five minutes. State the purpose and the rules.
- Ten minutes. Agree what was meant to happen, from the brief and the plan.
- Twenty minutes. Walk the timeline of what happened, from load-in to load-out.
- Fifteen minutes. For each gap, ask why until you reach a decision or a missing check.
- Ten minutes. Agree each change, its owner and where it will be written.
Write each change into the next brief and plan
A lesson that is not written into a document is just a story. Keep a change register, and give every line a home.
- First sign not seen from the main entrance. Change: Turn the sign to face the door. Owner: Designer. Goes into: Floor plan. Checked at: Plan review.
- Follow-up email went out late. Change: Draft it before the show. Owner: Client lead. Goes into: Run of show. Checked at: Final week.
- Coat check queue reached the door. Change: Move the coat check and draw its queue. Owner: Designer. Goes into: Floor plan. Checked at: Plan review.
- Load-in clashed with the caterer. Change: Book separate dock times. Owner: Producer. Goes into: Supplier contracts. Checked at: Contract stage.
Floor plan changes need extra care. Next year's plan usually starts from this year's file, and old mistakes travel with it. Zombie layouts shows how a file outlives its reasons. Mark each change on the plan with the review it came from.
Read the register first
Open the register when the next brief arrives, before anyone draws. A review only pays off when its changes show up in the next plan.
Frequently asked questions
What is a post-event review?
It is a short meeting held within days of an event, with every team that ran it. The group compares what was meant to happen with what did, finds the causes of each gap and agrees changes. Each change gets an owner and a place in the next brief or plan.
When should you hold an event debrief?
Hold it within a week of the event, while people still remember the details. Give the team a day off first, so they arrive rested. Ask each team to send three written facts beforehand, each with a time and a place.
Who should attend a post-event review?
Invite every team that touched the event. That means the producer, the designer, the client lead, the venue's event manager, the builder, the AV lead and the caterer. Each saw a part of the event the others missed, from the dock to the queues.
How is a post-event review different from an attendee survey?
A survey shows how guests felt. A review shows why things happened and who will change them. Use both. Bring the survey results into the review as facts, then trace each problem back to a decision or a missing check.
Many review findings end up as floor plan changes. In Monet, one change regenerates the plan, renders and drawings, and the exit, walkway and crowd-flow checks run again, so a lesson from the review reaches the next plan without a redraw.