Showing posts with label Perspective characters. Show all posts
Showing posts with label Perspective characters. Show all posts

Friday, February 13, 2015

Reasons To Use Multiple Perspectives In Your Story

We’ve discussed perspective quite thoroughly in previous posts—first-person, third-person limited, and third-person omniscient, as well as a host of perspective errors. But we haven’t much discussed stories with multiple perspective characters, where the narrative jumps from point person’s point-of-view to another’s and back again.

Multiple-perspective stories can be written with any type of perspective, but these days third-person limited is the most common for these types of stories. Third-person omniscient stories are uncommon these days in general because they are difficult to write and to read (though they are all, by definition, multiple-perspective stories). First-person stories, on the other hand, can often be confusing if there is more than one perspective because readers can easily lose track of which narrator is speaking, since all of the narrators simply refer to themselves as “I”.

The number of points-of-view in a multiple-perspective story can vary widely. On one extreme, you have the Harry Potter books, which feature only two or three chapters across seven books from perspectives other than Harry’s. On the other extreme, you have stories like George R. R. Martin’s A Song of Ice and Fire series, which follows dozens of different points-of-view and switches perspective with nearly every chapter.

There is nothing wrong with writing a story from multiple perspectives—if it’s good enough for Homer, Shakespeare, and Tolstoy, then it’s good enough for the rest of us. Keep in mind, however, that writing from multiple perspectives is much more difficult than writing from a single perspective. If you choose to undertake this sort of difficult task, make sure it’s a choice that serves your story. If your story needs multiple perspectives in order to cover all of the plot, then put in multiple perspectives. If you’re only doing it because George R. R. Martin did it, however, then that’s not a good reason.

Here are some reasons a story might need multiple perspectives:

One person can’t be there for the whole story

Take a story like The Empire Strikes Back. At the beginning, the rebels are driven and scattered from their hidden base on Hoth. Luke goes to Dagobah to train with Yoda; Han, Leia, and the others evade the Empire through a strangely-cluttered asteroid field and then flee to Cloud City. Plot happens, and they’re (mostly) reunited at the end.

If Luke were the only perspective character, the audience would miss Han and Leia falling in love, the dark intrigue of their arrival at Cloud City, their capture by Darth Vader, Han being frozen in carbonite, Lando’s change of heart, and Leia and the others’ escape from Cloud City. If Leia were the only perspective character, we would miss Luke’s plot-important training—from Yoda’s reluctance to train him, “Do or do not. There is no try,” Luke’s vision of Vader, lifting the X-wing from the swamp, Luke’s decision to disobey his trainer to go save his friends, all the way to the climactic duel between Luke and Vader and the famous reveal of Vader’s identity. If we were to follow only one perspective character, then we would miss half the plot—therefore, multiple perspectives are needed.

To avoid an overabundance of convenient coincidences (Chosen One Syndrome)

Almost every story from any place or time relies on a certain amount of coincidence. Characters just happen to be in the right place at the right time to overhear just the right conversation, or Luke just happens to crash on Dagobah within walking distance of Yoda’s house—those sorts of things. We all accept a certain amount of implausibility for the sake of story.
But single-perspective stories tend to necessitate more implausible coincidences than do multiple-perspective stories. Look at the Harry Potter novels—across seven books, how many times does Harry conveniently overhear an important conversation that he wasn’t supposed to? How many more do Ron and Hermione happen to hear and relate to him? The sheer amount of coincidence can get to be a little staggering. In a multiple-perspective novel, you can give the audience all of the important plot information that they need without having to get all of that information to a single person.

To avoid boredom (More Chosen One Syndrome)

When plotting a story, it is a good idea to follow the action—show whatever part of the story is most interesting and engaging, and skip over parts that are dull or repetitive. The problem that arises in a single-perspective character is that this means that your single protagonist has to be there for almost every plot-important event or conversation that ever happens. Everything! J.K. Rowling even had to invent the pensieve so that she could have Harry be present for plot-important events that happened before he was even born! (And it was an excellent way to handle this problem, in my opinion.) But not every story can whip out a pensieve when the main character needs to be present for something plot important. More often, they have to rely on yet more convenient coincidences and implausible situations.

When single-perspective stories try to handle this more realistically, the story tends to become less engaging. One of the most common complaints that I’ve heard about Mockingjay (book three of The Hunger Games) is that so much of the actual story happens “off-screen” while Katniss is doing little to nothing on-screen. It was realistic to have her suffering from a PTSD-esque problem; but planning a big, daring mission to finally go save Peeta and then not showing us when it happened? That was disappointing, to say the least.

Multiple-perspective stories can handily side-step this problem. If one character has to drive for three hours before they’ll get to where something interesting will happen, switch to a different character in a more interesting situation. More characters get to share more of the spotlight, and the story will usually be a bit more plausible for it.

To give greater understanding or increase tension

Have you ever read The Wheel of Time? There’s a character named Galad who is in and out of the story throughout the entire fourteen books, and almost everyone hated him. He was cold and strict, a man whose devotion to what he believed was right led him to throw in his lot with dangerous, unthinking zealots. Or at least, that’s what he was for ten books or so. Then, I think in the eleventh book, we were for the first time shown a scene from Galad’s point of view. For many people, it was a revelation. Once we could see things from his perspective, he became sympathetic and understandable. Once scene was enough to make him suddenly likeable for the rest of the series, even when we weren’t in his perspective.

Writing a scene from a character’s perspective is an excellent way to get the audience to understand and sympathize with the character, if that’s what you need. (Or, if they’re despicable enough, it’s a good way to get the audience to quickly dislike or fear the character.)

Multiple perspectives can also increase tension. Show us a scene from a side character’s point of view that reveals that they are a traitor with a plan to bring down the other characters. Bam. All of a sudden, the audience knows that something bad is coming that the main characters don’t. That’s dramatic irony, folks, and it’s a handy tool that is only available in multiple-perspective stories.

So there’s some handy reasons for using multiple points-of-view in a story. Next time, we’ll go over some of the difficulties and hazards to look out for when composing multiple-perspective narratives.





