I was once told, by a reader, that she was not going to read any further into the War of the Second Iteration series because the second book – Founders’ Effect – had ended in a cliffhanger. She loathed cliffhangers, considering them a cheap way to insure that readers went on to the next book. Instead of seeming defensive of my writing style, I observed that she must not be a fan of Tolkien. This comment produced a puzzled frown. The Lord of the Rings, as it happened, was one of her favorite works. And so I reminded her of the last line of The Two Towers: “Frodo was alive, but taken by the enemy.” A valiant effort was then made by the reader to tweak the definition of “cliffhanger” to exclude its use by Tolkien. The effort was abandoned when the ending of the Star Wars film The Empire Strikes Back came into the conversation. (A third party in the discussion pointed to similarities between the ending of my book and that film.)
To be sure, there are cliffhangers and there are cliffhangers. Like any technique applied to writing fiction (and here I am speaking of the creation of a multibook series) cliffhangers can be use well or badly. A good cliffhanger actually ends a story, providing closure for that portion of the story arc of the series. The characters are in a bad spot, but you close the book (or watch the credits roll) with at least some clue as to where things are going. You know Samwise is going to go after Frodo, and that Han Solo’s friends will not abandon him. This is exactly what I was trying to do at the end of Founders’ Effect. Apparently most readers have found my use of a cliffhanger in that book acceptable. According to the sales of the remainder of the series, better than 90% of the people who read Founders’ Effect go on to read the next three books.
I find that cliffhangers, like adverbs and adjectives, are best used sparingly, but not necessarily avoided entirely. As a reader, I’m not usually troubled by them. If the writer displayed enough skill to keep my attention all the way to the last page of the book, a cliffhanger at the end will more than likely have been handled properly. (The story has ended – but wait! There’s more! And I want more.) If the writer isn’t sufficiently skilled at this art to hold me all the way through a book – well, in that case, how the story ends would be a moot point. Very rarely, I find myself at the end of a book in a series that feels as if an arbitrary page limit had been reached. Something bad happens, the heroes are imperiled, and it just dangles there. I find that annoying as a reader, and I’m aware that it happens often enough to give the concept of a cliffhanger a bad reputation.
As a writer, aware of how badly readers might react to a clunky cliffhanger ending, few techniques I use cause me as much second-guessing. Does this segment of the overall series story arc really end here, in this deep pit of adversity currently occupied by the characters? Or would the larger story be better served by a resolution here, in this volume, that sets up the next book? In other words, does ending the book at this point, with the protagonist tied to the proverbial railroad tracks, actually make sense? In approaching such a decision, I’m usually going more on gut feelings than some sort of nuts-and-bolts analysis. A story has a way of evolving what I like to call an internal logic, a pattern that could also be called an emergent property. That logic or property can soon direct the story in ways that make sense – and should be followed – even when the writer started out with some other idea in mind. In my case, when it came time to end Founders’ Effect, the way that book had evolved, and what it suggested about the next book in the series, made a cliffhanger the most logical way to end it and set up The Plight of the Eli’ahtna.
If the cliffhanger feels right, thought must of course then be given to picking up the next installment in a way that repays the reader for their trust. That’s not always a simple thing to pull off, and this might explain why some cliffhangers misfire – and why I don’t often employ such endings in my books. I clearly did so in Founders’ Effect, and to a lesser degree in The Courage to Accept – and so far, those two books are my only examples. After all, it’s quite possible to leave a reader with the knowledge that there’s more to come, without leaving a character dangling from the edge of a cliff by their fingernails.
That being so, why use one at all? To my way of thinking, used properly – and sparingly – cliffhangers can be an effective way to increase the tension within a multi-book series, keeping the reader engaged in a way that avoids the dreaded middle-book syndrome. Cliffhangers raise the stakes, so to speak, and done well keep the flow of the story strong enough that the reader remains motivated. It really can work that way. The thought of Frodo in the hands of the orcs took me straight to The Return of the King. And guess where I was the day after they released Return of the Jedi? Yes, like so many of you, in line at a theater, eager to see that cliffhanger resolved.
Under Desert Stars 
Leave a Reply