Category: flashbacks

Happy Halloween, everyone! Hope you’re all prepared for tonight. And may the gods have mercy on those of you who aren’t…

Let’s talk about scary movies for a moment.

If you aren’t familiar, there was a long-running movie series called Resident Evil based off the long running game series of the same name, which also spawned a series of animated movies. But we’re talking about the live action ones. Well, the original live-action ones.

Specifically, I’d like to talk with you about the first one, written and directed by Paul W.S. Anderson. Rather than base the movie directly off the game story, Anderson decided to use lots of elements from the game with all-new characters. This gave him a lot more freedom in how he told the story, and let him structure the film for a general audience instead of specifically for fans of the game.

That structure is what I wanted to talk about. If you’ve been following the ranty writing blog for a while, you know I love pointing out how well this movie uses flashbacks. Seriously, it’s amazing. The movie’s pretty much a masterclass in how to do flashbacks well in a story. They all serve a clear purpose. They all advance either the plot or the story (often both). They all fit within the narrative and linear structure of the story. And none of them create fake-tension situations that are undermined by the present. You can read more about my rules-of-thumb for flashbacks right here, if you like.

So I figured, since it’s Halloween and all, I’d walk through these flashbacks one by one and show you how and why they’re so effective.

Now, you’re going to get a lot more out of this little rant if you’ve seen the movie. I highly recommend checking it out. It’s seasonal, it’s fun, it’s much more of an action-horror film than a gorefest. I don’t know if it’s streaming free anywhere, but I think you can rent it most places for three or four bucks? Also, kind of goes without saying but there are going to be some unavoidable spoilers in this discussion so… be warned.

Here’s a brief refresher for those of you who haven’t seen it in a while (or are just determined to go on without seeing it)…

Resident Evil begins with a few quick minutes showing the lab accident that kicks off everything before the lab goes into a drastic lockdown mode that seems to kill, well, everyone. And after that we’re with our heroine, Alice, who wakes up naked and wet on the floor of a bathroom, half-draped in a shower curtain and suffering from near-complete amnesia. Very quickly she learns she’s part of a security detail guarding a hidden entrance to the Hive, a massive underground lab/ testing facility operated by the multinational, multibillion dollar Umbrella Corporation. And the lab accident earlier has set a very nasty bioweapon loose down there, the T-virus, which has had, politely, some effects on the researchers and other staff members.

And we’ll stop there for now.

So let’s talk flashbacks. I’ll try to go over all of them and give you a little context for each one. I’m also going to mention where they are so if you’re actually doing your homework, you can skim around in the movie and find them.

Our first one shows up a little over nine minutes in. Alice has woken up, staggered to the bathroom mirror, and is staring at her reflection when this flashback kicks in for a few seconds. She was in the shower, there was a vent, her eyes rolled up, and she collapsed, dragging the shower curtain down with her.

So this first one does a few things. It tells us right up front Alice didn’t pass out she was knocked out—this is something that was done to her, not something that just happened. It also establishes her flashbacks are very distinct from the “present’ story line in the movie—they’re in overexposed black and white, with echoey sound and a fast cut, glitchyquality that helps sell her fragmented memory. And it fits story-wise. This is something she’s focused on and trying to remember, so it makes sense we’re seeing this and not, y’know, last night’s dinner or something.

Also worth noting Alice’s reactions after this flashback because it’s very clear this is all the information she got from this sparked memory. She still doesn’t know who or where she is, or what’s going on. This is going to hold for all the flashbacks—she doesn’t get anything “extra” out of them. She sees what we see.

Our next flashback comes at eighteen minutes in. Alice has been taken with the security team to the underground train that leads to the Hive, and they’ve found an unconscious man on board. Alice stares at the man’s face and flashes back to her and him together and happy. Again, just quick flashes. Her in a gown, him in a tux, laughing, posing for photos together.

Worth noting that Alice had also seen a wedding photo of her and said man a few minutes earlier, and this flashback pretty much explains where that photo came from. It also connects the two for the audience—the man here now on the floor of the train (we’ll learn his name is Spence and he’s also suffering from gas-induced amnesia) is the man we saw earlier in photos. Whoever he is, Alice has a definite history with him.

Which brings us to the third flashback. Maybe 22 minutes in now. It’s mostly a recap of the first one as the security team commander explains what’s actually going on here and gets everyone up to speed. So as he’s explaining the computerized security systems and known side effects of the gas (short-term amnesia), we see Alice get gassed in the shower again—this time with an extra few shots to show us how the vents are hidden away in the walls.