Monday, November 17, 2014

Perspective Errors: Name Placeholders

We’ve previously discussed how to use synonyms to avoid frequent repetition of a single word and the needfor description to remain true to the mindset of the perspective character. Today, we’ll discuss a point at which these two topics intersect.

I mentioned in this post that it is a common and useful practice to refer to a character by a short descriptor in order to avoid repeating their name too often. If you wrote a scene where a detective was interviewing a butcher named Mr. Giacomo, for instance, you might alternately refer to Mr. Giacomo as “the butcher,” “the witness,” or even simply “the man”:

     “What did the assailant look like?” Detective Mullens asked.
     “Well, he was short,” Mr. Giacomo replied. He held out his hand at about the height of his shoulder. “Maybe this tall. He was dressed in black.” The man shrugged. “That was all I could make out.”

However, a problem can arise when referring to characters by these sort of placeholders.

     Piotr did his best not to cry as his mother pulled him into the closet and shut the door behind them. She sat on the floor and pulled him into her lap, stroking his hair.
     “Shhh, you need to be quiet now,” his mother whispered. “We have to stay hidden, all right?”
     Piotr nodded and bit his lip, throwing his arms around his mother’s neck. He was still sniffling, but he held in the tears.
     There was a crash in the room outside. Piotr almost cried out, but his mother hugged him tight against her. He could feel that the woman was holding her breath, and so he did the same, trying to be absolutely silent. They sat in silence, trembling, as the men ransacked the bedroom outside.

The problem in this passage is a small but pervasively common one—it’s the point where Piotr’s mother is referred to as “the woman.”

In this post, we discussed the need for description to match the perspective of the character. In the example above, Piotr is our perspective character. How many children do you know that would ever refer to their mother as “the woman”? While his mother is, of course, a woman, for him to think of her by that term feels very distant and cold. It feels out of character.

"I love my mother, but the woman wouldn't let me have ice cream for dessert."
See how off that feels? This kid is either a brat or not being written well.

It wasn’t a problem for Detective Mullens to think of Mr. Giacomo as “the man” because the two of them barely knew each other—their relationship is not at all close or caring.  But Piotr and his mother are too close for that.

This problem sometimes arises in the works of authors for whom English is a second language. In many other languages, referring to someone as “man” or “woman” is normal and carries no connotation of emotional distance. In English, however, it does; so watch out for this.


If you use a name placeholder, make sure that it is a word that fits the relationship between the character and the perspective character.

Friday, October 17, 2014

Description and Degrees of Familiarity, Part Two

In the last post, we discussed how detailed description can be used to demonstrate that a character is unfamiliar with an object; we also covered how to describe objects that are unfamiliar to the reader but familiar to the character. Today, we’ll discuss two other reasons to dwell longer on description than you otherwise might.

When the character is intensely familiar with a type of object


Compare these three examples:

     Xin looked out the window. There was a red car parked outside; she couldn’t see the driver. Strangely, a bone-mouth Shar-pei sat on the hood of the car, watching her window. Its fur was a deep blue-black, and it was taller than any other Shar-pei she’d ever seen, maybe as tall as seventy centimeters. Its ears and tail were also usually long; it couldn’t have been a pure-bred.
     The dog barked suddenly, and the door of the car opened. A pale man in a dark suit and sunglasses climbed out, turning his gaze on her window. Xin ducked out of sight.

     Xin looked out the window. There was a red car parked outside; she couldn’t see the driver. Strangely, a black dog sat on the hood of the car, watching her window. It barked.
     The door of the car opened, and a pale man climbed out. He wore a black silk tangzhuang coat with gold snakes embroidered along the cuffs up to the elbows and around the stiff collar. His eyes were hidden by a pair of dark metal-framed sunglasses; Xin couldn’t see what brand they were from here, but she could tell they were expensive—not the cheap knock-offs most people bought on the street. The man turned his gaze on her window, and she ducked out of sight.

     Xin looked out the window. A red Lamborghini was parked outside, a Gallardo LP 550 that looked like its suspension system had been upgraded. A pair of holes on the rear of the car indicated that the car had once had a heavy spoiler attached; based on the marred paint, it had been torn free violently.
     Strangely, a black dog sat on the hood of the Lamborghini, watching her window. It barked, and the door of the car opened. A pale man in a dark suit and sunglasses climbed out, turning his gaze on her window. Xin ducked out of sight.

Sorry, you'll have to settle for just the car. Can you believe that I couldn't find a single image of a red Lamborhini Gallardo LP 550 parked on the side of a Chinese street with a black bone-mouth Shar-pei sitting on top and a driver in a gold-embroidered black tangzhuang and dark sunglasses? The internet has failed me. 

In each of these examples, Xin is a slightly different person, isn’t she? The first Xin clearly knows a thing or two about dogs, the second has a trained eye for clothing, while the last really knows her way around a car. And yet the only thing that changed was what object in the scene the writer chose to describe in greater detail. A person who is an expert in something—be it cars, dogs, clothing, guns, spaceships, a certain culture, or whatever—will discuss and observe that thing with a level of specificity that someone who is unfamiliar with the topic cannot.

Here’s a few things to keep in mind when showing familiarity through description:

Use specific terms. The first major difference between unfamiliar description and expert description is terminology. Someone who is completely unfamiliar with cars would describe one in very basic terms—large, loud, wheeled, shiny, fast, and so on. Someone who is an expert on cars will have a command of specific terms gained through years of study and osmosis—brand names, car models, engine types, and so on.

Make comparisons. The second major difference between unfamiliar description and expert description is that someone who is an expert on a type of object has a vast mental catalog of similar objects to which they can compare the one you’re describing. For instance, when our first Xin was describing the dog, she immediately noted the ways that this Shar-pei was different from others and concluded that it wasn’t pure-bred.

