Recent chats

How do I turn a playtest comment into a specific design question?

Quick answer

Separate a comment into what happened, what the player said they felt or thought, and any change they proposed. Keep missing details marked as unknown, and treat a proposed fix as an idea rather than proof of the problem. Then ask one focused question about the player experience you want to understand, such as whether players can notice a symbol when choosing an action.

LET’S WORK THROUGH IT

The question, the details, the next step.

Question

I have a pile of playtest notes, and some mix what happened with what people think I should change. How should I sort them?

Geez

Make three columns: Observation, Reaction, and Proposed fix. Put a directly observed action or event in Observation. Put the player’s stated feeling or judgment in Reaction. Put their recommended change in Proposed fix. Leave a column blank if the comment doesn’t contain that kind of information; don’t guess what the player meant.

For example, imagine a player says, “I missed the symbol twice; it’s frustrating. Make it glow.” You might sort it like this:

  1. Observation: “I missed the symbol twice.” If your note-taker saw this happen, record the relevant moment or action. If it is only the player’s recollection, label it as their report.
  2. Reaction: “It’s frustrating.”
  3. Proposed fix: “Make it glow.”

These parts serve different purposes: the observation helps locate a moment to examine, the reaction records what the player said, and the suggestion offers one possible solution. None alone proves what caused the difficulty.

Follow-up question

What if the comment is vague, like “That part was confusing”? I don’t want to put words in the player’s mouth.

Geez

Keep the vagueness visible rather than filling it in. Record the reaction as “Player described the part as confusing,” and mark the observation as “Not specified” unless your notes identify a particular moment. Don’t turn “confusing” into a claim about unclear rules, artwork, or controls without more information.

You can add a follow-up for a future conversation or test: “Which moment felt confusing, and what were you trying to do then?” If you ask during a session, avoid suggesting an answer. For instance, “Was the icon hard to see?” points toward one explanation; “What were you looking at when you decided what to do?” gives the player room to describe their experience.

Follow-up question

How do I turn the sorted comment into a design question instead of simply accepting the suggested fix?

Geez

Ask about the player experience or design goal underneath the suggestion. Name the situation and what you want to find out, without assuming a particular solution.

Using the symbol example, “Should we make it glow?” mainly asks whether to adopt one proposed fix. A more useful design question might be: “Can players notice and identify the symbol when they need to choose an action?” That question leaves room for several possible responses—or for finding that visibility was not the issue.

Keep the question narrow enough to investigate. If it includes multiple moments or goals, split it. Try this template:

When [specific situation], can players [intended action or understanding]? What did they notice or do?

For the hypothetical symbol comment: When choosing an action, can players notice and identify the relevant symbol? What do they look at or do before choosing? Treat this as something to examine, not a conclusion about the design.

Follow-up question

Can you give me a worksheet I can reuse on a whole set of comments?

Geez

Copy this for each comment. Keep the original wording so your interpretation doesn’t replace what was actually said.

Playtest comment worksheet

  • Original comment: [exact note or clearly labeled paraphrase]
  • Context: [what was happening, if recorded]
  • Observation: [specific action or event; otherwise “not specified”]
  • Reaction: [the player’s stated feeling or judgment; otherwise “not stated”]
  • Proposed fix: [the player’s suggestion; otherwise “none”]
  • What remains uncertain? [what the note does not tell you]
  • Design question: [one focused question about the experience or goal]
  • Possible next step: [review this moment, ask a neutral follow-up, or plan a later test]

For the hypothetical comment, the question might be, “When choosing an action, can players notice and identify the relevant symbol?” The note alone does not establish why the player missed it or whether making it glow would help. Preserve that uncertainty and use the question to decide what to examine next.

A practical checklist

  • Keep the original comment, or label any paraphrase clearly.

  • Separate observable events from the player’s stated reaction.

  • Record a proposed fix as a suggestion, not an established solution.

  • Mark missing details as “not specified” instead of filling them in.

  • Write one focused question about the intended player experience.

  • Choose a next step that can help examine that question.

A few more useful answers

Should I include every playtest comment in the worksheet?

Use the worksheet for comments you may want to understand or act on. If a note lacks context, record that limitation rather than treating it as a complete account.

Can one comment produce more than one design question?

Yes, if it points to distinct issues or moments. Write separate questions so each stays focused, and note which parts of the comment support each one.

When should I ask the player to clarify a comment?

Ask when a missing detail matters to understanding the moment. Use an open question about what they were doing, noticing, or trying to do, rather than offering a cause or fix for them to agree with.

YOUR QUESTION. YOUR DETAILS.

Let’s work through your situation.

Get a tailored answer or help with your next task. Starts at $1, with a quote before you pay.

Ask your own question
← Back to Geez at Work