Showing posts with label conflict. Show all posts
Showing posts with label conflict. Show all posts

Thursday, March 18, 2021

Good and Bad Conflict

Sorry I missed last week. Taxes. As I mentioned earlier.

A few weeks back, during my usual Saturday geekery, I had a sudden epiphany about Asylum movies. Even though, technically, it wasn’t an Asylum movie I was watching. I feel safe saying whoever made this film studied at the feet of the mast... well, at the feet of the Asylum producers. And it’s a problem I’ve seen in a lot of book manuscripts. So I made a note of it and told myself I’d have to do a post on it sometime soon.

And then last weekend’s geekery gave me a trio of movies that suffered from the exact same issue. So I thought, wow, serendipity. Definitely a sign of... something. So sometime soon became this week.

Once or thrice here I’ve talked about the ideas of plot and story. Plot is what happens outside my characters, story is what happens inside my characters. The basic idea of a narrative is that conflicts (of many different types) will drive that plot forward, and the plot and story will work together and feed off each other like some beautiful alien symbiote that bonds with you and manifests as bio-armor under times of stress or when you summon no, wait, that’s the plot of the Guyver. I’ve talked about how plot and story work together before. Stick with that, forget the Guyver. For now.

What I wanted to talk about was the conflicts, all those roadblocks that pop up between the beginning and end of the story. The things that get in the way of my characters getting what they want. Because some of these things are great and some are... not so great.

As I mentioned above, I have conflict in my book to drive the plot. My character has to overcome social pressures, financial constraints, power structures, ancient death traps, and a variety of other obstacles. Dealing with these things (or failing to deal with them)  forces my character to grow and change internally (sometimes called a character arc) while at the same time usually subjecting them to greater pressures/constraints/death traps. That’s dramatic structure. Who my character is at the beginning of the book starts and shapes the plot. Who they become at the end helps them resolve the plot.

Here’s a cool way to think of it. Picture a staircase. Every time we climb up a stair, it feels like we’re on level ground, but we’re actually higher than we were before. As we keep climbing stairs, we keep going higher. That’s conflict moving the plot. Climbing stairs moves us higher. Make sense?

Now, the problem I was seeing is that some storytellers had lots of conflicts popping up—but they didn’t actually do anything. They didn’t affect the plot in any way. They’d encounter a new obstacle, deal with it, and then be... right back where they started. Nothing gained. Nothing accomplished. Nothing learned. Our characters haven’t moved any closer to the end of the plot, haven’t grown or changed in any way. These conflicts were so self-contained we could just snip them and lift them out and there wouldn’t be any real change. Heck, we probably wouldn’t even need to stitch things together on either side.

If you wanted to use that staircase analogy, at this point the steps have kind of fallen over and become more a line of peaks. Every time we go over one, we’re just... right back at ground level. Not to mention, they’re all kind of the same peak. None of them stand out, and we realize pretty quick it’s just going to be that same thing again and again.

A term I’ve brought up here before is episodic. Yes, like TV episodes. Its when the conflicts resolve and the plot and story basically reset to where they were at the beginning. Our characters don’t grow or change in any way, they gain nothing, they just... go to the next episode. Which is exactly the same.

Neat thing to think about—because of that “reset,” it doesn’t matter what order we watch a lot of older shows in. We can go from episode twenty-three to episode fifteen to the eighth episode of season four and... you can’t tell. There’s no change because there’s no actual goal. The characters aren’t really trying to accomplish anything past the particular obstacles of this single episode.

When this happens in a larger story—say a novel or a movie—the storytellers are just dropping in these episodic conflicts because... well, we need conflict, right? So we’ll get a flat tire, spend ten minutes changing it, and then we’re back on the road. Or we’ll get caught in a super-embarrassing, borderline scandalous situation at work that nobody remembers or comments on the next day. Or we’ll find ourselves going out to rescue Wakko again and drag him back home because he just won’t stay put during the zombieapocalypse. These events are there. They fill pages. But they have no repercussions. No lasting effects. They don’t spark any changes in the way anyone thinks or acts.

Y’see Timmy, there’s conflict that advances the plot and conflict that just prolongs the plot. It isn’t there to help develop the characters or their stories, it’s just there to keep us from reaching the end too soon. So people get flat tires. Or wander out of their house during the zombocalypse. Or—no joke—fall off the Great Pyramid of Giza.

And absolutely nothing happens. No one suffer any consequences from these events at all. None.

Now, this isn’t to say nobody can get a flat tire in my manuscript. Flat tires are a real thing that happen to all of us. But I should think about why this flat tire’s happening. As I’ve mentioned before, I’m the all-powerful Creator-of-your-choice in the world of my story. Nothing happens here except by my choice and my will. So why is this flat tire happening? What purpose does it serve in my story? Is it advancing the plot? Giving someone a moment to expand their character arc?

Or is just happening to keep them from getting where they’re going too soon?

Look over some of your story points. Are they advancing your plot? Or are they just stretching it out?

Next time... I had a new idea I wanted to talk to you about.

Until then, go write.

Thursday, November 19, 2020

Shouldn’t Throw Stones

There’s an aphorism about writing I heard a while back—“get your character up a tree and throw rocks at them.” It’s one of those fun, quick statements with a lot of truth behind it. A complex idea boiled down to something simple.

There’s another one, part of Pixar’s rules of storytelling. “Coincidences to get characters into trouble are great; coincidences to get them out of it are cheating.”  Because we’ve all seen that, right? The character who randomly finds the exact thing they need just when they need it.

Put these two together and my character’s picked the worst tree to climb up. Because it turns out that’s the rock-throwing tree! Since our town was founded, people have always thrown rocks up at that thing. The local little league uses that specific tree for pitching practice. Young couples throw rocks at that tree to see if they’ll live happily ever after. And they say if you throw rocks at it under a new moon, you can speak to a lost love one final time.

Okay, maybe going a bit overboard there. It’s kind of silly to believe this one tree has so many legends and habits and traditions of rock-throwing associated with it, right? Especially because some of them, you’ve got to wonder... why? How the heck did this become a thing? Why would all these people one day choose to throw rocks at this tree?

Which is what I wanted to talk about.

We’ve talked about the need for conflict before. If there’s no conflict—or an utterly minor, negligible conflict—I can’t have much of a plot. And without a plot, my characters are just kinda standing around without any. So this idea of throwing stones—of putting lots of obstacles between my character and their goal—is a solid one. We want our characters to have something to do, and we don’t want it to be easy for them to do it.

BUT...

