I’ve been running games long enough to spot the pattern before Session 1.

Someone submits their character for review and it’s two pages. Sometimes three. There’s a child in a burning village, a mentor who betrayed them, a sibling they’re searching for, a mark on their wrist they can’t explain. The writing is good. The detail, impressive. And I already know this character is going to be one of the hardest to make feel real at the table.

Meanwhile, someone else sends me three sentences: “She wants to prove she’s not a liability. She doesn’t ask for help. She keeps a running tally of every favor she owes anyone.”

Three sessions in, the second character is the one everyone remembers.

This isn’t a coincidence, and it isn’t about writing ability. It’s about a fundamental misunderstanding of how TTRPG characters actually come to life. And the backstory trap is the most common thing I see getting in the way.

The Mistake Makes Sense

I get why we do it.

We grow up consuming stories where characters arrive with histories. Geralt of Rivia has a miles long list of contracts behind him. Katness Everdeen lost her father in a mine explosion before the story starts. Walter White has decades of choices that brought him to the moment we meet him.

In those stories, the backstory works because the author designed the history to collide with the plot. Every detail was placed deliberately. The protagonist’s wound is the wound the story is about. Nothing is accidental.

So we sit down to make a character and we do the same thing. We write the history. We build the wound they carry. We map out the complicated relationship with a dead parent or a corrupted mentor or a guild that wants them dead.

What we forget is that we’re not writing a novel. We’re showing up to improvise one. And those are completely different activities.

When Backstory Takes Over

Let me tell you about a session I ran a while back. It was a nautical campaign with sea monsters, cursed treasure. You know, the works.

One player built a character with an elaborate backstory. They were a formal naval officer, dishonorably discharged after a battle where his crew died under his command. Now, they sail under an assumed name to escape the shame. It was detailed, emotionally rich, and, on paper, a lot to work with.

The problem? Every session, this player was waiting. They were watching for the moment their backstory would become relevant. When we docked at a port, they’d mention offhand that they’d been to this port before, but nothing came of it. When we encountered navy vessels, they’d tense up. But the encounter resolved before it could develop. When other characters had emotional moments, this player stayed on the fringes, waiting for their turn.

It was almost like they were standing in a room waiting to be introduced.

Another player in the same campaign showed up with almost nothing for backstory. They were a disgraced dueling instructor who was always correcting other people’s footwork. That’s it. No backstory, just a habit.

Within two session, we all knew her. She’d corrected the deckhand’s grip of a mop. She’d offered unsolicited critique to an enemy swordsman mid-combat. This made everyone laugh but also revealed something real: she couldn’t turn it off, even when it was inappropriate, even when it annoyed people. She’d argued with the captain about the proper way to handle a boarding scenario and almost gotten herself thrown overboard.

We understood her because she kept doing things. Her character wasn’t explained. It was demonstrated.

The Problem With “My Character Wouldn’t Do That”

Here’s how you know backstory has become a trap: when a player starts using it to refuse choices.

“My character wouldn’t do that.”

I hear this and I know exactly what’s happened. The play wrote a character in advance, got attached to the concept, and is now defending consistency with that concept over responding to what the moment actually needs.

I had a player once whose character was written as cold and pragmatic. They were a mercenary who didn’t form attachments. It was a good concept with clear internal logic. But about four sessions in, the party was about to leave a wounded NPC behind, and I could see this player genuinely struggling. They wanted to help. The situation called for it. But their character “wouldn’t do that.”

They chose consistency. The character left the NPC behind. And the moment died.

What if they’d followed the pull instead? What if their cold mercenary had surprised everyone, even themselves, by staying? That contradiction would have told us more about this character than ten sessions of consistent coldness. Maybe something about this particular person got under their skin. Maybe they’re not as detached as they think. Maybe they’re lying to themselves.

That’s a character. Not the one who performs their backstory faithfully. They’re the one that cracks.

Backstory Makes Passive Characters

Here’s the other thing I notice: elaborate backstories almost always center things that happened to the character.

Their village burned down. Their parents were killed. They were betrayed by a friend. They were abandoned by a mentor. They were trained by a dying master. They were left for dead.

These are all passive events. Things done to the character by the world. This means the character starts the campaign already waiting for the world to do something to them again.

Active characters want things. They drive toward something. They make the world respond to them rather than waiting to respond to the world.

In a dungeon-crawl campaign I ran last year, one player’s character had an elaborate history of magical experimentation gone wrong. They had a whole tragic backstory about a spell that killed someone they loved. It was rich stuff. But at the table, they spent most of their energy referencing this history and waiting for it to matter.

Another player’s character had one driving goal: she wanted to be the one who figured out every puzzle before anyone else did. That’s it. That’s the backstory. She drove toward it every session, sometimes heroically, sometimes insufferably. She got it right. She got it wrong. The history was thin, but the want was clear and alive. She was one of the most engaging players I ever ran for, because her goal generated behaviour in every single scene.

The Homework Problem

When you hand a GM a detailed backstory, you’re handing them a debt.

You’ve written something elaborate. The implicit message is this: this should matter. This means your GM now has to track seven different characters’ elaborate histories and try to weave them all into the story they’re building. They have to engineer moments that make your past relevant. They have to hold your dead mentor and your guilty secret and your mysterious mark alongside everything else they’re managing.

Sometimes that works. Often, the organic story the table is building together doesn’t naturally create space for it. Then the GM either forces it (which feels contrived) or doesn’t (and you feel like your backstory was ignored).

Compare that to the player with three sentences. They showed up ready to generate story from the present moment. Their character’s history didn’t need to be integrated. It emerged from what they did. When it became relevant, the table found out together.

That’s collaborative storytelling.

—

In Part 2, we’ll get into what actually works instead: how choices under pressure reveal character faster and more clearly than any origin story, and why the moments you don’t plan are usually the best ones.

—

Want to discover who your character is through play rather than prep? Check out my available games on StartPlaying.

Cover image by Fanette Guilloud