Say no to "info dump"
What's info dump? We've all run into it, usually in the first chapter or whenever a new character is introduced. And we know when we run into it -- info dump will stop the flow of a story in its tracks while the author gets the "facts & figures" out of their system.
Since I'm writing a series, I find myself doing it and it's something I have to be especially on guard against. Ideally people will read my books in order, but a lot of times they don't. Heck, I do the same thing: I find a new author I want to read, pick up the book on the shelf, buy it, take it home and read it, and if I like it, go back and get the others in the series. Most bookstores carry only an author's most recent works since bookshelf space is a precious commodity. So a lot of the time, the first book in a series isn't on bookstore shelves.
So in my writing, I feel the need to bring readers up to speed -- but it's a fine line between dropping some needed plot "breadcrumbs" to familiarize a reader with a character or situation, and info dump. Anything that disrupts the flow of the story is bad. Anything that tells too much about a character or situation up front is bad. Tell only what needs to be told to move the story forward in that scene or chapter. If some facts aren't really needed until Chapter 8, don't include them in Chapter 4. It's confusing, unnecessary, and it makes the reader go "Huh?"
My editor caught quite a few of these in The Trouble with Demons. Since I'm writing a series, I carry storylines from one book to the next, and I felt the need to give some background on what had happened to Piaras at the elven embassy in Armed & Magical. Problem was, Piaras and the actual reference to that situation didn't happen for another ten chapters. Yep, I fell prey to info dump. Once Anne pointed it out to me, it was obvious that I'd screwed up.
But I'm learning. In Bewitched & Betrayed, Raine literally hits the ground running. And she doesn't trip over a big pile of info dump.
Some of what's coming this week and into next week:
- How to keep a story believable
- Start with a hook, end with a cliffhanger
- Let every scene advance the plot
- Never stop learning
posted by Lisa Shearin at
9:51 AM
5 Comments:
Actually, I respectfully offer a counter-example. The first hundred-odd pages of John Ringo's magnificent "The Last Centurion" are essentially nothing but info-dump AKA "How we got into the mess." and the discussion was so fascinating I didn't want to stop reading. There were things to think about, things to argue with, things to make me grind my teeth and things to cheer. And ALL of them were utterly relevant to the question of "How did the narrator end up chin-deep in slok?"
I can agree with the idea that either an info dump should not be or it should be so fascinating that the reader doesn't want to put it down. No middle ground.
And I'm massively looking forward to "Trouble."
I agree, Ed. Either it has to be an integral part of the story itself (aka, something the reader either needs or wants to know), or details that move the story forward in a chapter or scene. In TTWD, I'd done the bad kind of info dump. But rest assured, all unnecessary dumps are gone and the book is tight as a drum. ; )
I also have a tendency to do the info dump right in the middle of the narrative and, since my current project is written in first person, everything comes to grinding, squealing, screeching halt.
I'm getting better, though, but I have to keep reminding myself to watch out for it.
I'm sure Anne picks up on one you might've missed. But in generally, what do you do to keep your infodumps in check?
My gut tells me when my mouth is running too much. ; )
ROFLOL
Post a Comment
Subscribe to Post Comments [Atom]
<< Home