What my high school reunion taught me about writing BACKSTORY

Sitting at a table at my high school reunion recently, this thought struck me: “This is how backstory should work.”

Huh, you say. Let me explain.

I’ve know most of the people at my high school reunion more than half my life. I didn’t have to ask mundane questions to get to know them. When I looked in their faces, I saw not the wrinkles but teenagers I remembered from our school days.

We were (are) a close knit group, attending English class or studying for Algebra or cheering our Austin High School Maroon football team. We laughed about our Red Jacket (the drill team) adventures, relived football losses, groaned over teachers and relived our glory days on the yearbook and newspaper staff as reminisced.

I knew their past.

But what dawned on me was that what I remembered from those good ole days is only a small portion of their story. As we shared over the three day reunion, I learned of their triumphs, their heartaches, their success since we’d last been together.

Did I learn everything at once? No. Piece by piece they shared stories. Backstory came to light that had shaped who they were today.

Like all my high school friends, I know my characters. After all, I am creating them.

And like my friends who told their stories over the time we were together, that’s how I must reveal my character’s background–slowly as it relates to the story and character development.

This is where new writers often err in their opening scenes, revealing anything and everything that’s happened up to the time of the inciting incident.

There are times when a bit of backstory is necessary for the reader to grasp what’s going on and why it’s important. But, editors and agents agree a newly submitted manuscript with backstory dump in the beginning scenes is the biggest kiss of death for the work.

Writers, whether new or seasoned, must tread carefully when considering how much backstory to include. We should trust the reader’s intelligence to “get” what’s going on without providing lengthy backstory.

Think about it. Is it really necessary for the reader to know Mary has been married three times, each relationship ending badly, to “understand” why she’s looking for a good relationship. Usually, that kind of backstory, while indeed important, should be doled out later in the story and bit by bit.

A general rule is keep backstory either absent from the opening or only include as much as is absolutely necessary to set the scene for the inciting incident.

To quote Donald Maass, “no backstory in the first fifty pages.” And then, only to do one or more of these things:

1. Raise the stakes
2. Reveal motivations
3. Express innermost fears
4. Reveal obstacles

Easier said than done for most writers, including me.

I think of backstory as “BS.” Literally. I ask myself does the reader really need to know this in order to relate to my character? The answer is usually no!

Another way to think of backstory is as carefully placed clues to the mystery of the character and why they are the way they are. Hints to keep the reader turning the page.

Just as I discovered my old friends’ stories gradually, we writers need to let readers find backstory clues throughout the book until they’re brought all together to explain how and why the character changed or clarify whatever the character did.

What do you think about backstory dumps in the opening pages? Do you close the book or keep on reading?

15 Comments on “What my high school reunion taught me about writing BACKSTORY

  1. Pingback: BS aka Backstory – Part 2 | Judythe Morgan

  2. This is a great way of thinking about it. I think it depends on what you genre you’re writing too. For me, it’s all about the happy medium. Too much and I get bored yet too little and I feel like I don’t know the character well enough to care about her story yet. I’m always aiming for that happy medium.

    • You’re so right about happy medium. We want enough backstory to keep the reader interested and enough to keep them turning the pages. Thanks for stopping by the porch. Come again.

  3. Great analogy!
    Backstories bore me, so I strive to use as little as possible in mu books and always begin with my strongest hook, then weave in relevant backstory.And, like you, I usually find most of it isn’t!
    I enjoyed your post…

    • I’ve read your books and you do a great job with just the right amount of backstory. Thanks, P.J. for stopping by the porch. Come again.

  4. I laughed out loud when I read the “BS” comment. That will certainly stick with me – a great reminder to not fill my manuscript with it. 🙂

    • First time I heard “BS” used to refer to backstory it stuck with me too! Thanks for stopping by. Happy I gave you something you could use today.

  5. I’m not a writer, but I’m an avid reader. I can see where too much info can get in the way early in a book. I didn’t know the term “backstory” but now I’ll probably be looking for it!

    • Oops! Didn’t mean to spoil your reading. But, if you haven’t noticed backstory in what you read, it’s good for those authors. Thanks for stopping by the cyber porch and the real porch. Enjoying all your comments.

  6. Great post. It’s interesting that you thought of backstory at your reunion. It is kind of a similar spilling, isn’t it? Thanks for the tips.

    • You’re welcome. Getting our characterization on the page without info dumps is not easy. Glad I could help. Thanks for stopping by my porch.

  7. What a fine example of Characterization Judy. Great post! 🙂

  8. Never thought of the reunion as an example. I agree, the BS dump at the start does not bode well. I sometimes keep reading anyway but I don’t like having everything spelled out for me. It’s fun to discover the backstory along the way!

Leave a Reply

Your email address will not be published. Required fields are marked *