Keep it understandable to the reader. Using extremely specific terms can often be confusing to the reader. For instance, how many of you know what a “bone-mouth” Shar-pei is? I didn’t, before I wrote that example. I certainly couldn’t have identified a Lamborghini Gallardo LP 550 from any other Lamborghini, either. These specific terms add to the sense that the character knows what she’s talking about, but they don’t necessarily help the reader picture the object. You need to strike a balance between specific, in-depth terms and description that will be useful to the reader. For instance, the tangzhuang coat from the second example. Technically, the word “coat” is redundant—a tangzhuang is a style of coat and wouldn’t refer to a different style of clothing—but I included the word to help readers better picture the clothing. I also used the description of the embroidery to sneak in the fact that the coat had long sleeves and a stiff collar, so that the readers could get an idea of what a tangzhuang looked like without my needing to break perspective.

Don’t let the description get out of control. Xin number three was familiar with cars, so it was natural for her to notice several details about the Lamborghini but few about the dog or the man. However, it would be very easy for that level of familiarity to swell to unnatural levels. For instance:

     “When was the last time you saw Li?” the man asked.
     Xin thought for a moment. She couldn’t remember seeing Li since she’d dropped him off at work the day before in her 2013 Volkswagen Santana.

That was a little ridiculous, don’t you agree? The line should have simply ended after the word before. “She couldn’t remember seeing Li since she’d dropped him off at work the day before.” Just because a character is familiar with something doesn’t mean you need to shoehorn that familiarity in at every opportunity. Keep it real.

This is particularly common when the character’s familiarity with a certain type of object is one that the author shares. An author who is an expert on horses, for instance, might want to show that off at every opportunity in a story. Tone it back—give the readers enough to realize that the character (and by extension, you) knows what she’s talking about. Don’t shove it down their throats.

Another version of this problem is when every single character is inexplicably familiar with something that the author knows well. It’s fine to have a lot of characters who can identify a hint of saffron or rosemary from just a whiff of the dinner they’re about to eat, but not every character should be able to. To some people, it will just be a nice-smelling dinner.

When you just want to describe something


Our final reason for including in-depth description for something is the simplest, but the easiest to let get out of control: you just want to. Maybe you have a really vivid image of what a certain boat looks like, or you really feel like dwelling on the battered-up appearance of a character’s trenchcoat. Sometimes, you’ll just want to describe something. And that’s fine—go for it. Just be sure to follow the advice from this post; write the description, ask a lot of people to read it and tell you if it’s too much, and then pare it back if most of them say it is. And sometimes, if you really love that description, well . . . you’ll just have to hope you can find an editor who loves it as much as you do. Good luck!

Wednesday, October 15, 2014

Description and Degrees of Familiarity, Part One

Today we’re going to return to an example that I gave in the Writing Spicy Description post:

Don’t use two words where one will suffice: I once edited a story where a character approached a sea where “along the shore was a row of several straight wooden walkways that jutted out into the ocean, held up by thick pylons sticking up out of the water.” I edited this to say, “Along the shore was a row of wooden docks.” So that you don’t have to count for yourself, that’s nineteen fewer words. Everyone does this, at some point—I’ve done it myself. Always look for the shortest, most descriptive word possible.

This is generally good advice, but it’s not universally applicable. Let’s delve a little deeper into a few situations where you might want to say more than just “a row of wooden docks.”

When the perspective character is unfamiliar with an object



     Juba scuttled through a field of tall, thin plants. The tops of the plants were wider than their stalks and waved in the breeze.  They rasped against his carapace, far drier than any of the plant life on his planet.
     The field ended suddenly at a wide pathway of some black, rock-like material. More of the tall plants waved on the other side of the path, but the path itself ran to the left and the right as far as Juba could see. A series of yellow lines and dashes ran down the center of the pathway.

In this example, we’ve opted to describe a field of wheat and the road that runs through it without ever using the words “wheat” or “road.” The reason for this is that our perspective character, Juba, is some sort of alien being who has never seen wheat or paved roads—he wouldn’t know the proper terms for them. In fact, if we were to use the proper terms for them, it would be a perspective error! We can’t tell our audience what our perspective character doesn’t know, as we’ve discussed before.

Let’s return to our above-mentioned description of a row of docks. This description would have been entirely appropriate if the perspective character had never seen or heard of docks; in fact, that’s what I assumed after reading the passage. The problem arose a few sentences later when it became clear to me that the character not only knew what docks were, but had also been to these very docks before. It’s the Figure Problem—describing something or someone without first identifying what or who they are implies that the perspective character is unfamiliar with whatever is being described. This is a useful tool for implying unfamiliarity; just make sure it only happens when you want it to.

Caution: When using this technique to imply unfamiliarity, the character must remain unfamiliar with whatever is being described. To continue with our example from above:

     Bright lights suddenly appeared from down the pathway on the right, accompanied by an odd, grinding roar. Startled, Juba darted back into the wheat to hide from whatever was coming.

Wait, when did Juba figure out that these plants were called wheat? We’ve already used our description to indicate that he doesn’t know that term, so we absolutely cannot use the word wheat until someone else gives it to Juba. 

Writers generally make this mistake for one of two reasons: first, it’s awkward and difficult to write about a field of wheat without using the word wheat. That’s just too bad—you’ll have to soldier through. Don’t use this technique unless you’re ready to commit to it. The second reason is that the writer assumes that because the audience has probably figured out that the plants are wheat, it’s all right to call them wheat now. It’s not—in this case, what the audience knows is irrelevant. You have to keep the perspective consistent.

When the audience is unfamiliar with an object


Suppose your perspective character is a human colonist on a strange, distant planet. She is out exploring when suddenly she is attacked by a ruger! Now, she is an expert explorer—ruger attacks are a near-daily occurrence on this planet, and she is quite familiar with the beast and how to deal with them. The trouble is that your audience, of course, has no idea what a ruger looks like. So you absolutely have to describe it clearly enough for your audience to picture comfortably.

The trick to this situation is to describe the ruger without making it seem unfamiliar to the perspective character. We’ve already taken the first step toward this—we’ve identified the creature as a ruger.

Picture yourself walking down the sidewalk. A stray dog crosses the street toward you. When you see it, do you think, “hmm . . . a four-legged, furry beast is walking toward me with its tongue lolling out of its long snout—this is a dog”? No, of course not! You think, “a dog is walking toward me.”

