Turn the show into something you can learn from.
Bring the team together while the experience is fresh. Make room for the wins, the challenges, and the contributions that made a difference.
Ask the questions that move the team forward
What went well?
Talk about specific conversations, preparation, teamwork, and visitor experiences.
Where did we struggle?
Describe the situation and its effect. Give quieter team members room to contribute.
What will we do differently?
Choose changes your team can act on. Close with responsibilities, not a list of unresolved complaints.
Celebrate the contribution, not just the total
Highlight the work behind the results: the person who solved a difficult question, covered a teammate, or captured the detail that made follow-up possible. Share verified event results and explain how they connect to the company’s goals.
Make recognition specific
Use a newsletter feature, a team acknowledgment, or an event-photo post to name the contribution. Include people behind the scenes as well as those in the booth.
Bring the team together
A team lunch, dinner, or informal gathering can give people time to reconnect and recognize what they achieved together.
Connect the work to the outcome
Share what the event actually produced. Keep contacts, qualified opportunities, scheduled meetings, and closed sales clearly distinguished.
MAKE IT YOUR TEAM’S PLAN
Run a debrief that leads to action.
this workshop recommends a team debrief in the week after the show. Use these prompts to make it concrete.
See a filled-in example
Illustrative example. Replace with your own team’s decisions.
Northline Filtration · ProcessTech Expo
Our debrief: when, who, and facilitatorOctober 27, 2026, 10:00–10:45 a.m., with Maya Chen facilitating and Priya Shah taking action notes; Luis Ortega and Eli Brooks attend. Bring the CRM export, spend sheet, coverage notes, and recurring visitor questions. Spend 10 minutes comparing goals with the current count, 10 on what worked, 10 on friction, 10 assigning improvements, and 5 recognizing contributions. Review booked meetings again on November 5 because the target deadline is still ahead of the debrief.
What worked well?Illustrative outcome: after removing duplicates, Priya recorded 112 contacts and 48 qualified leads against a goal of 45. All 48 had a named owner and next action at the October 27 audit. Eight follow-up meetings were booked by the debrief; the November 5 checkpoint recorded 13 against the goal of 12. The short switching demo and named handoffs helped the team keep conversations focused. Booked meetings are not closed sales, and the sample makes no revenue claim.
What should we change?The demo queue twice overlapped the reception point during the busiest period on October 21. Move the demo farther along the side wall and test the route with four visitors before the next build. Six initial lead notes lacked operating conditions; Luis will add one prompt to the lead card and Eli will practice asking it. Three technical replies required more data than the team expected; agree an explicit status-update date as well as an answer date. Priya corrected the incomplete qualification fields before the final audit.
Who deserves recognition—and for what?Priya caught duplicate records and missing next steps each evening, making the next-day follow-up usable. Eli delivered the promised material and kept one owner on each conversation. Luis explained what the demo could and could not establish and converted unknowns into clear application-review tasks. Maya protected the entrance during peak traffic and covered the final hours so packing did not replace the welcome. Recognize these specific actions at the debrief and keep them in the next team briefing.