So this one’s a little more structural—it’s a quick reminder for the audience. It emphasizes things are run by the computer (some of you know where that’s going). It’s giving us a bit more information about how thing are hidden and automated in Umbrella facilities.

Our fourth flashback happens three or four minutes later (just shy of 26 minutes in). We’re in the Hive now, and Spence offers Alice his leather jacket to keep warm. It’s the first time they’ve actually touched and it sets off a bunch of memories for Alice. Really specific ones showing she and Spence knew each other. Like, y’know… knew each other. Physically. As was the style at the time.

And that means now Alice knows something about Spence. He’s clearly someone she has a history with, and a history that involved, well, a degree of sharing and trust between them. As always, she doesn’t remember anything else, but it’s enough that she clearly decides he’s someone she can trust.

Notice the pattern here so far. All four of these flashbacks barely add up to fifteen seconds. They’re not slowing anything down. They’re all related to the actual events going on and the information the movie’s giving us (and Alice). And every one of them tells us something new—there’s very, very little noise. They all keep advancing out knowledge of the plot or the characters.

The next flashback doesn’t happen for almost half an hour—there’s a lot of action going on and dropping in a flashback would just disrupt the flow of things. Then around the 53 minute mark, Alice saves Matt from a zombie that’s attacking him and she recognizes this zombie. We get our longest flashback yet (almost ten seconds!)– Alice and this woman meeting in a deserted graveyard, where Alice is offering her access to the T-virus, Umbrella access codes, surveillance plans… for a price.

So… this one does a bunch of stuff. It’s suddenly casting Alice’s real goals and loyalties into question (at a point when she still can’t even remember them). It’s showing us she was part of a larger story than just the current events going on in the Hive, and making it clear Umbrella has been a questionable company for a while now. It’s also a nice reminder all these zombies were actual people—people we saw back at the start of this doing their jobs, chatting, drinking coffee, and just living their own lives.

And it doesn’t help that shortly after this Matt tells Alice the mystery woman was his sister. The two of them were gathering information to expose Umbrella’s illegal, unethical practices. His sister had found someone who could get them all the information they needed to get out with the evidence… but whoever it was they betrayed her. So now this flashback has Alice really questioning herself—and us questioning her, too. Amnesia-Alice seems great, but maybe if she had all her memories…?

Now, something happens around 70 minutes in that’s worth mentioning. Alice gets some memories back but it’s not set up as a flashback. It’s not in blown-out black and white. It’s not glitchy. And she’s not part of it. She just suddenly recognizes an area of the Hive they’re in and pictures it up and running and full of people. And she remembers what should be in a nearby lab– the cure for the T-virus.

I think this is worth noting because by breaking the flashback format here, the movie’s showing us that things are changing. Alice is getting more solid memories, and they’re appearing more solid because of that. The flashbacks are a clever device and being used well, but things are moving past the point of needing them and trying to force this particular bit of information into that format could actually be distracting at this point. And we never want our flashbacks to be distracting. Also, this scene is a little longer and somewhat talky but it’s happening at a time when our main story has slowed down a bit. Again, it isn’t messing with our flow.

So… moving on. One final flashback, and it happens just two minutes after the last one. They find the lab with the cure and it’s gone. The vault is empty. And as our heroes look around the lab trying to find some clue what might’ve happened to it… Spence has a flashback. And it’s a big one.

Turns out Spence was spying on that meeting in the graveyard, and he decided to steal the T-virus first. And almost 2/3 of his flashback is… the very beginning of the movie. All seen from his point of view. Spence caused the lab accident! Deliberately! To cover his theft.

(fun fact—if you freeze frame at the three minute mark in the very beginning, you can actually see it’s Spence right then! At 3:02, to be exact)

So, what does this last flashback do? It tells us what really happened to cause the lab accident. It reveals Spence as one of our main villains all along. And it firmly establishes that Alice, with or without her memories, is our hero—we find out her “price” for giving Matt’s sister all this evidence is that they use it to destroy the Umbrella Corporation.

Again, new information given in a way that adds to the tension, doesn’t slow down the pace of the actual story, doesn’t undermine anything.

See what I mean? Seven flashbacks in a movie that’s barely a hundred minutes. And heck, really all of them are in the first seventy minutes or so. And every one of them works for both the narrative and linear structure. Every one of them gives us information that’s relevant to “now.”

