February 17, 2018

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 Pantheryet 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…
            Structureis 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 linearstructure, 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 Eis 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.
January 18, 2018 / 5 Comments

Down to Basics

            It’s come up once or thrice that I’m a lover of bad movies.  Partly for the laughing aspect, partly because I think you can learn as much from bad storytelling as you can from good.  Partly because I need to justify my drinking, and some of these movies make it reeeeeally easy.
            A while back I tossed out a list of really basic things a lot of these movies messed up.  Film school 101-level stuff that people were getting wrong.  Even though some of them went to film school.  And I wondered if it might be possible to do something with stories in general.
            Kristi Charish (of the fantastic Kincaid Strange series—book two coming soon) recently mentioned this idea (for a different topic) in a much better way—the invisible handshake.  It’s sort of an unofficial, unspoken contract between the author and the reader. If you’re picking up my book, there are certain automatic assumptions you’re making about what I’ll be providing you with, and I should be meeting these assumptions.  Basic things about plot and structure and character that are just… well, basic.
            At the end of last year I read a book that fumbled that handshake.   Fumbled it bad.  It was like that awkward moment with someone at the end of the night where you’re not sure how to say goodbye, so the two of you make a bunch of half-moves toward different things.  Do we hug?  Shake hands?  Peck on the cheek?  Write an awful book? 
            We’ve all been there, right?
            I ranted a bit about said book on Twitter, but even then I was thinking I should revisit a lot of those issues here.  And while said book was very rant-worthy, I’ve been .trying to keep things a bit more on the positive side here.
            So, a few general things I need to keep in mind when I’m writing.  I’ve mentioned most of them before, but I thought a general, all–at-once
            First, I need to be clear who my main character is.  If I spend the first four chapters of my book with Yakko… everyone’s going to assume Yakko’s the main character.  This book’s clearly about him, right?  So when he vanishes for the next seven chapters… well, people are going to keep wondering when we’re getting back to him.  Because he’s the main character.
            Now, a lot of books have a big cast of characters.  An ensemble, as some might say.  That’s cool.  But if my book’s going to be spending time between a bunch of characters, I need to establish that as soon as possible.  If the first three or four chapters are all the same character, it’s only natural my readers will assume that’s going to be the norm in this book.
            Secondis that I need to keep my point of view consistent.  This kinda goes with the first point—being clear who my main character is.  Even with a third person POV, we’re usually looking over a specific person’s shoulder, so to speak. Which means that character can’t walk away and leave us behind.  Likewise, we can’t start over Wakko’s shoulder and then driiiiiiiiiiiiiift over so we’re suddenly looking over Dot’s.
            Again, it’s cool to switch POV and there’s nothing wrong with it, but I need to make it clear to my readers that I’m doing it. If they start seeing things from new angles or hearing new pronouns, it’s going to knock them out of the story and break the flow.  That’s never a good thing.
            Thirdthing I need to do is be clear who my actual characters are.  Who’s part of the story and who’s just… well, window dressing.  If my two protagonists go out to dinner, there’s going to be other people in the restaurant.  But I shouldn’t describe them all. Or name them all
            Names and descriptions are how I tell my reader a character’s going to be important and worth remembering.  Three paragraphs of character details means “Pay attention to this one.”  So if I’m telling the reader to keep track of people for no reason, I’m wasting their time and my word count.

            I want to note a specific way people do this, too.  I’m calling it “describe and die” (trademark 2018).  This is when the author introduces a character, spends five or six pages describing them, their history, their goals, their loves, their life—and then kills them.  We’ve all seen this, yes?  Here’s Yakkoshiro, a twenty-nine year-old salaryman who spends all his free income on Gundam models and always wears long sleeves to the office because he won’t stop wearing his fathers watch, even though nobody wears watches anymore and looking behind the times like that could hurt his chances at a promotion so… long sleeves, never rolled up, even when the air conditioner dies (which happens a lot). And tonight he has a date with the beautiful woman from the Gundam store, who he’s exchanged nervous banter with for months now and, oh, he’s dead.  A kaiju stepped on him.  Now, back to our heroes…

            Don’t do that.
            Fourthis that I need to have an actual plot before I start focusing on subplots.  What’s the big, overall story of my book?  If it’s about Wakko trying to save the family car wash, I should probably get that out to my readers before I start the romance subplot or the backstabbing partner subplot or the Uncle Gus has cancer and wants to travel around the world before he dies subplot.  After all, they picked up my book because the back cover said it was about saving the family car wash or escaping that Egyptian tomb.  I should be working toward that first—meeting those expectations.
            If I’m spending more time on a subplot than the actual plot, maybe I need to revisit what my story’s actually about.
            Fifth, closely related to four, is that my subplots should relate to the main story somehow.  They should loop around, tie back in to the main plot, or at least have similar themes so we see the parallels.  If I can pull out a subplot out of my story and it doesn’t change the main story in the slightest… I probably need to reconsider it.
            And if it’s an unrelated subplot to an unrelated subplot… okay, seriously, I’m wasting pages at that point.  Not to mention this all starts getting, well, distracting.  I don’t want to kill whatever tension I’m building in my main plot by putting it on hold for eight or nine pages while I deal with… well, something completely unrelated.  It’s like switching channels in the middle of a television show. Nobody’s saying what’s on the other channel is bad, but it doesn’t have anything to do with the show we’re trying to watch.
            Sixth
            Okay, this is an odd one.
            Remember how much fun it is when you meet someone you’re interested in and there’s all these fascinating little mysteries about them?  We want to learn all their tics and hidden secrets.  Where are they from?  What’d they study in school?  What movies do they like?  How’d they develop a taste for that?  Why do they have that accent?  Where’d they get that scar?  Just how big is that tattoo?
            But… we don’t want to learn those secrets from a book report.  We want to hang out with these people, talk over drinks, go on road trips, maybe stay up all night on the phone or on the couch.  It’s how we get to know real people… and it’s how we want to learn about characters, too. Pages and pages of backstory often makes characters less interesting because it leaves me with nothing to reveal about them.  It kills that sense of mystery, because there’s nothing left to learn about them.
            There’s nothing wrong with me having all that backstory, but I don’t need to use it all in book.
            And I definitely don’t need to reveal it all in the first two or three chapters.
            Seventhand last is flashbacks.  Flashbacks are a fantastic narrative device, but they get used wrong a lot.  And when they’re wrong… they’re brutal. A clumsy flashback can kill a story really fast.
            A flashback needs to be advancing the plot.  Or increasing tension. Or giving my readers new information.  In a great story, it’s doing more than one of these things. Maybe even all of them.
            But a flashback that doesn’t do any of these things… that’s not a good flashback.  That’s wrong.  And it’ll bring things to a grinding halt and break the flow.
            Seven basic things to keep in mind while I’m writing my story.
            Now, as always, none of these are hard-fast, absolute rules.  If I hire a pastry chef for my bakery, there’s always a possibility this particular one doesn’t use a whisk.  There can always be an exception.  But I should be striving to be the exception, not just assuming everyone will be okay with me not following all the standards. My readers are going in with certain expectations, and I need to be doing honestly amazing things to go against them.  
            Because if that same pastry chef also doesn’t use a spatula…  Or butter… Or flour…
            Again—the invisible handshake (trademark K. Charish, 2018). 
            It’s a legally binding contract in forty-two states and four Canadian provinces.
            Next time, I’d like to tell you about something that happened off-camera on a TV show I worked on years ago.
            Until then, go write   
            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.
August 21, 2015 / 4 Comments

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

Categories