Let’s start with a question. I’m guessing most of you have read a Sherlock Holmes story or three, yes? Seems like everyone ends up going through the first dozen cases or so at some point in their lives. So let me ask you something about them.

Why did Doctor Watson live with Sherlock Holmes?

No worries if you don’t know. I want to talk about the answer a bit. Truth is, this is a trick question because there’s two very different answers.

One answer is that Watson moved in with Holmes because he’d just returned from abroad (Watson was a retired soldier and battlefield medic, as some of you may know) and, well, he needed to find an apartment in London. A friend put him in contact with Sherlock Holmes, who needed a roommate, and the two found each other agreeable enough and bam, a legendary duo was born.

But…

Watson also moved in with Holmes because Arthur Conan Doyle (still a few years out from being “Sir”) needed a reason to explain why the two of them were always together. Since Watson was going to be narrating these stories, it gave him an excuse to be there when Homes had a third-pipe breakthrough. When Holmes woke up early with a solution, Watson was just in the other room. This meant Doyle didn’t need any odd additional exposition to explain how/why Watson knew things he otherwise wouldn’t be present for. He was an active witness for everything.

Now, I chose this particular example for a reason. There’s a pair of terms that’ve been drifting around for a while– Watsonian and Doylist (or sometimes Doylistic). Essentially, they refer to the different reasons things happen in a story. On one level, they happen because the characters are responding to plot events, making decisions and being active participants in the story. But on another level, things happen because I—the author—have structured and plotted the story in such a way that it passes information to the reader and gets certain specific reactions from said reader.

Let’s pick apart the first few chapters of one my recent books– The Broken Room. I want to talk about meeting Hector and what happens in the bar. And why it happens.

When we meet Hector it’s mid-afternoon and he’s already had a few drinks because he’s a guy with a lot of regrets and guilt he’s trying to forget. He’s chosen this particular dive bar for safety/security reasons, because Hector’s trying very hard to live off the grid, but old habits die hard. Especially when you’ve maybe got good reason to be cautious. When little Natalie walks up and starts talking to him, he’s immediately suspicious of who she is why she’s here because… well, nobody should know him (see all those previous points). When he realizes she’s at least somewhat on the level, and hasn’t eaten in a few days, he orders her some food because he’s a halfway decent guy. And when the men show up to claim her, Hector’s gut reaction is not to trust said guys (again, see above). Then there’s a moment where Hector’s weighing his own desire/ need to stay under the radar against… well, two guys harassing a little girl. And then he beats the crap out of said guys very quickly and efficiently, because that’s how Hector was trained to deal with problems.

All good in-character, in-world stuff, yes?

Now, on my side of things… I began with Hector half-drunk in a dive bar in the middle of the day because it immediately tells you he’s a bit of a burnout. Right there on page one. But there’s also all these little hints about the kind of person he is as we’re giving a description of his average morning and his tactical analysis of the bar. It’s the kind of stuff that makes the reader intrigued about who he is (or was). When Natalie shows up, it’s more analysis, we’re getting a stronger sense of who Hector is and how he views the world. And again—it’s intriguing. We’re immediately understand this guy comes with a lot of backstory. Getting Natalie some food is basically a “save the cat” moment. It’s him doing something decent early on that he didn’t need to do, reinforcing in the reader’s mind that Hector’s a good man. Finally, when the two men in suits show up, it’s Hector’s big moment. Now he’s given a chance to step away and go back to his normal life and instead he’s making an active decision to become part of the plot.

There’s two and a half chapters roughly broken down for you. The Watsonian reason why Hector is doing things. The Doylist reason he’s doing things.

When I’m reading something (or maybe watching something) that’s just not working for me, one thing I ask myself is what is the storyteller trying to do here? What reaction is this chapter/ scene/ interaction/ line supposed to get from me? What information is it trying to get across?

I think it’s important to be able to answer these questions. Last time I talked about how it’s fine to break the rules as long as you have an actual reason for breaking them. This is kind of the same thing. If I want to do a weird structure or have a horrible protagonist or an odd way of doing dialogue, that’s cool. There are a bunch of stories out there that went against the norm and did some amazing things.

But…

There’s also a lot of stories out there that went against the norm and did… well, nothing. They end up being boring, erratic, confusing, or just plain bad. And I think it’s because those storytellers didn’t know why they were doing things. Their only reason was… they wanted to? They saw someone else do it in a book and just decided to do it in their own completely different book. They just… thought it’d be cool because they were doing something different?

