A Rulebook You Read vs. a Rulebook You Reach For

Role

Producer: decisions.

Team

The full 20 Below team, 15 people.

Result

Learning the game and looking things up mid-session became two documents, each doing one job.

The Problem

Nobody reads a rulebook mid-fight. They flip through it, hunting, while four other people wait.

That’s the actual failure mode I was solving for on 20 Below’s Player’s Guide. Rulebooks get written once, front to back, for a reader who has time — and then get used in the one moment that reader never has: mid-session, dice already in hand, table waiting on an answer. Writing everything as one continuous instructional document was solving the wrong problem for half its actual readers.

Analysis

There isn’t one reader here. There are two, and they want opposite things.

One is learning the system for the first time — has the time, wants the concept explained, will read start to finish or by topic. The other already knows the concept and just needs the exact number, right now, mid-turn. No amount of better organizing serves both of those at once with the same document. I stopped trying to write one file that satisfied both jobs and started treating them as two different deliverables.

Design Decisions

• Built “At the Table” as its own standalone section, pulled entirely out of the instructional flow, instead of just adding better headers to the same document.
• Wrote “How Do I…?” as a straight lookup: plain question in, exact roll out. No re-explaining the concept — the reader already has it, they just want the number.
• Built the Difficulty Chart as a chart, not a paragraph: color-coded band, one worked example each, because a table beats prose when the job is “match this situation to that number,” fast.
• Linked the two documents to each other in one direction only: new readers get routed toward the concept, players already at the table get routed to the lookup. Two doors into the same house, not one door with a longer hallway.

Outcome

The instructional path and the in-session reference path are now two different documents doing two different jobs, on purpose. That’s the same split most corporate training documentation never makes — treating “learn it” and “use it in the moment” as one problem, when they’re not.

See the live result: At the Table →