Month: June 2016

Ah, Save the Cat!—the screenwriting manual some swear by… while others forswear altogether.  Here are my thoughts on why it is a worthy—even indispensable—storytelling program that has been irreparably corrupted by the very people who teach it.

The folks over at Save the Cat!, which does not include the program’s late innovator Blake Snyder, offered an object lesson last week on the misapplication of craft.

It’s common practice for Save the Cat! to break down a current or classic movie and illustrate how it conforms to a story’s fifteen major narrative “beats” as Snyder identified them (Blake himself published an entire book dedicated to this skill-building exercise, which I recommend—certainly over any of the recent analyses on the STC! blog).  This is what a sample “beat sheet” (of my own authorship) would look like (click on it for a closer look):

Simple enough, right?  The entire story summarized at its most basic, macrostructural level.  That’s the kind of plot overview I’ll painstakingly compose before I begin Word One of my screenplay or novel, so I know the plot is always tracking in the right direction.  It’s an indispensable application to help a writer “break the back” of his story, as well as an excellent learning tool:  By reverse-engineering well-regarded movies, you can teach yourself the fundamentals of mythic structure.  That is ostensibly the reason Save the Cat! offers sample deconstructions on a near-weekly basis.

As part of the exercise, Save the Cat! assigns its cinematic subject a genre per Snyder’s codified classifications (you’ll notice I designated Raiders an “Epic Fleece”), but, quite frankly, the Cats are usually confoundingly off the mark:  In the last year alone, they’ve misidentified Brooklyn (for the record, it’s “Family Institution”), The Empire Strikes Back (“Fantasy Superhero”), Dr. Seuss’ How the Grinch Stole Christmas! (“Caper Fleece”), Room (“Family Institution”), Whiplash (“Mentor Institution”), Her (“Separation Passage”), and Birdman (which, as I demonstrated in a previous post, is a “Fool out of Water” story).  Not particularly encouraging.

In their most recent breakdown, they’ve attempted to apply Blake’s beat sheet to the pilot episode of Game of Thrones.  With my Raiders breakdown in mind, have a quick look at their effort here (feel free to skim—you only need to get the gist in order to follow my assessment of it).

Notice how clean and to-the-point the Raiders analysis is?  Now compare that with the Game of Thrones breakdown, which is mired in needlessly copious detail and author commentary, as the analyst attempts to illustrate that “Winter Is Coming,” like any other good story, conforms to the Save the Cat! precepts—and yet the more closely the episode is studied, the less it seems to actually adhere to them!

So, instead of saying, “Gee, this isn’t going like I originally thought at all—Game of Thrones appears to operate on an altogether different narrative wavelength,” the analysis is instead loaded with conditionals:  “this B Story doesn’t fully interweave with the journey of the main protagonist”; “the main story of the pilot episode is structurally the equivalent of just Act One from Blake’s beat sheets”; “many of the storylines weaved over the series often will not simply resolve where their Act 3 would normally otherwise end, but rather they then evolve into a new story.”

Wouldn’t any of that seem to suggest the conclusions of this experiment in narrative reverse-engineering aren’t supporting the thesis?  Not according to this examination, which posits instead that “Blake’s other beats are simply yet to come.”

Here’s the logical (read:  actual) takeaway:  The reason the analyst had such a hard time making Game of Thrones fit comfortably within the Save the Cat! paradigm is because it doesn’t.