Where to Begin

Look, taking all the requests and granting wishes in the holiday season.

A few weeks back a friend of mine from the Burbank Writers Coffeehouse (and hey, have you bought anything from Dark Delicacies during this rough time?) asked me about when you begin a story. To use his example, if 98% of my story takes place on Mars, but we need to know just how our protagonist got to Mars... what do we do? Do we start on Mars and do flashbacks? Do we start on Earth and have a slow burn to our main story on Mars? Where does the story actually begin?

I’d been mulling over how to answer this for a few days when I sat down with my partner to watch a Christmas movie or three. And one of them had...a lot of beginnings. It had a frame story. Then an introductory story. Then we jumped ahead a couple years to (I guess) the main story. And each new beginning forced us to ask is this when the story starts...? And if so, what was all that earlier stuff for?

So, hey... let’s talk about beginnings.

First and foremost, this is all going to be kind of vague and loose. Not in a hand-wavey “don’t think about it” way, but just acknowledging the fact that every story is going to have different needs. If I (or anyone else) tried to set down a hard rule for “always begin here” we could all come up with a dozen or more well-known examples that break that rule. Every story (and every writer) is unique, which means every starting point is unique.

That said...

One of the first things we should be clear about is that “where to begin” is a structure question. We have the linear structure of the story—A to B to C to D—but we also have the narrative structure, the order I’m choosing to tell this story to my audience. A lot of the time A is an acceptable starting point, but it’s not uncommon to start at B or maybe even D. It depends on what I’m trying to do as the writer, and being able to recognize that telling a story in a different way creates a different story.

Second, there’s one or two things we can say with a lot of certainty shouldn’t be my starting point. I talked a while back about the problems a lot of prologues have, one of the big ones being that describe-and-die thing that tends to show up in a lot of B-movies. Not saying these things will never, ever work as beginnings but... wow, it’s going to be a tough hill to climb, y’know?

Third, I should really be clear when things happen in a story has a lot of bearing on how we receive those things. Doing this now looks brave, while doing it then just highlights my cowardice. Putting this here is somewhat interesting, putting it there makes people shriek with excitement. There’s probably a whole post’s worth of stuff in that to discuss, but for now I just need to consider what this starting point is (or isn’t) doing to some of these first bytes of information I’m giving my reader.

Fourth is kind of the unspoken one under all of these. I can’t really figure out  a good starting point until I’ve got a story more or less assembled. It might not be written out in full, but I should have at least a rough sense of my plot and story. Maybe it’s a rough outline or just a good set of character ideas and plot points in my head. I can’t decide where to start telling my story if I don’t have a story, right?

I think this step trips some folks up. They come up with a cool opening, or they want to mimic the structure of a cool opening they saw somewhere else, but ultimately this opening doesn’t work for the story they’re trying to tell. It might be the coolest hat ever, but it just doesn’t go with this outfit. And if I keep insisting it does, I won’t notice that my little Kangol cap would go perfectly with that tie and really help bring out some subtle colors in the jacket.

(writing tips and fashion tips!)

But all of this still leaves us trying to figure out what makes a good starting point. Again, it’s tough because our stories are all going to be unique to us. I can’t really say “do this” and think it’s going to work for... well, maybe for any of you.

So here’s two thing to try.

Thing One—look at that rough draft or outline or framework and just lop off the first chapter (or its equivalent). Whatever you were thinking of using as a starting point, go past it and start there instead. As I mentioned above, a lot of us develop bad storytelling habits because we got hit too many times with the “start with action” stick. So our gut reaction is to create an artificial starting point that has a boxing match or a car chase or a two-headed shark attack.

And a lot of the time, if I snip off that artificial opening, what I’m left with is still a very solid opening—usually a better one. It gets me right to my characters. It gives me a stronger dramatic structure. It works better for reveals. Does it always work this way? Not always, but a surprising amount of the time... maybe 83%...

Thing Two—I’ve mentioned the idea of an elevator pitch before. Lucky me, I’ve just ended up in an elevator with a high-powered Big Five (is it Big Four now?) editor. So I’ve got one, maybe two sentences tops, to tell them my story and get them interested. No run-ons or rambling. I'm going to get three breaths, tops.

Do that right now—how would you pitch me your story in one sentence? Yes, now I’m the high-powered editor. Surprise twist!

Where did you start your pitch? Did you skip over anything? And if something wasn’t important enough to mention in the big sales speech... does it need to be there? 

And in both of these, please keep in mind I’m not saying I won’t ever need these bits I’m cutting loose in my story. They might be things to come out in backstory or flashbacks. I’m just saying maybe I don’t need to start my story with them.

 So go forth and find new beginnings! Or confirm the old ones are solid. That’s cool, too. Just as long as you’ve got a great opening.

Next time...

Holy crap. Next time is Christmas Eve. I’ve got to get these last few cards in the mail. And wrap stuff.

But maybe next week, as we’re all settling down for our long winter’s nap, we could talk about something seasonal. 

Like Die Hard.

Until then, go write.

A2Q Part Seven—Outlining

Here we are yet again. Welcome back, my captive audience. How’s everybody doing as we enter week... two? Three? How long have you been social-distancing at this point? Yeah, it sucks, but he way these numbers are going there's a good chance you're saving someone just by staying at home and... well, reading this.

Anyway, I know originally the A2Q was going to be an every other week thing, but we’re getting to some of the meatier stuff so I just wanted to continue with it. If anyone has any complaints, let me know down in the comments what you’d rather have me prattle on about. But for now... more A2Q.

It’s finally time to start putting things together. We’ve talked about plot, characters, story, setting, and theme. Now let’s talk a bit about how to put them all together and take a few big steps toward a manuscript.

Also, I’m going to warn you right up front... things are going to get a little vague here. As we get deeper into this it gets harder and harder for me to write out advice because you (yes, I’m talking to you, specifically) are your own person. You’re a writer with your own quirks and habits and preferences. And your story is your story. Nobody knows it like you do. Nobody knows how it should be told better than you. Which means a lot of this is going to be on your shoulders. I can offer you some general guidance, but it’s going to come down to you.

Think of it this way—and this actually ties in well to today’s topic. Let’s say you want to go on a road trip and ask me for advice. I've taken a bunch of road trips, but there’s only so much I can tell you without knowing about you, your interests, what kind of trip you want to take, in what direction, and for how long. My advice and experience might not line up with what you want to do. Doesn’t mean what your idea for a trip is wrong, and it doesn’t mean my advice is bad. It just means we all have different ways of doing different things