Kind of like with the rock-throwing tree, we need to feel like there’s a reason behind this. If our character was stuck up in a tree and people just happened to randomly decide “hey, let’s throw rocks at that!”... we’d probably call foul. It’s just not terribly believable.

Okay, it might be believable once. Our minds will give a little leeway (especially in fiction) for a single bizarre coincidence. To quote the esteemed philosopher Elim Garak, however... I believe in coincidence. Coincidences happen every day. But I don't trust  coincidences.

If I’m going to have a lot of rocks thrown at my character, I need some solid, in-story reason why they’re being thrown. Because after my characters lose their keys or forget the password or drop the flash drive or run into a third mugger... well, it starts to look less like coincidence and more like weak writing.

Because even coincidences have a reason behind them. Why this person showed up early. Why that battery isn’t charged. Why Dot forgot to bring the incredibly important goober that this entire mission hinges on.

Even when it’s less coincidence and more an active thing—if it’s the same mugger chasing my protagonist across the city and popping up again and again—I have to ask why. Why is Phoebe so obsessed with mugging Yakko? Why does she keep doing this? Or how does she keep ending up just where he is again and again and again. or why does Yakko keep ending up in places where he’s going to get mugged when it just happened to him the other day.

Get your character up that tree and throw stones at them. Throw boulders at them. And handfuls of loose gravel. But know, within the story, why they’re all getting thrown. Is there a real reason for it?

Or is the only person the reader sees throwing stones... me?

In other news, in case you missed it, the A2Q now has a table of contents, so you can find all of it quick and easy. Also, with everything going on in the world I made my usual Black Friday offer a little early this year, so if you’re someone who could use it, please get in touch with me.

Next time here on the ranty blog...

Holy crap, it’s Thanksgiving. How is this year moving so slow and so fast at the same time? The barriers have been shattered! All time is existing at once!

Seriously, though, unless someone’s got a specific, pressing question I’ll probably take the day off and maybe throw some Cyber-Monday gift ideas at you. And next time I’ll talk about binding agreements...

Until then, go write.

And throw some stones.

Friday, October 25, 2019

Some Outlining Questions

Look! Bonus content! It’s what the internet screams for!

Last weekend I was in Dallas talking to folks about NaNoWriMo. Overall I think it went pretty well. People laughed and chuckled in all the places I hoped they would.

However... there is strong evidence that I may have had waaaaaaaay too much caffeine before giving said talk. Combine that with a very echoey big room and, well, some of my brilliant observations about writing were lost. And most of my awkward jokes, too. So it’s a pros and cons situation.

Anyway, since I’ve been asked about a few things that got lost in my speed-echoes, I thought I could tweak part of the speech and post it here for everyone. It’s helpful for NaNoWriMo, but it’s some good overall stuff to keep in mind, too. Plus, this way I can add in a ton of links to help explain things even further.

What I’ve got below are eleven questions for you to think about when you're sitting down with your story.  Depending on your particular plot/story/genre/cast of characters, there’s a chance one or two of these might not work for you.  But a lot of them should. In fact, I’d say if a lot of these don’t apply to the story I’m trying to tell, I’m probably missing something important.

1) Who’s my main character—or characters, depending? Man, woman, non-binary, young, old, straight, gay, werewolf, vampire, bionic space Pope, who are they?

2) What’s a normal day for them? What would they be doing today if they weren’t falling in love or saving us from vampire kaiju? What’s their day job?

3) What happens to make this not a normal day? What changes in their life? Why are we writing a story about this day & not a day last week or next month? Fancy folks call this the inciting incident or introducing conflict. I just like to say... why is this not a normal day?

4) What are they trying to do? Really simply, what’s my book about? This is their goal.

5) Why are they trying to do it? Fancy people call this “their motivation.” Kidnapped friend? Revenge? The greater good? Nanite bomb implanted in their groin? Why aren’t they just saying screw this and going back to their normal life?

6) How are they trying to do it? What actions are they taking? Do they have a plan? Are they making it up as they go along? We want our characters to do something.

7) What’s stopping them from getting it done right now? Is their goal far away? Under guard? Super expensive? Only dates cheerleaders?

8) Do I have an antagonist? Somebody openly trying to stop my hero, for major or minor reasons. My antagonist doesn’t need to be a villain, but they’re definitely somebody with opposing views.

9) What does my antagonist want? This is another character, so we want to develop them. They’re going to have goals, too, even if it’s just “kill all those kids out at the summer camp” or “stomp across Vatican City once the sun goes down.”

10) Why do they want it? My antagonist needs to have motives, too. So just like with my hero–why are they doing this?

11) Finally, what happens when my hero achieves their goal? Are there parades? Explosions? Bloody vengeance? Long passionate kisses? What happens if everything works out right? And on the flipside, what’s going to happen if they don’t achieve their goal?

Now, again, these aren’t end-all be-all questions. There’s a good chance 1 or 2 of them might not apply to the story you’re telling. But the answers to most of these questions should exist, even if I’m never going to specifically spell them out in my story.

Y’see, Timmy, if I can answer all of these... look at what I’ve got. It means I’ve got characters. I’ve got an established norm. I’ve got an inciting incident. I’ve got goals and motivations and obstacles. And these are the kind of things that form the bare bones of an outline. They should spell out a basic plot and story. If I can answer these, I know I’ve got an actual story.

And if I can’t... well... odds are I’ve got some more work to do.

Hey, speaking of bonus posts, I wanted to toss out something else seasonal on Monday or Tuesday. And then back to our usually scheduled rants on Thursday.

Until then, get back to writing! Go on... write!

Thursday, June 13, 2019

New Challenger Approaching

Y’know, I just noticed that there hasn’t been a single comment here in weeks. Not sure if that’s because more people are leaving comments over on Twitter when I link to these... or if I just haven’t been that interesting.

...let me know down in the comments.

Anyway, I’m a bit short on time—the past few weeks have been a bit crazy for me—but I still wanted to get something up here. And I realized there was a topic I hadn’t talked about in a while. Not in any detail, anyway...

One of the basic parts of storytelling is the obstacle.  It's what stands between my characters and whatever they want. Maybe they want to save the farm, but they’re too far in debt and can’t raise the money in time.  Maybe they want the super-bedazzled mitten, but there’s a big purple guy with his own army who also wants it.  Maybe they just want to ask that cute barista if she’d like to, I don’t know, get some coffee sometime or... no, wait, that’s stupid. Auugggggh, I have to go hide for at least a year. And maybe change my name.

Anyway...