Y’see, Timmy, I need to know why my characters are doing things, and their reason for doing things need to make sense, on some level. But this also holds for me as the author, I need to know why I’m doing things with my story. What I’m hoping to accomplish. How I expect my readers will receive this structure, that format, those creative choices.

And like most things in life, if I’m just doing it to be cool… it’s probably not going to be cool.

Next time, tis the season and all, so I thought I’d talk about Leatherface, UberJason, and Frankenstein.

Until then, go write.

September 27, 2018 / 1 Comment

Elementary

            Many thanks to all of you who tossed some new topic ideas at me (here and on Twitter).  I think this might fill up all the slots I had for the rest of the year.  I may even take some time to rethink my upcoming plans.

            Anyway, for now, the potential Sherlock Holmes idea stuck in my head, so let me babble about that for a minute or three.

            There’s a pair of terms that have been floating around for a bit now—Watsonian and Doylist.  On the off chance you don’t get the reference, the terms come from Dr. John (or Joan) Watson, constant companion to Sherlock Holmes, and also to their creator, Sir Arthur Conan Doyle.  When we use these terms, we’re saying there’s two ways to look at any story element.  The in-story reason for this happening, and the author’s reason for this happening.  They’re often very different, but they’re both very important.

            For example…
            Why did Sherlock Holmes die in “The Final Problem,” plunging to his death at Reichenbach Falls?  Well, from Watson’s point of view, Holmes sacrificed himself because it was the only way to stop Moriarty.  The two evenly-matched men fight, and while Holmes dies, Moriarty’s now-leaderless criminal empire will crumble.  A net win for society. 
            From Doyle’s point of view, though, he was just sick of writing Sherlock Holmes stories.  He was making money off them, yeah, but he wanted to move on and start writing more serious, important stuff about, well… ghosts and fairies.  No, seriously.  So he killed Holmes off and tried (unsuccessfully) to move on.
            Yeah, don’t be the person pointing out Doyle later retconned the death.  When he wrote this story, Holmes was dead.  Toast.  Joined the choir invisible.
            Of course, this principal doesn’t just apply to Sherlock Holmes stories.  If you look at most stories, the elements break down into these two categories.
            –Whydid Han Solo get frozen in carbonite?  The Watsonian reason is that Vader wanted to test the carbon-freezing process and Boba Fett wanted to collect on Solo’s sizeable bounty.  The Doylist reason is that Harrison Ford wasn’t sure he wanted to come back to play Solo again, so George Lucas needed an ending that could explain Solo’s potential absence but also contain the possibility of bringing him back.
            –Whydid the Twelfth Doctor regenerate?  Watsonian reason—he was shot by the Cybermen and managed to hold off his regeneration briefly before transforming into the Thirteenth Doctor.  Doylist—Peter Capaldi was leaving the series, as was showrunner Stephen Moffat, and the new team decided to cast Jodie Whittaker.
            Here’s one of my own—Whydoes Ex-Patriots begin with a Fourth of July fireworks show?  Well, from a Watsonian point of view, the citizens of the Mount are celebrating.  It’s the Fourth, but it’s also one of their first major holidays since things have (for them) kinda stabilized after the zombocalypse.  So they’re partying hard.
            From a Doylist point of view, though… this opening lets me start with action.  There’s a lot going on.  It gives me a chance to re-introduce our four main heroes. It also lets be immediately bring up the idea of nations and patriotism, which are key themes in the book.  Heck, because this was one of those very rare times where I knewthere’d be another book in the series, this was also a setup for a plot thread in Ex-Communication.
            This all makes sense, yes?
            Why are we talking about it?
            I think it’s really important to remember these distinctions when we’re talking about writing.  To be more specific, when we’re talking about aspects of writing.  If we’re discussing dialogue or characters or settings, we should be clear if this is an in-world discussion or an authorial discussion.  Are we talking about things as they relate to the characters, or as they relate to the author (and the audience)?
            “Authorial”?   Ooooh, don’t I sound all clever…
            For example, once or thrice I’ve mentioned my belief that all good, successful characters have three common traits—they’re believable, they’re relatable, and they’re likable.  But I’ve seen some pushback on this.  I’ve had people online and in person argue that characters don’t need to be likable.  Characters just need to be fascinating or compelling or… well, look.  They don’t need to be likable.
            Here’s the thing.  In a Watsonian sense—I agree with this.  I mean, I’ve said this myself lots of times (pretty much every time I talk about these traits).  Likable doesn’t mean we want a character to marry into our family and they always have a kind word to say.  Within the story, there are tons of popular protagonists who aren’t remotely likable.  Who are kind of awful, really.  There’s not a version of Hannibal Lecter—books, movies, or television—that most of us would want to have a private dinner with.  We probably couldn’t count the number of books and movies that have hit men or assassins as their main characters.  And to bring us back around, most modern interpretations of Sherlock Holmes rightly point out that the guy’s an abrasive, condescending ass. 
            (…and that’s with the people he likes.)
            But in a Doylist sense, viewed from outside… we kinda like these people.  We admire Lecter’s twisted ethics.  We envy the ultra-competent man or woman of action.  And it’s kind of pleasant to watch Holmes point out what’s sitting right in front of everyone’s face.  That separation of fiction, the thin sheath that keeps us from absolutely immersing into the story, lets us enjoy these characters in ways we couldn’t in real life.
            I mean if we didn’t like them as readers, why would we keep reading about them?  Who’d torture themselves like that.  Hell, why would we keep writingabout them if we didn’t like them?  I can’t imagine sitting down and working for months on a story about a character I didn’t enjoy on some level.

            This holds for so a lot of aspects of writing.  I’ve mentioned before that realistic dialogue in fiction is different from the actual conversations we have with each other in the real world.  Other characters might not get my protagonist, but the reader should be able to relate to them.  And I’m never going to be able build any sort of tension if I don’t understand the difference between what my readers know and what my character knows.

            Y’see, Timmy, when I’m taking in advice I need to be clear if we’re talking about things in a Watsonian or Doylist sense.  And when I see advice from other writers, I should stop and think about how they mean it.  Are they talking about the actual pace of events in the timeline of the story, or the pacing in the narrative?  Are they talking about the motives of the characters or the writer?
            In the future, I’m going to try to be better about this, too.
            Next time…
            Well, thanks to some of you, I’ve got next time all planed out in advance.
            Until then… go write.
