7/29/09

A Drizzle of Back-Story goes a long way

My post on Monday started the juices flowing in my brain cells. How do authors inject back-story into a story without stopping the flow and pace of the scene?

As writers, we all know that beginners tend to write their back-story as the first chapter. *raises hand* {guilty!} But the more stories you write the more you learn to leave off the page.

Yes, back-story develops the character of the story. And yes, you need to know your character's back-story, but for the most part the reader doesn't need ALL this information, maybe only 1-2% of this. And the reader definitely doesn't need it right at the beginning of the story.

Tangent #1: It's just like research. The writer spends hours upon hours of learning XXX, but only uses the information to add color to the story. Was the research needed? Yes. But did the reader need to know everything the writer does about XXX? Uh, sorry, but NO.

Tangent #2 warning: Years ago, I sat on a Federal jury involving racial discrimination. Tangent on the tangent, tangent #2b: In Oklahoma, when you get called to Federal jury duty you are 'on call' for four weeks. Every Friday night you call in to see if you've been selected in their jury lottery. Two out of four weeks, I WON! Oh, wait. I don't really think that's 'winning'. What really sucked about it was I worked the 11-7 shift in a hospital--and I worked weekends that month. Major suckage having to work Sunday night and show up down-freakin'-town for jury duty on Monday morning.
Back to my original tangent #2: The racial discrimination case took place at a rebar factory. Those pieces of thick steel posts they lay in cement to strengthen it. Yeah, you know what I mean. I had to sit through hours upon hours of them detailing how to make rebar. Don't know WHY they went into so much detail, but it sure put me to sleep. This falls in the TMI (too much information) category.

Much like back-story. So how do you weave in the important information?

In the story I showcased on Monday took place in the 1700's and the wife of a Calvary officer was telling him how to ride his horse. 1) this didn't make sense, 2) why would a wife be telling him how to ride his own horse, 3) as a reader this REALLY pulled me out of the story.

I discovered later that this female had the back-story to pull off this scene (raised on a stud farm), but the reader was missing a vital part of the back-story. I didn't know this history, so the scene didn't make sense, and I vocalized it in my judging comments.

My suggestion was to add a sentence in the female's POV. Of course, this is just an example and might or might not work for the story, but it is a way of showing enough back-story without slowing the forward momentum. Something like this:
Rage flowed over her as her husband abused her deceased Papa's prized stud.
1) this sentence shows her closeness to her father by calling him Papa, plus you know he's dead
2) Papa raised horses. I think the term stud is a little more detailed versus the term stallion
3) Husband is bad man. Anyone who abuses animals should die, plus he probably abuses the humans in the family.
4) She reacts with rage, which ultimately ends up with her voicing her opinion. This could have dire consequences (a possible beating) and she can't run away (Papa's dead)

This example shows the reader back-story without the detail of boring back-story. The reader files it in their subconscious and when the character acts out, then it makes sense.

It just goes to show that every word does count. Writers need to be aware how they weave back-story into the novel without jarring the reader.

Write on!

8 comments:

  1. Great example! In my Chase the Dream finalist entry, I had questions from the agents/editors looking at the first 1000 words or so (I think that was the amount, but I'm not sure). In my revision, I weaved in a few sentences to make it more clear.

    ReplyDelete
  2. Thank you for the example -- yet another thing that has gotten me thinking. With the current WiP, I tried a new strategy: no back story in the first chapter, and so far so good: It's working!

    Have a great week.

    ReplyDelete
  3. Glad you stopped by, Edie! It is so hard to spot problems like this in one's own work because we KNOW the back-story.

    Our CP's know the story because as a writer we throw ideas/scenes/chapters/etc at them for critique and they absorb this info without realizing it.

    Beta readers, and contest judges, are the ones who 'discover' the oopsies, because they don't KNOW the story. Sometimes a cold read will give you answers to questions you didn't even know you had!

    ReplyDelete
  4. Hi Weronika!

    Keep the back-story where it belongs--in your mind. If you need to drop a hint about something then work it in a little at a time.

    I think a story has more impact if the reader has to keep reading to find out the answer for a character's actions/reactions.

    ReplyDelete
  5. In the last book I wrote, I skipped all the back-story of my heroine. I just dropped enough so the reader knew what was going on. I think that's the key. Like you said, I learned the hard way, but once you get it...you get it. :)

    ReplyDelete
  6. Actually, Kira, you're a pretty quick learner. I had to do things the hard way before I got hit on the head with a clue stick. :-)
    --I think a few of you might get the reference. :-P

    ReplyDelete
  7. Aw Margie, I didn't haveta hit you THAT many times.....

    ReplyDelete
  8. You were very gentle, Jods. :-P

    ReplyDelete

Welcome to my little blog.