Personally, I think an obstacle’s slightly different from a conflict.  It’s just terminology, yeah, but exterior problems tend to be called obstacles, while interior ones are almost always labeled as conflicts. Captain Marvel wants to save Earth from an alien invasion (obstacle), but first she needs to come to terms with the fact that her adoptive alien race, the Kree, may have been lying to her for years about a lot of stuff (conflict).  See what I mean?

Because of this, I prefer the overall term challenge.  I find that thinking about "obstacles" tends to make me think more about physical things in the way of my heroes, like parts of an obstacle course.  And, again, while this isn't technically wrong, it tends to lead to a lot of the same things in my writing.  This is when I get challenges with more of an episodic, low-end videogame feel to them.  My character defeats obstacle A then moves on to obstacle B, obstacle C and finishes up with D.

So here are a few thoughts about challenges, external and internal, that might be worth thinking about while I’m planning out my story—whether I’m writing a novel, short story, screenplay. or six-part epic somethingorother. I’ve mentioned them once or twice before, so if they sound familiar... good job.  You’ve been paying attention

First Thought-- I must have a challenge
I’m sure we’ve all run into books or movies where people either sit around doing nothing or just meander through events with little to no effort.  If the character needs something, they either already have it in their backpack or it’s in the first box they open. If they need help, people are always  able and willing.  Any lucky break that has to happen does happen just when they need it to.  I know these examples sound silly, but it’s stunning how often I see this happen in screenplays and/or books.

There needs to be something between my characters and their goals.  If there isn't,  they would've accomplished these goals already.  Look. I just got up and made myself a drink. I wanted one. I got it. Heck, if I hadn’t said anything you never would’ve known. That’s just not the stuff we see as bestselling, high-stakes drama.

Second Thought--My characters need a reason to confront said challenge.
If my characters are going to take on a challenge, they need a reason to do it. If I’ve spent the past four days walking through the desert, getting that drink is probably a life-or-death thing for me. Captain Marvel isn’t pursuing the Skrulls as a part time hobby—it’s her sworn duty as an officer of the Kree military. I need to make sure this reason is really there.  It might be clear in my head why the characters are going to undertake a challenge, but is it clear on the page?  This is doubly true for internal things, which can be a lot more subtle depending on what point of view I’m using

Third Thought—My challenge needs a reason to exist.
Like I said right at the start, I need to have some kind of challenge, but I don’t want a challenge that only exists to be a challenge.  It’s got no reason for existing in the world of my  story, no past, no future, no motivation.   It’s only there to serve as an obstacle for the protagonist to overcome.   We can probably all think of a book or movie where, for no reason at all, an obstacle just popped out of nowhere.   That kind of stuff just weakens any story.

Challenges have a purpose.  Whether they’re the driving force behind my story or minor distractions my characters need to deal with quick, they're a kind of antagonist—something or someone working against my heroes. That oasis is the only source of water for a hundred miles in this desert, which is why the people who used to live here set so many guards to protect it. There’s also a reason the Skrulls are on Earth (they’re searching for a hidden lab) and there’s a reason they’re tough to find (they’re shapechangers). I need to think about why a challenge is in my story, and if there isn’t a real reason... maybe re-think it
.
One other note. I think it’s generally better if my audience (reader or viewer) has at least some idea why this challenge exists.  They don’t need to know all the details immediately (or even accurately), but I also shouldn’t be saving them for a last-page reveal.

Fourth Thought—My challenge needs to be daunting.
Not only am I weak from dehydration and facing ten armed guards around the oasis, the actual spring itself is booby-trapped. Someone centuries ago built all sorts of pressure plates around the thing and I’m not exactly in the best condition right now to be tip-toeing and balancing through this spike-launching mine field. Plus, if Captain Marvel can’t find the Skrull agents on Earth, they could establish a foothold here, rebuild their strength, and endanger peace throughout much of the galaxy.

This may be a weird way to look at it, but challenges are things we need to deal with, but we don’t want to deal with. My characters don’t want to deal with this because they don’t even want to be in this situation. I think we can all agree things would be a lot easier if that challenge wasn’t even there.

But it is there, so... goddammit...

Fifth Thought—My challenge can’t be impossible.
Okay, we all write fiction. But even within a fictional world there are things that just can’t happen. Normal people can’t punch out gods or outsmart supercomputers. And if all those guards around the oasis have motion sensors, night vision goggles, and shoot to kill orders, there’s very little I’m going to get—holy crap there’s fifty guards? I thought there were only ten. And when did they all get machine guns?

If you've ever watched a horror movie where the killer is merciless,unstoppable, and inescapable... well, that gets pretty dull after the second or third kill, doesn't it?  One of the reasons Jason Voorhees was scary is that he never ran.  He just sort of... marched? Lumbered?  It always felt like somebody could get away from Jason if they could just go a little faster. If it feels like there’s no chance, it’s not interesting. We already know the outcome.

There are two  other issues with the impossible challenge.  One is if I make my challenge out to be completely impossible and my hero pulls it off anyway, there’s a good chance it’s going to knock my audience out of the story. I’ve just shattered the rules of what’s possible in my story. That usually means it’s “throwing the book across the room” time.

The second issue is when I have challenges that seem impossible to my characters, but have painfully obvious solutions to my readers.  We just don’t like these characters, by nature of their stupidity, and that’s not going to win me any points.

Sixth Thought—Holy crap there are a lot of these
This was supposed to be a quick rehash of an old topic, but I keep finding things I want to add to this. I’ve got editing to do, dammit!

Seventh Thought—My challenge should be unexpected.
This isn’t a hill-I-will-die-on rule... but I’d be willing to fight on that hill for a little while. Once I admit that I need a challenge, it’s kinda the next logical step.

If my heroes are so prepared, so trained and equipped that they’re completely ready for this challenge... well, there isn’t really a challenge, is there? If they’ve covered all the angles, researched every possibility, how can they lose? And if they can’t lose... well, that’s kinda boring, isn’t it? We know the outcome again.

A standard part of so many stories—including Captain Marvel-- is when something changes or goes wrong.  The one thing we didn’t prepare for happens. We learned something new that completely flips our goals and  understanding of the situation.  One way or another, the plan’s shattered into a million pieces. I beat the guards and made it past the booby traps and WHAT? There are albino crocodiles in the oasis? Wait, are these guys actually poachers?

But think about it—when this happens in a story, it’s almost always the moment we love. It’s when my characters get to look good and show how smart or clever or tough they really are.

Eighth and Last Thought--I need to resolve my challenge
Once I’ve set up a challenge, it needs to be resolved somehow. I can’t crouch on a sand dune outside the oasis for five chapters studying the guards and their patrol patterns, then just wander off back into the desert. It leaves a lot of dangling threads and unanswered questions. Who were all those guys? How did they get here? Why did I give up when I desperately needed water?? How did I wander away if I was weak from dehydration? Why did the author spend five chapters on this if I was just going to wander away...?