Also-also... this is kind of a huge step. It might not seem it, but it is. We’re going to take this huge pile of elements, arrange them, connect them, and try to do it all in a way so this contraption of words creates specific emotional and intellectual reactions from people we don’t even know.

Nervous yet? Don’t be. Well, I mean, you can be, but you don’t need to worry about it. We all get nervous at this point. Yeah, seriously. Everyone. Yep, even her. Him too. And her. Okay, no, not him—he’s kinda delusional. Nice guy, but take his advice with a grain of salt.

Also-the-third... speaking of fear, there’s one other really important thing to keep in mind at this point. Absolutely nothing we’re doing is set in stone. It’s not like once I put this element here and connect it to that it’s fused solid and they can never be moved or separated again. They can and they will. Nothing’s locked. We’ll be changing things now, and while we write it, and while we’re editing it. So I don’t need to stress out too much while I’m doing this.

Anyway...

I thought about this for a little bit, and I think there are four big pieces of advice I want to offer you at this stage. Plus a dozen or so links to earlier posts where I’ve talked about some of this stuff in much more detail. When the A2Q gets a book deal, I’ll make sure more of that stuff’s right here, but for now—links.

So, when we’re talking about arranging and connecting all these elements, there are four things I think we need to keep in mind.

—What parts do and don’t belong in my book

—The starting point
—The end point

—How I’m going to tell my story

Let’s talk about each of these and how they relate to that big pile of elements.

First, which of these elements do and don’t belong in my book. Which ones are part of the tale I’m telling and which ones are backstory or character details. I need to sift through them and figure out which ones belong in which pile.

Now, I know the first instinct is to say “it all matters,” and in one sense that’s true. All of these backstory elements and little nuances are going to affect my character and shape the kind of person they are. But that doesn’t mean they all need to be in my book. Some of these things will just stay in my notes or in my head and shape things from there.

Also, we mentioned weeding them out earlier but even so there’s a good chance some of the elements we talked about before that just don’t fit anymore. They’re good ideas, they just don’t work for this particular book, or maybe the book it’s become as I gathered all the different elements and polished them off a bit. The werewolf being a cyborg from the future? Really fun, I bet I could do it well, but it’s not going to fit here. Part of doing this is realizing that and accepting it. Not every idea works for every book.

Don’t worry—if Tor picks this up for a series, we’ll definitely see the time-traveling werewolf by book three.

Second is the starting point. Where am I going to begin my book? What is page one going to be? I think this gets messed up a lot, for a couple different reasons....

One is that, as the writers, we know all the lead-up events, and the impulse is to put them all in. But this quickly becomes a trap, because there are always going to be earlier events that lead to these events. I don’t want to start with the police detectives at the crime scene, I want to start with the jogger finding the body. Except I don’t want to start with finding the body, I want to start with the murder. Except I don’t want to start with the murder, I want to begin where the murder was being planned. Except I don’t want to start with the murder being planned, I want to see the event that pushed her into killing him. Except I don’t want to see that event...

See what I mean? We can always go further back. So one of our jobs is to figure out where do things actually begin for my heroes.

Another way this gets messed up feeds a bit off the last one, and it’s the old “start with action” thing. I’ve talked about this at length before, but essentially it’s a piece of advice that gets misunderstood a lot by people starting out. They twist their outline to begin with exploding cyborg ninja conflict when it might just need two people arguing about laundry from different ends of their house.

Finally, feeding off both of the last points, I think there’s some other bad advice out there that usually takes the form of “get into it as quickly as possible.” Again, this advice isn’t wrong, it’s just lacking context. Which is kind of my point—if I dive into the story too fast I won’t have time to establish any sort of norm for my heroes. Without that context—the bar to measure everything else in the book against—things won’t have the proper weight and I’ll just be confusing my readers. So I don’t want to spend five or six chapters on my hero’s normal, day-to-day life, but I can’t neglect it, either.

Third is the end point. No matter what kind of road trip I’m planning, I need to have some idea where I want to end up. Maybe this is just a long weekend away and we’re going to end up back home. Maybe it’s a longer-than-necessary trip to visit a friend. Maybe I’m moving cross country.

Whatever kind I decide it is, it’s hard to have any sort of structure if I don’t know where I’m going. I can’t tell if I’m going the right way when I don’t know what direction the right way is. It becomes less a book and more of a firehose with nobody holding the end, just thrashing around and spraying water everywhere as it slams into things.

Keep in mind, I don’t need to know exactly where I’m going. For road trip purposes, I can just say “I’m gonna drive to Los Angeles.” I don’t need a specific part of town or  a street address or the name of a nice restaurant for dinner. I can figure out the details when I get there. But I want to have enough sense of my ending that I can say “I need to head north-west from here.”

And also... there’s nothing wrong with deciding to change destinations halfway through. Maybe I’m going to shoot straight through LA and head for San Francisco. Maybe I’m going to veer off and spend a long weekend in Las Vegas. Or out a Joshua Tree. But at any given point, I should be able to say “I’m trying to get to there.”

Fourth and last of these key things is how I’m going to tell my tale. How am I going to arrange things in an interesting, compelling narrative that also creates ongoing, climbing tension? Do I want to use a straight linear narrative? A series of flashbacks? Am I going to have a completely non-linear structure?

All of these are big questions. In the past I’ve talked about structure and it usually covers three pretty big posts. I’m not going to go over them all at length here, but in my opinion it’s always best to make sure my linear structure makes sense before I try to work in lots of flashbacks, time shifts, or the like. There haven’t been a ton of studies that I know of, but I think readers always know, on some level, if a book doesn’t make linear sense.

But past that... a lot of this is going to depend on you and your tastes. It’s how you want to tell your tale, after all. Maybe you want to start simple, or maybe you’re going straight to the most complex, interwoven plot you can manage. That’s all going to be your choice, and you’ll need to think about it as you start outlining.

Speaking of which...

With those four things in mind, let’s try to make some kind of outline. Again, this is something I’ve talked about a couple times before, so I don’t want to talk too much here (look how big this is already). But let’s try to address a few things.

