The point of running a playtest is the next version of your game. This page covers reviewing the results of a playtest, both what to look at and how to turn observations into tasks.

What this page helps you do

See all responses for a playtest in one place.
Spot patterns across responses (vs. one outlier opinion).
Capture what you learned in the playtest record.
Turn observations into tasks on your project board.

Open the results page

Open the playtest from the Playtest Hub and click Results (or the tab equivalent). You'll see:

Total responses so far.
Each response listed with timestamp and (if collected) the playtester's name or email.
A small summary section with aggregate stats for choice and rating questions.

Read individual responses

Click into a response to see the full set of answers. Long-text answers often contain the most actionable insight, read them carefully and look for:

Specific moments the playtester remembers (positive or negative).
Confusion about rules or components ("I thought X meant Y").
House rule suggestions, even if they're not what you'd implement, they signal where the rules-as-written are unclear.
Pace complaints (too long, too short, dragged at X stage).

For long-text fields, copy striking quotes into the playtest's description or notes for later reference.

See aggregate patterns

Choice and rating questions roll up automatically:

Single choice: bar chart of how many people picked each option.
Multiple choice: same, but options can stack.
Rating: distribution of scores, with average and median.
Yes / no: count of yes vs no.

Look at the distribution, not just the average. A 4-out-of-5 average can hide a polarized "half loved it, half hated it", that's a different problem than "everyone thought it was fine."

Look for recurring themes

If five out of seven players said the same thing in different words, that's a signal. If one player said something nobody else mentioned, it might be a real issue or it might be that one person, gather more data before acting.

A simple way to surface themes: re-read all long-text answers in one sitting and tag each response with one or two short labels in your head ("scoring unclear", "endgame drags", "loved the cards"). Recurring tags are your themes.

Capture what you learned

In the playtest's description or notes, write a short summary:

What worked. Things the playtest confirmed; don't change these.
What didn't. Specific issues raised by multiple players.
What you'll change in the next version. Concrete actions.
What's still uncertain. Questions for the next playtest.

This summary is the bridge between feedback and action. Future-you will thank past-you when you come back to design after a few weeks.

Turn results into tasks

Each "what you'll change" item should become a task on your project board.

The fastest path:

Open the playtest's notes / summary.
For each change item, click Create task (or open Boards in another tab and create one manually).
Title the task with the change ("Rebalance scoring track to slow the leader").
Link back to the playtest in the description so the context isn't lost.
Move the task to the right column on the board (usually Backlog or To do for v0.8).

For a back-to-back planning session, batch-create all the tasks first, then prioritize.

Mark the playtest done

Once you've extracted what you can, change the playtest's status to Done (or Reviewed). The hub will show it as concluded; you can still come back to read responses anytime.

Tips & common questions

Can I export responses to CSV? CSV export of playtest responses is on the roadmap. For now, copy a filtered list into a spreadsheet manually if you need it elsewhere.

Can I delete a single bad response? Yes, open the response and pick Delete from its menu. Use sparingly; including all responses (even the ones you disagree with) keeps the data honest.

A response was submitted twice, duplicate. Delete the duplicate. Sometimes playtesters click submit twice on a slow network.

Can I share results with someone outside Boardssey? Not as a single shareable view today. You can copy the summary out manually or take screenshots. Internal team members with project access can see the results page.

How long are responses kept? Responses persist for the lifetime of the playtest. Deleting the playtest deletes its responses too.