To paraphrase Chekov, if we see a phaser on the bridge in act one, we need to see it on overload in act three. And then either disarm it or watch it take out the Enterprise. Because if I just leave it there buzzing and getting hotter, readers are going to ask what happened. They remember this stuff.

And they will judge me on it.

Those are my way-too-many thoughts on challenges. Maybe take some time and look at the challenges your own characters are facing. Are there any? Are they challenging enough? Does your character have a desire to avoid them and a need to face them?

Next time, speaking of challenges, I’m going to do something I’ve tried really hard to avoid here for years. I’m going to go negative.

Until then... go write.

Thursday, December 13, 2018

Holiday Triangles

            Well, it’s that time of year again.  Time to cue up that playlist of holiday music and pick out your stack of favorite movies.  Maybe you go a little more unconventional with your choices, maybe you stick to the classics, but whatever your flavor is, I’m sure there’s a lot of them.
            Hell, holiday movies are pretty much a solid, dependable genre at this point.  Just between Hallmark and Netflix, I think there’s forty or fifty new ones just for this year alone.  I worked on one ten years ago and it still gets heavy circulation.  People go nuts about the “plague” of superhero movies, but seriously—Christmas movies are the real machine.
            Anyway...
            We laugh at a lot of these and roll our eyes because they often feature some kind of painful romance.  And that’s what I wanted to talk about.  Where that awkwardness comes from and why these stories kinda keeps us at arms length rather than pulling us in.
            The standard Christmas movie goes something like this.  A young woman (it’s almost always a woman) falls for a guy who’s a few weeks away from getting engaged, married, etc.  The two of them have chemistry, while his girlfriend/ fiancé rages away at her job or as a larval Bridezilla or maybe just as a generally awful, awful person.  Eventually the guy comes to see the error of his ways and our two impossibly good-looking people end up together just in time to kiss on Christmas Eve.
            I’ve talked about this general type of romantic triangle once or thrice before, and before we dive in at might be worth going back and glancing over that real quick—it sums up the ground rules of how and why these triangles work.
            Y’see, there’s a really basic flaw in how a lot of these holiday movies set up that triangle.  It’s why they always come across as a bit weird and the protagonists always seem a bit... well, wrong.  And I think it’s one of those things that’s really easy for me to avoid once I see it all laid out
            Let’s use that basic structure up above for our example.  Our test story, so to speak.  Amy (A) has a meet-cute with Bob (B), who is in a relationship with Kat (C, just to keep you on your toes).  Amy and Bob have chemistry, Kat is bordering on (if not openly) awful and clearly wrong for Bob.  And it’s Christmas because... y’know, that’s when this always seems to happen.
            Now, normally in a romantic triangle situation like this, our protagonist would be Bob.  Bob, after all, is the one who needs to make a choice here, right?  He needs to be active and decide if he wants to be with Amy or Kat.
            But...
            Our protagonist is Amy.  And the only way I can make Amy active in this situation is to make her... well, kinda unlikable.  If she does anything to improve things with Bob—all those standard romance bonding moments like long talks and quiet dinners and heartfelt discussions about shared passions—it kinda means she’s undercutting Bob’s relationship with Kat.  Which is a little rough, morally, no matter what we think of Kat.
            And geeeeez, if things get physical to almost any level, well, now they both look bad.  Amy’s making moves on somebody in a relationship.  Bob’s in a relationship and hooking up with someone else.  I mean, how bad does Kat have to be for us to be cool with Bob cheating on her?  And if she’s not that bad, then... well, yeah, he’s a jerk.
            And, yes—sometimes odd things happen between people in really specific situations.  Everybody reacts differently to stress and fear and all that.  Firm embraces may happen.  Maybe even a kiss or odd proclamation.  But that’s a reeeeeeeeeeeeeeally fine line.  Scary fine.  It’s so easy for that situation to go from understandable and excusable to what-the-hell inappropriate.
            Y’see, Timmy, when Amy’s this point in the triangle, she isn’t the one with a choice to make. Not a real one, anyway. She has two options. She can do nothing (which ends the story pretty quick) or she can try to disrupt Bob and Kat’s relationship. Those are her only paths, as far as our plot goes, and neither of them is a great one from a storytelling point of view.
            I think when writers do this, they’re confusing the outcome with the choices that lead to it. We’ve all heard “the ends justify the means,” but this tends to ignore the fact that the means I use also determine what kind of end I get. There are tons of ways Amy and Bob can end up together, but a lot of them can be paths that make one of them—or both of them—characters we don’t really like or care about. In some cases, we may even be actively rooting against them. Cause they’re horrible people.
           Don’t worry about outcomes. Outcomes are the conclusion of a story.  Think about the path to that outcome. The choices my character has to make in order to get there. 
            Because those choices are my story. They’re my plot.  And if there aren’t any real choices, or they’re all being made by supporting characters, or they’re the wrong kind of choices, or they’re just all bad ones... well...
            I shouldn’t be too shocked if people think it’s a bad story.
            Speaking of stories, here’ s one last reminder that books make fantastic holiday gifts, and to maybe check this out if you're having trouble affording things this year.
            Next time, I wanted to talk a little bit about time.
            Until then, go write.

Wednesday, November 22, 2017

