A 10-minute post-show debrief that turns gig notes into rehearsal actions

On this page
Note: the source text I was given cuts off mid-sentence, so this rewrite sticks to the ideas that were actually there. The practical framing around them is general common sense, not extra claims about the original method.
A 10-Minute Post-Show Debrief That Turns Gig Notes Into Rehearsal Actions
The gig is over, and the room is full of distractions. Cases need packing, friends want to say hello, and everyone is thinking about the drive home. In the middle of all that, the useful information about how the show went starts to slip away.
A short debrief fixes this. It takes about ten minutes, and it does three jobs: it protects what went well, it points to what needs work, and it leaves your band with no more than three clear things to practice. This guide covers why it works and how to keep it short and useful.
Why the details disappear
Most players leave a show with a general feeling rather than a record. You might think, “That one section felt awkward.” That’s a real observation, but it isn’t much to act on.
By the next rehearsal, the feeling is still there and the details are gone. You can’t say which entrance (the moment a player or section comes in) caused the trouble. You can’t say which cue (a signal telling someone when to start, stop, or change) got missed. You can’t say which transition (the move from one song or section to the next) wobbled. Without those specifics, rehearsal turns into guesswork. You end up running whole songs again and hoping the problem shows itself.
The fix isn’t to remember harder. It’s to capture the specifics while they’re still fresh, which means talking soon after the show.
Photo by ANTONI SHKRABA production / Pexels
What the debrief is, and what it isn’t
It’s easy to assume that reviewing a show means a thorough critique. After a performance, that’s a bad idea. Everyone is tired, and adrenaline and fatigue make people either too harsh or too vague. A long post-mortem at that hour tends to drift into opinions about the whole night, which helps nobody.
Think of the debrief as a short, focused conversation instead. Its purpose is to pin down specific moments. It isn’t a verdict on the performance, a vote on who played best, or a place to relitigate every choice. When the talk stays tied to particular moments, it stays useful and stays short.
A few ground rules help:
- Keep it brief. The ten-minute limit is part of the method. Short sessions are easier to repeat after every show.
- Talk about moments, not people. “The entrance after the break” is something the band can fix together. “You came in wrong” starts an argument.
- Aim at rehearsal. Everything you say should end up as something to practice, or as something to protect.
Gather specific moments first
Start by collecting observations without judging them. Go around the group and ask each person for the moments that stood out, good or awkward. The more precisely people can name a place, the better. A song title plus the part of the song gives you a spot you can find again in rehearsal.
Pushing for specifics is the most useful thing whoever leads the conversation can do. When someone says “the middle felt shaky,” ask which song and what happened there. Was it an entrance, a cue, a transition? Even a rough answer is far more useful than a general impression.
Write things down as you go. A note on a phone is fine. The point is to get the details out of your heads and onto something you can look at before the next rehearsal, because your memory will have moved on by then.
Photo by cottonbro studio / Pexels
Sort what worked from what needs attention
Don’t skip the good moments. A debrief that only lists problems gives you a skewed picture and a gloomy mood, and it can make you change things that were fine.
Noting what worked does something practical: it tells you what to keep. If a transition felt smooth or an entrance landed cleanly, name it. That gives the band something to protect, and it stops you from fiddling with parts that already function.
Then turn to the rough spots. For each one, try to say what happened in plain terms. Who needed to do what, and when? You’re not hunting for blame. You’re trying to describe the moment clearly enough that the band can rehearse it on purpose.
Narrow it down to three actions
Now comes the step that makes the whole exercise worthwhile. Look at your list of rough spots and choose no more than three to take into rehearsal.
The cap matters. A long list of fixes feels productive in the moment, but it’s too much to work through, and it gets quietly ignored. Three clear actions are a realistic amount for one rehearsal. The rest can wait or may sort themselves out once the main issues are handled.
When choosing, ask which items would make the biggest difference next time you play. Then phrase each as something you can do, not something you feel. Compare these:
- Vague: “The ending of that song was messy.”
- Actionable: “Rehearse the entrance after the break in that song, and agree on who gives the cue.”
The second version tells everyone what to practice and what decision needs making. Aim for that kind of wording every time.
Make it stick
A debrief only pays off if the actions reach the rehearsal room. Before you leave, make sure someone has the three items written down and knows they’re responsible for bringing them up. Sending the list to the group is a simple way to do this, so nobody has to rely on memory.
At the next rehearsal, start with those items. Work on them early, while people are fresh, rather than leaving them for the end of the night when energy has dropped.
Over time, the habit builds on itself. Because the conversation is short and tied to specific moments, it doesn’t feel like a chore, and because it always ends in a few clear actions, rehearsals become more focused. You stop leaving gigs with only a vague sense that something was off, and you start walking into practice knowing exactly what to work on.
Sources
A 10-minute post-show debrief that turns gig notes into rehearsal actions, www.soundbrenner.com