August 19, 2011 / 1 Comment

Stop Me If You’ve Heard This One…

My apologies for not posting anything last week and being late this week. To be honest, I was so wrapped up in the new draft of this book I forgot what day it was. Soon the fall season will start back up and I’ll be able to tell where we are in the week by episodes of Fringe and Castle.

Anyway, there was a suggestion for a topic and it got me thinking about something funny…

A joke is a great diagram for a story, because all good stories have a setup and a punchline. Not in the sense of evoking laughter, but in the sense of that one beat near the end that strikes a chord and gives you a little rush. In jokes and stories, you have a setup and a payoff. For example…

A nun, a priest, and a rabbi walk into a bar. The bartender looks up and says “What is this, a joke?”

It’s very short, but it does the job. It’s just setup, payoff, done. That first sentence is the setup. To be exact, it’s a type of setup we’ve all heard a dozen or more times, which is what makes the second sentence (the payoff) funny. Adding in other elements would just slow the story—the joke—and probably detract from the punchline.

Now, let’s take this a step further. Has someone ever told you a longer joke, maybe one that took a minute or three to tell? If they knew how to tell it, odds are you chuckled a couple times during the setup, yes?

In this case it’s not just the A-B of that first joke. We’ve got A-B-C-D and then the payoff of E at the end (E is for end, after all). There’s enough space to work with for B and C to be a bit funny themselves and get that extra chuckle before the punchline.

Here’s the thing to keep in mind, though. B and C are still serving the greater payoff of E—the greater good, if you will. They aren’t filler or random asides. Even though they get a laugh of their own, they’re necessary steps on the way to the punchline.

This is a lot like your standard short story. Most of them really just have one big payoff and that’s it. Think of some of the collected stories in Isaac Asimov’s I, Robot or most of the classic Sherlock Holmes tales by Arthur Conan Doyle. The characters set out to accomplish goal A and by the end of the story they’ve done it. Or, in a few rare cases— “Evidence” and “A Scandal in Bohemia” come to mind—they admit they haven’t.

Even though they’re two hours long, most feature-length scripts tend to have more in common with short stories than books. In fact, if you talk to lots of screenwriters, they’ll tell you it’s always easier to adapt a short story than a novel. Most of us have read a short story and thought it would be fun to see more of him or learn about her backstory and maybe get a better sense of what happened there. That’s the stuff which is great to expand on in a screenplay. If you look at most films, you’ll see that they’re still a pretty straight line from A to E (or maybe up to J with the expansion). You may have heard some guru-types calling this the through-line. It’s how you make way through a story (or a joke) without any odd segues.

Look at the first Pirates of the Caribbean movie. There’s one main story—catch the Black Pearl, stop Barbossa—which is made up of two side-by-side stories (arguably three). Despite this, though, each one of these elements has a very simple and clean A-B-C-D story. Will just wants to rescue Elizabeth, and all of his scenes reflect that. Jack just wants to reclaim the Black Pearl and sail free, and all his scenes reflect that.