You’ve probably got a ton of plot and story points piled up so far. Little snippets of dialogue, cool action moments, neat reveals, maybe some good character beats. For now, let’s just deal with plot and story elements. Try to get them more or less together in one document. What do you have, two or three pages? More?

What I generally do at this point is start rearranging things. I want to put all these in some kind of order pretty close to my story. I think a quick, easy tool here is basic three act structure. Beginning, middle, end. Grab any plot element out of your pile. Seriously, look at your list, close your eyes, point your finger at something.

Now, gut reaction, is this element from the beginning, the middle, or the end of your book? Is it one of those basic establishing/introducing/setting-things-up points? Is it one of the last big twists? Don’t think about it, just drop it where it goes. You’ve probably already got a sense of where these things belong, so don’t overthink it for now. Remember—if it doesn’t work, we can always fix it later.

Once you’ve got them all arranged, read through it. Does it make sense? Does it feel like it’s lacking anything? If there’s stuff you’ve kept in your head (there’s always a few things) feel free to jot those down now, too. If you want to swap a few things around, that’s cool too. Just poke at it for a day or three until it feels like a loose summary of your story. Not a complete one, but I want enough of one that I can see the shape of it.

That thing in front of you is an outline. A simple one, but that’s what it is. If we’re talking about a road trip, this is our rough map. Or maybe an itinerary? Little of both, really.

And this brings us back to another “up to you” moment. Maybe this simple outline’s enough for you. Your brain’s buzzing to get to work, to start writing. If that’s the case, go for it. But if you want a little more that this—if you want a more detailed map or a few more things locked down on the itinerary, that’s cool too. Start pulling in your character elements, maybe add a few setting details where they’d be relevant.

For my first book, Ex-Heroes, I barely had an outline. One page of random notes, most of them about characters, a lot of stuff still in my head. For my last book, Terminus, the outline was 23 pages long. And for this new thing I’m working on, I think I had three pages of notes when I launched into it. It’s going to be different for every writer and it’s going to be different for every book. So don’t worry if yours is “right” or not. Just work with it until you think it’s enough to keep you on track from the beginning to the end.

All that said... let’s toss down a few elements of our werewolf story, move them around a bit, and see what we end up with. It's going to be rough because it's just for me. You’ll probably recognize a couple of these elements from earlier A2Q posts...

+++++

Start with Phoebe and Luna at home.  Both getting ready to go out for the evening, but Luna’s heading out to another party and Phoebe’s going hunting. So they’re looking for things, asking who borrowed what, warning each other to be safe, and so on.

Phoebe’s going to be out hunting and encounter the super-werewolf (although she doesn’t know it’s super yet, or who it is). She’s going to put a silver crossbow bolt in it and it’s going to ignore it and run off. This will also give her a chance to grumble about losing a silver bolt because they’re expensive. She can track it for a while, find the bolt... but no body.

The next morning Phoebe goes to the lodge and we meet Luc and talk about hunting last night, if he saw anything noteworthy. Maybe some one-sided flirting?

Intro. Andrea.  Maybe Andrea’s actually the head of the lodge. Warden? That sounds Masonic without going all weird with “master.” She’s willing to entertain the ‘super-werewolf” idea, and will pay an extra $2500 bounty for proof.

Down to check in with Quinn. Crossbow took a beating last night. One knife needs a nick ground out of it.

Gets a call from her job at the bar—she’s late, supposed to be there for deliveries.

Go to the bar, intro. her “norm” boss.

Work night.

After work??

Breakfast with Luna the next day. Talk about the bounty, using it to pay for college?

+++++

It’s very, very loose, but I think that’s eight or nine chapters right there. Into the second act, easy. It’s also very straightforward and linear. I’d write out more of it, but as I mentioned... this is getting ridiculously long.

One thing that immediately occurs to me—and I’ve come up against this before—werewolf stories have an inherent time limit built into them, especially if I want to go “classic” light-of-the-full-moon werewolves. And that is... the full moon only comes out every four weeks. So I’m looking at a lot of time here with, well, no werewolves in it. I’ll need to space a few things out and skip over some time. Which won’t be a huge problem since I’ve already said Phoebe’s stuck with a normal job and Luna doesn’t know she’s the werewolf.

What I might do, right now, is take the bit with Quinn and drop it down to the bottom of this little outline fragment. So that just became another day. Plus, now it means Phoebe’s getting that call from her day job while she’s in her meeting with Andrea, which can create some fun.

And at this point, forget about writing a book—I’m worried the sheer size of this post might be intimidating to some of you.

Get your elements. Organize them. Make your road map, and make it as simple or detailed as you like.

Next time... our first draft.

Until then, go write.