Identification implies familiarity.  The more quickly your character is able to identify a creature or object, the more familiar they are implied to be with said creature or object, and vice-versa. So, if your colonist immediately identifies the approaching creature as a ruger, the audience will know that she is familiar with rugers. If she sees the creature and you describe its appearance before she identifies it as a ruger, then the implication is that she knows about rugers but isn’t intensely familiar with them. If she describes the creature but never identifies it as a ruger (as Juba did with the wheat and the road), then the audience will know that she is entirely unfamiliar with rugers.

Once your colonist has identified the ruger, you are free to describe it without creating perspective errors. Be sure to keep the description true to the perspective character, of course—don’t use terms they wouldn’t, even if it would get the image across to your reader. Bonus points if you can frame the description in such a way that it seems natural for the character to be mentally dwelling on the description: perhaps your colonist notes that this ruger has different coloring than most and is unusually large. In describing how this ruger is different from most rugers, you can potentially tell the audience about rugers without it seeming out of character for the colonist to dwell on the ruger’s appearance.


Next time, we’ll discuss two more reasons to dwell on description—when a character is intensely familiar with a type of object, and when you just want to.

Monday, October 6, 2014

Characters With Multiple Names: Keeping It Consistent

Let's say that your main character has a friend named “James T. Mitchell, Jr.” His family calls him Jimmy, his mother calls him James, his grandparents call him Junior, and his friends call him Mitch.


Now, your audience probably has enough to do keeping track of the names of several different characters; if you try to make them remember more than one name for a single character, they’re going to have trouble. So if you have a character like this, consider pruning down the number of names you’ve given them. Ask yourself why this character has so many names and whether or not it actually adds anything to the plot or the character. If the answer is no, just cut down to one name.

But if you absolutely must have all of these names for James T. Mitchell, Jr., than you need to be consistent. Here's an example of too many names being handled poorly, patterned off of stories I've edited:

     Dan waved as Mitch came running out of the house.
     “James, you can’t leave until you finish your chores,” James’s mother shouted from the kitchen window.
     Mitch winced. “I can do them tonight, mom!” he shouted back. He grinned at Dan and gestured to the hole in the fence. Dan smiled and climbed through into the neighbor’s yard.
     “James Mitchell, don’t you dare leave!” James’s mother screamed. James ignored her. “James!”
     “Let’s go see if Sally is home,” Mitch said.

In the dialog of this example, Mitch was called by three different names—James, James Mitchell, and Mitch—and that's okay. What makes the passage confusing is that his name also alternates in the prose (that is, in the text that isn't dialog): he's Mitch in the first, third, and fifth paragraphs, but he's James in the second and fourth. This makes it seem as though two different characters are being referred to. Sure, your reader would probably figure out what was going on, but they shouldn't have to “figure out” something as simple as what character you're talking about.

The answer to this problem is to only refer to the character by one name in the prose. In our example above, Dan is our viewpoint character; and Dan thinks of James T. Mitchell, Jr. as "Mitch," just like the rest of their friends. So James T. Mitchell, Jr. will always be "Mitch" in the prose, even if his mother and family call him by other names in the dialog.

Done well:
     Dan waved as Mitch came running out of the house.
     “James, you can’t leave until you finish your chores,” Mitch’s mother shouted from the kitchen window.
      Mitch winced. “I can do them tonight, mom!” he shouted back. He grinned at Dan and gestured to the hole in the fence. Dan smiled and climbed through into the neighbor’s yard.
     “James Mitchell, don’t you dare leave!” Mitch’s mother screamed. Mitch ignored her. “James!”
     “Let’s go see if Sally is home,” Mitch said.

Note that this scene will still be confusing if we haven't already made it clear to our readers that people call Mitch by many different names; you can't just drop a character into the story and have everyone call him something different without explaining what's going on. If it seems like it would be difficult to fit in an explanation about Mitch's name before we introduce him, that's because it would be! That is one reason why I recommend against giving one character multiple names.

Now, if this story had multiple viewpoint characters, then we might be able to refer to Mitch by a different name in the prose. In sections written from Dan’s viewpoint, Mitch would always be “Mitch,” as we've discussed. But if you had sections written from Mitch’s mother’s point of view, you might switch to calling him "James," because that is how his mother thinks of him. But remember that you would be running the risk of needlessly confusing your readers. And either way, you must always be sure to keep each viewpoint consistent—when we’re in Dan’s head, Mitch is always “Mitch,” and when we’re in the mother’s view, Mitch is always “James.” Always.

Friday, September 19, 2014

The Figure Problem: Part One


     The scene begins. Wind blows across a harsh desert, or maybe rain is falling on a dreary city alleyway, or perhaps sun is shining through gaps in the leaves of a peaceful green forest. Wherever the story is taking place, a figure appears in the distance. The figure is stumbling, or hurrying, or strolling; maybe we’re told that the figure is lost, or avoiding being seen, or is relaxing. They could be panting, or mumbling, or whistling. Slowly, the view dials in on the figure. It looks to be male, or female, or perhaps neither. We’re told the figure has a ragged beard, or a dark hat and trenchcoat, or metallic skin. Gradually, we get more and more details about the appearance and behavior of the figure. Perhaps we’re expressly told that the figure has survived a plane crash, or is a cat burglar on the way to a job, or is an oddly-built android; after this point, the “figure” might begin to be referred to as the survivor, the thief, or the android. Whoever they are, the figure keeps moving, and more details of their appearance and what they’re doing are gradually revealed.

     Finally, after anywhere from several paragraphs to several pages, we find out the name of the figure—maybe they meet someone else who calls them by name, or maybe the writer simply felt that this would be a good point to reveal it. From this point on, they cease to be the “figure,” the “survivor,” the “thief,” or the “android.” They are called by name for the rest of the story, whether they’re the protagonist, a side character, or a temporary, otherwise-unimportant vessel to carry us to the actual plot.