Not-That-Bad Guys

            So very sorry I missed last week.  I’ve been trying to get this draft finished before Thanksgiving and last week just kind of sped by before I realized it.  My apologies.
            Also, thanks to all of you who sent me suggestions for topics. I think the rest of the year is filled up kind of nice, but if you happen to be reading this and still have some things you’d like me to blab about, feel free to mention them below.  I’m always up for more writing-related ideas you’d like to hear about.
            On which note...
            Thanksgiving.  A holiday we in the U.S. equally love and dread.  Love because... well, lots of food, friends, and family.  Maybe some booze and a lot of old black and white movies, or football if that’s your thing.  Perhaps a Twilight Zone marathon.  All wonderful things to enjoy on this feast day of thanks.
            Dread because... okay, let’s be honest.  The in-laws are kind of political zealots.  It’s almost impossible to have any discussion with them that doesn’t hit “those crazy liberals” within five minutes.  Your cousin’s significant other, the would-be-chef, is going to have lots to say about the turkey (and the stuffing, and the pie, and the potatoes, and...).   And if Uncle Randy has a third glass of wine (he says it’s just wine, anyway)... well, that’s when all the dark family secrets start coming out.  Some of them are even true.
            Granted, it’s not like these people are actually evil.  They’re not villains.  Okay, yeah, Uncle Randy had a brief stint in jail but that was over parking tickets (he says he was protesting the state government).  And two-thirds of the sentence was reduced to time served.
            But, seriously, they’re not villains.  They’re not what we’d think of as “bad guys.”  They’re just... kind of annoying.  Closer to obstacles than enemies.
            So let’s talk about antagonists for a few minutes.
            I’ve talked before about bad guys and antagonists.  About how my story often needs someone to oppose my hero or heroine, even if that someone is just standing in for a larger, less defined opponent.  An IRS agent can represent the government.  A junior executive can represent big business.  A doctor can represent a debilitating condition or perhaps even death.
            These people aren’t necessarily villains, though.  They may be working—or seem to be working—against my protagonist, but it’s not like they’re up to some nefarious plot.  Oh, sure, they could be, but in most of these examples, they’re probably just people doing their job.  I’m sure pretty sure most IRS agents aren’t gleeful about telling poverty-stricken people they messed up some forms and owe thousands of dollars.  I have a good friend who’s a doctor, and she’s never mentioned getting overly excited about telling people they’re going to need an organ transplant.
            And yet... we still tend to see these people as a challenge to overcome.  Someone we have to beat or prove wrong.
            This isn’t exactly a unique thing.  Having antagonists who are also (on some level) good people is a very common plot device.  Especially once we bring in police, soldiers, doctors, and even government agencies. Yes, even in this day and age.  So my hero has to deal with antagonists that are basically... well, heroes in their own right.
            For example, let’s take a look at a classic antagonist from one of America’s iconic folk tales, one that’s been produced for film and television.
            Captain Gantu from Lilo & Stitch.
            Gantu (voiced by the super-talented Kevin Michael Richardson—seriously, check out this guy’s resume) is the chief antagonist in the movie.  He imprisons Stitch at the beginning of the movie, tried to ship him off to what amounts to eternal exile on an asteroid, and then—after Stitch escapes—Gantu hunts him down to make sure that sentence is carried out.  Although his attitude at this point could loosely be described as... well, it wouldn’t be stretching things a lot to say “dead or alive.”
            But... is Gantu really a villain?  He is Captain Gantu, after all.  He’s risen through the ranks to be an officer of the Galactic Federation, and he’s the right hand man of the Grand Councilwoman.  When he goes after Stitch, it isn’t a personal vendetta—he’s following his leader’s orders to enforce the law.  Stitch is, after all, a fugitive from justice who’s broken even more laws by escaping to Earth.
            So Gantu’s definitely the antagonist of Lilo & Stitch.  And he’s a bit overzealous, yeah.  Maybe even a bit prejudiced against lab-created life forms.  But he’s not exactly a villain.
            Which means... what, as far as we’re concerned?
            Well, first off, this is an empathy issue.  As the writer, I have to be able to see things from Gantu’s (or Uncle Randy’s) point of view.  There has to be more to them than just “opposed to my protagonist,” especially if they’re not a villain... I might want it to be more on the positive side.  Is my antagonist doing this out of a sense of duty—even a misguided one?  Are they a reluctant antagonist?  Maybe it’s a lesser-of-two-evils situation?
            Keep in mind, this doesn’t have to work both ways.  While my readers need to have some empathy for the antagonist in this case, my antagonist doesn’t necessarily have to have any for my hero.  After all, in their eyes, there’s a good chance my hero is “the villain,” and should be treated as such.
            Second is that these antagonists actually need to be good people. If we find out Gantu’s in charge of the Galactic Federation’s concentration camps, or that the in-laws regularly firebomb Planned Parenthood offices and burn crosses on people’s lawns... well, they really are villains, then.  Again, empathy. If they’re going to be good guys then they need to be good guys.  Their actions may be antagonistic towards my hero or heroine, but it should still be clear to my readers they’re decent people at heart.  At the least, they're just trying to do their jobs.
            Also, something related to keep in mind here—something a writer-friend of mine was recently wrestling with.  If my antagonists are secretly good guys, if this is a twist that comes out somewhere in my third act... well, like any good twist, things still have to line up.  It’s going to be hard to reconcile a last minute “we’re actually the good guys” after 300 pages of murdering innocent bystanders and torturing supporting characters.  If I need my readers to misunderstand the antagonist’s earlier actions... they need to be actions that can be misunderstood.  It’s really tough to come back from shouting a bunch of racist, xenophobic slurs at strangers or shooting schoolteachers in the head.
            Y’see, Timmy, all I have to do is make them good people and have a little empathy.  If I have a real conflict, everything else should fall into place.  Or pretty close into place.
            Assuming I have solid characters.  And an actual plot.  And good dialogue. And... you know.
            Happy Thanksgiving, if you’re here in the states.  Hope tomorrow’s a peaceful and pleasant day for you, wherever you are.
            Next time... a great mystery tip.
            Until then, go write.

Thursday, June 15, 2017