The First Time Around

            Is it still a pop culture reference if I’m referencing one of my own books? I mean is it really a “reference” when J.K. Rowling talks about Harry Potter? Or is it just self promotion...?

            Anyway, this week I wanted to blab about an issue that cropped up in a book I just read. I mean, it’s a fairly common problem, truth be told, and it’s easy to see why it happens.  But it’s one of those things that almost always makes readers grind their teeth. Even if they’re not sure why they’re grinding their teeth.

            And to explain this, I’d like to start by talking about my mom.

            My mom had me when she was really young.  Not scandalously, Gilmore Girls young, but young enough that there was still a touch of scandal.  Especially back in New England during Nixon’s presidency.  It’s struck me a couple times in my life to think where she was in her life at the same age.

            Of course, I didn’t always think like this.  I didn’t really put the math together until some time late in high school, I think.  Because my mom didn’t look young. She looked... well, mom-aged.  Why would I look deeper into something that was totally normal?  My thoughts just never turned that way.

            No, the odd thing when I was growing up was how all of my friends had old parents. I think I was around seven or eight when it first struck me that the friends I’d ended up with all had parents that were at least a decade older than my mom. It was odd, yeah, but I logically assumed that all those many, many parents I hadn’t met were normal mom-age.

            Hopefully the point I’m trying to make is clear.  All of us assume our lives are normal.  That we’re the baseline.  Even when we come to realize they might not be normal in a greater societal sense, they’re still normal for us.  It still doesn’t surprise me that my mom’s not-quite twenty years older than me because... well, she always has been.

            And this is true for fictional people, too.  The world they live in is—big shocker—the world they live in.  It doesn’t surprise them.  Kincaid Strange isn’t shocked spirits and voodoo are real because that’s her world.  Since Charles grew up in a world of metal spiders, a horned God on television, and mechanical implants in the back of people’s skulls, these things are more annoying background noise to him than disturbing.   Constance Verity doesn’t get surprised by aliens or androids or monstrous creatures at the center of the Earth because for her... well, that’s a Thursday.

            Granted, they can still get surprised when something changes in their world. We tend to call that “plot."  But the day to day aspects of their life shouldn’t come as any big shock.  They’ve seen it and experienced it before.  It’s normal to them.

            One mistake I see a lot in stories and screenplays is when characters in my story go for a hover-drive, go to work at the vat-meat processing plant, or telepathically scan perps for evidence of crimes... and are in awe of these things.  Maybe even feel the need to dwell on these things for a paragraph or three.  It knocks a reader out of the story because it’s immediately apparent this is something the characters should be familiar with.

            But it’s not just genre stuff. This happens in “real world” stories, too.  I’ve seen characters be eyes-wide amazed at the smell of dog food and the price of milk.  Not because these things are radically different than expected, mind you.  Just because... they’re there.

            Let me put it a slightly different way. And I’ll give you another personal example.  Or, in this case, you can give yourself the example.  No, you don’t need to share or even write it down, don’t worry.  Just keep it in your head.

            Do you remember the very first time you saw your current (or most recent) significant other naked?  Girlfriend, boyfriend, wife, husband, whoever they may be.  I’m not asking for a date and time—do you recall how you felt at that moment, at the sight of them exposed to you?  What was running through your mind?  What your heart was doing in your chest?

            Okay, now get yourself under control--there’s a follow-up.

            How did you feel the last time you saw them naked?  Maybe this morning or just the other night. Were you as focused? As breathless?  Heck, were you even thinking about them?  Not in a “someone else” way, I just mean maybe you were working out a problem from one of your own stories.  Or thinking about stuff you had to do this weekend.  Heck, maybe you were reading and they were just walking around in the background.  You knew they were there but you just had to finish this chapter.

            Y’see, Timmy, sometimes, storytellers get focused on the fact that this is the first time my readers have seen Wakko perform an exorcism.  Or it’s the first time we’ve seen a dynochromium field in use.  Or it’s the first time we’ve seen Phoebe and Yakko together (in any sense). And so the writer want to explain these things—to show how horrible or amazing or beautiful they are.

            But just because this is new for the reader doesn’t mean it’s new for the character.  It’s not their first time.  These are normal things for them.  Mundane. Perhaps even a little boring.  Definitely not cause for heart-pounding excitement.  

            When I start shaping dialogue and reactions to be informative for the audience rather than to make sense for the other characters, my focus is going in the wrong direction.  It might seem right on a quick-pass, mechanical level, but when we really study these examples... they just don’t work.  You may recall all the times I’ve brought up that most hated of dialogue phrases-- “as you know.”  It’s a perfect example of writing my dialogue for the reader and not for the characters.

            Now, there’s an addendum to this, and it’s a real killer.  It’s when I make plot points out of these things people should’ve known about before.  If my characters all know Wakko can actually use dowsing to find water, they shouldn’t be completely baffled why he’s digging a deep hole out in the field.  At the very least, they should have some suspicions about why he’s doing it. 

            Because if they don’t—or they don’t even consider his dowsing abilities—well, they’re going to look like idiots in the end.

            An easy way to get around this is something I’ve mentioned a few times before.  I call it the Ignorant Stranger.  It’s pretty much the opposite of “as you know.”  In some cases it can help a lot to have a character in my story who’s not quite as in the know.  Someone who things need to be explained to, because this is the first time they’re being exposed to something.  They can even be my protagonist.  In fact, it’s not a bad thing if they are.  If my hero needs things explained to them, it means they’re in new, unknown territory.  And—as mentioned above-that’s where I tend to find a plot.

            One of the worst things I can do as a writer is confuse the first time my readers see something with the first time my characters do.  It’ll ultimately come across as false and it’s one of those clumsy mistakes that’s hard to recover from.  I need to find the balance point, the sweet spot where I’m informing my readers but things still make sense and feel natural for my characters.

            Next time... okay, I’m trying to get a draft done before the end of the month, so next time might just be a few quick questions for you to think about.

            Oh, and if you’re going to be at Wonder Con this weekend, I’m there all day Sunday.  At 11:00 I’m doing a two hour version of the Writers Coffeehouse, at 2:00 I’m on a panel called “Knowledge: Handle With Care,” and we’re doing a book signing right after that.

            Until then... go write

