Board Games Lab

Before I call a board-game design healthy, I want to see that the rules explanation is tight, the prototype supports fast iteration, and the playtests are teaching the designer something specific. If the table feedback stays vague, the design process is still hiding from the real work.

The metrics I care about are how quickly players internalize the turn, how often a rules explanation gets interrupted for clarification, and whether a playtest points to one fixable bottleneck rather than a vague sense that the game did not sing. Those are the signals that help a design improve. Before I call a board-game design healthy, I want to see that the rules explanation is tight, the prototype supports fast iteration, and the playtests are teaching the designer something specific. If the table feedback stays vague, the design process is still hiding from the real work.

The clearest signals usually live in rules clarity at the table, quality of the prototype feedback loop, and usefulness of the saved design artifacts. A good archive helps future-you compare decisions over time instead of restarting each month from a vague sense that things are improving.

Keep these nearby while you evaluate:
- Tabletop Simulator video tutorials: kb.tabletopsimulator.com/getting-started/vide...
A good bridge for readers who learn prototype workflows better through motion than prose.
- boardgame.io documentation: boardgame.io/documentation/
Worth saving once a designer wants to model phases, moves, and turn order explicitly.
- Watch It Played video archive: youtube.com/@WatchItPlayed/videos
A durable library for seeing how rules explanations land when clarity actually matters.