Stage and performance
Run a useful debrief after a performance
A useful debrief ties each point to a moment that can be named. For every item, record what happened, what shows it, what effect it had, one change to try and who owns it. Keep taste and operational problems in separate lists.
A text to start with
We just finished [performance name]. My notes on what happened: [moments, issues, audience or crew observations]. People involved: [roles]. Organize these into a debrief with what happened, the evidence, the effect, one change to try and an owner. Separate operational problems from matters of taste, and mark anything where the cause is not yet known.
Example request. Change the details to fit your situation.Debrief record
Performance and date: [ ] People present at the debrief: [ ] What happened: [ ] Time or moment: [ ] Evidence, such as a recording or cue sheet line: [ ] Effect on the show: [ ] Type: [operational / taste] Cause known: [yes / no, and how to find out] Change to try: [ ] Owner: [ ] How we will tell it worked: [ ] Date to revisit: [ ]
Keeping feedback fair
Sort each point into operational or taste. A late cue, a blocked exit or a missed handoff can be checked and fixed. A preference about a performance choice is a discussion, not a defect. Watch for blame attached to a person where the evidence only shows an outcome, since a missed cue may come from an unclear sheet. Each claim should point to a specific moment or record. Where the cause is unknown, say so and plan how to find out. Every change needs an owner.
Ask another agent to check the result
Read this debrief and separate the points that are operational problems from those that are taste. Find places where blame falls on a person without evidence, and any problem listed without a moment, a cause or an owner for the proposed change.
Turn notes into trials
Share the debrief with the people it names and invite corrections before it is final. Pick a small number of changes to try at the next rehearsal or show and confirm each owner agrees. Write down how you will know a change worked. Hold taste points for a separate conversation, and store the notes where the next production team can find them.