If you have been writing for any length of time, then you’ve probably written some variation of this scene. Everyone does, at some point or another, and I do mean everyone. It’s almost always a bad idea.

Why is this a problem?

Because it is slow, distant from the character, and usually distant from the plot; put those together, and you’ve got a whole basket of boring. And being boring is the worst sin a piece of purported entertainment can commit.

Slow: Usually, not much is happening while the “figure” walks across the screen for us to admire. Why? Because it is difficult to blend description and action, so the writer is getting all of that pesky description out of the way before they actually get to the action. That’s an adequate workaround, but it would be a better idea to start closer to the action and learn to work in shorter, quicker bits of description along the way. We’ll go over tips for doing that well at a later date.

Distant from the character: Why don’t we know the character’s name? There is almost never a good reason—new writers simply withhold information out of habit, trying to give every bit of info through some sort of “reveal.” This isn’t a movie; we don’t need to zoom in from an establishing shot, drawing closer and closer to the figure until we suddenly get their name and jump inside their head to start finding out what they’re thinking about what they’re doing and the things around them. That just doubles up on the slowness of the piece—first, we spend pages setting the scene, and then we have to sit through the character thinking about everything that we’ve just seen, forcing us to go over it all again? Just put us in their head and give us their name right from the start. Help us know them through their actions and how they perceive their surroundings, and it will be more interesting.

Distant from the plot: All of this scene-setting isn’t the plot, it’s a gradual meander toward the plot. But your readers already approached the story—they bought your book or borrowed it from a friend or looked up your story where it’s available online. Don’t languish in non-action because you’re so impressed with your breathtaking powers of description. Your readers picked up a story, so just get to it.


As I mentioned before, almost every writer has done this at some early point of their career, usually well before they got published. I did this on multiple occasions before someone pointed out to me why it was a problem. Ask an author sometime; they’ll probably know about the Figure Problem (though not necessarily by that name) and will be able to remember when they did it themselves. So don’t feel bad if your current masterpiece begins this way—you’re in good company.


In this post, we discuss how the Figure Problem can become even worse.

Friday, September 12, 2014

Perspective Errors: Too Little Information

            A knock at the door awoke Sally. She squinted against the light coming through the window and groaned, pulling her warm blanket over her head. But the knock came again, louder and longer this time. With a sigh, she pulled herself out of bed, keeping her blanket wrapped around her shoulders for warmth.
            She opened the door again mid-knock, and found Beth standing there with her fist still raised.
            “It’s about time,” Beth said with a frown, lowering her hand. “Go get dressed, we’re going for a drive.”
            “What?” Sally grumbled. “Why would we do that?”
            Beth folded her arms. “It’s about the Grimoire.”
            Sally blinked, suddenly alert. “The Grimoire? What happened?”
            “We can’t talk about it here,” Jacob said from beside Beth. “Just get ready.”

I’m sure you noticed the problem at the end of that passage—if Jacob was standing next to Beth that whole time, why wasn’t he mentioned when Sally first opened the door? This is another common type of perspective error, when the author fails to share every important thing that the perspective character knows or can sense.


Introduce things to the scene before they're being used


Picture another scene: A burly man in a black suit drags Sally into a parlor, where a sinister-looking old woman is waiting. Clever and threatening words are exchanged, and then the woman tells her burly henchman in the black suit to take Sally out back and dispose of her. The man reaches for Sally, but she grabs the bowling pin on the table and hits him over the head with it.  And then the reader goes, “wait, what bowling pin? Since when was that there?”

If there is a bowling pin on the table, that is something that Sally would have noticed when she came into the room. If you didn’t mention it when it would have been visible, then you can’t use it later—that’s the rule. If you get to the middle of the scene and realize that you need a bowling pin for Sally to use, then scroll back and put it in at the beginning of the scene. The important thing is that your character becomes aware of things naturally; the scene won’t feel real, otherwise.

Now, if your character suddenly realizes that there’s a bowling pin on the floor by their feet just a moment before they grab it, that’s okay—there are situations where that’s the best way to go. The important thing is that you show your character becoming aware of it, so that your reader can become aware of it, too:

Sally suddenly noticed a bowling pin, of all things, lying on the ground by her feet. Without taking time to think, she snatched it up and swung it at the burly thug’s face.

This is still a little abrupt, but it is acceptably and realistically abrupt.


Using perspective errors to create tension = bad writing


The examples above are simple mistakes; the writer forgot to mention Jacob and the bowling pin when they came into the scene instead of when they became important. There will be times, however, where you are tempted to break perspective in this way deliberately. Why? Almost always, it will be for the purpose of artificially creating tension.

For example: Sally, after hitting the thug over the head with that convenient bowling pin, runs from the room. She gets out of the building and into the spacious yards around it. But as she runs up to the open gate that leads off the grounds, a guard steps in front of her and points a rifle at her head. She stops and raises her hands. He tells her to turn around and go back. She pleads, explains, cajoles, and maybe even threatens him—she talks and talks and talks, stalling. Then Jacob suddenly hits the guard over the head (probably not with a bowling pin), having crept through the gate while Sally was distracting the guard.

The writer didn’t mention Jacob until he hit the guard over the head so that the readers would wonder how Sally was going to get out of this situation. If they’d known that Sally could see Jacob sneaking through the gate (she was looking that direction, after all), then the tension of the scene wouldn’t have been as high.

I’m not going to mince words—this is a cheap trick, and you should not do it. Your readers will feel cheated, and they’ll be right to; you flat-out lied to them in an attempt to keep them from figuring things out sooner than you wanted. Your characters can lie to one another all you want; if your story is narrated by one of the characters, then you have the possibility of having them lie about the events of the story (though it won’t necessarily feel less cheap if you do this, so be careful); but you, as the author, as the person telling this story to your readers, cannot ever lie. If you do so, it will be bad writing, and that’s the end of it.


Find a better solution


