Is it considered lazy writing to have a dry prelude at the start of a book?
I'm thinking of the crawl sequences at the beginning of Star Wars, that just give you the background information straight up, and then start the excitement. I've just been wondering if putting a prelude like that at the beginning of a novel would be too 'lazy'?
Lazy in the way that I'm providing context directly instead of having it explained by characters throughout the story. The book I'm writing is a Sci-Fi set a certain amount of time after society has been rebuilt/is being rebuilt after Nuclear War, so the prelude would somewhat detail this.
Too lazy?
This post was sourced from https://writers.stackexchange.com/q/37862. It is licensed under CC BY-SA 3.0.
4 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
The thing about the Star Wars crawl sequences is they’re very short, less than 100 words. They work because they’re short, interesting and presented in a novel way (back then). They’re also necessary to provide context to the opening scene of action that follows.
I would ask yourself the same questions.
Is it absolutely necessary and essential for your story? Where does your novel start? Does it start in media res where the opening scene wouldn’t make sense without the prelude giving context?
Is it really really short? The last thing you want to do is info-dump the reader on page one. You have very little time to hook a reader. Some say it’s only a page, some say five. For some readers, it may be a paragraph. Readers may tolerate a brief prelude but a long info-dump will be a turn off. Much better to start with an action scene that introduces your main character.
Is it really interesting? If your prelude sparkles with an exciting premise, you may get away with it. But if it’s boring, you’ll lose your reader before they even put your book in their shopping basket.
Can you present it in a novel way? If it’s absolutely necessary can you spice it up with a unique delivery? Erin Kelly with He Said She Said has a prelude about a total eclipse. She separates it out into small sections describing each ‘contact’ alongside a picture of an eclipse. She also uses interesting descriptions to keep this prelude alive.
Generally readers like to be shown your story, not told it. They want to figure things out for themselves and draw their own conclusions rather than having a narrator lay it all out on the page in exposition. But, ultimately, it’s your book and you are allowed to be as ‘lazy’ as you like about how you present your backstory. Whether a reader will tolerate it is another thing. Do you really want to risk losing a single reader because it was too much effort to bleed the backstory into the narrative?
In short, ask yourself if the prelude is absolutely essential to provide context to your opening scene/s. If it isn’t, I would avoid it.
Good luck!
This post was sourced from https://writers.stackexchange.com/a/37865. It is licensed under CC BY-SA 3.0.
0 comment threads
A feature of modern SF and fantasy is that readers are expected to tolerate not knowing the details of the world at the start, and to pick up these details as they go along. Instead of an info-dump at the start, the relevant information is presented more naturally as the story unfolds. This requires the reader to be more active, and as a result this can pull the reader deeper into your story.
The classic method is exposition to another character. Frequently you'll have one or more audience surrogate characters who start ignorant of basically everything. As those characters learn more about the world, we learn with them. Often this character is also the lead character too, because that gives us a classic Hero's Journey, but it's not always the case - sometimes the lead character is the one dropping exposition on a sidekick.
This can be obvious, clunky and boring, as anyone who's read Dan Brown will know. But it can be done elegantly too, especially when the way in which this is handled provides more background to the people concerned. In Dune, many interactions with the Bene Gesserit are infodumps, but the way the Bene Gesserit characters approach the situations and the way others react make them an essential part of the story. The infodump provides some detail, but simultaneously you're picking up characterisation and implied information about how the society works.
Sometimes you don't even get that, and you're expected to pick up smaller details as you go. Maybe you have an alien race whose appearance isn't explicitly described initially, because all the characters are familiar with them; but the details slowly emerge as things happen. You don't have to say "he's got tentacles instead of hands", you casually say "I transferred credits with a touch of finger to tentacle", for example.
It's also perfectly acceptable to start in media res, and drop short infodumps or timeline jumps as interludes. This is used pretty frequently by Neal Stephenson and Charles Stross, for two examples off the top of my head.
This post was sourced from https://writers.stackexchange.com/a/37875. It is licensed under CC BY-SA 3.0.
0 comment threads
It's not exactly lazy, it has the potential to be considered bad writing. If an agent asks you for the first five pages of your book (and many ask for just five), is that what you want to send them? They don't want to represent "dry" writing, they want something engaging from page one. Not fireworks and battles or the world blowing up, but an engaging character doing something in their normal world, and leading into the story.
You'd be misleading them to send them anything else, likely guaranteeing they won't represent you. And if you did send them the first five pages after your dry prelude, if you were relying on that prelude to orient the reader, then the agent won't like those five pages either, because they won't make much sense. So ... rejection on route two.
Like the Star Wars lead in, readers/agents/publishers, by opening the book, will give you a small allowance to get the ball rolling. If your dry prelude is clearly less than a page long (say less than 200 words) then you can probably get away with it.
But if it takes you less than 200 words to provide this back story, you can probably dispense with it! That much information can be conveyed indirectly or in scene, or truthfully, not at all.
Human beings IRL are very adept at picking up clues and piecing together what is going on without being explicitly told what is going on. We can watch a conversation in a restaurant and guess many things about the characters having it. In writing, you can use place names, names of people not present in the scene, and all sorts of things and trust your readers to figure it out.
Just like in real life, we meet new people we have to work with and don't know anything about them, nearly everything we learn about them we learn in context, not by somebody telling us all about them. The same thing can be true of your setting and plot. You can have pages where all the reader knows is "they are going to Seattle" without knowing why. As an author it is up to you to devise scenes to fill in why and the background. Aha, they don't want to go to Seattle but they are. Aha, somebody named "Jack" is going to punish them somehow if they don't. Aha, they are going there to steal something that was stolen from Jack!
I honestly think Star Wars could have opened without the text prelude, and everybody would have figured it out just fine, who the heroes and villains were. The visuals showed underdogs massively outgunned just fine, and we would naturally root for them. The movie might even have been better for it.
0 comment threads
Not too lazy. Your work habits really have nothing to do with it. The question is, can you make it interesting?
Providing context is difficult because it is a chicken and egg problem. No one cares about the context until they know what is a stake, and no one can tell what is really at stake until they know what the context is.
Ways of handling this go in and out of fashion, and the idea that you can avoid an infodump at the beginning by having two characters fill in the background with dialog later is a popular approach at the moment (though more so with aspiring than published authors). But when it comes down to it, this is still an info dump, and an infodump with dialogue tags is not really an improvement.
The real answer, as you can see in the works of successful authors, is not any form of info dump, but compelling immersive writing. Thus LOTR starts off by immersing us in the Shire. HP starts off in Privet Drive. Cannery Row starts off with a stunning description of Monterey. These are not info dumps. These are vivid immersive portraits of a world, a place, a time, a people.
This stuff is compelling by itself, if it is done well. It does not have to start with a plot. (How far into LOTR do we get before the plot is properly initiated?) At most they require a kind of tension that suggests that the material for a plot lies ahead, that this is the sort of place where something interesting could happen.
That is what you need to do. Not an infodump, in any form or in any place, but an immersion in a compelling situation.
0 comment threads
0 comment threads