I used to design balanced encounters that nobody remembers.

They weren’t bad. They were technically fine. The numbers worked. The CR lined up. The fight lasted four or five rounds and nobody died.

And six months later? No one at the table could tell you what happened in that fight.

That was the moment it clicked for me:

Encounters don’t suck because of bad math; they suck because they don’t matter.

“A perfectly balanced encounter that changes nothing is still forgettable.”

You can perfectly balance damage output, action economy, and terrain. But if nothing changes when the dust settles, it was just noise between long rests.

Over time, through planning, revising, and occasionally realizing I’d built something forgettable, I started running every encounter through a quiet internal framework.

If it didn’t pass the test, I rewrote it. This is that framework.

The Big Idea: Encounters Must Change Something

An encounter doesn’t need to be deadly, it doesn’t need a legendary action, it doesn’t need reinforcements or a twist villain, but it does need to change something.

A meaningful encounter shifts at least one of the following:

• The story
• The stakes
• The characters
• The world

If it doesn’t move any of those, it’s probably filler.

Here are the seven guidelines I now use to make sure my encounters don’t fall flat.

1. Every Encounter Needs a Job

Before you open a stat block, ask: Why does this exist?

Encounters can do a lot of work for you:

• Reveal information
• Escalate tension
• Introduce a faction
• Foreshadow a villain
• Drain resources intentionally
• Force a moral choice
• Show the consequences of something the party already did

In my early planning, I used to drop in fights because “the party hasn’t had combat in a while.”

That’s not a job. That’s pacing anxiety.

Now I ask: “What narrative function does this serve?”

If I can’t answer that clearly, I either rewrite the encounter or cut it entirely.

A fight that doesn’t serve the story is just hit point bookkeeping.

“If the encounter doesn’t have a job, it’s filler.”

2. Every Encounter Should Ask a Question

The most memorable encounters resolve uncertainty. Not just “Do we win?” But something more interesting.

• Will they protect the innocent or chase the villain?
• Will they expose corruption or profit from it?
• Will they save the farm or pursue the source of the corruption?

When an encounter asks a question, tension rises naturally. When it doesn’t, it’s just initiative order.

In my campaign prep now, I literally write a question in my notes:

“Will they secure the evidence before the city watch arrives?”

If I can’t phrase the encounter as a question, it probably lacks meaningful tension.

Good encounters don’t just reduce hit points, they resolve uncertainty.

3. Stakes Before Stat Blocks

This is where my design process changed the most.

I used to start here: “What’s an appropriate CR for this party?”

Now I start here: “What changes if they win? What changes if they lose?” If the answer is “not much,” the encounter isn’t ready yet.

Stakes can be big or small:

• A faction shifts its opinion.
• A rumor spreads.
• An NPC loses faith.
• A rival gains leverage.
• The party burns time they can’t afford to lose.

When you define consequences first, the creature choice becomes obvious.

The monsters aren’t there because they’re CR appropriate; they’re there because they enforce the stakes.

Start with consequences, then choose opposition that makes those consequences possible.

“Stakes first. Stat blocks second.”

4. Make It Personal

Generic danger is forgettable. Personal danger sticks.

An encounter becomes memorable when it pressures something the characters care about:

• A backstory thread
• An ideal
• A flaw
• A relationship
• A promise they made

When scarecrows attack a random farm, it’s a fight. When they attack a farm tied to the druid’s connection to the land, or a family the party has grown fond of, it becomes something else.

The encounter stops being about survival; it becomes about values.

The most memorable encounters don’t threaten the party, they threaten what the party cares about.

“Generic danger is forgettable. Personal danger sticks.”

5. Run It as a Scene, not a Speed Bump

Encounters that “suck” often share one trait: They begin abruptly and end abruptly.

Roll initiative. Reduce hit points. Collect loot. Move on.

Instead, think cinematically.

Before

Why now? Who wants what? What has already set this in motion?

During

What makes this dynamic? Is there unstable terrain? Are there civilians in danger? Is a timer ticking down? Are reinforcements approaching?

After

What shifts in the world? Who reacts? What rumors spread? Who is angry? Who is impressed?

If nothing changes after the fight, the fight probably didn’t matter.

Treat encounters as scenes in a story, not speed bumps between plot beats.

6. Let Consequences Linger

This is the part many DMs skip. The fight ends, and everything resets.

But meaningful encounters echo.

• The city watch starts asking questions.
• A faction reconsiders its trust.
• An enemy marks the party for revenge.
• Supplies run thin.
• An innocent is injured.
• A political situation worsens.

Consequences don’t have to be catastrophic; they just have to be real. When the world reacts, players start treating encounters as meaningful decisions instead of tactical puzzles. Consequences are the echo of the encounter; without the echo, it fades quickly.

7. Run the Encounter Audit

Before I lock an encounter into my notes, I run it through a simple filter:

• Does this change something?
• Does it reveal something?
• Does it pressure a resource?
• Does it create a decision?
• Would my players talk about this later?

If the honest answer is “not really,” I adjust it.

Sometimes that means adding stakes, sometimes that means tying it to a character, sometimes that means cutting it entirely.

Not every session needs nonstop combat. But every encounter you choose to run should earn its place at the table.

Encounters Don’t Need to Be Deadly

There’s a quiet assumption in tabletop design that tension must come from lethality.

It doesn’t. An encounter doesn’t need to threaten a TPK to matter.

It needs to shift something.

Balance keeps the party alive; meaning keeps them engaged.

“Balance keeps the party alive. Meaning keeps them invested.”

A perfectly balanced encounter that changes nothing is still forgettable, but an encounter that reshapes relationships, shifts factions, tests ideals, or alters the trajectory of the campaign?

That one sticks.

And those are the encounters players remember years later.