Getting Our Story Straight

            Running a little late this week.  Again.  Crazy busy these past few days.  Craig DiLouie was here in southern California, so we hung out for a day. Then there was Valentine’s Day.  And if you haven’t seen Black Panther yet I highly recommend it.  Fantastic movie.

            Oh, plus a couple of outlines for new projects, too...

            Anyway...

            This past week at the Writers Coffeehouse I babbled on about different forms of structure and how they work together.  I haven’t really gone into that here in a couple of years, so I figured now might be a good time.  While it’s all fresh in my mind.

            Fair warning—this is kind of a sprawling topic so it’s going to spread out over the next two posts as well as this one.  I also may use a few terms in ways of which your MFA writing professor would not approve.  But I’ll do my best to be clear, despite all that.

            Speaking of professors...

            Structure is one of those terms that gets thrown around a lot when we’re talking about writing.  Sometimes in a generic sense, like that last sentence, other times in much more specific ways. You may have heard gurus talk about narrative structure, dramatic structure, three-act structure, or maybe even four- and five-act structure (if you’ve been dabbling with screenwriting a bit).

            An important thing to be clear about before we go too far—all of these are very different things.  I think this is why people get confused about structure sometimes.  A lot of things fall into this general category, and while some of them are vital to the storytelling process... some aren’t.  And it doesn’t help when “expert” gurus try to conflate them.  I read an article once where one guy was trying to use the five-act structure of television shows to demonstrate that three-act structure was an obsolete form (ProTip--it’s not).

            When we talk about structure, we’re talking about the underlying framework of a story.  The skeletal system, or maybe the nervous system, depending on how you want to look at it.  And, just like with anatomy (or architecture or programming) there can be more than one underlying system. And they all work together to make a functioning person. Or house.  Or story.

            It’s key to note that all these systems (or structures) are not the same. Sometimes things will overlap and serve multiple purposes. Sometimes they won’t. And, as I mentioned above, just because something worked in that story doesn’t mean it’ll work in my story.

            Okay.  Got all that?

            Good.  Get ready to take a few notes

           The three main structures in a story, for our purposes these next few weeks, are linear structure, narrative structure, and dramatic structure.  They all interact and work with each other.  Just like with anatomy, if two elements are strong and one is weak, a story won’t be able to support itself.  So it’s important that I have a good grasp of all three and understand how they work.

            The one we’re going to deal with this week is linear structure.  Simply put, it’s how my characters experience the story.  There’s a Russian literary term for this called fabula.  Another term you may have heard for this is continuity.  Thursday leads to Friday which leads to Saturday.  Breakfast, coffee break, lunch, dinner.  Birth, childhood, college years, adulthood, middle age, old age, death.

            There’s a simple reason linear structure is so important.  Almost all of us are experts with it.  That’s because linear order is how we experience things all the time, every day.  We notice when effect comes before cause, even if the story gives them to us out of order.  A good way to think of linear structure, as I mentioned above, is a timeline.  When detectives break down the clues of a crime, them may discover them out of order, but it doesn’t change the order the events actually happened in.  If I’m writing a story—even if I’m telling the story in a non-linear fashion—there still needs to be a linear structure. 

            A good way to test the linear structure of my story (a method I’ve mentioned before) is to arrange all the flashbacks, flash-forwards, recollections, frames, and other devices in chronological order.  My story should still make logical sense like this, even if it's lost some dramatic weight this way (more on that later).  If my story elements don’t work like this (if effect comes before cause, or if people know things before they learn them), it means I’ve messed up my linear structure.

            Now, I want to mention a specific example where linear structure gets messed up a lot-- time travel.

            In a time travel story, it’s very likely there’ll be multiple linear structures.  My time traveler might be experiencing Thursday, Friday, then Wednesday, and then Thursday again.  They’re still experiencing four days in a row, though—even if their friends and coworkers are only having three. And their three are Wednesday-Thursday-Friday.

            I mentioned this diagram at the Coffeehouse on Sunday. It’s a pair of timelines featuring two characters from Doctor Who—Jack Harkness and the Doctor himself.  I’ve marked a few key, mutual events in their lives.

            Jack’s life is pretty straightforward, for our purposes here.  A is when young Jack first meets the Ninth Doctor and decides to travel with him for a while.  B is when he later encounters the Tenth Doctor and Martha.  C is when they all briefly meet again a year or so later to stop Davros and the Daleks.  They meet again (D) much, much later in Jack’s life.  And E is when the Doctor’s there for Jack’s death at the ripe old age of twenty billion or so (mild spoilers, sorry). 

            That’s a pretty normal, linear timeline.  Young to old.  The one most of us have (just slightly exaggerated in his case).

            Now... look at the Doctor’s.  This is the linear structure of the show because we (the audience) are following the Doctor around (more on this next week).  He travels in time, though, so he meets Jack in kind of an odd order.  First time for him isn’t the first time for Jack, and vice-versa.  But it’s still a logical, linear order for the Doctor—he’s living his own timeline, A-B-C-D-E, just like Jack.  A and B are the Ninth Doctor, C through E are the Tenth.

            Make sense?

           Y’see, Timmy, no matter what order I decide to tell things in, the characters are experiencing the story in linear order.  If halfway through my book one of my character flashes back to what happened a week ago, this isn’t new information for him or her—it happened a week ago.  So all of their actions and reactions up until that flashback should take that information into account.

            It sounds pretty straightforward and it really is.  Linear structure is going to be the easiest of the three forms I blab about over the next few weeks because it’s logical and objective.  But, alas, people still mess it up all the time.  And the mistakes are usually because of... narrative structure.

            But we’ll talk about that next week.

            Until then, go write.

Q-n-A Bonanza Extravaganza

            Spectacular spectacular!

            What I’m going to do this week is run through a few questions and requests that have shown up here this summer.  A few of them I can do a full post on, but some of them are things I’ve touched on before (or, at least, I think I have) so I think I can answer them with a few paragraphs and links.

            So... let’s get to it.

How similar are your drafts in terms of character arcs and overall plot? 

            Tricky question that’s going to be a little different for every writer and for every project.  For me, once I get a pretty solid draft, it’s really rare for things to change that much.  It happens sometimes, but not often.  I think once the plot and story are solid, for most writers, there won’t be any real changes to them.

            Please note, though, that I didn’t say no changes.  Every draft is going to be a little different as I tweak and cut and make other adjustments.  But all of these adjustments serve the plot and the characters.  Things are just getting tighter and clearer.  Maybe it means omitting a few story beats or changing someone’s second language from French to Spanish.  But these changes aren’t changing the bigger picture, they’re enhancing it.

           It’s probably worth mentioning that if I’m making changes that do radically alter my plot or characters, what it really means is that I don’t have a solid draft yet.  Yeah, even if I’ve done six drafts before this.  If I suddenly realize Yakko should be my main character while Dot’s the supporting character who dies in the second act... that’s a big change.  That’s a lot of changes.  It means different interactions between different characters, new motivations, possibly a whole new linear structure.  And it also means I’m kind of going back to square one.  Now I need to tweak and cut and make adjustments to this plot and story.

            Do you have any thoughts on working on multiple projects at once? Like editing one, drafting another, plotting a third? Is that something you do?

            Yeah, I do this, but in a bit more limited sense.  When I’m working on a first draft of something, I focus pretty much exclusively on that.  Once I’m out of that, though, and into the editing, I’m always jotting down character ideas, lines, beats—all sorts of elements—for whatever I’m going to be working on next.  So while I’m doing drafts on one I’m setting all the groundwork for another.  I’ve also  found this helps me as far as any kind of block goes—being able to dip my toes into something else helps keep my brain from getting stuck on a project.

            Overall, though, this is one of those things that’s definitely more advice than rules, because it’s all going to come down to the individual.  Am I someone who can split their attention or not?  And to what extent?  Some folks can do it (to different degrees), some folks can’t.  Unfortunately, the only way to find out is to try it once or thrice.  I’m comfortable at the level I just described.  You might be able to do two or three  things side by side.  Someone else might need to focus on one thing at a time.   

            I do think it’s worth noting that “another project” can easily be a distraction, too.  Sort of like eating when you’re bored.  I’ve also seen some folks use multiple projects (consciously or not) as an excuse to never finish anything. Sooooo... something to keep in mind.

