Reviewing outcomes

Turn a finished session into concrete next steps for the table, the rules, and the next round of testing.

Review the session while it is fresh

As soon as the playtest ends, capture the strongest signals before memory gets cleaned up by hindsight.

Look for:

  • repeated confusion
  • surprising player behavior
  • bottlenecks or dead time
  • moments that created energy or clarity

Separate symptoms from fixes

First record what happened. Then decide what to change.

That separation helps you avoid overreacting to one session with the wrong solution.

Feed the next iteration directly

A useful review ends with concrete follow-up: update the table, adjust the prototype, or change the next survey so the next playtest answers a sharper question.