Your reader doesn’t need a character’s history before they have a reason to care about their present.
Peter walks into a bar.
Before he reaches the bartender, you should probably know some things about Peter.
His father left when he was nine. His mother never really recovered. Peter was an excellent student but struggled socially, particularly after the family moved to Connecticut during his sophomore year. His younger brother stayed behind for college, which caused some tension between them. Peter eventually married his college girlfriend, but the marriage ended after six years because…
I don’t care.
Peter hasn’t even ordered a drink yet.
This is one of the strangest impulses writers have. We invent a character, spend months figuring out who they are, and then apparently become terrified that the reader won’t understand them unless we immediately hand over the file.
The information may be important. It may explain everything Peter is about to do. It may be the most interesting thing you’ve ever written about Peter.
But there’s a problem: I don’t care about Peter yet.
And every paragraph you spend explaining him is another paragraph in which nothing is happening to make me care.
Exposition has a cost: it stops the story
This is what makes excessive backstory more than an annoying writing habit.
It can make a reader stop wanting to read.
Stories create momentum by making us wonder what happens next. Peter walks into a bar looking for Wendy. Wendy is sitting with another man. Peter sees them.
Now we have a question: What is Peter going to do? That’s a valuable thing to have.
Then the novel says:
Before Peter does anything, let me explain why seeing Wendy with another man is particularly difficult for him.
And off we go.
Peter’s first girlfriend. His parents’ marriage. The time Wendy left him three years ago. His lifelong fear of abandonment.
Eventually we return to the bar.
By then I barely remember what Peter was about to do.
The problem isn’t simply that exposition slows the story down. Sometimes slowing down is exactly what a story needs.
The problem is that you replaced a question I wanted answered with information I didn’t ask for.
That’s a terrible trade.
Think about the books you’ve stayed up stupidly late reading.
One more chapter. Then another. Then it’s 1:14 in the morning and you’ve started doing the math about how functional you could theoretically be tomorrow on five hours of sleep.
Books like The Hunger Games, The Girl with the Dragon Tattoo and Gone Girl can produce that feeling for very different reasons. They aren’t devoid of exposition. They have worlds to explain, histories to establish and characters with complicated pasts.
But the information exists alongside a much more powerful engine:
I need to know what happens next.
That’s the feeling you are protecting.
Every time you interrupt the present to explain the past, you’re spending some of it.
Spend carefully.
The writer needs the biography. The reader doesn’t.
You should know things about your characters.
Know too much. Know where Peter grew up. Know what his father did for work. Know the thing his mother used to say when she was angry. Know what happened at his 16th birthday party. Know why he hates hospitals. Know the name of the first person who broke his heart.
All of that can make Peter easier to write.
It gives you a reservoir of information from which his behavior can emerge.
But character development is an input. It isn’t prose by default.
If you wrote a 12-page biography of Peter before starting your novel and it helped you understand him, fantastic.
You do not now owe the reader 12 pages about Peter.
The distinction is simple:
The writer needs to understand the character. The reader needs to experience the character.
Those are different jobs.
Before putting a piece of backstory into the manuscript, ask:
Does the reader need to know this now, or do I just want them to know it?
Those are also very different things.
Make us want the backstory
Let’s say Peter hasn’t spoken to his father in 12 years.
You could tell me that.
Peter had always had a complicated relationship with his father. They hadn’t spoken since an argument shortly after Peter’s 25th birthday, when…
Or you could let Peter’s phone ring.
He looks at the screen.
DAD
He lets it ring.
Wendy looks up.
“You’re not going to answer that?”
“No.”
The phone stops.
A few seconds later, it rings again.
Peter turns it facedown.
Now I want to know.
Nothing about Peter’s history has changed. The difference is that the story has created a question before supplying the answer.
That order matters.
Backstory becomes more powerful when it answers a question the reader is already asking.
Curiosity is an asset. Don’t spend it too early.
Let the past leak through the present
You don’t always need to stop the story to explain what happened to someone.
Usually, the past is already showing.
Peter wears a watch that hasn’t worked in six years. Wendy knows not to mention Thanksgiving. Peter gets invited to his brother’s wedding and leaves the invitation unopened on the counter.
Someone asks where he went to college.
“Nowhere.”
Wendy looks at him.
He changes the subject.
We don’t know what any of those things mean yet.
Good.
Readers are allowed to not know things.
More importantly, readers like not knowing things when they believe the story eventually will make them matter.
That’s one of the pleasures of reading fiction. We notice. We wonder. We form theories. We revise them when new information arrives.
If you immediately explain every unusual behavior, loaded object and uncomfortable silence, you take that experience away from us.
You also flatten the character.
Instead of watching Peter behave and gradually understanding why, we’re given an explanation and then asked to watch him demonstrate it.
That’s less like meeting a person and more like reading the notes before the meeting.
Stop introducing characters with résumés
This gets particularly bad when a novel has a large cast.
Peter enters. Biography. Wendy enters. Biography. Michael enters. Biography.
Three chapters later, I’m trying to remember which one had the dead mother and which one went to boarding school.
The author thinks they’re giving me information that will help me understand the characters.
But information isn’t necessarily characterization.
If Wendy is fiercely independent, you don’t need to tell me that when she enters the novel.
Put her in a situation where accepting help would make her life considerably easier.
Then have her refuse it. If Peter is protective of his younger brother, let the brother screw something up and see what Peter does.
If Michael desperately wants people to think he’s successful, don’t give me three paragraphs about the insecurity that started in high school.
Have his card get declined at dinner.
Now we have a scene.
Characterization first. Explanation later.
Give me a reason to remember someone before giving me things to remember about them.
Backstory should change something
Gradually revealing information isn’t automatically better.
You can still spend 300 pages dribbling out useless facts.
A better question is what the information does when it arrives.
Good backstory can change our understanding of something we’ve already seen.
Remember Peter refusing his father’s phone call?
At first, maybe we assume Peter is angry.
Fifty pages later, we learn his father didn’t abandon him.
Peter abandoned his father.
Now the phone call means something different. The scene hasn’t changed. Our understanding of it has.
That’s one of the most satisfying things backstory can do. It reaches backward into the novel and alters something the reader thought they understood.
The information matters because the story gave it somewhere to land.
That’s very different from stopping Peter on page six to explain the entire relationship just in case we need it later.
Sometimes you should just tell us
There is an obvious way to overcorrect here.
Suddenly nobody in your novel is allowed to explain anything.
Peter stares mysteriously at a photograph.
Wendy touches the scar on her wrist.
Michael goes silent whenever anyone says “Cincinnati.”
Three hundred pages later, the reader is screaming:
WHAT HAPPENED IN CINCINNATI?
You don’t need to turn every piece of character history into a mystery.
Sometimes the reader needs two sentences of information. Give them two sentences.
Sometimes a character can simply remember something.
Sometimes a narrator can tell us what happened.
Sometimes explaining the history immediately makes the present scene more meaningful, and withholding it would feel artificial.
This isn’t another version of “show, don’t tell.”
The question isn’t whether you’re allowed to use exposition.
The question is:
Why does the reader need this information, and why do they need it now?
If you have a good answer, tell us.
If the answer is because otherwise the reader won’t know it, that’s not good enough.
Don’t give us information just because you have it
Writing a novel requires knowing far more than you’ll ever put on the page.
That’s not wasted work. It’s what allows the page to feel like there’s a world beyond it.
You can know where Peter went to elementary school.
You can know what his mother said when he left for college.
You can know exactly why he hasn’t spoken to his father since he was 25.
Know everything you need to know to write him. Then have the discipline not to tell us.
Not yet.
Let Peter walk into the bar. Let him see Wendy. Let something happen.
Make us care about the person standing in front of us before explaining the person who came before.
Don’t give readers information because you have it. Give them information because you’ve made them want it.