That’s some good zombie flashbacks.

Next time, I’d like to talk about how long all this takes.

Until then… well, enjoy Halloween.

And then go write.

So, I’d like you to cast your mind back a few weeks to when I told you what we’d talk about next time. Which, by odd coincidence, was casting you mind back a few weeks to thhink about what I told you then…

Yeah, I’m running late, but it turns out it works thematically so… yay.

I thought it might be cool to talk about flashbacks for a minute or six. I’ve mentioned them half a dozen times over the past few years—usually relating to story structure, but I haven’t really talked about how to do them in a couple years. Maybe ten years? Wow I remember it as if it were only yesterday…

Anyway, for our purposes, when I’m saying flashback it can cover a few things. It can be an element within the story like a recalled memory, or something more physical like a letter or journal entry. Sometimes, like in my Ex-Heroes series, it’s part of the way the narrative has been structured. All I need to remember is that whatever form my flashback takes, it just needs to follow a few rules-of-thumb if it’s going to work.

<insert usual disclaimer of yes it’s always possible to find a way, exceptions do not disprove the rule, etc, etc>

Now, first rule of thumb is I can use a flashback anywhere in the story, but this switch in the narrative structure can’t affect the dramatic structure. If I’m going to drop linear point E between points R and S in my narrative, it still has to keep the story moving forward. It needs to keep building tension and/or pushing the character arc. If it doesn’t do either of those things… what was the point to this flashback?

A lot of writers use flashbacks as infodumps. The flashbacks are seen as a chance to show how Wakko met Phoebe, how Phoebe became a ninja, why Wakko hates snakes, and so on. The mistaken belief is that if I do this in a flashback, I’m not affecting the pacing or tension of the present storyline because these events aren’t happening now—they’re happening in the past.

When I do this, I’m confusing linear structure with narrative structure. A flashback has to keep moving the story forward. It doesn’t matter where the events fall in the linear structure of the story, but wherever I’m using them they have to fit into the narrative structure I’ve established.

I mentioned the Ex-Heroes books and, in all fairness, I did this with the first one. I dropped a flashback dead in the middle of the big climactic end battle and brought things to a grinding halt. Full-tilt, non-stop action to no-tilt, standing-in-place dialogue chapter in one page. Which meant (once it was pointed out to me) weighing if I needed this flashback or not, and if I did… where should it be instead? Where would it actually fit?

Now, the second rule of thumb is just the reverse of the first one. It’s when I confuse the narrative structure with the linear one. This is similar to a problem I’ve mentioned once or thrice before, understanding when something happens for the first time in my story. When I do this with flashbacks, instead of messing up the tension or the pacing. I mess up the internal logic of the story. It also happens sometimes with poorly set-up twists or reveals.

F’r example let’s say I’m telling a werewolf story, and on page 100 my protagonist has no idea who the werewolf is. Then, on page 200, I flash back two weeks to something that happened “off camera” earlier. Here I reveal that she learned the identity of the werewolf because of a clue she spotted in the old family Bible.

And yeah, in a quick, don’t-think-about-it-too-much way, this makes sense. On page 100 she doesn’t know, but by page 200 she does. Except… it’s new information for the reader on page 200, yeah, it’s not new to my heroine. She’s known all along, right? Pg 200 happened before page 100 once we look at this in linear order. Which makes her actions, motivations, and even some of her dialogue for the last hundred pages… probably don’t make a lot of sense.

The simplest way to test this is to take my narrative apart and put it back together in linear order. When I read it now… are people doing or saying things that don’t make sense? Does that twist land really flat? Are they acting strange for no reason? If my flashback doesn’t work once it’s in linear order… something probably needs work.

Now there’s one last thing I need to watch for, and that’s my third rule of thumb. This one had a bit of venn diagram overlap with the last two, but I think it’s pretty its own thing. It’s also a common problem in prequel stories which, if you think about it, are just big flashbacks.

By its nature a flashback is giving my readers a glimpse into the past. This also means, though, that they’ve effectively seen the future. They know, to a large extent, how things are going to play out. So trying to create a lot of drama and tension within my flashback can end up feeling… well, a little silly. Did forty-year-old Phoebe get eaten by a shark when she was fifteen?!? Hopefully we’ll find out in her next flashback…

