Every long-running group has one: the player who keeps a notebook of half-finished maps, odd NPCs and dungeons sketched on the back of a receipt. Turning that notebook into a module other people can run is a craft, and it is far more learnable than it looks. You do not need a publishing deal or a hundred pages. You need a clear premise, encounters that do something, and the willingness to watch your own material fail at the table and then fix it.

Begin With a Situation, Not a Story

The mistake most first-time designers make is writing a plot. Plots belong to the players, and they will wreck yours within twenty minutes. Start instead with an unstable situation that demands a response. A mine has flooded and something is living in the water. The bridge collapsed the night before the harvest festival, and the timber meant to repair it has vanished. The wizard's apprentice has not been seen for three days, and the tower has started locking its own doors.

Then answer three questions in writing:

  • What is wrong right now that was not wrong last week?
  • Who wants it fixed, and what are they offering?
  • What happens if nobody does anything?

Those answers give you stakes and a clock. Compress them into one sentence — "the party must clear the flooded mine before the town's water runs out" — and pin it to the top of your document. Every scene you write afterwards has to serve that sentence, or it gets cut.

Keep the Map Small

A module for one or two sessions should fit inside a village and a handful of nearby sites. Sketch six to ten locations and note what sits between them: "the ruin is two hours north of the ford; the ford is watched." Distance and terrain create choices, which is what you actually want. Spectacle is easy to write and hard to run.

If your premise needs three towns and a cathedral-sized dungeon, split it into parts or trim it. Small and finished beats ambitious and abandoned, every time.

Write Encounters That Change Something

An encounter is not a fight with a description attached. It should spend resources, reveal information or shift an alliance. A useful test: if the players walk away without engaging, has anything changed? If the answer is no, you have written scenery.

For each key encounter, note four things:

  • The pressure. What forces a decision? Rising water, a patrol due back at dusk, a wounded NPC who will not last the night.
  • The options. At least three plausible approaches — talk, sneak, force, bargain, leave. Add a line on what each one costs.
  • What changes. What is different once it resolves, and what does it teach the party about the wider problem?
  • The details you will forget. Names, one physical trait per NPC, one want and one secret each.

Resist over-writing read-aloud text. Two sentences set a scene; two paragraphs put the table to sleep, and you will end up paraphrasing them anyway.

Give Every NPC a Want and a Secret

An NPC who wants something incompatible with another NPC's want generates scenes without your help. The ferryman wants the road to stay broken; the merchant wants it repaired by market day. Now the players have a decision to make, and the module starts running itself.

Format Your Notes to Be Used, Not Read

Design for the worst moment: you are mid-session, three people are talking at once, and someone has just asked what the innkeeper's name is. Short paragraphs, bold names on first mention, one page per location. Put the map, the premise, the clock and the key NPCs on a single front sheet.

Habits worth borrowing from published modules:

  • Open each location with a one-line summary in bold.
  • Bullet your clues. Never bury one mid-paragraph.
  • Cross-reference properly — "see the miller, p. 4".
  • Number your pages and your rooms so you can call them out loud.
  • Print it. Screens hide mistakes that paper does not.

If you cannot find a piece of information in five seconds while players watch you, it may as well not be written down.

Playtesting Is Where the Real Writing Starts

Run the module yourself first, with whatever group you already have. Take notes in the moment: every time you invent a name, a motive, a number or a route on the spot, you have found a gap. Mark it and keep going. The game matters more than the document.

Then run it for a different group, ideally one you do not play with regularly. Afterwards, ask specific questions: When did you feel stuck? What did you think the goal was? Which NPC did you trust, and why? "That was fun" tells you nothing you can act on.

Then revise in this order:

  1. Fill the gaps you improvised around.
  2. Cut the travelogue. If two groups skipped it, delete it.
  3. Add or move a clue where the party stalled twice.
  4. Tighten the opening ten minutes; they set the table's expectations.
  5. Test once more with the changes in place, if you can.

Try not to defend your choices when feedback arrives. If two separate groups miss the same clue, the clue is the problem, not the players.

Make Something Small This Weekend

Pick a premise you can state in one sentence. Choose six locations and stop. Write one page for each, plus a front sheet, and set a two-hour timer so the writing does not sprawl. Then run it.

A finished four-page module will teach you more than a beautifully outlined sixty-page one you never quite complete. When it is done, file it away, note the two things you would change, and start the next one. The second module is always easier than the first, and the fifth is easier still.

Photo: Pexels / Pixabay