Designing Rulebooks People Actually Read
A great rulebook sells as much as great mechanics. Here is how to write one that teaches in five minutes and answers questions before they are asked.
By Kheeladi team · · 1 min read
Players do not experience your mechanics. They experience your rulebook, and only if it is good do they ever reach the mechanics. A confusing rulebook is a wall between your design and the people who would have loved it.
Structure for learning, not for reference
Open with the goal and an overview of a turn, then teach in the order a new player needs to know things — not in alphabetical or "complete" order. Save the exhaustive reference for the back pages.
Show, do not just tell
Every non-obvious rule deserves a worked example with a picture. "Resolve combat" means little; a small diagram showing exactly what happens makes it click instantly. Examples are not filler — they are the rulebook's most-read content.
Pass the five-minute test
Hand the rulebook to someone who has never seen the game and time how long until they can take a sensible first turn. If it is more than five minutes for a mid-weight game, the teaching order — not the reader — is the problem.
Sweat the small things
- Consistent terms: pick one word per concept and never swap it.
- Clear iconography with a legend players can find fast.
- An index and a quick-reference card for the table.
Write the rulebook for the most casual person who will ever open the box. Everyone else will thank you too.