The Best Pace

I know I said I was going to try to do two posts this week but Tuesday was second shot day which ate up a bit of time but I’m now fully vaccinated! With no real side effects. So go get your second shot so we can all hang out together and things can get back to normal. Well, normal but with some major social reforms that this pandemic has really highlighted as necessary changes.

Anyway...

Look! More questions, more answers! And this takes so much pressure off me, because I don’t have to think of topics...

So, last week, after I prattled on about prologues, JD asked...

“I’m wondering if you have any suggestions on how to judge my pacing? I know every story is different, but in general, are there any tricks or tools to better know when I’m “running out of time” to get back to action before I lose the interest of my (hypothetical future) readers? Not just during the world build, but throughout?”

This takes even more pressure off because this question already contains part of the answer. Not all of it, but, y’know... maybe 20-25%.

When we talk about pacing, the first important thing, as JD said, is to recognize that every author (and every story) is going to approach things differently. Some need to dive right in with the fist fights and explosions. Others may take the slow burn, ramping tension approach. Right off, we need to recognize that pacing isn’t something that’s going to hit a bunch of universal guidelines. I think I’ve mentioned once or thrice before (here and at the Writers Coffeehouse) that I’m verrrrrrrry leery whenever folks set down rules like “introduce your love interest on page 16, inciting incident on page 23,  your first conflict by page 42.” Following blanket rules like this either creates cookie-cutter, formula stories... or it just turns good stories into bad stories. Because they’re being forced to hit benchmarks that don’t apply to them.

I mean, my new book doesn’t even have a love interest. So does that mean everything else bumps up by one page, or...?

The second important thing is to always remember Lee Pace is the best pace. I mean, seriously, look at the range this guy has. Pushing Daisies to Guardians of the Galaxy? I don’t know about you, but I freaked out when I realized that was the same guy.

But, seriously, let’s look at a few rules of thumb. Things we could probably consider as loose guidelines if nothing else. Because again, every book’s going to be different.

I think the best thing to remember is that pacing is a structure issue. Specifically, dramatic structure. I’ve talked about dramatic structure a few times before, so I won’t bore you with it again now. The important thing to remember for this discussion is that it’s always a slope. Sometimes that slope goes up, sometimes it goes down. But what it should never do is amble along on a flat line. Because a flat line means... well, you know. Dead.

Any chapter (or broad swath of my book, if I’m being clever and not doing chapters) should have a clear up or down on that slope. It doesn’t have to be a huge slope, but if I’m starting and ending at the same level of character growth, of overall tension, it probably means I’m doing something wrong. A chapter (I’m just going to keep using chapter as our nice, simple, unit-of-book-construction) should lean things one way or another, whether it’s holy crap you found the lost sword Dyrnwyn or just no, Jules, I’m not just going to give you some of my Doritos. Things need to move higher or slip downwards.

Probably worth mentioning... sometimes in our stories we plant things that don’t pay off until later. Character details. Worldbuilding. Set-ups for twists or other cool reveals. Such things are fantastic, of course, but they still need to work within my overall dramatic structure. It can’t be a situation where a chapter will be interesting in retrospect—it has to be interesting now, on the reader’s first time through.

Granted, this doesn’t mean it has to be interesting for the same reasons. It’s a wonderful skill to be able to pull that sort of sleight of hand, to make my readers look at this and be totally enjoying it, only to later realize that was the thing they should’ve been watching. But it still needs to be a chapter that moves things one way or another on that slope.

Because, again... the worst thing my chapter can do is flatline.

The sort of parallel to this—should be obvious but I’ll say it anyway—is that something needs to happen in every chapter (just to be clear, still using chapter as our basic, large-scale building block). In the same way we want to start with someone’s life changing, on some level or another, we want to keep having things happen. That’s what a good story is—the plot driving someone’s arc and their arc, in turn, is driving the plot. And driving implies we’re going somewhere, not sitting in a parking lot with the engine running.

Again, this doesn’t need to be huge movement. Every chapter doesn’t need huge leaps forward from the plot or broad swaths of character development that completely changes how we look at someone (that’ll usually ring a bit false anyway). Because every story is different and they’re going to move at a different pace depending on where we are in said story.

But they should always be moving. At some speed. In some direction.

How about this. Remember back in the A2Q when I made up a rough outline for a werewolf novel? Let’s take a look at those first few chapters I planned out and how they’re paced.

--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.

(You can see a more fleshed out version of this here)