Basic Geometry

            I wanted to blather on about challenges  today. Simple, basic challenges.  Well, a type that should be simple, but still gets messed up sometimes.             
            That challenge is called choice.
            We’ve all used or come across choice.  As I said, it’s probably one of the easiest challenges a writer can create.  Character A has to decide between two options (B and C).  It’s s triangle.
            Sometimes these choices are tough. Sometimes they’re not. Sometimes A is pursuing B, but it’s clear C should be the priority.  Making the decision between B and C provides the conflict, the drama, and maybe even some comedy depending on how it’s done.  There can also be an opportunity for some character growth in there.
            You’ve probably heard of romantic triangles.  It’s one of the most common ones out there.  A is dating B, but then comes to realize C is their real soul mate.  Maybe Dot is engaged to an antagonistic jock, but can’t help falling for the free-spirited caterer.  The standard in most romantic triangles is that B is very clearly not the right person for A, while C is so blatantly right it’s almost frustrating.
            Another common one is “work vs. family.”  Will Wakko choose to spend the weekend with his family or working on the MacGuffin account?  There are a few versions of this.  Sometimes it’s family instead of friends.  It’s usually work on the other leg, but it could be any sort of mild obsession or compulsion.  Am I choosing my best friend or this treasure map?  My pets or my new apartment?
             Triangles are fantastic because they’re a very simple plot and framework that we can all immediately relate to and understand.  They make for easy subplots in novels, and in short stories or screenplays they can almost be the entire story.  This is one of the reasons we keep seeing them again and again and again.
            However...
            Simple as they are, there are still a few basic rules to a triangle.
            Actually, that’s a lie. There’s only one rule.  Triangles are so simple there’s just one rule to making them work.
            We have a triangle because there’s A, B, and C.  Three points.  If I toss out one of these—let’s say B—then I’ve only got two points. That’s a line.  Our structure is just A to C now.   
            Let me expand on the examples above...
            Wakko is so obsessed with landing the MacGuffin account that he misses his daughter’s karate tournament, his son’s piano recital, and the anniversary party his husband arranged for their best friends.  But Wakko keeps at it because this promotion will put him in a key position for the next account, and that’s the big one that’s going to put him in the corner office and change their lives. 
            The stress of all this is too much, though, and Wakko snaps.  He screams at a client.  When he’s called on it, he even yells at his boss and gets fired.  But after a week at home with his kids and husband, he realizes this is where he was supposed to be all along, with his family.  They may not be filthy rich, but the film ends with all of them happy together.
            Or what about this one.  Dot’s a painter-turned-graphic designer engaged to a square-jawed former quarterback turned TV producer. He’s crass, he’s mean to every waiter, and he undresses every woman he meets with his eyes—even when Dot’s right there with him.
            Then she meets their potential caterer, a free spirit who does watercolors and incorporates his talents into his food.  They talk art.  They talk careers.  They have a casual lunch and talk more art.  When Dot comes home early one night and catches her fiancé with his secretary (who he’s decided to marry instead for... reasons), she finds herself calling the caterer.  And suddenly, Dot’s heart is fluttering like it hasn’t in years as she realizes this is the person she’s supposed to be with.
            Do both of those examples feel a little... lacking?
            Y’see, Timmy, what happened in both of them was that character A never really did anything.  Once B was eliminated, there wasn’t anywhere to go, story-wise, except with C.   Character A didn’t make a choice, they just went with what was left. 
            Make sense?
             B and C both have to remain valid choices.  My story has to maintain that triangle up until the moment of choice.  B can still be a bad choice, but A has to actively realize that and then decide to go with C instead.  Once that’s happened, I can get B out of the picture, but not until then.
            If not, ending up with C isn’t a triumph.  It’s a consolation prize.  Which I’d guess isn’t terribly satisfying for C.
            Or for the readers.
            Next time....  Next time’s going to be golden, that I can promise you.
            Until then, go write.

Thursday, April 20, 2017

A Trick in Three Acts

             Very sorry I missed last week.  Last month was copyedits, this time I got layouts back for my next book (Paradox Bound, out this September, available everywhere somewhat-adequate books are sold) and spent my days going through it line by line and making notes.  Far too many notes, if you ask my editor.
            But we’re all here now.  Soooooo... let’s talk about magic tricks.
            Most people tend to think of magic tricks as kind of a bam done thing.  I pull your chosen card out of the deck or out from beneath your drink or out of your own shirt pocket.  I cut the lady in half without killing her.  Then I make the other lady float on air. 
            The truth is, though, well-done magic tricks almost always have a very specific set of steps.  There’s a casual set-up.  There’s a moment of confusion.  And then there’s the big surprise that makes the audience ask “How did you do that?!” 
            Think about it. When I do a card trick, the first part is actually showing you the deck of cards—a totally normal, regular deck of cards, right?  And then, after you pick a card, it vanishes from the deck... waaaaait a minute.  How’d I manage that, right?  And then when I reach over and pull the card out of your sleeve, or point it out sitting face-up under your own drink, right there in front of you the whole time... the crowd goes wild.
            And if you like, you can hear Michael Caine explain all of that in the trailer for a fantastic, underappreciated Christopher Nolan movie.
            So... why are we talking about magic tricks?
            A common term that gets thrown around a lot is three-act structure.  If you’ve been poking at this storytelling thing  for any amount of time, you’ve probably heard it from someone.  Doesn’t matter if you’re working on novels, screenplays, short stories, or even magic tricks—I’d be willing to bet late night Jack-in-the-Box money that you’ve come across this term or had it pushed at you.
            I’m a big believer in three-act structure. I think a good number of flawed stories can tie their problems back to it. Or to a lack of it.
            I also believe three act-structure gets misunderstood a lot.  And I think there are a lot of gurus and producers out there pushing “three act structure” who... well, don’t have any clue what they’re talking about.  We’ll get to that in a little bit.
            Oh, one other thing.  It’s important to note that three-act structure doesn’t really fit in with the other story structures I’ve talked about in the past—linear, dramatic, and narrative.  It’s kind of a different thing in the way a car can be an automatic and a rifle can be an automatic, but they’re not the same kind of automatic.
            Okay, so here we go...
            Any sort of storytelling has a beginning, a middle, and an end. 
            That’s three act structure.
            No, seriously. That’s pretty much it.
            If we want to go into a little more detail... every kind of story needs these three stages.  I’m not talking about page count, but the way my story develops.  If it’s done right, any reader can tell you when these parts begin and end in my story.
            In fiction we can even hang a name on each of these three acts.  We call them establishing the norm, introducing conflict, and then resolution.  You’ve probably heard of these, too.  I’ve talked about them here before, but let’s do a quick sum up.
            Establishing the norm is just that—showing how things normally are.  This is when my characters go to work, pay bills, spend time with their loved ones, and so on. It’s when we often find them at their most relatable.
            Remember that everybody has a “usual day.”  For Rey, a usual day means scavenging parts from middle-of-nowhere wrecks on a middle-of-nowhere planet.   For Steve Rogers, a usual day means going for a morning jog, meeting up with a coworker, and then dealing with some international terrorists who’ve seized a ship on the high seas. If my characters don’t have a normal day, they can’t have an abnormal day, a day when they’re thrown out of their element and have to impress us somehow.
            Introducing conflict means something is knocking my characters out of their comfortable little world and forcing them to take some sort of action.  The new manager says they have to pay all their back rent by the end of the month.  A dying stranger shoves a magic amulet into their hands.  Turns out that one night stand is going to have nine months of consequences followed by eighteen years of repercussions.  Or maybe some little droid shows up claiming it has information it has to get to the resistance, followed by a lot of people with guns who want said droid.
            Note that this can happen more than once in my story.  If my character keeps getting pushed further and further out of his or her comfort zone... that’s great.
            Also worth noting that conflict has to cause, well, conflict.  If I introduce something that doesn’t bother my protagonist, or takes no real effort to deal with... that’s just boring.  If it’s boring to them, it’s going to be boring to my audience.
            Resolution is, big surprise, when things come to an end. Usually because my protagonist has taken some action and made things come to an end.  It’s when answers are made known, hidden things get revealed, and plot threads all come together.
            Word of warning—if I’m submitting to contests or trying to catch the attention of an agent or editor, ending my story with “to be continued” immediately costs me at least twenty points in whatever grading system they’re using (so hope it isn’t a ten-point one).  If I’m doing this, my story doesn’t actually have a resolution.  It might even mean that I—the writer—don’t have a resolution for it.  And since this third step is an important part of the story, well...
            Look if I stop at mixing the cake and don’t take that last step, I can’t be surprised if most people don’t want to eat it, right?
            Or that some of it call it “sludge” instead of “cake”...
            That brings up another point.     Y’see, Timmy, a story that doesn’t have these three parts has a sort of... meandering quality to it.  Characters either do nothing or do tons of stuff without any real motivation to it. 
            This generally comes from writers only having one or two parts of a story.  Maybe they had a great opening and a cool middle, but didn’t quite know how to end it.  Or they came up with a cool opening and a clever end, but never figured out how those two acts would connect.  I’ve even seen a few folks write a very cool opening... and nothing else.  There was a great set up and then the story sort of spiraled off into... nowhere.
            Okay a few last notes. I’ll try to be quick.
            First, there are still a few little caveats to this, of course.   Many stories start in the middle and take a bit before they go back and explain the beginning.  In medias res some folks like to call it.  Other  stories start at the very end, and use the ending as a frame for the whole story. All of this is fine, and I’m sure all of us could list off a ton of great examples of books and movies that do this.
            What we need to remember, though, is all these stories still have a beginning, a middle, and an end, even if they’ve been juggled around a bit in their tellings.  As I’ve mentioned before, the narrative structure of a story doesn’t change the linear structure.  The events have a definitive starting point.  The characters have a baseline the audience sees them at.  There’s a progression brought about by conflict and changes resulting from the conflict.  And it all leads to a definitive conclusion. 
            Like the examples I mentioned above, I’ve seen stories that try to come in on the action, on the conflict. Thing is, they never go back to explain how these events began.  The story’s left flailing without that first act, wondering what set off these events and why the character’s invested in stopping them (or helping them along).
            Second thing, which I promised at the top, is some of the nonsense that gets spread about three act structure.  I see a lot of folks try to argue that all these acts have very specific lengths--you have to be done with this by page sixteen, this must happen by page twenty-three, that must be revealed by page forty-two.  That’s just nonsense, and it’s easy to find hundreds of examples that prove it’s nonsense.
            I think a lot of this comes from people who want to quantify stories somehow.  They want to be able to create a marketable formula of “how to make a bestseller,” and that’s just not possible.  Every story is going to have its own pace, and altering that pace at arbitrary points isn’t going to make it appeal to more people.
            I’ve also seen some people who try to argue for six act structure, seven act structure, or some other number. They justify this by pointing out that television shows often have four or five acts.  Sometimes a teaser and a closing, too.
            I think these arguments come from misunderstanding what three-act structure really is.  These particular gurus are trying to tie it back to those larger, more expansive structures I mentioned earlier.  Television shows do have multiple acts, yes, but that’s structuring for a format, not for a story.  I know a bunch of television writers, and none of them think that their scripts have a beginning, a middle, another middle, one more middle, and then an end.
            Now, all of this leads us to a question some of you have probably been wondering about since I started this little rant.  What’s so important about three-act structure? Why do we need it?
            The big reason is because a beginning, middle, and end in my plot usually means we’ve had character growth in our story.  You may have heard me mention one or thrice that good writing is about good characters.  As readers, we want to see who they start off as, what changes them, and how the change affects them in the long run.  That change is a real response that grew out of his or her experiences. 
            When that happens, readers stop thinking about these creations of mine as characters and start thinking of them as people.
            Next time, since I’ve just waded through a ton of tweaks and edits... I thought we could talk a bit about tweaks and editing.
            Until then, go write.