I'm still struggling with how writers develop an interesting narrative voice - character voice I think I'm getting the hang of, but the narrative bits still sound like me reading a grocery list. 

            Narrative voice can be tough.  Part of it depends on how much I want to insert myself as the author. Some folks do this extremely well, others... not so much.

            As far developing a narrative voice goes, think of it like a narrator. Who’s actually telling this story to the reader?  I’m not saying my book or short story has to be in first person, or that a narrator even has to exist, but in my perfect world, who’s reading this aloud?  Christopher Lee?  Felicia Day?  Doug, the guy down at the garage?  Ms. Phoebe, my college English professor?  Knowing the narrator tells me how they talk and what kind of words my narrative voice will use. 

            So, from a certain point of view, the narrative voice is another character. Even if it’s me, it’s the version of me I’m choosing to project through my writing (a friendly me who wants you to enjoy the story and is going to tell it in fun, simple terms, and who also has much better abs...).  So narrative voice is a lot like character voice, which is something I mentioned here just a few months back.  Well, okay, a year and a half ago...

            It’s probably worth mentioning that if there isn’t some kind of narrative voice in my head to start with, that might be a sign of a bigger problem.  If I have no sense of how my story should be told—how my audience should be hearing the words in their heads—I may need to stop and think about things some more.   Maybe the plot or the story aren’t as solid as I thought, and if they’re not clicking with me, there’s a good chance they won’t click with anyone else.

            Do you feel  an author should stick to one genre for the most part?  I want to go write something as far from my current genre as possible. Will that throw my fans for a loop?  I notice that you and most other authors pretty much stick to one thing.

            Well, I’d argue not much of my work falls in the same genre, unless we’re talking in broad, sweeping terms.  I’ve got a superheroes vs. zombies series (sci-fi fantasy with some soft horror), a suspense-mystery-horror novel, a sci-fi thriller, a classic mash-up where I share credit with Daniel Defoe, and I just started work on a historical time-travel road trip story.  I’ve also got some short stories out there that are straight horror, some that are straight sci-fi, and even a pulp action war story.

            And I’m not alone.  The majority of writers work in a bunch of genres.  They may be known for one thing, but they’ve usually got a lot of other stuff past that.  Jonathan Maberry, Seanan McGuire, Scott Sigler, Craig DiLouie, Eloise Knapp, Timothy Long—and these are just the ones I know personally. All of them have written in at least two or three genres.

            Heck, look at Stephen King.  He’s known as a horror writer, but Firestarter and The Dead Zone, two of his earliest works, are pretty much straight sci-fi when you really look at them (there’s a post in that alone).  Under the Dome and 11/22/63 are both pretty solidly sci-fi, too.  The Dark Tower series is an epic fantasy.  Eyes of the Dragon is a young adult novel.  And then there’s “Rita Hayworth and Shawshank Redemption,” a  prison drama/character study that was adapted into a wildly popular film by Frank Darabont.

            So, no.  I don’t think an author needs to stick to one genre.  Yeah, there are some fans who might get upset I’ve moved away from their particular interest, but there’ll be just as many who’ll be intrigued to see how I deal with something else, and new ones who’ll come to me because of that something else.  And it’s my opinion that flexing those other muscles, so to speak, usually makes someone a better writer overall.

            I will say, though (there’s a “however...” on almost all of these, isn’t there?), that I don’t recommend chasing the popular trend.  It’s tempting to jump on the nymphomaniac-android-biker-school-romance bandwagon, I know.  But it rarely works out well in the long run.
           

            And I think that’s everything for now, yes?  Okay, I went over three or four paragraphs for some of them, but if you’re going to complain about that... Also, if I misread your question somehow, or if my answer just wasn’t complete enough, please say so down in the comments and I’ll try to answer there.  Or maybe bump it up to a full post.

            Next time, I’m going to answer one of those larger questions I mentioned up at the top. 

            Until then... go write.

