A finding connects feedback and the process
Feedback initially describes a perspective, not a cause. “The workshop was too hectic” could mean that the explanations were too fast, the start was delayed, or the group missed part of the lesson during a room change. To make your event debrief useful, connect the statement to a time, a situation, and an impact.
Use these fields for each finding: observation, source, impact, possible cause, and unresolved question. An explicitly fictional example: guests report missing the start of a workshop; the guest instructor remembers participants arriving continuously; the team noted that the room was made available late. Together, these details give you a coherent account, but they do not yet prove every suspected cause.
Keep the original goal alongside it so you can put complaints into perspective. A reference to your event concept with its target audience and participation format is enough. An intentionally open social calls for different standards than a progressive workshop.
The debrief ends with decisions about the process. Financial accounting and long-term customer retention remain separate tasks. Then add the agreed changes to the documents you use to organize your dance event, rather than creating a second, conflicting planning system. Also explicitly preserve processes that worked well as standard practice: otherwise, the next edition might change exactly what worked reliably.
