Good games need
good questions.

Try a prototype without reading its source code first. Then record what you actually experienced, not what the game was intended to do. You can fill in just the questions you know.

1 · What did you try?

Experiment

Select the experiment you actually played. No game is preselected or inferred. Once a game has report details, changing it asks before clearing those details to prevent wrong-game attribution; copy or download first. You may still fill a neutral worksheet before choosing a game. Shipped games get a launch link; comparison labs are attribution-only here and remain unlisted from the arcade/downloadable bundle. Opening a game does not submit your notes.

Session

Device type actually used

Input actually used (select all that apply)

Keyboard Mouse/trackpad Touch Other

Browser/version (optional)

Version or commit actually tested (optional)

2 · Your first minute

Was the goal clear without looking at the source?

What did you try first?

What happened? What confused you?

3 · How did it feel?

Enjoyment, your impression (1 = low, 5 = high)

How meaningful were your choices? (1 = low, 5 = high)

Pacing

Would you choose another round or level?

What worked best?

What single change would help most?

4 · Optional experiment-specific follow-up — open after playing

Keep this closed until after your first-play notes. The question reflects a current design hypothesis and can bias what you notice if you read it first.

If you played levels 1–4, which felt hardest and why? Did level 4 feel easier than level 3?

Your observation

5 · Bug details (optional)

Only write a bug report if you observed a failure; leave everything blank otherwise.

Steps to reproduce

What did you expect?

What actually happened?

Good games needgood questions.

Good games need
good questions.