This is a slow opening, yeah, but there’s stuff happening. Both characters are doing things, I’m establishing relationships, doing some worldbuilding, which will should build some interest. And things are actually progressing. Both of them are getting closer to their goal of being ready to head out for the night.

--Phoebe’s out hunting and encounters the super-werewolf (although she doesn’t know it’s super yet). She puts 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.

Now we’re moving at a faster pace. A lot more action, and it’s action moving the story forward as it introduces a bit of an unexpected mystery and what looks to be a greater challenge. The first part got my reader intrigued, so now hopefully this gets them a bit more hooked with a sample of what’s to come.

--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, the Warden of the lodge. She’s willing to entertain the ‘super-werewolf” idea, and will pay an extra $2500 bounty for proof.

Things slow down here, but logically so—it’s daylight, the hunt’s over. Also, structure-wise, we can’t keep things ramped up to nine for the entire book or it’ll make getting to ten seem a lot less interesting. And when everything hits ten on the tension-ometer, I want it to mean something.

Plus, there’s some more worldbuilding, a possible love interest/rival/both, and a new goal for my heroine. It’s a lot of talking, but there’s some physical action taking place and it’s all nudging things along in the plot. Creeping forward, inching the tension up a bit with this new goal (and the implied possibility of not achieving it).

See where I’m going here? The pacing speeds up and slows down, but the big thing is that there’s always a pace. The story’s always moving. I mentioned something a while back that's very true here--stories are like sharks. If they stop moving they'll die.