Friday, May 6, 2016

The Challenge Round!

            Back from Texas Frightmare, where a fantastic time was had by all.  Well, maybe not all, but everyone I talked to seemed to be having a good time.  If one of those folks happened to be you, thanks for stopping by...
            Also worth mentioning—this is post #350 here on the ranty blog.  I’m kind of amazed I’ve managed to come up with this many posts. Even more amazed that so many folks keep reading it.
            So thank you all very, very much.
            But on to today’s (hopefully) helpful rant...
            A basic element of storytelling is the obstacle.  It's what stands between my characters and whatever it is they want.  In The Fold, solving a puzzle for his oldest friend is what stands between Mike and getting back to his normal life.  A lot of time and a whole lot of space stands between astronaut Mark Watney and getting home to Earth.  The monstrous Zoom stands between the Flash and keeping his home city safe, but so does the potential risk of regaining the “speed force” that makes him the fastest man alive.
            Although, seriously... is it just me, or for “the fastest man alive” does Barry run into a lot of people who are faster than him?
            Folks may have different thoughts on this, but—personally—I think an obstacle is slightly different from a conflict.  It’s just terminology, but I’ve noticed that exterior problems tend to be called obstacles a lot of the time, while interior ones are almost always labeled as conflicts.  In that example above Barry has to defend the city and his friends from Zoom (obstacle) but also has to weigh the risk of setting off the particle accelerator again to regain his powers (conflict).  Make sense?
            Now, while in strict literary terms either of these can be correct, I prefer to use the term challenge.  I've found that thinking about “obstacles” tends to guide the mind toward physical impediments, like parts of an obstacle course.  While this isn't technically wrong, it does seem to result in a lot of the same things.  This is when you get challenges that have an episodic feel to them.  Character A defeats obstacle B, then moves on to obstacle C, and finishes up with D.
            Anyway, I’ve gone over it in the past, but I thought it might be useful to go over some tips about challenges.  Some of them you might not have considered before, and a few of them... well, one or two it’s kind of sad that I feel it’s necessary to bring them up.
            For example...

I have to have one.
            Yeah, this sounds basic, I know, but it’s surprising how often I see stories where people either sit around doing nothing or just stroll through events with no worries or effort.  They’re geared up for whatever they might run into, from werewolves to biological warfare.  Anything they don’t have just appears.  Anyone they meet is willing to help.  Any lucky break that has to happen does so at the perfect moment.  I know this sounds silly to most of you, but it’s honestly stunning how often this happens in amateur books and screenplays.  Heck, it’s bothersome how often it happens in professional writing.
            There needs to be something between my characters and their goals, because if there isn't, they would've accomplished these goals already.  If I want a LEGO set, I  can walk up the street to Toys R Us and get one-- that's it.  Not exactly bestseller material, no matter how much pretty language I use.  On the other hand, if I want the Transforming Interlock-Cube Tactical Operating Chestplate that MIT designed for a black-ops branch of the NSA... well, getting that’s probably going to involve getting past fences, computer-locked doors, armed guards, a laser security net, pressure-sensitive floors, a badass female ninja, and that’s before we find out Theodore’s a traitor and he betrays us all (knew we shouldn’t’ve trusted that guy...)
            That’s a story.