So, when you’re tempted to do this, just don’t. Find a way around it. Rearrange the scene so that the guard is standing near a corner that Sally can’t see around, so that Jacob can appear suddenly without a perspective error. Have the guard come up behind Sally, so that she can’t see Jacob sneaking up. Give Jacob the ability to teleport, for all I care—unless you’re writing creative non-fiction, then you can do whatever you want—the possibilities are limitless! Just don’t lie to your reader.

To make things even more difficult, the same thing goes for the information your character knows. If you’re writing from the perspective of a detective investigating a murder, and at the end of the story you suddenly reveal that he knew all along that their primary suspect was innocent and that his boss was the real murderer, then you’ve cheated. If he knew that the whole time, and we were in his head, then we should have known, too.

Picture Ocean’s 11 written through Danny Ocean’s perspective: it wouldn’t have worked, because the movie ends with a big reveal about what the real plan was. In a movie that's okay, because we’re not actually in Danny’s head—there’s not technically a perspective error. No lies. But in a book from Danny’s perspective, it wouldn’t work. If he knew the plan from the beginning, and we were in his head, then we should have known, too.


You can get around it—take us out of the detective’s head and put us in someone else’s head (as Arthur Conan Doyle did in the Sherlock Holmes stories, relating them through Watson) or have the detective suddenly figure it out at the end instead of having known the whole time. For your version of Danny Ocean, have the plan go wrong and he suddenly has to improvise; or put the story from someone else’s perspective, someone who wouldn’t be in on the plan. Again, there’s tons of options. 

Just don’t use the perspective error because it’s easier—you want to be better writers than that.

Monday, September 8, 2014

Perspective Errors: Too Much Information

Another very common perspective error occurs when the author gives the audience too much information—that is, more information than the perspective character should have. For example, let’s say you’re reading a book written in third-person limited perspective from the viewpoint of a man named Sam, and you come across this passage:

     Sam glanced at the notebook on the table and then shook his head. “I won’t need it today,” he said, turning and walking out the door. Little did he know that, by leaving his notebook behind, he had just ensured that this would be the single worst day of his life.

Do you see the problem? Since this story is written in third-person limited perspective, we should only receive information that the viewpoint character has access to. Sam doesn’t know that he’s just ruined his day . . . the passage explicitly states that he doesn’t! Therefore, in giving us this information, the author has just made a perspective error—they leaped briefly from third-person limited to third-person omniscient narrator.

Generally, when an author makes a TMI perspective error, it’s because they’ve described the emotions, thoughts, or motivations of a non-viewpoint character:

     “I’ll be fine,” I said, kissing Emily on the cheek. “Go have a good day.”
     “Wait a second James,” she said, worried that I was still upset. “You’ll still call me at lunch, right?”

or described action that the viewpoint character cannot see:

     “I don’t want to go,” Missy said, thinking of the long drive and the awkward silences that would surely fill their conversation on the way. She turned away from Frank to look out the window at the storm. “It’s just going to get cancelled because of the weather, anyway.”
     Frank sighed and ran a hand through his hair. “Well then, what do you want to do?”

In the first example, we’re in James’s perspective—therefore, we shouldn’t know that Emily is feeling worried. James can speculate that perhaps she is worried, or note that she looks worried; he can even say that he knows she’s worried, just as long as the action remains in his head rather than jumping into hers.

In the second example, Missy is our viewpoint character. She has just turned away from Frank, and therefore she cannot see when he runs a hand through his hair—and if she can’t see it, we shouldn’t be able to, either. 

Here are some options for how the previous examples could be fixed (italics for emphasis):

     “Wait a second James,” she said, probably worried that I was still upset. “You’ll still call me at lunch, right?”

     “Wait a second James,” she said. Her face still looked worried. “You’ll still call me at lunch, right?”

     “Wait a second James,” she said. I could tell that she was worried I was still upset. “You’ll still call me at lunch, right?”

     “I don’t want to go,” Missy said, thinking of the long drive and the awkward silences that would surely fill their conversation on the way. She looked out the window at the storm and then turned back to Frank. “It’s just going to get cancelled because of the weather, anyway.”
     Frank sighed and ran a hand through his hair. “Well then, what do you want to do?”

     Frank sighed and stepped up beside her, running a hand through his hair. “Well then, what do you want to do?”

     Frank sighed. “Well then, what do you want to do?”

Friday, September 5, 2014

Perspective Errors: Slip-ups

Now that we’ve gone over the different perspectives from which most novels are written (first-person, third-person limited, and third-person omniscient), we can begin to discuss the many, many ways in which writers can make mistakes in regards to perspective.

A perspective error is any point in the story where the writer unintentionally presents information that is not consistent with the perspective in which the story is written.

The simplest type of perspective error is when an author accidentally switches perspectives. It happens most often in stories that have been adapted from one perspective to another—say the first draft was in third-person limited, but the author decided the story would have more impact written in first-person perspective from the protagonist’s point of view. So, they rework the second draft into first-person, but they miss a few lines here and there. Other times, this is just an absent-minded mistake. Here is an example:

     “You can’t keep going like this, Rachel,” Geoff said to me. “You need to get some sleep.”
     “I need to be here when Diana gets back,” I replied, shaking my head.
     Geoff sighed. “Rachel . . . it’s been two weeks. No one survives outside the walls for more than a day. You know that.”
     She refused to look at him. “When Diana gets back, she’ll need someone to throw her a rope.” I knew that she was still alive, somehow. But I couldn’t say it out loud. I just couldn’t.

Although the example is written in first-person from Rachel’s point of view, there is one point where Rachel is referred to as “she” rather than “I”—a slip into third-person perspective.

The two best ways I know of to catch these slip-ups are:
  1. Read your story out loud—often, your mouth and ears will notice mistakes that your eyes didn’t.
  2. Have someone else proofread your story—you know what you’re trying to say, and often your brain will fill in what a sentence was supposed to say rather than noticing what it actually says. Other people won’t have this problem when it comes to your writing, so ask them for a hand.
This is just the first of dozens or even hundreds of ways that writers can make perspective errors. We’ll discuss more in the future.

Wednesday, September 3, 2014

Overview: Third-Person Omniscient Viewpoints

