The first time you sit behind the screen, the plan looks straightforward: build a world, put a story inside it, and let the players walk through. Then someone asks whether the tavern keeper has a brother, the party decides to sail in the opposite direction, and your neatly ordered notes become the least relevant thing on the table.

That gap between what you prepared and what actually happens is where most new Game Masters learn their craft, usually by making the same handful of mistakes everyone else made first. None of them are fatal. Most are fixable with a small change of habit.

1. Over-preparing and writing a novel nobody will read

Hours of lore. A full regional map. Three pages of backstory for a blacksmith the players will never meet. It feels like diligence, and it often produces a flat session, because you have invested so heavily in one version of events that you start steering towards it without noticing.

Prepare situations instead of plots. A situation has pressure and moving parts; a plot has a sequence that must be followed. For a three-hour session, this is usually plenty:

  • A location with a problem in it — a flooded mine, a toll bridge run by a corrupt keeper.
  • Two or three NPCs, each with a name, a mannerism and one thing they want.
  • A countdown that advances whether or not the players act.
  • A couple of stat blocks you can reskin in seconds.

If the players burn through it in an hour, you have room to improvise. If they spend the whole evening arguing with the bridge keeper, that is a good session, not a wasted one.

2. Railroading, or mistaking a plot for a script

You have prepared a confrontation in the duke's wine cellar. Your players, sensibly, bribe a servant and leave through the kitchens. The temptation is to drag them back: the doors lock, the servant betrays them, the villain appears anyway. Do that twice and your table will stop making decisions.

The fix is to move the confrontation, not the players. The traitor is now waiting at the docks, or the bribe works and the duke's steward comes looking for them the next morning. Keep the drama, release the geography. Player agency is not a threat to your story; it is the thing that makes it feel like theirs.

3. Calling for dice rolls when failure is boring

Not every action needs a check. Rolling to search an empty room, to climb a fence that anyone could climb, or to recall a fact the party already knows slows the game and invites anticlimax.

A useful rule: only call for a roll when both success and failure lead somewhere interesting. If a failed roll just means "try again", skip it and describe the success. When you do call for a roll, make failure change the situation rather than halt it — the lock opens, but loudly, and something in the corridor hears.

4. Saying no by reflex

"Can I swing from the chandelier?" is not an attempt to break your game. It is a player engaging with the room you described. "There isn't a chandelier" ends the conversation; "there is, and it will take your weight for about six seconds" starts one.

Try yes, and or yes, but. Yes, you can vault the barricade, but you land prone. Yes, you can intimidate the guard, and now his sergeant is watching you. That said, a clear no is fine when a request breaks the tone you agreed on or spoils another player's fun. The difference is between refusing the idea and refusing the person.

5. Skipping the session zero conversation

Half an hour of honest talk before the first game prevents months of quiet frustration. Cover the basics: what the campaign is actually about, how serious or silly the tone will be, how often you play and what happens when someone cannot make it, how character death is handled, and whether player-versus-player conflict is welcome.

Agree on content boundaries too. Ask what people would rather not have appear in the game, and take the answers seriously. Everyone at the table should be able to say "let's skip past this" without needing to justify it.

6. Treating the table as a contest

You are not the party's opponent. You run the world, and the world can be hostile, but gloating over a downed character, targeting the same player every fight, or quietly fudging rolls to protect your villain all point at the same confusion.

Build encounters you would be genuinely happy to lose. Describe the players' victories with the same energy you would give your own. When your monster dies in two rounds, that is not a failure of design — it is a scene your friends will retell next week.

7. Letting the quiet players disappear

Confident players fill silence easily, and it is tempting to keep following the momentum. Over a campaign, that leaves half the table watching instead of playing.

Give out the spotlight deliberately. Ask the quiet player's character a direct question — what does your ranger make of this? Put a piece of their backstory in front of them. Cut between groups rather than running one long scene while everyone else waits. If a scene is going nowhere, end it early and move on; pacing is part of your job, and nobody minds a quick cut.

A five-minute habit that fixes most of this

After each session, before everyone drifts off, take five minutes and write down four things:

  1. What did the players spend the most time on? That is what they care about.
  2. Which rule did you have to look up twice? Put it on a card.
  3. Who spoke least, and what would have given them an opening?
  4. What did you improvise that worked? Keep it and build on it.

Keep a running page of consequences — who the party upset, what they promised, what is now hunting them — and your preparation almost writes itself. You will still make mistakes. Every Game Master does, in every campaign, forever. The ones who improve are simply the ones who notice, adjust a little, and come back next week ready to play.

Photo: Bru-nO / Pixabay