Spotlight Isn't Shared by Accident. It Gets Written Down First.

Six sessions in, and the party's fighter has had exactly one scene built around them: getting knocked prone by a trap nobody else triggered. Nobody's checked out, the dice are rolling fine, everyone's still having fun. It's just that every improvised NPC question goes to the bard, every ambush roll goes to whoever has the highest passive Perception, and the one thread the fighter actually cares about, a debt owed to their old mercenary company, hasn't come up once. Nobody decided to sideline anyone. It happens at a lot of tables, because spotlight time that isn't planned gets improvised, and improvisation defaults to whoever's already talking.

That's a different problem from the one player who won't stop talking, which is really a table-etiquette conversation. This version is quieter and easier to miss, because nothing goes wrong in any single session. It only shows up when you zoom out across four or five sessions and notice the same one or two characters are doing all the narrative lifting while everyone else is along for the fight scenes.

Why reacting in the moment doesn't fix it

Most GM advice on this treats it as an in-session read: watch the table, notice who's gone quiet, throw them a question. That works for the session you're currently running. It does nothing for the session after that, because by next week you're prepping new NPCs and a new set of complications, and the mental note about who got skipped is gone. The fix that survives past Tuesday isn't a sharper read on the room. It's deciding who gets a beat before you sit down to run the game, the same way you'd decide what the villain does next.

The one-beat habit

Before each session, write one planned beat for every PC. Not a scene, just a single specific hook: an NPC who addresses them by name and brings up something only they would know about, a consequence that only lands because of a choice that character made two sessions ago, a complication built around the one skill only they have. It doesn't need to be the centerpiece of the session. It needs to exist on paper before the table sits down, so it isn't competing with whatever's loudest in the room for your attention.

After the session, mark which beats actually landed. Not every planned beat survives contact with how the table actually goes, and that's fine. What matters is the pattern: if the same character's beat keeps getting bumped two sessions running, that's the signal to move it to the top of next week's list instead of hoping it comes up on its own.

Where it actually lives

A plan like this fails the same way "the cult finishes the ritual eventually" used to fail: if it only lives in your head, it gets skipped the first busy week and never comes back. Keep it next to the rest of your prep instead of running it as a separate system. GameMasterCraft's NPC and session-recap notes already hold the hooks and loose ends tied to each character's thread. Drop the planned beat there, next to whichever NPC or faction is going to deliver it, and check it off in the recap the same way you'd log any other open thread. It's one more line in prep you were already doing, not a new habit bolted on top.

None of this requires reading the table better. It requires one sentence, written down before the session, that can't get skipped just because someone else is more comfortable jumping in first.

Comments (0)

More from the Blog

Ready to create something?

Subscribe to an individual app or get the full GameMaster Studio.