Skip to content
Dashpop

Turn a hunch into a useful playtest

You have a theory about your game. Now make a test that gives it a fair chance to be wrong, and leaves you with a clear next decision.

By DashpopLesson 12 of 123 min read
In this guide

Allow 30–45 minutes for the reading, interactive experiment, and a notebook exercise. Bring a prototype or use our Night Mail courier example. No account or code required.

By the end of this lesson

  • Match a prototype’s fidelity to an uncertainty.
  • Write a prediction and a result that would challenge it.
  • Choose a bounded next revision from mixed observations.

Make iteration answer a question

Tracy Fullerton’s Game Design Workshop emphasizes a playcentric process of prototyping, playtesting, and revision around player experience goals. The important step between builds is explaining what you learned and how it changes the next experiment.

Suppose three testers avoid the Night Mail bridge. That observation supports several hypotheses: they miss the sign, misunderstand oil, dislike the route, or simply have enough time. Building a more spectacular bridge does not distinguish those explanations.

Choose an uncertainty you can investigate today. “Can a first-time player predict the oil cost?” is narrower than “Is the bridge good?” State the task, the audience, and the point where you will ask for a prediction. Keep the route costs fixed while testing the sign.

Choose a test that could change your mind

Match the question to a prototype and an observation. A paper map can help with route understanding. It cannot establish how comfortable a moving touch control feels. Try both questions in the planner, then write a one-sentence plan for your own game.

The smallest useful test

Start with an uncertainty
Choose a prototype
Choose the most relevant evidence
Choose a prototype and an observation to inspect the match.

Your notes stay here while this page is open. Copy them to your notebook before leaving.

Watch for another explanation

If a tester plays the old map and then the new map, familiarity can improve their second attempt. Use fresh players when studying first impressions, or vary the order when comparing versions. A small informal comparison can still guide work; record its limits instead of pretending it establishes a general law.

Keep assistance in your notes. After you explain the oil icon, later success tells you something about play with that knowledge. It does not show that the new icon teaches itself. Helping a stuck player is reasonable; silently treating the help as part of the game is misleading.

A prediction should include a plausible result that would challenge it. If every outcome can be described as success, the test will protect your opinion rather than improve the game. Decide before the session what would send you back to the drawing board.

Write a decision someone else can follow

RecordNight Mail example
QuestionCan new players predict oil use at the junction?
PredictionA cost shown beside each route will support accurate explanations before crossing.
Challenge to the predictionPlayers see the cost but still explain it as a reward.
Keep fixedRoute layout, costs, deadline, and starting oil.
Next decisionRevise the sign if misunderstood; inspect the tradeoff if understood but ignored.

Run a small, honest cycle

  1. Name one audience and one uncertainty.
  2. Build the smallest prototype that preserves that uncertainty.
  3. Write a neutral opening and a stopping condition.
  4. Record actions, player reports, and your explanations separately.
  5. Choose one next revision, name what it should change, and keep what worked.
A brief to make your own

I am testing whether the route signs explain oil costs to someone new to the game. Please plan a delivery and tell me what you expect before crossing. I am testing the signs, so any uncertainty is useful feedback.

Your next lesson is a real player

Bring your experience promise, a playable moment, and a question into the next session. You do not need to finish a whole game to learn something useful. Keep a short record of the build, observation, interpretation, and next change so your next session starts with evidence.

Sources & further reading

Sources for the ideas discussed here, plus further reading. The lesson’s examples and interactive exercises are original.

Put your idea to work with the Dashpop Game Engine. Describe a game, play it quickly, and shape it yourself. Start with one change you can test.