Third-person omniscient is a viewpoint where the perspective jumps from character to character, showing many points of view over the course of any given scene at once. It generally comes in one of two styles: the omniscient narrator or head-hopping omniscient.

Omniscient Narrator


As the name implies, a story told through an omniscient narrator is given through the perspective of a usually-nameless storyteller, someone who is not a character within the story. This narrator is, so far as the story goes, omniscient, with complete knowledge of what all the characters are thinking or doing at any given time. They will often tell the audience what one character is thinking, and then mention what another character is thinking immediately after, rather than restricting what the audience sees to the perspective of one character at a time. Here is an example from the opening of The Lion, the Witch and the Wardrobe by C.S. Lewis:

ONCE there were four children whose names were Peter, Susan, Edmund and Lucy. This story is about something that happened to them when they were sent away from London during the war because of the air-raids. They were sent to the house of an old Professor who lived in the heart of the country, ten miles from the nearest railway station and two miles from the nearest post office. He had no wife and he lived in a very large house with a housekeeper called Mrs Macready and three servants. (Their names were Ivy, Margaret and Betty, but they do not come into the story much.) He himself was a very old man with shaggy white hair which grew over most of his face as well as on his head, and they liked him almost at once; but on the first evening when he came out to meet them at the front door he was so odd-looking that Lucy (who was the youngest) was a little afraid of him, and Edmund (who was the next youngest) wanted to laugh and had to keep on pretending he was blowing his nose to hide it.
As soon as they had said good night to the Professor and gone upstairs on the first night, the boys came into the girls' room and they all talked it over.
"We've fallen on our feet and no mistake," said Peter. "This is going to be perfectly splendid. That old chap will let us do anything we like."
"I think he's an old dear," said Susan.
"Oh, come off it!" said Edmund, who was tired and pretending not to be tired, which always made him bad-tempered. "Don't go on talking like that."
"Like what?" said Susan; "and anyway, it's time you were in bed."
"Trying to talk like Mother," said Edmund. "And who are you to say when I'm to go to bed? Go to bed yourself."
"Hadn't we all better go to bed?" said Lucy. "There's sure to be a row if we're heard talking here."
"No there won't," said Peter. "I tell you this is the sort of house where no one's going to mind what we do. Anyway, they won't hear us. It's about ten minutes' walk from here down to that dining-room, and any amount of stairs and passages in between."
"What's that noise?" said Lucy suddenly. It was a far larger house than she had ever been in before and the thought of all those long passages and rows of doors leading into empty rooms was beginning to make her feel a little creepy.
"It's only a bird, silly," said Edmund.

Notice how over the course of these few paragraphs the narrator first sets the scene without focusing on any specific character, and then how he describes to us the internal thoughts and emotions of both Edmund and Lucy. These are hallmarks of third-person omniscient.

Head-hopping Omniscient


The “head-hopping” variation of the third-person omniscient viewpoint is similar to the third-person limited viewpoint in that it eschews narrators and instead conveys the story directly through the viewpoint of the characters, as though the reader were riding along in the characters’ heads. However, unlike the limited viewpoint, the omniscient viewpoint jumps from perspective to perspective within any given scene—hence the “head-hopping” description. Here is an example from the beginning of Frank Herbert’s Dune:

Paul felt his left hand aching, uncurled the clenched fingers, looked at four bloody marks where fingernails had bitten his palm. He dropped the hand to his side, looked at the old woman. "You did that to my mother once?"
"Ever sift sand through a screen?" she asked.
The tangential slash of her question shocked his mind into a higher awareness: Sand through a screen. He nodded.
"We Bene Gesserit sift people to find the humans."
He lifted his right hand, willing the memory of the pain. "And that's all there is to it—pain?"
"I observed you in pain, lad. Pain's merely the axis of the test. Your mother's told you about our ways of observing. I see the signs of her teaching in you. Our test is crisis and observation."
He heard the confirmation in her voice, said: "It's truth!"
She stared at him. He senses truth! Could he be the one? Could he truly be the one? She extinguished the excitement, reminding herself: "Hope clouds observation."
"You know when people believe what they say," she said.
"I know it."
The harmonics of ability confirmed by repeated test were in his voice. She heard them, said: "Perhaps you are the Kwisatz Haderach. Sit down, little brother, here at my feet."
"I prefer to stand."
"Your mother sat at my feet once."
"I'm not my mother."
"You hate us a little, eh?" She looked toward the door, called out: "Jessica!"
The door flew open and Jessica stood there staring hard-eyed into the room. Hardness melted from her as she saw Paul. She managed a faint smile.
"Jessica, have you ever stopped hating me?" the old woman asked.
"I both love and hate you," Jessica said. "The hate—that's from pains I must never forget. The love—that's...."
"Just the basic fact," the old woman said, but her voice was gentle. "You may come in now, but remain silent. Close that door and mind it that no one interrupts us."
Jessica stepped into the room, closed the door and stood with her back to it. My son lives, she thought. My son lives and is ... human. I knew he was ... but ... he lives. Now, I can go on living. The door felt hard and real against her back. Everything in the room was immediate and pressing against her senses.
My son lives.
Paul looked at his mother. She told the truth. He wanted to getaway alone and think this experience through, but knew he could not leave until he was dismissed. The old woman had gained a power over him. They spoke truth. His mother had undergone this test. There must be terrible purpose in it ... the pain and fear had been terrible. He understood terrible purposes. They drove against all odds. They were their own necessity. Paul felt that he had been infected with terrible purpose. He did not know yet what the terrible purpose was.

Although there is no narrator directing us through the scene, notice how the reader is shown the thoughts of all three characters at various points—the Reverend Mother, Paul, and Jessica.

Advantages and Disadvantages of Third-Person Omniscient Viewpoint


Advantages of the Omniscient Narrator


Easier to write than head-hopping: Since this perspective is very similar to first-person (a narrator relating the story to the readers), it can be somewhat easier to write than the head-hopping style of omniscient.
Tension: Since the author can share with the reader any character’s thoughts or even information that none of the characters know, it is easy to introduce tension through obstacles that the characters don’t know are coming.
Infodumping: Since the narrator can show thoughts from multiple characters and even pause to explain information, it is possible to get across a lot of information in a very short space of time.
Direct address to the reader: As always, a narrator can address the reader directly if necessary.