Also, as I mentioned above, adding in unnecessary clutter would just slow the story—either the individual element or the film as a whole—so there isn’t any. Will never has a segue where he rescues puppies from a burning building or decides he needs to learn karate to rescue Elizabeth. Jack seems very scattered at first, but as the movie goes on it becomes clear how sharp and how focused he really is. Every scene in the film, no matter which thread it’s part of, is leading us to the same big payoff.

Let’s go another order of magnitude bigger and consider novels. The average novel’s going to be six or eight times the word count of most screenplays. It’s where the writer’s got time and space to go all out. We’ve now got A through Z. Maybe it’s even looping around to something like A through AF or something. The writer has a little more space to wander down those paths or maybe take the scenic route to their destination.

Good analogy, that one. Remember that when you take the scenic route, as a writer, you still need to get where you’re going. When you go down a random road for no reason it doesn’t matter how pretty the foliage is at this time of year. If there was no purpose to it you weren’t on the scenic route—you were lost. It’s cool that you enjoyed being lost and you got some nice pictures, but not everyone’s going to feel that way. A lot of folks are just going to see four hours of driving time they lost.

So even in a book, with all that extra space for plot and characters, you need to be aiming for that big punchline. Each of those smaller elements that got a chuckle are expected to get a full laugh on their own now, but they’re also still expected to serve the greater good. Remember, you don’t want to drop 4-5-6 in the middle of H-I-J-K-L.

Here’s another tip. Have you ever heard the term “episodic” used to describe something. Yes, television, of course, but there’s a reason for that. When something is episodic, the setups and payoffs come one after another. A is the setup for B, C is the setup for D, E is the setup for F, and so on. Think of older videogames where you’d move from one level to the next. New problem, solved, next problem. You rarely got a sense of the big story because nothing carried over. That’s what episodic writing does–it presents challenges that are immediately dealt with, so the story feels more like individual episodes than a coherent whole. To use our joke analogy, it’s the difference between a two hour stand-up routine and a two hour comedy movie.

If your story involves multiple setups and payoffs, take a second look at where they fall. Make sure they’re spread out, and make sure they’re all leading somewhere. Hopefully the same somewhere.

Finally, here’s a little exercise for you. Yep, there’s homework. I’m sure at some point in your life you’ve had to listen to someone who didn’t know how to tell a joke. So ask yourself—what did they do wrong? Was it their pacing? Did they give away the punchline to soon? ‘Cause the real trick to telling a good joke is being able to tell a good story. If you don’t know why they did it wrong… are you sure you aren’t?

Next week, why you should never carry just a screwdriver.

Unless you’re the Doctor, of course…

Until then, go write.

January 9, 2010 / 2 Comments

The First Rule of Fight Club

Starting the year off late, which doesn’t set a good precedent, but also with a surprisingly clever pop-culture reference (as you’ll come to see), which does. If you don’t know the reference… go. Just go. I’m not joking, please leave now.

All those wanna-bes and posers gone?
Good. So, I figured I’d start by ranting about something I see crop up more and more in fiction. Would-be screenwriters, this week might be a bit thin for you, but if you follow along, who knows, I may say something clever.
Anyway, there’s a fiction writer (and sometimes writing coach) named Damon Knight who points out that first person is really a bit of a trap. A lot of people use it because they think it makes their story more personal, more realistic, and easier to get into. It also creates an instant character in the story—the narrator.
Truth is, though, first person is one of the most difficult tenses to write well. It isn’t personal, it isn’t realistic, and it makes it extremely difficult to create a character. I mean if it’s so easy, why aren’t the so-called hacks like Stephen King or Dean Koontz using it more often? Oh, sure, King’s written a few first person short stories, a novella or two, but the vast majority of his work is plain old third person perspective.
The reasons first person is so tough are kind of invisible, which is why it’s a trap. They’re things that make perfect sense when they get pointed out, but until then… well, it’s easy to wander in, set off a dozen tripwires, step into the beam of light, and suddenly you’re at the bottom of a deep hole. Hopefully not one filled with stakes.
To be clear, I’m not saying first person is a bad tense to write a story in. Far from it. Some of my favorite stories are written from this perspective, and it is some gorgeous, genius writing. It’s definitely not an easy viewpoint, though. Even experienced writers will run into a lot of problems with it, and inexperienced writers will often hit them at terminal velocity.
Here are a couple of those hidden problems. If you’ve got a first person story, you may want to take a glance through and make sure it doesn’t suffer from any of them.

