Welcome back readers to another installment of Being a Better Writer! Today’s installment is somewhat unusual in that it was written days before the actual posting. Why? Because if all has gone as planned, today I am off on my way to Alaska to visit family, taking my first travel vacation (and my first trip to where I grew up) in about half a decade.
Yikes. When I say it like that, it does sound like I need a break. Here’s hoping it is a relaxing one and I get some peace of mind from it.
Anyway, that means no news with this post, because it was written a while ago (and it would all be out of date). So sit back, relax (like I’m supposed to be doing) and get ready to talk about writing. While I, if all has again gone to plan, will be traveling through the air or spending my night at an airport. Or something like that.
So let’s talk about infodumping for a moment. Infodumping is one of those things that worries a lot of writers both young and old—and with good reason! Anyone that’s picked up more than a few books in the last year can probably recall a moment where the story might have slowed down and turning into a page or two of just … information. About the world, about the setting, about the characters … but it was just information that hit the audience with the force and subtlety of a firehose.
This is the infamous infodump. A moment when the author sits back and says “Well, the readers need to know about this” and just dumps it all on them in solid paragraphs of informational text. Or worse, does this for information that the audience doesn’t need to know, but the author really wants to talk about (you’ll see this more with “author fillibusters” or “soapboxing“).
But the result is roughly the same in the end: Solid paragraphs of pure information, something usually akin more to a work of non-fiction than fiction, and a wall for the audience (barring the few who would naturally read this sort of thing anyway). Infodumping remains a cardinal sin in the writing world as a result, a giant speed bump to any reader that comes across it. It messes with pacing, such as one book I can recall where the author interrupted a plot-critical meeting to give a page-and-a-half long aside on the origins of a phrase one of the people in the meeting had used … and then cut right back to the meeting, in the middle of the previous sentence they’d cut off in, and somehow thought this wouldn’t be an issue.
Their editor also apparently thought so, which was why this title did this multiple times, and each time the information that was actually presented was superfluous to what was actually going on and purely unneeded. Like I said above, some authors just really want to talk about things they came up with for the setting, and well … yeah. Imagine watching a movie where every time things really got moving, the director would pause the film and talk about some behind the scenes stuff. Not as a bonus feature, but as the film you went to see in theaters.
Annoying? Yes. This, and other forms of infodumping are like kryptonite to readers. They sap the reader’s will to, well, read. But this introduces a conundrum for a lot of young writers because well … How can you get a reader invested in a world and knowing what’s going on if you don’t inform them of what the world is like? Or the characters’ backgrounds? Or anything else that’s relevant to the plot?
So hit the jump, folks, because today we’re going to talk about the right and wrong ways to infodump. Or rather, how to avoid the wrong of infodumping while still informing our readers of what they need to know.Continue reading