Advantages of Head-Hopping Omniscient


More immediate than the narrator: Since there’s no one between the reader and the events of the story, the narrative can feel more immediate and real and less like just a story.
Tension: Just as with the narrator, you can convey information from multiple viewpoints or information that none of the characters know.
Infodumping: Again, it is possible to convey information from multiple perspectives very quickly, rather than having to give a separate scene to each perspective.
Most reliable narrator: With its absence of a biased, actual narrator and ability to show the thoughts of many characters in quick succession, this is the single most reliable narration that a writer can provide to a reader.

Disadvantages of Both Types of Third-Person Omniscient


Difficult to write correctly: Third-person omniscient is the most difficult to write without creating viewpoint errors or getting confusing—when you move from head to head, the reader can get lost very quickly and become unsure who is thinking what.
Unfamiliar to many readers: To make matters worse, very few books are written in third-person omniscient these days, so readers are unused to reading it. This means that even if you get it right, readers may still end up confused. This is particularly true with the “head-hopping” variation of omniscient, because to the reader it will often seem like third-person limited until the first time the narrative jumps to another character’s thoughts. This can be very jarring to readers, even if they’ve read omniscient before.
Lack of tension: It can be difficult to keep secrets and tension going if the readers are getting too much information about what is going on.
Infodumping: While it is an advantage that omniscient allows you to convey lots of information more quickly, this is a very difficult thing to do well. Often, this can turn into a firehose-esque flood of information that the reader will be unable to follow.

Monday, August 18, 2014

Overview: Third-Person Limited Perspective

Today we'll continue our series of discussions on common perspectives. We've already discussed what perspective and tense are and first-person perspective; today we'll delve into third-person limited perspective.

Third-person stories are told from the perspective of someone who is not part of the story; hence, all of the characters are referred to as "he," "she," or "it," rather than "I" or "we." In third-person limited perspective, your goal should generally be to not draw attention to the narrator—in a way, you're pretending that there isn't a narrator, that the audience is simply riding in a character's head and seeing what the character sees and thinks. Take a look at these examples from the first and second chapters of Game of Thrones by George R.R. Martin:

     It was not until they were mounted and on their way that Bran allowed himself to taste the sweet air of victory. By then, his pup was snuggled inside his leathers, warm against him, safe for the long ride home. Bran was wondering what to name him.
     Halfway across the bridge, Jon pulled up suddenly.
     "What is it, Jon?" their lord father asked.
     "Can't you hear it?"
     Bran could hear the wind in the trees, the clatter of their hooves on the ironwood planks, the whimpering of his hungry pup, but Jon was listening to something else.
     "There," Jon said. He swung his horse around and galloped back across the bridge. They watched him dismount where the direwolf lay dead in the snow, watched him kneel. A moment later he was riding back to them, smiling.
     "He must have crawled away from the others," Jon said.
     "Or been driven away," their father said, looking at the sixth pup. His fur was white, where the rest of the litter was grey. His eyes were as red as the blood of the ragged man who had died that morning. Bran thought it curious that this pup alone would have opened his eyes while the others were still blind.
     "An albino," Theon Greyjoy said with wry amusement. "This one will die even faster than the others."
     Jon Snow gave his father's ward a long, chilling look. "I think not, Greyjoy," he said. "This one belongs to me."

     [Chapter Two]
     Catelyn

     Catelyn had never liked this godswood.
     She had been born a Tully, at Riverrun far to the south, on the Red Fork of the Trident. The godswood there was a garden, bright and airy, where tall redwoods spread dappled shadows across tinkling streams, birds sang from hidden nests, and the air was spicy with the scent of flowers.

In this example, there is no narrator to speak of—we don't know who is telling the story, because the narrator isn't a character. Instead, the narrator follows the thoughts and experiences of some perspective characters: Bran Stark in the first chapter and Catelyn Stark in the second. Even though Bran and Catelyn aren't personally telling the story, as they would be in a first-person narrative, we still see the world through their eyes. This is what limited perspective means—our view as an audience is limited to that of one character at a time. When the author wants to switch perspective characters, he begins a new section or chapter.

Advantages of Third-Person Limited Perspective

Reliable narrator: Because the narrative is not relayed by one of the characters, third-person stories tend to seem more trustworthy and objective. The audience feels like they're inside a character's head without a narrator, so what they are shown is probably true.
Character sympathy: While not usually quite as intimate as a first-person narrative, third-person limited stories can still feel very close to the characters—the story takes place in their heads, after all.
Multiple perspectives: As demonstrated by the example passage, third-person limited narrative makes it very easy to switch from one perspective character to another. Some books have two or three perspective characters, while others—like Game of Thrones—have dozens and dozens.
Eloquence: Not all characters are as intelligent or well-spoken as others. If you wanted to write a first-person story from the perspective of a thick-headed thug, it would be difficult to describe the action as well as you would like with the thug's limited vocabulary. In third person, however, you can write a scene from the thug's perspective without sacrificing eloquence or creativity.

Disadvantages of Third-Person Limited

Easy to over-do: Just because you can write from multiple perspectives does not mean that you can do so well. Many new authors attempt to branch their story out among too many perspective characters, resulting in a slow and confusing story that loses track of its own plot. Yes, George R.R. Martin did it—but you're not George R.R. Martin. (Unless you are, of course. Hi George! Thanks for stopping by.) Try to keep your novel to two or three perspectives until you've really got the hang of juggling all those characters.
Difficult to withhold information from the reader: Since the narrator is so reliable in third-person limited, and since the audience is inside the heads of various characters, the audience will often feel cheated if you don't tell them information that the main character should have known.
Perspective errors: It is very easy to make perspective errors when writing a third-person limited story; in fact, this perspective probably sees more mistakes than any other perspective. We'll cover the many errors that writers make in third-person limited in future updates.