The first problem is suspense and tension. You’ve probably heard this one before, because it’s one of the first issues that needs to be addressed in a story with this perspective. Any story has to have a degree of conflict and tension, but in a first person story a thick layer of that tension is scraped off the top because of the format. If we’re only halfway through the book, we know there has to be more than the narrator’s tale than just getting the girl. We also know the main character isn’t going to be killed in a first person tale because… well, they’re telling us the story.
Yeah, there’ve been a couple clever stories that have gotten around this roadblock, but they usually do it with a bit of a cop out. At this point, enough stories have revealed their first-person character is a ghost, angel, vampire, or some such thing that this reveal is probably just going to frustrate or bore readers more than anything else.
From this angle, writing in first person just drives us into a corner.

Next, first person is a very limited viewpoint. The reader can only see, hear, and experience things the main character does. We never get to see the other side of the door and we have no idea what happens to Wakko when he leaves the room. We don’t get the suspense of us knowing something’s happening that the character doesn’t know about. This also means we can’t be privy to extra detail, nor can we have any doubt if something did or didn’t register with the main character.
By its very nature, this also requires most first person stories to be told from a very “average-man” level. If the character is too smart and figures things out too fast, it kills the story. If said character is rock-stupid and can’t solve a single problem, it kills the story and frustrates the reader. Consider that Sir Arthur Conan Doyle’s detective stories are told in first person, but not by Holmes. They’re told by Watson, a very smart and able doctor–but nowhere near the range of his best friend.
So, from this angle, writing in first person drives us into another corner. A different corner, yes, but a corner nonetheless.

Another problem that relates back to viewpoint is that you can’t have forward motion in your story without action, and the common way action grinds to a halt is when the writer stops for description. I mentioned a while back that the problem with pausing to describe details about the main character‘s height, weight, eye and hair color, shoe size, skin tone, education, and preferred underwear color (sorry Facebook folks) is that everything comes to a halt while we do.
This kind of gear-grinding stop is bad enough in a regular story, but in a first person story what’s the only way we can get this description? That’s right– if the main character starts talking about themselves. And what would you think of me if I spent the next ten or fifteen minutes talking about my chiseled abs, broad shoulders, or rock hard glutes (all of which, I can assure you, are a complete fabrication).
So in a first person story, this kind of description brings the story to a halt and it makes your main character look more than a bit egotistical. What kind of woman writes two pages in her diary about how hot she is? How much of a ninja are you if you pause to admire your posture and build in a convenient mirror?
Heck, imagine how awkward this would seem in a horror or adventure story? I open the door to reveal the armed terrorist/ hungry zombie/ angry ninja and I pause to describe them as they’re leaping at me. The thing is, we see a lot faster than we can write or read. My first person character may register a lot of details, but it’s a very tricky balance leaving those details in or out during moments of action. I can notice the ninja is a woman with green eyes and a wisp of red hair peeking out of her hood, but if I pause to say that it seems that she’s just standing there in a very un-ninja-ish way. If I describe her afterwards, I now have to pause and refer back to something the character actually saw two or three pages back.
And so, here we are, written into a corner again.
For the record, I’ve just decided the word for a female ninja will be ninjette. At least for our purposes here. Just thought I’d get that in writing.
Now, Knight has a nice exercise in his book Creating Short Fiction. What he suggests is to rewrite a few chapters into third person with as few changes as possible. Don’t restructure, don’t add anything– just turn me into him or her. He really suggests rewriting the whole thing, but he’s usually talking about short stories. Twenty or thirty pages will do for most of us here.
Once you’ve done this, re-read your story. If the character you had in first person has vanished, it’s because there wasn’t a character there to start with. Just the illusion of one. If your story vanishes… well, there’s some work to be done. That’s the trick of first person, and why you have to be careful with it. It gives the impression of creating a personality and defining a person, but it rarely does.
This ranty blog (any blog, really) is a great example of a first person trick. I may seem personable, funny, and clever–but do any of you reading this actually know me? Okay, granted, a handful actually do, but I know there’s another, much larger handful that wouldn’t know me if they bumped into me on the street. It feels like you know me, my likes, my dislikes–you may even have an image of me in your head. Once you stop and think about it, though… you really don’t. Try writing down a rough character sketch of me based off the two or twenty times you’ve read something here and you’ll be surprised how little there really is. If I rewrote this post as a third-person column I would vanish altogether.
Which is a great time to wrap this up.
Next week I’d like to take a moment to re-introduce the blog for those who came in late. It’s still early in 2010 and I’ve been at this for almost a year and a half, so it might be good for all of us to recap.
Until then, go write.

Categories