I think some writers feel like they’re adding to the tension or suspense when they do this with flashbacks. Thing is… there really isn’t any tension in this cliffhanger, is there? Because y’see, Timmy, the moment the reader pauses, even for an instant (like, say, at this chapter break), they’ll remember forty-year-old Phoebe’s back here in the main narrative of the story and pretty solidly un-shark-eaten. No missing limbs. No major scars. Not even any nibbles that we’ve seen or heard her mention. So the attempt to build tension here just feels, well, artificial. It’s me trying to create tension in a situation where there clearly isn’t any.

So, to recap, my three three rules-of thumb for flashbacks.

1) My flashback needs to work within the narrative structure.

2) My flashback needs to work within the linear structure.

3) My flashback can’t create tension that’s undermined by the present.

Also, as I’ve been doing for years, I’m going to suggest some homework for you. Go watch the first Resident Evil movie. Yeah, the one with Milla Jovovich. Seriously. It’s action-horror fun but it’s also got some of the best flashbacks I’ve ever seen. Each one nudges either the plot or Alice’s personal story forward a little bit more, they all fit together flawlessly (as the movie even shows you), and rather than get undermined by the “current” narrative these flashbacks actually rack up the tension in it. Honestly, it’s well worth a watch and you can probably find it for free on Netflix or Tubi or something.

You only have to watch the first one. I mean if you want to watch them all, I happen to think they’re kind of fun. No, they don’t follow the games but it’s a pretty solid sci-fi/ horror series in its own right, especially when you consider almost every movie is clearly done as “okay, this is the last one…”

Anyway, next time, I’m going to revisit my simple four step plan for success.

Until then, go write.

Very sorry this is very late. I ended up with a clever thought about how I could restructure the whole thing. And then ha ha ha ha I kind of slashed half my fingertip open while working on some little toy soldiers (always be extra-careful when you’re using fresh X-acto blades, folks) and the bandages made typing a little challenging for, oh four days.

But here we are. Finally. For one last blathering-on about structure. This is the cool one, though.

So, I started off talking with you about linear structure, and then I talked a bit more about narrative structure. This week I want to combine these two and talk about dramatic structure.

As the name implies, dramatic structure involves drama. Not “how shall I recover from this sleight, woe is me” drama, but the tension and interactions and momentum within my story. Any story worth telling (well, the vast, overwhelming majority of them) is going to involve a series of challenges and an escalation of tension. Stakes will be raised, then raised again. More on this in a bit.

Speaking of which, before I dive in… okay, look, on one level I hate breaking all this stuff down and quantifying it because we’re talking about art. We’ve all got our own likes and dislikes and styles and methods, and there’s rarely any good, one-size-fits-all advice The art part of this is personal, and we should all be a bit cautious when some guru starts telling you how stories go together and slaps down graphs and charts or some nonsense like that.

So. with that out of the way… let me dive in and tell you how stories go together. I’ve got graphs and charts to help out.

Now, dramatic structure means I want to arrange my story so tension is rising. The plot needs to advance. Characters need to make decisions, and those decisions should have an effect on them and what’s going on around them, for better or for worse. Usually for worse. It may sound silly to say out loud, but tension should be higher at the middle of my story than the beginning, and higher at the end than it was in the middle. That’s just common sense right? Nobody wants to read (or write) a story that gets less interesting and compelling as it goes on. Or a story that starts sort of compelling and then stays… sort of compelling, and at the big climax is sort of compelling. I mean, maybe I’m just weird that way?

Mind you, these don’t need to be world-threatening challenges or gigantic action set pieces. If the whole goal of my story is for science-nerd Wakko to ask out popular girl Phoebe, a challenge could be working up the nerve or just finding the right clothes. But there needs to be something for my character to do to bump that tension line higher and higher. Stand up to the bully. Get to work in time for that important meeting. Come up with $30,000 by five o’clock on Friday to save Aunt Dot’s car wash. And, yes, defeating the cyborg ninja werewolf from the future so I can deactivate the terraforming device before it turns North America back into primordial tundra.

So let’s talk and let me show you some fun visual aids. On all of these graphs, the individual points are going to represent the linear structure. I’m going to be using the alphabet to mark them because we can all recognize that order pretty quick– A, B, C, D, and so on. Our X-axis (oooh, look at me, talking all mathy and sciencey) is going to be the progression of the story—our narrative structure. Think of it as the arrangement of plot points from the first page of my story to the last page (and damn, I wish I’d thought of that explanation earlier). Finally, the Y-axis is going to be our tension levels—dramatic structure.

