Beta Reader Group discussion
Writing Advice & Discussion
>
Tips with mitigating infodumps in Sci-Fi?
date
newest »


The only other thing I'd advise is to try to assess each piece of information and ask whether or not it could be revealed earlier or later (possibly a surprise) in order to distribute the length throughout the book more but it seems like you may have already considered that. Good luck.


I write historical fiction. I agree with Dana about doing your best to make it natural. I wrote a novel about the heart-lung machine. Pediatric heart surgery isn't exactly the most accessible topic. I needed the reader to have a basic understanding 1) of how the human heart works and what a ventricular septal defect is, and 2) how a heart-lung machine works. For the heart and the VSD, I had my main character, a heart surgeon, explaining to his 11-year-old patient how the heart works and what is wrong with her heart. The information gets across to the reader, and I have a scene that reveals character, both the girl and the MC.
For explaining the machine itself, I had my MC have to seek approval to use the machine from his bosses; he has to take them thru the basics of how it works. I tried to interject some tension into the scene & discussion - my MC really wants to use what he's built, but it doesn't look like much, and his bosses aren't exactly impressed. The scene serves to explain the heart-lung machine, but it also serves to advance the plot: the MC, it turns out, is going to have to prove his machine is safe and works.
Sometimes, though, I do just simply jump in and provide the plain exposition. For example, at one point, a child develops heart block; I simply provided a paragraph or two of exposition explaining what heart block is and why, in 1956, this condition would be a disaster. But I always try to limit explanatory exposition to a paragraph or two. My thought is: what's absolutely necessary, get it in and get out and back to the story as quickly as possible. Straight-up plain exposition generally doesn't just slow your story - it brings your pacing to a dead stop. For what you're describing, I'd try to find a creative way to present the information so as not to bore the reader. I'm not familiar with sci-fi specifically, but at least as a historical fiction reader, 2-3 pages of straight-up plain exposition would feel like a lot, and I would try to avoid doing that if you can.


- write what is really exciting about something in a lot of geeky detail, not just checking boxes
- use what I call pseudo-dialogue. Basically, keep alternating paras from the info-dump with something else (not crap like "hmm" said the other person). So character may be thinking about info dump while doing something else. One para info, one para action. Rinse, repeat.
- juxtapose TWO info dumps. Problem with this plane he's building and its physics vs background on inventors how they contributed to the history of that plane. Wing designed by this fellow who wanted his son to fly, fuel efficiency was increased from blah to bleh when that fellow did.... background story and it resulted in...
- Split out into a format. A brochure about something that is its own scene/section. Sign on a door.
- Break it up. Some info dump happens, then fellow bangs his head on something accidentally. Gets back to the rest in a bit when he has an idle moment.
- Turn info dump into narration. 5 detailed rules of sneezing is boring. The story of how they came to be could be interesting.




I'm thinking of how The Davinci Code ended, for example, where Langdon in mentally realizing what's beneath the pyramid at the Louvre.


if you really want the reader to know, just explaining it isn't going to work anyways unless that person regularly reads non-fiction, maybe. so the characters might have different understandings or opinions on the thing and as the talk slightly above the reader's knowledge level little bits and pieces of exposition will be revealed.
Are there ever times where you just have to go on for 2-3 pages of exposition? This information has to be clear to the reader before the story goes further, but I'm worried about the amount of telling it involves.
Thoughts?