My characters need a reason to confront it.
            If my characters are going to take on a challenge, they need a reason to do it.  A real reason.  Watney isn’t alone on Mars growing potatoes as part of a psychology experiment—this is his only real chance at survival.  When things start to go bad at the Albuquerque Door project, Mike doesn’t stick around because he can’t get an Uber to the airport—he stays because the lives of his new friends are at risk.  If Zoom isn’t stopped, he’ll kill thousands of people just to amuse himself.
            Make sure this reason is really there.  It may be obvious in my head why the characters are going to undertake a challenge, but is it that clear on paper?  This is especially true for more internal challenges, where my readers need to see why Mike is so hesitant to use his gifts and why it’s a big deal when he finally embraces them.

I need a reason for it to exist.
            A combination of the first two points.  Nothing’s worse than a challenge that has no reason for existing in the world of the story.  No past, no future, no motivation—it’s just there to be something for the protagonist to overcome.  We can probably all think of a book or movie where an obstacle just popped out of nowhere for no reason at all.  That kind of stuff just weakens any story. 
            Challenges have a purpose.  They're characters in their own right, or maybe obstacles other characters have set in my protagonist's way.  There’s a reason Zoom exists (he was caught in Earth-2’s particle accelerator explosion), and there’s a reason he’s going after the Flash (he needs to absorb speed force to keep himself alive). He didn’t pop through a breach and start tormenting the Flash and company for no reason.  I need to think about why a given challenge is in my story, and if there isn’t a real reason... maybe I should stop for a few minutes and re-think it.
            I’ll add one other note here.  It’s generally better if the audience (reader or viewer) has at least some idea why said challenge exists.  They don’t need to know immediately, but I also shouldn’t save it for the last ten pages... or never reveal it at all and just vaguely hint at it.  “Oh, that demon that’s been hunting us since sundown... it’s probably after me. We’re psychically bonded.  Probably should’ve mentioned that sooner.”

It has to be daunting.
            It’s bad enough Zoom is about ten times faster that the Flash on a good day, but now Barry’s lost his powers altogether.  He can barely sprint across a parking lot.  Voodoo practitioner Kincaid Strange has to risk her career, her freedom, her life, and maybe even her immortal soul to figure out who raised an impossible zombie in her city.  If the Avengers don’t stop Ultron, it’s going to cause an extinction-level event and wipe out all life on Earth.  This is something I mentioned a few weeks ago—the stakes.
            Characters should never want to deal with a challenge, because let's be honest-- we'd all love it if more things were just handed to us.  Again, getting LEGO vs. getting the TICTOC.  A challenge needs to be something that gives the character (and the audience) pause, or else it isn't really a challenge.  Tony Stark has built a suit of armor that can take on armies, and an even bigger suit of armor that goes over that one, but he still feels his bladder tremble when he realizes he just got the Hulk angry.

It can’t be impossible.
            There’s nothing worse than being on the wrong side of a sure thing.  Nobody reading this wants to get in a fist fight with Dwayne “The Rock” Johnson because we all know it’d be no contest.  None of us want to be given the responsibility of stopping a runaway asteroid or even just a runaway bus, because I’m willing to bet for all of us here (myself included) those would be things we just couldn’t deal with.
            If you’ve ever watched any sporting event, you’ve probably noticed they're more or less evenly matched.  The Red Sox don’t play against little league.  NFL teams don't face off against pee-wee football teams.  The most boring stories tend to be the ones where the heroes have no chance whatsoever of meeting the challenge.  Torture porn or Ju-On horror are great examples of this.  They’re great for a bit of squeamishness or a few jumps, but we can’t get invested when we already know the outcome.  I recently recalled someone theorizing that zombies are so popular because zombies are the monsters we can beat. Werewolves, vampires, demons, kaiju—if these attack, we’re just screwed.  They’re too far past us.  But I’m willing to bet everyone reading this has something within ten feet of them that they could take out a zombie with.
            As long as it’s just one zombie.  Maybe two or three...
            The other risk to be careful of here is if the challenge is completely impossible and my hero pulls it off anyway, it can look unbelievable and knock my reader out of the story.
            Actually, one last thing.  The challenge can’t seem impossible to the character, but have a painfully obvious solution to the reader.  My readers have to identify with my characters, and this kind of thing makes my characters unlikable by nature of their stupidity. That’s not going to win anybody points.

It should be unexpected.
            This isn’t an absolute rule, but it’s something I still lean heavily toward. 
            If there’s a challenge and my characters know about it, then that challenge immediately loses some of its strength.  If they have time to plan or prepare or equip themselves, the challenge shrinks accordingly.
            Consider this—every heist movie involves an enormous challenge—usually getting past security to break into a vault or museum.  There are many chapters or scenes of preparation.  Then, almost without exception, in the middle of pulling the job, something happens that the heroes aren’t prepared to deal with.  A new set of guards, new security equipment, or just that bastard Theodore betraying us and setting off the alarms in the elevator shaft.   This is where the story gets exciting.  If my heroes are so trained  and ready for anything that the job goes off without a single hitch, then there really wasn’t a challenge, was there?
            A bonus of the unexpected challenge is that it often gives my characters a chance to look better.  When they beat the unexpected challenge through sheer skill or cleverness, it makes them all the more likeable.  Because my readers are going to identify with them, and most readers like identifying with skillful, clever people

I need to resolve it. 
            Once I’ve set up a challenge, the readers need to see it resolved somehow.  We can’t set Zoom loose on Earth-2 and then just forget about him.  Once Mike realizes what’s going on with the Albuquerque Door, he doesn’t wash his hands and walk away.  I can’t have my hero pining over their lost love for the first third of my story and then never, ever address those feelings again.  Believe me, readers will remember these things.  Once I present a challenge to the audience it can’t be forgotten or ignored.  As Chekhov once said, if we see a phaser on the bridge in act one, we need to see it fire in act three.

            So make sure the challenges in your writing really are challenging, for the characters and for your audience.
            Next week—I’ve been going over a lot of general story stuff for a while, so I thought I’d take a few minutes to go over some things aimed more at the big screen.
            Until then... go write.