Got all that?

Also, apologies up front. I didn’t realize how rough these graphs would be shrunken down. Sorry. Just open ’em in another tab. Also graphic design is my passion, yadda yadda, moving on.

Okay, let’s do an easy starter graph.

This is the story of me sleeping. It’s pretty simple. We start when I go to bed, and end when I waking up. It’s told in a linear fashion, so the linear and narrative structures line up. There’s a brief moment in there when a cat woke me up (maybe Julius or Alucard?) and I went back to sleep, but that’s pretty much it as far as dramatic tension goes.

Like I said, simple. Really, this is a story where nothing happens. It’s pretty boring. You may notice it’s pretty close to a straight line. A flat line, really. And if you’ve watched a lot of medical shows, you probably know what it means when they say something’s flatlined…

So, if we want to see our heroes overcome challenges and watch the overall tension rise… what would that look like?

Well, here’s a very bare-bones dramatic structure. We start small, and tension increases as time goes by. Low at the start, high at the end. Makes sense, right?

But… this is pretty much another straight line, right? And straight lines are pretty close to flat lines (see above). So how am I supposed to have a dramatic structure that constantly rises but isn’t a straight line?

Well, let’s think back to high school physics for a minute (sorry if this is traumatic for any of you). Did any of you ever deal with that problem of playing pool on a train? As long as the train’s moving at a steady speed, you can play a game of pool on a moving train without any weird effects. Because you, the floor, the pool table, the balls… all of it’s moving together at the same speed. We’re not aware of the speed because everything’s moving together. We don’t hit a problem until the train speeds up, slows down, or goes around a corner.

Maybe a more familiar example—if I’m driving my car at a nice, even speed, I can reach out and play with the radio. I can have a drink of water or soda or coffee. I can wiggle around and take off my jacket or get my wallet out or whatever. And it doesn’t really matter if I’m moving at 40 or 60 or even a hundred miles per hour. Going in a straight line at an even speed is just like… well, not moving at all.

Y’see, Timmy, we don’t feel a constant velocity—it’s the change that stands out. That’s what grabs our attention. When I have to hit the gas or slam on the brakes or turn fast. that’s when I’m very aware I’m on a train or in my car. And these are the moments that demand attention. These points stand out above the constant ones.

So my dramatic structure can’t be a nice, even rise like that last graph. In a good story, there’s going to be multiple challenges and my hero isn’t always going to succeed. No, really. He or she will win in the end, sure, but it’s not going to be easy getting there. There’s going to be failures, mistakes, and unexpected results. Ups and downs. Because that’s normal. We don’t want a character who’s good at everything, never has a problem dealing with anything, maybe never even encounters anything to deal with. So that line is going to be a series of peaks and drops. For every success, every time we get a little higher, there’s going to be some setbacks. Any time my characters complete a challenge, new, bigger challenge is going to appear. Hell, it might even appear before they finish the current challenge.

Still with me?

Okay then, let’s try a third graph.

So, now we’ve got peaks and valleys. Things start small, but are pretty much always rising. Also, notice how even when there are lulls or setbacks, things never go all the way back to zero. The breather we get on page 150 is not the same as the one we got back on page 16. The overall dramatic structure is that tension is rising.

This might sound like a blanket statement, but pretty much every story should look something like this graph if I map it out. I mean, they’re not all going to match up precisely peak for peak, but they should all be pretty close to this pattern. Small at the start, increase with peaks and dips, finish big.

That’s it. The easy trick to dramatic structure that Big Novel doesn’t want you to know. No matter what my narrative is doing, the tension needs to keep going up.

Simple, yes?

Okay now let’s take a look at another one…

Do you see what’s different about it? Looks the same at first glance, yes? But check out that bottom row. I’ve changed the narrative structure by breaking up the linear structure. There are three flashbacks in the story now. So—for the reader—the events aren’t unfolding the same way they did for the characters.

BUT… again, the overall graph still isn’t that different. For this story, the flashbacks are adding to the tension. Learning this information at this point has made the drama stronger. I’m choosing to put this plot point here in order to create a specific dramatic effect.

