Our stories consist of many elements: dialogue, action, setting, description, internal thought, emotion, visceral reaction, worldbuilding, backstory, etc. Each of those contributes to our story, and none of them are “evil.”
Not even backstory. *smile*
Our stories are stronger for including all of the elements. Yet given my mention of backstory, it’s probably obvious that we can overdo those elements as well.
Information dumps can happen with any aspect of our story. Backstory has a bad reputation from getting cozy with too many info dumps, but it’s not alone.
Too much dialogue in a row can lead to “talking head syndrome,” where readers lose track of the environment around the characters. We’ve recently talked about finding the right balance for settings and descriptions. Too big of a chunk of internal thought can feel like “navel gazing.” Etc., etc.
On the other hand, if we don’t include any backstory, our characters might lack context for their motivations. Backstory—what they’ve experienced and learned (for good or ill) about the world—is often the driving force behind why they do what they do.
In the same way, our stories need the other elements too. They’re all important for creating the tapestry of our story.
No matter what story elements we’re talking about, we need to include them without crossing over into Info Dump Land by using too much. How can we make sure we don’t cross the line? Let’s talk about our options…
Why Is It Important to Avoid Info Dumps?
Information dumps are when we tell readers things we think they need to know, but we’re not sharing the information as part of the story. In other words, an info dump is like pressing pause on the story to give more information.
It’s all fine and good to make sure readers have the information they need to understand the story, but the problem is with that “pressing pause” aspect. Readers come to us for the story, and if we stop the story in its tracks, readers can lose interest. (Backstory and info dumping are one of the top five reasons readers close a book.)
Info dumps can also jar readers out of the story by feeling like an intrusion. Maybe the characters are telling each other things they’d never really say (“As you know, Bob, you’re my brother.”). Maybe we’re inserting our authorial perspective into a deep point-of-view scene. Or maybe we’re spoon-feeding information to the reader to make sure they “get it.”
How Can We Share Info and Keep Up the Pace?
Stories are information, so we obviously need to share it with readers. *smile* But how can we prevent the story from losing momentum while we share it?
We should make the information…
…Relevant to the Story
I’ve spoken before about making sure the information we’re sharing with the reader is relevant. Just because we discovered a cool thing during our research doesn’t mean it should be included in our story.
I typically include only about 5% of what I discover during research. Pages of research might result in only one sentence. We should only include information that’s actually needed by readers.
…Timely to Current Story Events
Relevant can also refer to the timing of sharing information. Although it might be relevant to let readers know that the protagonist had a rough history with her father, she wouldn’t necessarily think about that fact while rock climbing on page one.
Instead, we should save that backstory information until it’s relevant to what’s currently going on in the story, such as when she checks her voice mail after her workout and finds a message from him.
…Shown and Not Told
Both of the previous tips have to do with being judicious with our use of the pause button, but we can also eliminate the button sometimes. As I talked about with that info dump post above, we can show information instead of telling readers about it.
Showing tends to include more action, so the pause is less noticeable. Showing in a deep point of view also keeps the information in the character’s voice, which makes the insertion less noticeable as well.
…Woven with Other Story Elements
Another way to make the pause less noticeable is to weave the information with our storytelling. That means that we mix the information with other elements of our story so that any information shared isn’t in a big chunk.
So if information is relevant, timely to current events, and shown and not told (if appropriate), let’s talk about how we can weave that information into our story on three different levels…
Usually when we talk about weaving different elements together, we focus on smaller chunks, but I want to start here—at the scene level—to give a complete picture.
Our scenes need to have more than one reason to exist. If they have just one purpose, they’re not working hard enough to justify themselves, and they might, in fact, be a tangent that takes away from the point of our story.
As I’ve written about before, our scenes need to include at least three reasons to exist, such as: plot points, character goals, character development, conflict, stakes, etc. Ensuring that we’re weaving different purposes into a scene is the reason behind my Elements of a Good Scene Checklist (and Worksheet).
The Elements of a Scene Checklist is meant to help us identify when a scene isn’t pulling its weight for the story. When we spend a lot of words on unimportant things, we drag the pacing of our story down, and a scene that’s only an info dump will make our story stop dead in its tracks.
Conversely, if a scene moves forward a reader’s understanding of the story, the pace remains solid because there’s a feeling of forward momentum being driven by an all-encompassing purpose. In other words, a scene with a purpose prevents readers from feeling that the pause button has been pushed. *smile*
The next level of weaving is making sure that we don’t have paragraph after paragraph of the same element in a row. Action, description, exposition, dialogue, internalization, etc. should all be used but not overused.
I often think in terms of a Two-Paragraph Guideline. We can switch between action, exposition, dialogue, internalization, etc. every two paragraphs (or so) to prevent reader boredom, pacing issues, and choppiness.
(Note that the two-paragraph guideline is just that—a guideline. *smile* It’s a reminder to use all the tools in our toolbox.)
We’ve heard that readers can follow three paragraphs of unattributed dialogue (assuming there are only two speakers), but after that, readers need a descriptive dialogue tag or an action beat to ground them in the scene again. On the other end, setting description can get boring after one paragraph. So two paragraphs of any one writing element in a row is a good guideline.
If we need more than two paragraphs of introspection, we might look at how we can mix in action. Is the character doing something while they’re thinking? Even better, can we make the action add to the scene by creating conflict or showing subtext?
Maybe a wife is thinking about leaving her husband while she’s folding laundry. Does she discover a lipstick stain on his shirt, and she decides that’s the last straw? Or does she take care in folding his clothes “just so” to prevent wrinkles, showing that she still cares about him?
At the sentence level, we can break information into sentences, or even just phrases, that are woven with other elements. These short insertions allow us to share information with a reader without calling attention to it.
Much of writing is about creating layers, and that’s what weaving is all about. We don’t have to paint the full picture of our settings, worldbuilding, or a character’s backstory (or any other potentially tricky element) all in one go.
For backstory, in chapter one, we might mention that the hero has a bad relationship with his father in a single sentence or phrase. In chapter three, we might reveal the detail about how long it’s been since they’ve spoken. In chapter eight, we might share the words of their last fight. Etc., etc.
Similarly for setting, at the start of every scene, we need to anchor readers within the setting. However, that doesn’t mean we should open every scene or chapter with a paragraph of setting description. Instead, we can include a phrase here and there.
In the same way, our world-building can be constructed one phrase or sentence at a time. Over time, they’ll give readers an impression of our world.
To illustrate, here’s the opening two paragraphs of my novel Treasured Claim:
Jewelry trickled through Elaina’s fingers, scattering reflections across the peeling linoleum of her bathroom floor. Each piece hinted at how she’d acquired it for her collection—a broken clasp on a silver chain, earrings missing their backs, a loose sapphire she’d rescued from a sink drain. But the precious ornaments lacked the satisfying clink of gold coins when they landed in the safe-box at her knees.
Humans didn’t make treasure like they used to. Such a shame.
Setting: Just two phrases—”peeling linoleum of her bathroom floor” and “they landed in the safe-box at her knees”—are enough for readers to visualize the scene. We see that she’s in a bathroom, that her bathroom is low-end (peeling linoleum), and that she’s kneeling in front of a safe-box of her treasure collection.
Backstory: We get that there’s something different about this character. Who is she that her linoleum is peeling, that her jewelry collection is made up of broken pieces (and she’s not bothered by that fact), and that she finds the clink of gold coins satisfying?
Worldbuilding: We understand from one short sentence—”Humans didn’t make treasure like they used to”—that she’s not human. Readers might also pick up on the subtext of how she values jewelry that humans wouldn’t, thinks gold coins are superior, and finds it a shame that humans’ concept of treasure has changed. If readers start thinking “dragon,” they also get the world-building hint that this dragon has fingers. Ahh. A shapeshifting dragon.
That’s a ton of information shared in four and a half sentences. Yet none of it interrupts the story flow, feels irrelevant, out of character, or outright told as an authorial interruption.
(Bonus Tip: We can use color-coding to check for paragraph or sentence-level weaving.)
Putting It All Together: Avoiding Info Dumps
Readers don’t mind backstory (even flashbacks), or anything else that could potentially hit that pause button, if the story flows and moves forward. That’s the key for including backstory, worldbuilding, or anything else in our story.
Backstory has a bad reputation because it’s often used so poorly. Writers include big chunks of information before a reader needs it (or is even curious about it), and the chunks don’t feel like they fit the story, character, voice, or point of view.
Avoiding problems requires us to include information in a smart what, when, and how way. We should share necessary information only when the reader needs it in a way that fits the story (and scene, paragraph, sentence, voice, point of view, character, etc.).
- Relevant information doesn’t interrupt the story’s pace.
- Timely information fits current events and keep the story’s flow.
- Shown information feels active and true to the character.
- Weaving information in layers gives readers what they need to know without dumping information all at once.
That said, we’re not likely to get this right in the first draft. First drafts are all about discovery, discovering the story and the flow of scenes. But when we begin revisions, we have to take a hard look at those info dumps and see where we can:
- cut what’s not relevant,
- move information to the scene where it’s needed,
- change told information to shown information, and
- weave information over layers of scenes, paragraphs, and sentences.
If we interweave those details with other elements, we’ll have a better chance to keep the natural flow of a scene and maintain our story’s pace. And all of that will help us keep our readers immersed in the story. *smile*
Have you read stories with too much info dumping of backstory, setting, worldbuilding, or other element? How could the authors have fixed the problem? Do you struggle with info dumps? What type of information is hardest for you to weave within a story? Does this post help, or do you have other questions?Pin It