Earlier In Our Story...

            Lots of requests from last week, thanks to you who've answered so far.  However. I’m still gathering my thoughts on how to answer some of them.  Plus, I’d already finished most of this, sooooo...

            I wanted to take this week to go back to something I’ve talked about before.  Flashbacks. I’ve encountered a few books recently that lean heavily on this device and... well, most of them weren’t good.  One of them was good to a point, but after that point it quickly tipped into frustrating, and from there to just plain bad.

            Why?

            Well, let me bring up a more important question for us all to ponder while I babble on.  Why does my story use flashbacks?  What purpose do they serve within the story?

            Let me give an example.

            I read a novel recently about a Black Widow-esque assassin who’d gone through a nightmarish bout of training and indoctrination before being set loose on the world and her assorted targets.   Its chapters alternated between present day and the past.  The “now” of the story was her carrying out a series of missions while the “then” was how she was recruited and trained.

            Except...

            The two plot lines didn’t make linear sense.  Y’see, for the first two-thirds of the book, our assassin (let’s call her Phoebe) was hunting down one target, finishing her assignment, and moving onto the next one.  It was kind of a Bond movie setup.  But she was paranoid-nervous the whole time. Was someone watching her?  Hunting her while she hunted down her targets?  She’d built up a lot of enemies over the years. Was one of them lining up on the base of her skull right now?

            Meanwhile, in the parallel past plotline (say that four times fast...), we saw how she was recruited out of the foster system after a series of schoolyard fights.  Her brutal apprenticeship.  Her first kill.  Her early missions.

            And then, the last third of the book rolled around...

            In the final “then” sections, Phoebe met Nadia, one of her peers (and, it’s vaguely hinted, maybe even a long-ago love interest or at least regular friend-with-benefits).  And it turns out Nadia is a traitor, a double agent who Phoebe exposes and they end up in a huge battle that rages through a shopping mall (again, really cool).  In the end Nadia gets away, but swears to return and kill Phoebe for exposing her. And from this page on, in the “now” sections, Phoebe wonders if it’s Nadia out there waiting to kill her.  Maybe Nadia has a rifle aimed at her head.  Nadia, the only one she ever let get away, could be right around that corner.

            See the problem here?

            As the “then” storyline progressed, it became clear that the “now” timeline was cheating and tweaking things to create dramatic moments that wouldn’t exist if the two lines were being honest.  The author forgot that all of “then” happens before every minute of “now”—the order they were telling the story in didn’t matter.  The author tried to set this up as paranoia in the “now” sections, except it turns out Phoebe was completely justified in feeling this way.  She knew all along someone was actually hunting her.  Hell, for the first two-thirds of the book she knew the name of the person hunting her, a person it’s strongly implied she’d been intimate with, and she never thought of Nadia once—even though most of the story is from her point of view. She just had vague thoughts about “a possible threat” or “maybe another operative” until this convenient point in the story.

            This is the type of thing people are talking about when they say flashbacks don’t work.  Well, okay, those people are kind of stupid.  Flashbacks do work and you should use them... if they make sense within the story’s structure.

            From a linear point of view, does my story still make sense with this flashback?  Or flashbacks, as the case may be.  What happens if I rearrange everything so all the chapters are in linear order?

            If a lot of my character motivations or behaviors become murky, it means I’ve got a problem.  I don’t have a good thread for my character, and their reactions are based off my narrative, not their linear experiences.

            If large parts of my story now drag, that’s a sign I’ve got a structure problem.  The flashbacks were the only thing creating tension.  It means my story is really either in the past or the present.  I’m just killing time and eating up word count in the other setting.

            If I put everything in order and my story works better—it reads smoother, its easier to follow, and the plot moves faster—then that takes me back to those early questions.  Why does my story use flashbacks?  What purpose do they serve?

            Don’t laugh at that last one.  I’ve seen people who turned their stories into a mess of non-linear flashbacks that served no purpose whatsoever, and they ruined an interesting story by doing it.  It happens more often than you’d think.

            Like any element in my story, I can’t be throwing in flashbacks for no reason. Just because something worked in that story doesn’t mean it’s going to work in my story—especially if I don’t understand why it worked.

            Do cool stuff in your stories.  But have a reason for doing it.  A real, honest reason that doesn’t cheat or frustrate your readers

            Next time...

            Well, I actually got a fair number of requests and questions last time, so here’s what I was thinking.  I’m going to pluck out the one or two that would work as full posts and we’ll probably see them in the next three or four weeks.  But next time I’m going to do a whole post of quick topics that I can address in four or five paragraphs (and maybe a link or three).  So if you have something writing-related you’d like me to address, mention it down in the comments and it’ll end up on one list or the other.

            And until then... go write.

How I Learned to Stop Worrying...

            Classic movie reference.  Come on, broaden your horizons.  Watch something made before 1976.

           Anyway, I’d like to start today by telling a story or two.  They’re examples of a problem I see crop up now and then, and one I just finished wrestling with myself.  It’s one of those issues where it’s easy to either write myself into a corner or (worse yet) write something where characters are acting in an unbelievable way.

            Oh, and by the way, before I forget, there’s a thermonuclear warhead in the apartment next door.  Something like ten megatons, if I read the specs right.  Armed and everything.  Just thought you should know.

            Anyway, let me tell you the first story.

            In my often-referenced novel The Suffering Map (unpublished, for good reason), one of the main antagonists is Uncle Louis.  Louis is an old-school mobster with a legendary temper, and he’s rather upset that someone (we’ll call him Rob) threatened his niece (who’s in her late fifties).  He sends a man to rough Rob up a bit, and that man ends up dead with his body horribly mutilated.  So Louis sends two men to kill Rob.  They both end up dead and mutilated.  And when this news reaches Louis he decides...

            Well, actually, he decided to wait for three days and then go after Rob.

            See, I had this whole structure of days worked out, and it turned into kind of a vicious circle.  I needed three days to pass, so Louis had to wait.  Which meant I needed to come up with stuff for everyone else to be doing.  By the time I abandoned that structure, though, I’d grown kind of fond of the reveals and character moments I’d created.  Now Louis had to wait so I’d have room for those bits, no matter how strange and out of character it seemed.  It wasn’t until my fifth draft that I realized this was just dragging things and creating a huge lag in the plot.

            Though not as huge as that bomb sitting next door.  I looked it up.  That’s almost fifty times the size of the bomb they dropped on Nagasaki.  Think about that.  I mean, I think it’s small compared to some missiles and such, but right here in the middle of Los Angeles that could still kill a lot of people.  Millions, easy.

            Anyway, back on track.

            Here’s another example of what I wanted to talk about today.

            A few years back a woman I knew wrote an urban fantasy story and asked me to look at it.  A single mom activates a portal and she and her kids are transferred to a mystical realm.  There’s some magic, some disobeyed instructions, and all three kids vanish.  Invisible?  Teleported?  Dead?  We don’t know, and Phoebe, our heroine, was desperate to find out.

            Well... until she ran into the handsome barbarian chieftain, anyway.  Then Phoebe became aware of just how shredded and torn her clothes were after coming through the portal... and how much skin they exposed... and how much skin the chieftain was showing.  Tight, tanned, well-muscled skin, and Phoebe started wondering if there was a Mrs. Chieftain, and if not... just how prudish were people in this semi-medieval world?

            Speaking of kids...  Hmmmm.  Sounds like one of the little kids next door is hitting the warhead with something.  Maybe a hammer.  Yeah, there are kids next door, too.  Didn’t I mention that before?  I guess one’s technically an infant and the little girl’s a toddler, but they third one is seven or eight.  He’s hammer-competent.

            Well, probably can’t do anything about it.  At best, he might turn on the timer.  If he hasn’t already.

            But I’m wandering away from the point again...

            Or am I...?

            Y’see, Timmy, there are some threats that are just too huge for me to ignore.  Either as physical threats or emotional ones.  One of my children vanishing.  A man in a hockey mask stalking toward me through the forest.  An armed nuclear bomb. 

            Once I know about these things... that’s that.  I can’t establish a huge threat and then ignore it.  If I tell you there’s a nuclear bomb next door, that has to be the priority.  Not being polite.  Not property laws.  Not getting a good night’s sleep and dealing with it in the morning. 

            In my new book, the characters found out about an immediate global threat.  Not a ten years down the road thing—this time tomorrow half the planet will be dead and by the weekend all of it will be.  And it put me in an awkward spot when they did, because at that point nothing else could matter.  Nothing.  Once they realized how big that threat was, they couldn’t be thinking about anything except taking care of it.  Yeah, they could have little asides or chuckles, but nothing that distracted them. 

            It forced me to restructure the end of my story.  But it also made the end much stronger.  And nobody’s standing around wondering about that bomb next door.

            Alas, I’m going to miss next week because of the San Diego ComicCon.  Please swing by the Random House area (technically the Crown/Broadway booth) on Friday after 2:00, say “hullo,” and call me a talentless hack in front of important people.
            When I come back, odds are I’m going to be very fatigued.

            Until then, go write.

