Describe your game and current design question. Makeform creates a focused online survey for player context, rules friction, pacing, balance concerns, and actionable observations.
Send playtest responses to Google Sheets, Slack, and Zapier.
Sample prompts for your playtest
Choose a session, adapt its prompt, and edit the generated structure in Makeform.
Audience
Designers testing the core loop with invited players
Format
Short debrief with scales and incident notes
Prompt size
256 chars
Example feedback structure
Short debrief with scales and incident notes
Player count, role, and experience
How clear were the objective and turn sequence?
Where did play stop for a rules question?
Did any strategy seem dominant?
One change for the next build
Suggested routing tags
Rules clarity
Balance concern
Ready to retest
Ask for the moment behind a low score. The specific turn, card, or choice makes the rating useful.
Step 1
Set context
version, player count, roles, and session type
Step 2
Play
testers note confusing and decisive moments
Step 3
Debrief
ratings are paired with concrete examples
Step 4
Revise
patterns become changes for the next build
Better playtest evidence
Preserve the build, match context, ratings, and examples that tend to vanish after a post-game discussion.
Tie opinions to version, player count, role, and experience so unlike sessions are not analyzed together.
Follow low ratings with the exact rule, component, turn, or interaction that shaped the answer.
Consistent scales reveal repeated friction; open comments explain why it happened.
Designed around the test
Start with the decision the session needs to inform, then choose questions for that development stage.
Test whether turns create understandable, consequential choices.
Track setup, repeated lookups, and conflicting interpretations.
Record factions, seats, outcomes, key effects, and counterplay.
Keep required questions brief and separate players from observers.
Build the feedback loop
Generate a focused form and review responses against the question your playtest examined.
Choose learning, pacing, balance, replay interest, or a specific mechanic.
Edit scales, choices, terminology, and follow-ups for the current build.
Send it after play, or add brief checkpoints when recall matters.
Sort by version and issue, then create a small retest list.
Debrief options
Pair comparable questions with room for session evidence.
Field guide
Keep fields that support the current test and remove those that do not.
Session context
Capture version, setup, and group before opinions so sessions remain comparable.
Rules and onboarding
Ask what players expected, where they looked, and how they resolved uncertainty.
Choices and agency
Ask when alternatives felt meaningful and when players lacked enough information.
Pacing and engagement
Ask which phase dragged, whether off-turn play stayed engaging, and when the outcome felt settled.
Balance and counterplay
Pair outcome data with the combination, timing, and responses behind each balance concern.
Priorities and retest
Request one strong moment, one obstacle, one change priority, and optional retest interest.
Related tools
Use adjacent feedback, issue, and request forms when a playtest needs a separate intake path or a broader product research survey.
Collect structured reactions from invited testers across early versions of a physical or digital product.
Open toolCreate a wider survey for comparing satisfaction, usability, expectations, and improvement priorities.
Open toolGather participant feedback about group games, facilitation, enjoyment, pacing, and activity selection.
Open toolGive testers a separate route for reproducible component, rule, scoring, or companion-app issues.
Open toolCapture requested additions without mixing wish-list ideas into evidence from the current playtest.
Open toolCollect general product reactions from audiences beyond a scheduled board game testing session.
Open toolFAQ
Practical answers for designers planning useful post-session feedback.
Include build, player context, duration, rules clarity, pacing, choices, balance, and engagement. Pair ratings with the moment behind each score.
Send it immediately after the session. For long games, use brief round checkpoints and save overall judgments for the end.
Ask for an event, not only a preference. Follow low clarity or fairness scores with the rule, card, turn, response, and available counterplay.
Anonymous responses can ease criticism; identified responses support follow-up. Make names optional, require session context, and ask separately about future contact.
Yes. Route first-time players to onboarding and rulebook questions, and returning testers to version comparisons and emerging strategies. Keep a small shared set.
Capture setup, order, factions, outcome, and duration, then ask when the result felt decided and what responses existed. Treat one session as evidence to investigate.
Yes. Makeform offers unlimited free forms and responses. Create separate forms for versions or test types; the paid tier only removes Makeform branding.
Review responses in Makeform or route them to Google Sheets, Slack, or Zapier. Version fields and issue labels make builds and repeated signals easier to compare.
Make the next playtest easier to learn from.