(the shark thing's not entirely true? Depends on the type of shark? Huh. Learn something every day...)

Again, every story is going to be different, so please don’t look at this as me saying “go slow, then fast, then slow again.” Your story is your story. It’s going to have its own pacing requirements that need to line up with what you want your story to do.

But hopefully this has given you a few things to look for.

Next time, I might finally get to clowns. Or maybe I’ll talk about plotting. That was a question I got a while back that’s still owed an answer. And questions get answers.

Until then, go write.

Our Binding Contract

Enough holiday stuff for now. Let’s get back to what you’re all really here for—the thing you specifically came here for. Half-assed writing commentary! That’s the deal, right? You keep showing up, I prattle on for far too long and maybe make one or two useful points.

Which is, ho ho ho, what I wanted to talk about.

The act of telling a story is sort of an unspoken agreement between two people. Kristi Charish has called it “the invisible handshake.” As audience members, we expect certain things from our story. As storytellers, we expect certain things from our audience. When we sit down together, even if we’re separated by a few months and a printed page, we’re both assuming the other half of this experience is going to follow certain conventions.

So let’s talk about this contract between writer and reader. Or storytellers and audience, if you’d like to keep it a little broader. I think this agreement is kind of universal in that regard.

As the writer, what am I promising you?

This Is Readable
I think we can all agree books come with different levels of reading difficulty. They get aimed at different age groups or demographics. So it’s not impossible to believe we could stumble across a book that seems too simple or too difficult for us.

But this should never be my goal as a writer. Nobody should struggle to get through a book, fighting through convoluted, never-ending sentences filled with obscure words that describe dozens of irrelevant characters. And if I’m writing specifically to exclude people (“Only the people who really understand art will enjoy this...”) I’m doing this wrong. If you pick up one of my books, I want you to feel welcome, and to actually enjoy the act of reading it.

This Makes Sense
It doesn’t matter if my book’s set on a cruise ship, in a Victorian mansion, or on a space station—it has to have an internal logic. Characters need to make decisions and take actions that fit within their world and their personal experience.

A simple test I always try to give myself is “would this book be enjoyable to read again?” If twists aren’t earned, if betrayals aren’t set up, if explanations don’t line up with what I’ve said before this... my story probably doesn’t make sense. And you deserve better than that as a reader.

This Finishes Arcs
Nobody likes getting to the end of a book and finding out ha ha maybe everything will get answered in the next book. If we’re going to get immersed in a story, one thing we’re inherently expecting is some kind of resolution at the end. That sense of closure is a natural part of storytelling. We expect the heroes to have a final showdown with the villains, for this year’s Hunger Games to end, or for them to perform the last exorcism. And when they don’t and everything’s left unresolved... it just doesn’t sit right.

And sure, there might be dangling threads or even an overall arc that needs to continue. But when we get to the end of this story we expect, well, an ending. Some aspect of this story has to be done and wrapped up in a satisfying way (to the reader if not the characters)

This Was Worth It
This is a twofold thing. One ties back to an idea I’ve mentioned before—we want our hero to win, even if it’s a pyrrhic victory. We need to see them have some level of success, because if not we’ve just read a book where the hero, the person we’re supposed to relate to and empathize with... loses.  Or doesn’t do anything. Or just has a textbook ending we’ve seen dozens of times before. After three hundred or so pages, these things can really make a book feel like it wasn’t worth reading.

Two is that, well, we want to feel like it was worth it financially. Nobody likes shelling out ten or fifteen bucks for a book that just wasn’t their thing, but shelling out that much for a book that’s incoherent, filled with typos, and half-copied from an old Doctor Who plot? And then has a bad ending? I mean, even a buck can feel like too much for something like that. If I’m trying to get you to give me money for this story, this story should be worth money.

In my opinion, that’s all the big promises we’re expecting on the writer side of things. Yeah, there might be more expectations depending on the genre, the author, the intended audience, but I think this is probably a good contractual boilerplate. From this direction.

Coming from the other side of the negotiating table, what should I expect from my storytelling audience? If someone’s willing to engage with the story, there should be a few basic things they’re promising me, the storyteller. Things like...

The Benefit of the Doubt
If I’m going to pick up a book, I should at least begin with the basic assumption the writer knows what they’re doing. They meant to use this word or that term, and yeah, there’s a reason these people have a collection of HD-DVDs and not Blu-rays. If something isn’t clear on page two, I should be assuming there’s a reason things aren’t clear on page two, not that the writer has somehow screwed up telling their story.

This doesn’t mean there can’t be problems in those first few pages or minutes. But if I see something I don’t understand I shouldn’t be immediately labeling it as a mistake or a problem and using that to guide my ongoing interpretation of things. There’s a term for that—it’s called hatewatching.

The Time to Tell Their Story
Related to the above, if I pick up a murder mystery, I shouldn’t be complaining that we still don’t know who the murderer is in chapter three. Those two cute folks may not have kissed by page forty-two. There’s a good chance the aliens’ true motives could still be unclear a third of the way in. 

Stories take time to unfold. We need build-up. We need to establish things. Some narrative devices just won’t work at certain parts of a story. If I’m reading a book, I need to be willing to accept that not everything’s going to be given to me in the first hundred pages—and that’s okay.

Judging It for What It Is, Not What I Want It to Be
It’s not uncommon to pick up a book not being 100% sure of what it is. What I thought was a sci-fi story might be more of a horror novel. This romance might involve a lot of historical drama. This superhero book might really be more of a superpowers thing. And sometimes this shift of genres and/or perspectives might be really annoying for us as readers.

But that doesn’t make the story wrong. Maybe it was poorly marketed or maybe I just don’t like horror novels. Maybe I wanted Dot to find true love or Yakko to go on a revenge-fuelled killing spree, and neither of these things happened in the book. But these things aren't inherently flaws in the story. The writer told story A, it isn’t wrong because I wanted story B.

That’s what I think we should be expecting from the other half of the contract. And again, we could probably add other things depending on the book, the genre, the author. That’s why contracts get adjusted. This is, as I mentioned before, the basic starting form that you get for free on the internet.

And I’m sure some of you think this has just been some silly, meta-writing thing that you skimmed over. But y’see, Timmy, when this doesn’t happen—when one side or the other breaks the contract—we get frustrated. As audience members, we hate it when we need to struggle through a story, not getting the relevant details or getting buried in irrelevant ones. As authors, we grind our teeth when someone gives negative criticism because “I didn’t know this was a horror novel” or “I quit reading after three chapters” or “Amazon delivered this with a folded cover.”

Okay, that last one has nothing to do with our storytelling contract, but we all still grind our teeth when we get a one star review for that kind of nonsense.

So remember the contract. Make sure you’re holding up your end of it. Because nobody wants to be known as the person who breaks it. That’s just not a good look from either side.

Next time... well, I want to talk about what you’re not getting for the holidays.

Until then, go write.

A Lull in the Action

I know the A2Q thing just got started, but I wanted to pause for a few moments to talk about action.

I’m a big believer that action—especially dynamic action--shouldn’t take much longer to read than it would take to happen. Swordfights, shootouts, fistfights, even sex scenes—all of these are events where we kind of expect people to get caught up in the moment and not focus too much on minutiae. When I’m telling these events as part of a story, it creates an odd situation where I want to advance the action, but I also need to explain what’s going on. It’s especially tough in first person narratives, but really it can happen anywhere.

An example I’ve used before is when a ninja leaps out of the shadows to attack me. On the one hand, I want to mention the mask and the gloves and the sash belt and those special shoes that ninjas wear. Plus maybe they’ve got weapons in their hands or tucked in their belt or strapped to their back. Maybe even cursed weapons with extra barbs or weird auras. And wait... is that long red hair? Is this ninja a woman? Holy crap, the robes are kinda loose but, yeah, I think she is.

Of course, during all this time... what’s the ninja doing? They leaped out of the shadows and... froze in the air? Are they waiting to punch or kick or maybe skewer me with their short sword or something like that?

Heck, did you even remember the ninja was in the process of attacking me while you read through all that description?

Which is the problem in these situations. Once I’m in an action moment, I’ve got to be careful about bringing it to a pause for descriptions of other characters, weapons, fighting techniques, heck sometimes even overly-describing the action itself. I can blow the rhythm and wreck the flow, knocking my readers out of the story right when I want them desperately turning pages.

And it’s not just descriptions that can do this. Another thing I’ve seen is people trying to do funny, snarky dialogue in the middle of action sequences. Sure, this can work to an extent, but when every other character is making one or two quips during every gunfight or car chase or building collapse, these events begin to stretch out. It doesn’t take long for them to start dragging.

Another common one is the sudden need to share information, either between characters or sometimes the narration relaying these facts directly to us, the audience. I think a lot of the time when this happens it’s the writer feeling the sudden need to remind the readers of something important. The potential double whammy here is this can be breaking the flow of my action and it may just be a bunch of noise that we already know and don’t need to be reminded of at this crucial moment.

The worst of all of these has to be the introspective moment. That point when the arrows are flying and plasma bolts are crashing around us and my character pauses to dwell on how fragile the connections are between all of us, and the series of decisions that unknowingly brought him to this moment. And this place. Of all the possible places he could’ve been right now. One different choice and maybe he’d be on a date with that cute barista, instead of here, pondering the threads of destiny...

Anyway, where were we. Right! Raw plasma exploding everywhere and whoa when did Wakko get fried? How’d I miss that?

Other popular introspective topics that can disrupt action may involve lost loves, found loves, children, aging parents, the ephemeral nature of beauty,  and a single raindrop, frozen in that moment of impact that so perfectly symbolizes the inevitability of death...

The real killer for all of this? Lots of stuff counts as action. There've been a few times I’ve mentioned that often-misunderstood chestnut, start with action. It doesn’t mean my book needs to begin with a ninja leaping from the shadows, it just means I need to start with something happening. With my characters doing something. Anything. And all those things that count as action are things I want to be careful about disrupting and slowing down.

Now, yeah, of course, there’s always going to be exceptions. There are lots of reasons why my character might have an unusual, unrelated thought in a moment of peak action, or why they might get distracted by that single raindrop. But I need to remember that exceptions are rare.

So don’t break the flow of your story by letting your action get bogged down.

And speaking of action and doing things... have I mentioned that my new book, Terminus, comes out next week? Like, one week from today. It’s an Audible exclusive, and if you wanted to preorder it now that’d help further convince the people who pay me that my books are a good investment. Which mean more books down the line. Which means we all win.

Next time here on the ranty blog, we continue with the next part of the A2Q, where I’m going to try to explain plots and how to put one together.

Until then, go write.

NaNoWriMo—FIGHT!!

            Hey!  It’s November.  Like, just barely scraping into November.  By hours.  You’ve probably still got the taste of chocolate in your mouth, don’t you?

            Yes you do.  Don’t lie.

            Anyway, if you’re even a semi-regular reader of this site, you’ve probably heard of a certain November writing event that starts... well, probably right about now, depending what time zone you’re in.  Some of you may have been writing for the past hour or two, fueled by miniature Heath bars and Reese’s cups.  Power to you for starting right at midnight.

            On the off chance this is all new to you, I’m talking about NaNoWriMo.  National Novel Writing Month.  You sit yourself down at the keyboard, scoop up your legal pad, jack in to your hexadecimal cerebral port, and try to get an entire novel done—start to finish—in just thirty days.

            And when you finish, you get...

            Well, bragging rights, basically.  Pride.  A feeling of accomplishment.

            Sounds a bit intimidating, yes?

            It sure as hell is. 

            Don’t get me wrong.  It can be fun, recharge your batteries, stoke the fires, and lots of other clever aphorisms.  But the simple truth is, it’s a huge, exhausting undertaking.  I do this full time, for a living, and the idea of writing an entire book in thirty days makes me feel a bit overwhelmed just thinking about it.

            So here’s four quick thing to keep in mind so you don’t get as intimidated or overwhelmed.

            1) Don’t be Hard on Yourself—this is supposed to be fun.  You’re on a deadline, yes, but it’s a self-imposed deadline with no consequences if it’s missed.  Seriously, relax.  Don’t beat yourself up if you don’t make your daily or weekly word count.  That’s the kind of thing that makes you feel bad about yourself and about your ability as a writer.  It doesn’t help anything, it just makes you enjoy the act of  writing less.

            Push yourself, but don’t pressure yourself.  The big goal here is to improve, so any and every improvement counts.  Have fun and enjoy all the little victories this month.  This is a time when coming in second or third is still a great achievement.

            2) Pace Yourself—nobody wins a marathon by sprinting the entire way.  Trying to fill every single waking moment with writing is going to burn you out quick.  And it’ll show in your work.

            Try to be aware of diminishing returns.  A lot of times when I’m on a deadline, I’ll work late into the night.  Sometimes it goes great, but sometimes... I start to slow down.  My productivity drops.  And eventually it hits a point where I would’ve been better off going to bed two hours ago because I would’ve gotten just as much done in half an hour on a good night’s sleep.

            It’s so friggin’ simplistic, but think of the Tortoise and the Hare. Slow and steady gets the worm and the second mouse gets the cheese.  Something like that.  You get the idea.

            3) Rest and recharge—if the last two pieces of advice got together and had an advice baby, it would be this.  Don’t be scared to step away, just for a little while.  Have a nice meal and maybe a drink.  Go for a walk.  Take a nap.  Take a shower.  No, seriously, take a shower.  You should probably do that before going out—you’ve been sitting there for days typing and you’ve got writer stink on you.  Play a game.  Call a friend.  Curl up with somebody on the couch and watch an episode of Legends of Tomorrow or The Chilling Adventures of Sabrina or something.

            Point is, don’t feel bad about stepping away from the computer for an hour.  You’re trying to get a lot done, yeah, but with that in mind you don’t want to overwork the machine to the point it overheats and seizes up.  Give it time to cool down and refuel.  I’m not saying take a day or three off in the middle of this, but don’t be scared to get up, stretch, and walk away from your computer for an hour.  In the end, it’ll run smoother and faster overall.

            4) This Won’t Sell—no, seriously.  It’s won’t.  Kick that idea right out of your mind and stop worrying about it altogether.  It’s just not going to happen.  You’re worrying about your wedding venue and playlist when you’re not even dating anybody right now.

            The name NaNoWriMo is kinda deceptive, because you’re not really writing a novel this month.  You’re writing the first draft of a novel.  Maybe even just the first draft of a novella.  And there’s a huge difference between a first draft and a polished, completed manuscript.

            Most importantly... nobody’s going to buy a first draft.  No agent’s going to look at it.  No film studio will pre-emptively buy the rights after a prolonged bidding war.

            This draft is for you.  It’s to do whatever you want with.  Don’t spend a second second-guessing what those other people will want.  They’re never going to see this.  They may see the third or fourth draft—and be interested in it—but what you’re doing right now?  This is just a mess of cake batter.  It’s barely halfway through the process.

            So forget them.  Right now, just crank up the music and let your imagination run wild.  Do whatever you want.  Tell your story.  Drop all inhibitions and expectations and just write.

            Keep these things in mind over the next couple days.  Hopefully they’ll make things a little easier for you. Which’ll make the writing a little more enjoyable.

            Next time...

            Well, it’s been a while, so I figured we could talk about characters.  Or, to be more exact, who deserves to be a character in my story.

            Until then... go write.