Structural Engineering 101

            The first chapter is titled “Zefram Cochrane.”

            Geek reference.

            Anyway...

            Well, for a couple months now I’ve promised that I’d blather on about structure.  I’ve actually got a bit of time now, so let’s do it.  I’ll warn you all right up front, this is probably going to be spread over two or three posts because it’s a big topic.  I also may be using terms a bit loosely and in ways your MFA professor may not approve of.  But I’ll do my best to make it easy to understand, despite that.

            When we’re talking about structure in stories, it really means the same thing it does when we’re talking about architecture or biochemistry or auto engineering.  It’s the underlying framework that helps us figure out how things go together.  Different structures work for different projects, so just because something worked when we were building One World Trade Center doesn’t mean we should use it when we’re building a house.  Or a motorcycle.

            Now, there are three types of structure in stories, and they all interact and work with each other.  Just like a house or a skyscraper, if two elements are strong and one is weak, a story won’t be able to support itself. So it’s important to have a good grasp of all three and understand how they work.

            First up, the one we’re going to deal with this week, is linear structure.  Simply put, the linear structure of a story is the chronological timeline the characters experience.  There’s a Russian literary term for this called fabula. I’ll prattle on more about this in just a bit.

            Next is narrative structure.  This is the manner and order my story is told in.  Put another way, it’s the way my audience experiences the story.  A flashback is part of the narrative structure, as are prologues, epilogues, and “ten years later...”  Again, if you studied (or over-studied) this sort of stuff in college, you professor may have used the term syuzhet.  I’ll talk more about this one next week.

            Last but not least, there’s dramatic structure.  This is the way linear and narrative structures work together to form a coherent, enjoyable story.  Dramatic structure is why tension builds, why mysteries intrigue us, and why twists and reveals surprise us.  I’ll talk a little more about this on the 26th, if all goes well.

            For now, though... linear structure.

            As I mentioned a few moments ago, linear structure is the order your characters experience the story in.   Another term you may have heard for this is continuity, or maybe cause and effect.  Day comes before night, which leads to another day.  People start young and then get old (Benjamin Button and Doctor Who excepted).  Turning a key in the ignition starts my car.  Or, sometimes, sets off a bomb.

            Now... check out this list

            Yakko dies peacefully in his sleep.
            Yakko celebrates his fifth birthday.
            Yakko gets married.
            Yakko is born.
            Yakko witnesses the birth of his grandchild.

            These are five random events from a life.  Now, despite the fact that I started the list with Yakko’s death, we all inherently understand this is not the first event in his life.  In fact, I’m betting most of you reading this can put that list in linear order in just a few seconds.  That’s because linear order is the most natural structure for all of us—it’s the one we experience all the time, every day.

            This is also why linear structure is so important.  Most of us are experts on it.  We’ll notice when effect comes before cause, even if we’re getting them out of order like I just gave them to you.  A good way to think of linear structure, as I mentioned above, is a timeline.  When you see detectives breaking down the clues of a crime, them may discover them out of order, but it doesn’t change the order they actually happened in.  If I’m writing a story—even if I’m telling the story in a non-linear fashion—there still needs to be a linear structure. 

            A good way to test the linear structure of my story (a method I’ve mentioned before) is to pull everything apart and then arrange all the flashbacks, flash-forwards, recollections, frames, and so on in chronological order.  They should still make logical sense like this, even if they’ve lost some of their dramatic weight this way (again, more on this later).  If my story elements don’t work like this (if cause doesn’t come before effect, or if the same thing is happening multiple times), I’ve done something wrong.

             Which brings us to time travel.

            Time travel stories depend a lot on linear structure.  If I don’t have a clear then and now, before and after, then time travel means nothing.  I need to be able to see that linear structure so I can see how my traveler’s timeline moves back and forth along the world’s.

            Check out this little diagram.  Here’s a pair of timelines featuring two characters from Doctor Who—the Doctor himself and his friend, Jack Harkness.  There’s kind of a big spoiler in here (or not, depending on which fan theories you subscribe to) which I’ll try to avoid, but if it makes things too confusing just say so.

            Jack’s life is pretty straightforward, for our purposes here.  A is when young Jack first meets the Ninth Doctor and decides to travel with him for a while.  B is when he later encounters the Tenth Doctor, and C is when they briefly meet again to stop the Daleks.  They meet again (D) much, much later in Jack’s life.  And E is when Jack finally dies at the ripe old age of about five billion or so (no, seriously).  All in all, this personal timeline isn’t much different than the one I showed for Yakko up above.

            Now... look at the Doctor’s timeline.  This the linear structure of the show because we (the audience) are following the Doctor around.  He travels in time a lot, so he actually meets Jack in kind of an odd order.  But it’s still a logical order for the Doctor—he’s still living on his own timeline A-B-C-D-E, just like Jack.  A and B are the Ninth Doctor, C through E are the Tenth.

            In fact, this linear order creates a big twist for the Doctor (and the viewers, since we’re following him).  He doesn’t realize the person he first meets at D is the same person he later meets at A (as I mentioned, a lot of time passes for Jack).  But this isn’t a twist for Jack because he’s following his own linear story.  That’s why he can address the (somewhat confused) Doctor as “my old friend.” 

            Make sense?

            Y’see, Timmy, no matter what order I tell things in, the characters are experiencing the story in linear order.  If halfway through my book one of my character flashes back to what happened a week ago, this isn’t new information for him or her—it happened a week ago.  So all of their actions and reactions up until the flashback should take that into account.

            It sounds pretty straightforward and it really is.  Linear structure is going to be the easiest of the three forms I blab about over the next few weeks because overall it’s logical and objective.  But, alas, people still mess it up all the time.  And the mistakes are usually because of narrative structure.

            But we’ll talk about that next week.

            Until then, go write.