This is something I’ve mentioned twice or thrice here on the ranty blog. There needs to be a reason for this shift to happen at this point—a reason that continues to feed the dramatic structure. If my dramatic tension is at seven and I go into a flashback, it should take things up to seven-point-five or eight. And if it doesn’t—if it actually drops the dramatic tension to go into a flashback—why am I doing it? I shouldn’t be having a flashback right now. Not that particular one, anyway.

Now to be clear, this isn’t an automatic thing. Events E-F aren’t ten times more dramatic just because I stuck them near the end of the story instead of the beginning. This is something I need to be aware of—me, the writer—while I’m working out my narrative structure. if I map out my story like this, even in my head (and be honest about it), I can get a better sense of how well my story’s structured. I probably don’t want a super-fast, high-tension story beat right at the start of my story. A scene with no dramatic tension in it most likely shouldn’t be in my final pages. If I’ve got a chapter that’s incredibly slow, it shouldn’t be near the middle of my book.

And if I do have things like this—things that are bending that story structure waaaay out of shape—it might mean I’m doing something wrong.

Okay, I think with that I’ve thrown enough at you. Ask any questions down below. Just remember, a lot of this is going to depend on you. The other two forms of structure are pretty logical and quantifiable, but dramatic structure relies more on gut feelings and empathy with my reader. I have to understand how information’s going to be received and interpreted if I want to release that information in a way that builds tension. And that’s a lot harder to teach or explain. The best I can do is point someone in the right direction, then hope they gain some experience and figure it out for themselves.

On which note… next time, I think we’re due for another talk about Zefram Cochrane.

Until then… go write.

Okay, we’re in the middle of a big discussion/ lecture/ infodump about story structure. To be more exact, the different types of story structure, because there are a bunch of them and they all serve a different purpose. That’s what I blathered on about last week. Well, that and linear structure. So if you skipped last week, you might want to jump back (look, a handy link) and read that first. Or maybe re-read it as sort of a refresher before we dive into this week’s little rant.

Now I want to talk about narrative structure. As I mentioned last time, these things have a few different names, depending on who’s talking or teaching, so maybe your stuffy literature professor called this syuzhet or something like that. But for now (and because it’s what I’ve done in the past) I’m going to call this narrative structure.

Remember how I said linear structure is how the characters experience the story? The narrative structure is how I, the author, decide to tell the story. It’s the order and style and viewpoint I choose for how things are going to unfold. It’s me saying I want to start with a prologue or ten minutes before the finale and then jump back to the beginning. Or that every third or fourth chapter will be a flashback. Or that I’m going to tell the whole thing from the point of view of the sidekick instead of the superhero. Or maybe, somehow, all of these things in one story. All of these are narrative decisions.

Actually, that’s a good before-we-go-any-further thing. My story might use a point of view or a device (say, a journal or epistolary form) that gives the appearance of “telling” the story. For our purposes here, though, if I talk about the narration I’m talking about me, the writer, and the choices I make. Watsonian vs Doylistic, remember? Because that first-person narrator or journal scribbler doesn’t say or do anything I don’t want them to. No I don’t care what that one other writer says about the characters having a life of their own and telling the writer what they want. I’m in charge. I’m God in the world of the story.

So, now that we’ve got our weekly blasphemy out of the way…

In a good number of stories we encounter, the linear structure and narrative structure are identical. They’re linear stories. Things start with Phoebe on Monday, follows her to Tuesday, and conclude on Wednesday. Simple, straightforward, very common. These books may shift point of view or format, but the narrative pretty much just goes forward hour by hour, day by day. My book, Dead Moon, fits in this category. It’s got a bunch of twists and reveals, but the narrative is pretty much a straight line from the beginning to the end. No flashbacks or frames or anything.

I’m not going to talk about this type of narrative too much because… well, I already did. If my narrative matches my linear structure, any narrative issues I might have are also going to be linear ones. And we talked about those last week (here’s another handy link in case you missed the last one).

Our focus right now is going to be stories where the narrative doesn’t follow the linear structure of the story. Sometimes the story has flashbacks or a frame, where it’s mostly linear with a few small divergences. Others might split the story between multiple timeframes, with one thread taking place in the present and one in, say, the 1950s. Or maybe the story’s broken up into lots sections and the reader needs to keep track of how they all line up—these are called non-linear stories, or you may have heard it as non-linear storytelling. It was the hip new thing for a while there. My book, The Broken Room, has a large flashback section where Natalie talks about her past, and it’s worth noting that her extended flashback/ retelling is all linear within its own subset of the book (she’s very precise about that sort of thing).