Meanwhile, At A Secret Island Base...

            As has come up here once or twice or thrice, I like to watch bad movies (and usually offer a bunch of half-drunken live tweets as I do).  I’m a big believer in learning from the bad stuff over copying the good stuff.  Plus it’s kinda fun, in a masochistic sort of way.  I mean, statistically, somebody must’ve made a good shark movie, right?

            Yeah, sure, Jaws, but I’m thinking in the forty years since then...

            Anyway, a few times now I’ve noticed an issue that I’ve also caught in some literary fiction.  By which I just mean “fiction on the page,” to distinguish it from cinematic fiction.  It can be brutal in movies, but it stings in books, too.   So I wanted to blab on for a minute or three about an aspect of pacing that seems to get overlooked a lot.

            It’s a very natural part of storytelling to shift between locations or timeframes. At a particularly dramatic moment, we may leap over to a parallel storyline, or maybe flash back to a key moment that happened hours, weeks, or even years ago.  Depending on our chosen genre, we may leap across centuries or galaxies.

            And that’s cool.  We all love it when a story covers a lot of ground and shifts between points of view. It lets us tell multiple stories and tie them together in clever ways, or to get information across using different methods.

            But...

            There are still some things I need to keep in mind as a storyteller. As beings that live more-or-less linear lives, we tend to notice when there’s a jarring difference in the passage of time.  We understand that time spent here is also time spent there... even if we don’t see it happen.

            That’s the thing to keep in mind.  Just because we cut from scene A to scene B, it doesn’t mean scene A stops. Time still passes.  Characters keep doing things.  They continue to talk and discuss and explain and comment on things.

            It’s not unusual to skip over swaths of time in a narrative.  As I was recently reminded, we don’t need to see the four-day cross country trip if... well, nothing happens during those four days. No matter how beautiful the language or evocative the imagery is, if nothing happens to further the plot, it’s an irrelevant scene.  Or chapter, as it was in my case.

            But here’s the thing I need to remember.  That time is still passing.  My character may get on the bus at the end of chapter six and get off at the start of chapter seven, but that doesn’t mean the journey was instantaneous.  There were meals and probably some conversations and a few bathroom breaks and some sleeping.

            More to the point, it wasn’t instantaneous for everyone else.  Four days passed for all the other characters, too. Time progressed for everyone.

            Now, I can fudge this a bit in a book.  It’s much harder to do in a movie, but in a book we can be made to understand that time did come to a halt between chapters nine and eleven.  We went off to deal with something else for fifteen pages, yet when we come back everyone’s still standing here with pistols drawn, cards on the table, or awkward confessions hanging in the air.

            But...

            Yeah, another but.  Sorry.

            Whenever I have one of these cutaways, in prose or on screen, I need to consider the pacing and flow.  My readers will need to switch gears and jump into a new headspace for this different scene with different characters.  Sometimes it can be fantastic.  Cutting away can increase tension, ramp up the stakes, or just heighten emotions.  Done right, it can take my readers from screaming to laughing and back.

            Done wrong... and it just reminds people that things weren’t happening.  That the  action just froze during the time we shifted attention to something else.  The writer skipped over it... and they assume the characters did, too.

            I saw this in a friend’s book.  Some characters went through a major event together, drove two hours back home... and then started talking about what had happened.  And my comment was, what were they talking about during the two hour drive?  Or there was a recent geekery movie where one of the aspiring victims was running from the homicidal killer, and then we cut away to six or seven minutes of the local sheriff discussing the recent killings over coffee.  And then... back to the victim.  Still running.  Still with the killer a few yards behind...

            And I did it once, too. In an early draft of Ex-Heroes, right in the middle of the climactic battle, the story cut away to a slow, almost introspective flashback.  Conversations were had, moral decisions were made, and in the end a plan was created to help save as many—WAIT, back to the fight with the zombie demon!!

            My beta readers made fun of me, too.

            Part of this is a pacing issue. If the action is happening with breakneck, life-or-death speed in this scene, I probably want to be cautious about jumping over to a slow stretch of decompressed storytelling.  I don’t want my reader stumbling as they try to figure out what’s happening and when it’s happening.

            Y’see, Timmy, when that stumble happens, it knocks us out of the story.  The cutaway brings things to a jarring halt.  We go from experiencing the story to analyzing it.  Puzzling over it.  Maybe even... laughing at it.

            Laughing at, mind you.  Not laughing with.

            So be careful where you make your cuts.

            Next week I’d like to talk about another aspect of writing that’s really close to this, one I’ve been bringing up a lot lately, to be honest.  This’ll flow really well right into it.

            Until then... go write.

