A community debrief should leave people with a useful next step, not the feeling that they have attended an unexpected tribunal. This is especially important after playing with a new group: you may not yet know how teammates prefer feedback, how much time they have or which parts of the evening they found difficult.
This short review format can follow a MegerSkill community session or another organised match. Ask whether people want to take part before starting. The time budget is a practical suggestion, not a rule or a claim about how any platform operates.
Open with the purpose and a stopping point
Say what you want to review and how long you intend to spend. “Could we use twenty minutes to look at one coordination problem before we finish?” gives everyone a clear invitation. Someone who needs to leave should be able to say so without being judged as uncommitted. If the group is upset, a later review may be more productive.
Choose one shared issue. An entire match contains too many decisions for a short conversation, and a list of every mistake usually produces defensiveness rather than understanding.
Describe a moment everyone can recognise
Use a round, timestamp or simple sequence instead of a broad label such as “bad teamwork.” Ask what each person knew at the time. Players see different parts of the situation, so a decision that looks obvious in a replay may have been uncertain from one viewpoint. Keep that difference visible.
For example, two players might have moved in opposite directions because each assumed the other was covering a position. The useful discovery is the unspoken assumption, not which person can deliver the sharpest criticism.
Keep observation separate from interpretation
Start with what happened, then discuss why it may have happened. “We made two different calls” is easier to examine than “no one listens.” Give people a chance to correct a mistaken observation. A review becomes less trustworthy when the first explanation is treated as a fact simply because someone sounded certain.
Make space for a useful success as well. If one handover worked clearly, identify what made it repeatable. Learning does not require pretending that every positive moment was accidental.
Choose one experiment for next time
Translate the discussion into a small action the group can observe. You might agree to confirm a request once, name who holds a position or state when a player is no longer able to support the plan. “Communicate better” is too vague to evaluate. “Confirm the first rotation call before moving” is something the group can notice.
Do not change every setting or role because one evening was disappointing. Keep the experiment narrow enough that you can tell whether it helped.
Finish with a short shared note
- The situation we reviewed.
- The information or assumption that mattered.
- One action to try in the next session.
- Who will remind the group, if everyone agrees.
- When we will check whether it helped.
Keep the note factual and avoid storing private information or embarrassing clips without permission. Ask before sharing it outside the group. You can use the GGS Playbook library to explore a specific skill afterwards, or follow the MegerSkill community links to plan another appropriate session. A good debrief does not prove who cares most. It makes the next evening easier to understand and easier to improve.





Join the conversation.
Ask a question, share what worked, or add your take.
No comments yet. Bring a useful question or a tip from your own experience.