What is the role of "flashback" in my novel?
I start my Revolutionary War novel on August 21, 1780, when "boy meets girl." Specifically, the hero is rescued from British captivity by a bunch of guerrillas. One of these guerrillas takes him home to meet his sister.
Shortly after the meeting, I show a flashback to the battle where the hero was wounded and captured, on August 16, 1780, five days before the story "officially" begins. This battle generates the conflict; the hero has had enough of war, while the heroine wants him to join her brother in his successful fight.
A critic felt that this "backstory" was unnecessary. I believe that it is necessary.
How does one determine who's right? And if I'm right, is "flashback" or some other method a good way to present the battle? In a movie, I would present the battle first, because of its "action," but in a novel, I reversed the order and presented the "meeting" first.
This post was sourced from https://writers.stackexchange.com/q/35690. It is licensed under CC BY-SA 3.0.
2 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 determining criteria will be how much information the reader needs. Generally you want to use flashback for a few reasons.
1) Need to know protag and/or context for emotional impact. A battle scene may not make much sense to the reader/viewer if you open with it: Everybody in it is a stranger, the reader doesn't know or symapathize with your character, doesn't even know if she is the hero or villain, doesn't know the cause or stakes of the battle. It is JUST action, and action without stakes or investment can be boring or confusing instead of exciting.
Who are these people and what are they fighting for? To tell them that you would need all kinds of interrupting explanatory BS in the midst of battle, and in movie or book, that is just bad writing. The flashback solves this by letting us get to know the protag for a bit, sympathize with her, and then we have some context in this battle.
2) Need to hide information from reader. This can be similar to reason (1), but we may want to intentionally NOT reveal information that will come out in the battle. In the battle we may reveal the hero we have come to know for a chapter is not exactly who we thought she was. She is lying about her actions in battle, she is not the innocent bystander we thought but a merciless killer, not the soldier following orders but a commander on the field. Or vice versa; she has lied to other characters in the book about her role in the battle or who she is or what she has done.
3) Importance ranking of reveals. This is more of a writing strategy. Whatever first conflict your story opens with is generally more important to the whole story than subsequent conflicts. Both battles and love stories are conflicts; which one is more important to the whole plot should be found first. So if the bloody battle is necessary, describing it physically after the love life begins makes the bloody battle a secondary conflict, perhaps a complication, perhaps just an explanation of our hero's psychology, even though it is temporally out of order.
Putting the bloody battle before the love conflict does the opposite, it seems to the reader like something that should be resolved, and if resolved too quickly then it is disappointing to the reader; a head fake. You gave the battle too much prominence by putting it first; getting your character known to the reader is more important, getting the romance underway is more important, then whatever it is the battle explains about the character and complications of the romance can be told without the reader mistakenly thinking this story is about battles.
On a related note, most (highly rated) movies and books begin with "establishing shots/scenes" where very little conflict is going on. Neither battle or romance. This is for the audience to get a feel for their hero, what is being "established" is the every day world of the hero before that world changes forever. The audience/reader must identify with the personality of the hero first or nothing the hero does is care-worthy.
This is not to say you should not begin with conflict: It just needs to be clearly inconsequential conflict. In "When Harry Met Sally", the two romantic protags are introduced and immediately in philosophical disagreement, but this is just a verbal, funny, sometimes frustrating conflict. (they are "in a box", i.e. sharing the expenses of their long car trip prevents either from walking away from their temporary partnership out of philosophical irritation).
How characters respond to conflict reveals them to the audience. It is valid advice to begin with conflict (and have conflict everywhere), but character revealing conflict, not high stakes life-and-death conflict like a battle. Many beginning writers get confused by this and use the easiest conflict to write: A physical fight. But the high-stakes fight falls flat when we don't know the stakes, or the characters or have any reason to care.
In general, save your battle for physically later in the story, when the reader wants your hero to live, and hopefully wants the villain to lose (even if that is not how the battle works out).
Also there are alternatives to flashback. The hero can reveal what happened verbally, in conversation or interrogation.
Is the battle necessary? The battle is only necessary if something in it has specific ramifications to the plot line. Just "I've killed many men" is enough to cover the emotional impact on the hero of the battle; i.e. just a few lines of dialogue can do the job, you don't need a scene.
If there is some specific action we need to see (e.g. in battle rage she intentionally kills somebody with valuable intelligence she knew she should not have killed, or she made a mistake and unintentionally killed a child and this haunts her, or she impulsively disobeyed orders and got her comrades killed, or took an impulsive risk that got them killed, our hero was a coward and NOT a hero in this battle like everyone thinks, etc).
Some things need to be shown, not told, and vice versa. It depends on the pacing of the story, and whether you can afford to interrupt it for a whole battle scene, and it depends on how important the ramifications or consequences of the battle are: if they are big and plot-changing, show it. If they are more general information (our hero has experience in battle) use a short version to refer to this un-shown battle in dialogue, not flashback.
0 comment threads
You should be able to answer a few questions here.
Why is the flashback necessary for the story? What does it add or change, that makes this a better story than without it?
Why is the flashback interesting now, to the reader? You may know the flashback is setting up important stuff, but the reader has to take that on trust. You don't want them to feel the new bit is a distraction from the "real" story; nor that the first piece was just a throwaway prologue, and could have been skipped. This means that at the moment you cut to flashback, the reader starts seeking a reason for both the new and old scenes to be interesting in conjunction; it's up to you to provide them with one.
What would this look like if I did this without a flashback? I'm by no means against flashbacks, but this is worth asking. Could you possibly encapsulate your conflict in one, sharp scene, rather than contrasting two opposite ones? I'm not encouraging you to prefer one over the other, but to tell whether something is necessary, it's helpful to consider the alternatives.
The three of these form a very solid justification for a flashback -- or help you see where its issues may lie.
0 comment threads
0 comment threads