Hitting The Fan

            Running a little late this week. Sorry.

            Truth be told, I don’t have a ton of time so this is going to be a bit short. So’s next week, honestly. Right now I’m trying to do a bunch of pre-publicity stuff for the release of Paradox Bound next week, and next week is... well, four signing events with about five hundred miles between them, plus some other stuff, plus getting ready to go to New York Comic Con..

            I’m going to be busy, okay?

            Plus, I have a bad habit of over-preparing for things. A holdover from being dirt poor.  I just assume everything bad is going to happen and try to cover all my bases.

           Of course, inevitably, the bad thing is something I didn’t plan for. I mean, if I’d planned for it, it wouldn’t be that bad, right?  It might be annoying, a minor obstacle at best, but it’d be tough to think of it as some kind of crisis.

            Anyway...

            I wanted to talk today about the moment in a story when things go wrong and our characters suddenly have to depend on their wits to make it through.  They’re in a position they didn’t intend to be in.  I’m a big believer in that moment.  I think it’s what seperates a lot of average-to-good stories from great ones.

           Let’s use a heist as an example.  We’ve all read a good heist story (or at least seen one of the Ocean’s Eleven movies).  In a heist, we usually see our heroes and/or heroines go through lots and lots of planning, working out every detail. They know when the guards change shift, how long the elevators take, how much weight sets off the pressure plates, and more.

            But then—always—something goes wrong.  There’s a new alarm system.  They’ve changed the guard rotation.  There’s a power outage before our power outage—one we’re not in control of!—and Jake doesn’t know!  How’s he going to get out of there?!

            This is the moment we grow to love characters. When they have to think fast to get themselves out of a tricky situation.  When they’ve got to do something they weren’t prepared to do.

            Now, on the flipside of this... there’s a show I’ve been watching, and I really want to like it. It’s got a lot of elements I usually enjoy.  But nothing ever goes wrong for them.  I mean, they’ll hit problems.  Have thing they need to deal with.  Sometimes major adversaries to overcome.

            But again and again, they’d hit a problem, figure out what they needed to do in order to beat it... and that would work.  I need to do this.  I did this.  The end.

            Sounds kind of unsatisfying, doesn’t it?

            Spoilers—it was.

            This all ties back to something I’ve mentioned here before.  When someone’s so over-prepared that nothing’s a challenge, my story is boring.  My characters aren’t being pushed in any way, so it diminishes whatever’s driving the plot.

            Likewise, if my characters barely even need to be prepared and nothing’s a challenge... well, then my story’s still boring,  It might even be more boring.  Because now, no matter what this week’s crisis was, it’s clearly something that takes minimal effort to deal with.

            And let me take a quick minute to clarify something about effort.  Effort doesn’t just mean gritting my teeth and sweating.  If we know the hatch Wakko needs to open weighs three hundred pounds and he heeeeeeeaaaaaves it open, that’s just planning to do something strenuous.  What we’re talking about is when Wakko goes to heave open that three hundred pound hatch... and somebody padlocked it since yesterday when he scouted the place.  And he’s still only got ninety seconds to get it open before the zombie horde reaches us.

            That’s going to take some effort.

            And impress the hell out of my readers when Wakko does it.
            Speaking of readers, hopefully I’ll see some of you next week during my crazy California signing tour.  Or next weekend at NYCC.
            Until then... go write.

            And put some effort into it.

Six Years Ago In Kazakhstan...

            If any of you happen to follow me on Twitter, you know I have a habit of watching bad B-movies on the weekend--usually while I’m geeking a bit.  While I do, I tweet out random observations about the story, dialogue, plot points, and so on. More often than not... they’re not positive ones.

            There’s usually a lot of drinking going on, too.

             A few weekends back I was watching this movie that went for the standard “group of assorted soldiers thrown into an unnatural situation” scenario.  The same one that’s been kind of become the standard since Aliens did it with the Colonial Marines.  Often copied, never duplicated, as they say.

            Maybe twenty minutes in, one of the civilians asked a grunt why they were all so dedicated to the sergeant.  And said grunt told him this two or three minute story about how, five years ago, they’d been stationed on Theta Sigma, things went belly-up one night on patrol, and Sarge was the only one who kept it together.  He got them out of that hell-zone on the death planet, and he even carried Bronsky for the last three miles.

            Then, maybe thirty five-forty minutes in, one of the civilian scientists asked the lieutenant why he was such a hard ass.  And he told her about how four years ago he’d been walking the perimeter, checking on his men, and he found some civilians in a restricted area. But he cut them some slack... and then the Lictors attacked. If he’d been hard then, if he’d sent them away as soon as he found them, those three people’d be alive today.

            And then someone sat with the Sarge for a while as he recovered from a wound (he’d been impaled right through the chest, and that put him off his feet for, y’know, almost six hours).  She asked how he could stay so positive, making jokes while the whole mission was turning to crap around them.  And he told her about how, seven years ago, he’d been on this bug hunt on Ceti Alpha Five...

            Look, you get the idea, right?  Do I really need to finish that story?

            Yeah, most movies don’t do it that many times, sure.  Still... that element’s kind of become a standard in a lot of military stories, too, hasn’t it?   The soldier/Marine/Amazon/Mooncop who gives us a flashback in dialogue to explain a strange bond, a weird character tic, or maybe even that scar she’s got that runs from her temple down past her jaw. 

            Here’s the funny thing, though. This never happens in Aliens.  Not once. Not even for a few seconds.

            Y’see, Timmy, in Aliens the story only goes forward. We don’t need to go backwards to learn interesting stuff about these characters.  We’re learning about them through how they react to things now, not how they reacted to them six years ago in Kazakhstan.

            If the only way I can make my characters interesting is by flashing back six or seven years... maybe I don’t have interesting characters.  Not now, anyway.  It’s possible they were interesting back then, but if they’re interesting now... why’s all their character development in the past?

            At the very least, I don’t have an interesting story.  If I did, wouldn’t there be  cool stuff happening now?  Stuff my characters could be reacting to and giving the reader a better sense of who they are, even as it drives the plot and story forward?

            If it’s only that recollection or flashback that’s making them cool... maybe that’s the story I should be telling.

            Anyway, just wanted to toss that out real quick.

            Thursday, our regularly scheduled post.

            Until then, go write.

The Pace Car

            Okay, first off, I’m afraid I need to have a shameful self-promotional moment. The Ex-Heroes series is Amazon’s Kindle deal of the month.  You can pick up digital copies of all four books for less than ten dollars.  So... there’s that.

            And now, moving on to our actual topic of the week...

            Last week I gave some more-or-less quick answers to a couple questions and requests folks had left here on the ranty blog.  This week I wanted to address one in particular that was worth a little more space.

            So... here we go.

            I'd love to hear your thoughts on plotting and pacing. I'm struggling with knowing when to do what plot elements so things don't drag and so they seem natural, and don't feel like the story is on rails.
            Okay, this is another tough one because every story is going to have its own specific pace. 

            One of the reasons a lot of folks end up worrying about this, in my opinion, is because of an often misunderstood writing rule that gets thrown at them all the time—start with action!  There’s a bunch of problems with this statement, many of which I’ve talked about before, but one key one is that it gives people a very skewed view of pacing.  If my story starts cranked up to eleven, it’s hard to make anything feel urgent after that point.  And if it doesn’t start at eleven, well, why is anyone going to keep reading, right?

            Part of this is about dramatic structure, knowing where things should happen in my story for maximum impact.  It’s also about compressing time so things don’t sprawl.  Yeah, maybe four hours passed while Wakko was pulling his turn standing watch, but do I really need eight pages of him standing around doing... well, nothing?

            I think that’s one of the biggest problems when people have “pacing issues.”  It’s not whether or not my chapter is slow or fast, if it’s filled with action or dialogue or inner monologues. It’s about whether or not anything’s actually happening.  When my story come to a grinding halt, it’s not because I’ve got characters doing research instead of kung-fu... it’s because the story’s come to a grinding halt.  It’s stopped moving forward. 

            A good way to check pacing is to go through my story and ask myself this—what purpose does this element/ scene/ chapter have in the overall story?  Is it forwarding the plot?  Is it forwarding a character’s story?  If it doesn’t do either of these things... why am I spending time on it?  As William Goldman said in The Princess Bride, “What with one thing and another, three years passed.”

            Speaking of famous screenwriters, Shane Black once made a great observation about what he called “shoe leather” scenes in scripts.  If I have a scene where two guys are having a conversation and another scene where there’s a key news story on the television... why aren’t they the same scene?  A good part of storytelling is trying to accomplish two things at once rather than spreading things so thin they’re see-through.  It’s great to have a character scene, sure, but maybe those character moments could also advance the plot somehow.  I really want to use a lot of this research material, but could it advance someone’s story?

            Y’see, Timmy, if I’m lucky and somewhat skilled, my audience might let me have one scene that doesn’t really do anything.  Maybe two.  But pushing it to a third means my story is dragging, and four is going to get eyerolls.

            Now, all that being said (yep, there’s always a however), there is still one thing to keep in mind for pacing.  Every story is going to start slow and pick up speed, yes.  And all those stories are going to be moving at their own pace. I need to be careful, though, when I try to slow things down, for whatever reason.  If you’ve ever driven a car with a manual transmission (or know of such things), you’ve probably heard the term downshifting.  It’s when I shift into a lower gear to help with slowing down (you’ve probably seen James Bond do it a few times).  It’s one thing to go from fifth gear to fourth, it’s something else entirely to go from fifth down to second.  Odds are that’ll going to leave parts of my transmission  (read—story) scattered behind me, possibly on fire.

            So if my story involves a lot of zero-to-sixty-to-ten-to ninety-to-fifteen pacing—yes, even though it’s still technically moving forward—I may want to rethink a few things.  And if it doesn’t involve any forward motion...

            Well, I may need to rethink a lot of things.

            Next time, I’d like to talk about how Darth Vader killed Luke Skywalker’s father.

            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.