Most structural frameworks are designed for people who already have a story and need to organise it. The Story Spine is different. It’s for people who have an idea, a character, a situation, a feeling, and need to find out if there’s actually a story in it.

It takes about ten minutes. If the story is there, the spine will reveal it. If it isn’t, you’ll know that too, before you’ve spent months finding out the hard way.

Where It Comes From

The Story Spine was created by Kenn Adams, an improv theatre teacher, as a way to help performers build complete, satisfying stories on their feet. Rebecca Stockley brought it into Pixar in the late 1990s, where it became part of how story teams tested ideas in development. Emma Coats included it in her widely shared “22 Rules of Storytelling” in 2012, which is when most writers outside film encountered it.

It’s not a Pixar invention, and it’s not a secret formula. It’s a fill-in-the-blank prompt sequence that forces you to identify the causal logic of a story: the because of that chain that makes events feel connected rather than coincidental.

Writing Desk tip: Try the spine directly in a Story Plotter chapter note before committing to a full outline. Ten minutes of “because of that” prompts will tell you whether an idea has a working causal chain long before you’ve invested in a full Board or Timeline structure.

The Template

Seven sentence starters. Fill them in, in order.

Once upon a time… Introduce your protagonist and their world. Who are they? Where do they live? What’s the condition of their life before the story begins?

Every day… What is the routine? What does your protagonist’s ordinary life look like? This establishes what will be disrupted, and what they have to lose.

Until one day… The inciting incident. The event that breaks the routine and sets the story in motion. The arrival of the thing that changes everything.

Because of that… The consequence of the inciting incident. What does your protagonist do in response? What changes? This sentence can, and usually should, be repeated several times. It’s the escalation engine of the structure.

Because of that… The next consequence. What does the previous event cause? Each because of that should be a genuine causal result of what came before, not just the next thing that happens, but the thing that had to happen given what just did.

Because of that… Continue as many times as the story needs. Each iteration should raise the stakes. The chain of cause and effect is the plot.

Until finally… The climax. The chain of consequences reaches its peak. The central conflict comes to a head.

And ever since then… The new normal. Who is your protagonist now? What has changed? This is your resolution: brief, but honest about what the story costs and what it transforms.

Why the “Because of That” Chain Matters

The most common structural failure in unpublished fiction isn’t missing beats. It’s events that don’t cause each other. Things happen, and then other things happen, but the connection between them is loose. The reader senses that the story could have gone any number of ways, which means it doesn’t feel like it had to go the way it did.

The because of that chain is the antidote. It forces every event to be the direct result of the previous one: your protagonist makes a choice, because of that the antagonist responds, because of that an ally is lost, because of that the protagonist is cornered, because of that they have to act differently than they planned, until finally the confrontation arrives that only this sequence of events could have produced.

When the Story Spine is working, removing any link in the chain breaks everything after it. That’s the test: could you cut this event without affecting what follows? If yes, the causality is loose. Tighten it.

Using It for a Full Novel

The Story Spine was designed for short form, a five-minute improv scene, not an 80,000-word novel. But the underlying logic scales up.

For a novel, each because of that can represent a chapter, a sequence, or an act rather than a single scene. The spine gives you the causal skeleton; the rest of your structural planning (three-act beats, pinch points, character arc) gives you the flesh.

Use it early in development, before committing to any structural framework, as a way of testing whether the story has internal logic. Can you trace the through-line from inciting incident to climax without the chain breaking? If not, you know where the structural problem is before you’ve written a word.

It’s also useful in revision. If a draft doesn’t hold together, try writing the Story Spine for the novel that was actually written, not the one that was planned, and see where the causal chain breaks down.

The Story Spine vs Other Frameworks

The Story Spine doesn’t replace three-act structure or the Hero’s Journey; it sits upstream of both. It’s a story-finding tool more than a story-building one. Once you’ve established that your story has a working causal spine, you can map it onto whatever structural framework suits your novel and your working style. The spine tells you the story exists. The framework tells you how to build it.

A Familiar Example

Finding Nemo follows the spine cleanly, which isn’t a coincidence given the tool’s origins at Pixar.

Once upon a time, a clownfish named Marlin lives on a reef with his son Nemo, whom he protects to the point of being overbearing.

Every day, Marlin worries and shelters Nemo from the ocean’s dangers.

Until one day, Nemo is captured by a diver and taken away.

Because of that, Marlin sets out into open ocean, somewhere he’s never dared go, to find him.

Because of that, he meets Dory, who agrees to help despite barely being able to remember why.

Because of that, the pair are forced through a series of escalating dangers, sharks, jellyfish, the open trench, each one testing exactly the caution Marlin built his whole life around.

Until finally, Marlin reaches Nemo and helps him escape captivity.

And ever since then, Marlin lets Nemo take real risks of his own, having learned that overprotection was never the same thing as safety.

A Worked Example

Once upon a time, a forensic accountant in Edinburgh discovers a discrepancy in her firm’s client accounts.

Every day, she does her work, avoids her difficult boss, and tells herself it’s probably nothing.

Until one day, the client whose account she flagged turns up dead, and the police come to the firm.

Because of that, she realises the discrepancy was evidence of something much larger, and someone knows she found it.

Because of that, she starts investigating quietly, not because it’s her job, but because she’s the only one who knows what to look for.

Because of that, she discovers the fraud goes all the way up to the firm’s managing partner.

Because of that, she has to decide whether to take what she knows to the police, knowing it will cost her career, and possibly more.

Until finally, she goes to the police, alone, with everything she’s found.

And ever since then, she runs her own practice. The case never went to trial, but the discrepancy she found was listed in the evidence. Her name is in the footnotes.

Ten minutes. A complete story with a working causal chain, a clear arc, and an ending that earns its quiet. That’s what the Story Spine does.

Related reading: