Puzzle Maker’s Dictionary

Puzzle Testing, Tuning, and Development

You can make a great, unique puzzle that people will like. Testing is how you learn which part of that possibility already works, which part players cannot yet see, and which part needs a different form.

A prototype is a question made playable. Playtesting is not a referendum on your worth as a maker; it is evidence about the relationship between your intention, the system, and another person's actual experience.

Look for the owl mark beside a passage to read or begin a discussion.

System Tuning: Adjust Relationships Without Confusing Numbers for Structure

Technical terms: System tuning

System tuning adjusts values, timings, probabilities, capacities, and relationships after the basic structure exists. It shapes pacing, viable strategies, risk, frequency, and reward; it does not merely make a game easier or harder.

Tuning can reveal that the underlying structure is wrong. No perfect number repairs an action that is uninteresting or a reward that encourages the opposite of the intended behavior.

What you can do with it

Change related values together and state the expected effect. Use observation, instrumentation, simulation, and judgment for the kinds of evidence each can provide.

Ask a player

Which choices became more or less attractive after the adjustment, and did the intended experience become clearer?

Nearby ideas

  • Game balance — preserve intended positions and strategies.
  • Feedback loop — see how one tuned value compounds.
  • Difficulty — distinguish challenge from numerical punishment.
  • Structural change — replace a mechanism rather than endlessly tune it.

Robert Zubek, Elements of Game Design (2020), “Systems,” discussion of system tuning. ---

Game Concepts and Pitches: State the Promise Before Listing Features

Technical terms: Game concept, Pitch

A game concept compactly names the intended player, experience, core activity, distinguishing idea, scope, and feasibility. A pitch communicates that concept to collaborators, funders, publishers, or players.

It is a decision-making hypothesis, not a miniature rulebook and not proof that the game works.

See it in Same Circles

“A calm social word-making space where people arrange crossing words inside a circle, share the resulting creation, and discuss what they notice” communicates more than a list of input rules.

What you can do with it

Lead with the player's activity and why it matters. Change emphasis for the audience without changing the underlying truth.

Ask a player

After hearing the concept, what did you expect to do and care about?

Nearby ideas

  • Experience goal — name the intended response.
  • Essential game — preserve the defining recurring decision.
  • Audience — communicate to a particular person rather than everyone.
  • Design intent — state what a feature is meant to accomplish.

Robert Zubek, Elements of Game Design (2020), “Prototyping and Playtesting,” discussion of concepts and pitch documents. ---

Game Development Lifecycle: Retire the Largest Risks Before Building at Full Scale

Technical terms: Concepting, Preproduction, Production, Release, Postrelease

Concepting identifies and communicates the idea. Preproduction resolves major risks through prototypes. Production builds the validated design at scale. Release prepares and delivers it to players. Postrelease observes, supports, repairs, tunes, and sometimes expands the live experience.

Iteration continues throughout, but the price of fundamental change rises sharply as production advances.

What you can do with it

Resolve uncertainty in descending order of danger. Polish cannot prove the central activity is worthwhile, and a successful prototype does not prove moderation, onboarding, or community systems will work at scale.

Ask a player

What did real use reveal that the prototype or closed test could not?

Nearby ideas

  • Individual prototype — isolate one risky assumption.
  • Accumulative prototype — integrate validated systems.
  • Postrelease observation — learn from real community behavior.
  • Scope control — postpone work not needed to test the promise.

Robert Zubek, Elements of Game Design (2020), “Prototyping and Playtesting,” discussion of production stages. ---