It’s important to understand narrative structure is more than just switching around my story elements. It means I need to start actively thinking about how all these structures interact. So here’s a few things I need to keep in mind when I start playing with my narrative structure.

First off, putting things in a new narrative order doesn’t change the linear structure of my story. As I mentioned above, the week goes Monday through Friday, and this is true even if the first thing I tell you about is what happened on Thursday. Monday was still three days earlier, and the characters and events in my story have to acknowledge that. I can’t start my book with everyone on Thursday baffled who stole the painting, then roll the story back to Monday where everyone was a witnesses who saw the thief’s face.

That’s a kinda stupid, overly-simple example, yeah, but you’d be surprised how often I’ve seen this problem crop up. Sometimes in really simple ways like this. Storytellers want to switch stuff around, but then they ignore the fact that just because they told us about Thursday before Wednesday doesn’t mean Thursday happened first. Again, the story collapses when the narrative elements are put in linear order. This is a really easy problem to avoid, it just requires a little more time and work.

Yeah, weird, I know. Telling a story in a more complex way is more work. Go figure.

The second thing to keep in mind when experimenting with narrative structure is… why? Seriously, why am I breaking up my story instead of telling it in order? I mean, yeah, all that non-linear stuff was edgy and bold for a while, and a lot of folks still do it, but… what’s the point of it in my story? Why am I starting five years ago instead of today? Why do I have this flashback at that point?

As an aside, I know some people hate “why is it happening now” as a story critique, and in a Watsonian way, I kind of get that. Sometimes things happen just because they happen. That’s how life works. I think sometimes things can work this way. I think sometimes they can’t.

But remember, we’re not talking about the Watsonian view of the story, we’re talking about the Doylist one. So why did I, the author, arrange these events in this way in the story? What effects am I trying to create? How is the narrative improved by shaping it this way?

And if I can’t explain how the narrative’s improved by shaping it this way—or if it plainly isn’t improved—again, what’s the point?

The third and final issue with a complex narrative structure is a little more subjective.

Last week I mentioned that we all try to put things in linear order because it’s natural for us. It’s pretty much an automatic function of our brains. This flashback took place before that one. That’s a flash forward. This flashback’s showing us something we saw earlier, but from a different point of view. Our brains latch onto the little details (or sometimes the big headers) and sort things accordingly.

But our brains have limits. There’s only so much we can keep track of and—let’s be honest—only so much we’re willing to keep track of. if I give you four or five numbers or letters and ask you to put them in order, it’s not a big deal. G X B N. See? You did that without too much effort.

On the other hand, if I throw a deck of cards on the floor and ask you to put them all in order… well, now this is a task. Heck, first you’ve got to find all the cards. And are they all supposed to be in numerical order or should you be doing them by suits? Are aces high or low? And if this is all in order, where do we put the jokers?

Point is, there’s a point where I’ve tweaked my story so much, my audience is going to spend less time reading it and more time analyzing it. Diagramming it like some photo-and-yarn covered conspiracy board. When somebody hits the ninth flashback done in a third tense from a fifth point of view… there’s a good chance they’ll need to pause to reorganize or re-analyze things in their head. And every time they have to pause, it’s breaking the flow. It’s knocking them out of the narrative when I want them to be sinking deeper into it.

And once I break the flow, that’s when people set my book aside to go have a glass of wine and watch gardening shows. I can say whatever I want about art or attention spans or readers putting in some effort, but at the end of it people can’t get invested in my story if they can’t figure out my story. And if they’re not invested… that’s on me.

Y’see, Timmy, narrative structure can be overdone if I’m not careful. I know some of the examples above sound a little extreme, but the truth is… they’re not. I’ve seen manuscripts where writers tossed linear order out the window and jumped tenses and povs and timeframes a dozen times. And some of them did all of that in the first fifty pages. Seriously.

This is something that can be tough to spot and fix, because it’s going to depend a lot on my ability to put myself in the reader’s shoes. Since I know the whole linear story from the moment I sit down, the narrative is always going to make a lot more sense to me, but for someone just picking up my story… this might be a bit of a trainwreck.

That’s narrative structure. However I decide to tell my story, it still needs to have a linear structure. Maybe even more important, it still needs to be understandable.

Next time, I’ll try to explain how linear structure and narrative structure combine to (hopefully) form a powerful dramatic structure.

Until then… go write.