Story Spine: The 8 Lines That Hold a Story Together

Where does the story spine come from?

The story spine was created by Kenn Adams, a playwright and improv teacher. In a June 23, 2026 NPR interview, Adams describes it as an eight-sentence exercise for creating or analysing stories, with the sentence beginnings preplanned — "once upon a time, every day, but one day, because of that, because of that, because of that, until finally, and ever since then" — and the rest improvised by the storyteller.

It is often called the "Pixar story spine", and Pixar's storytelling classes are why the nickname stuck. But the attribution belongs to Adams. Pixar popularised a tool that was already decades old; if you borrow the spine, you are borrowing from improv.

What does each of the eight lines do?

Each line has one job. Together they force cause and effect.

1. Once upon a time — sets a character and a world.
2. Every day — sets the routine the world runs on.
3. But one day — breaks the routine. The disruption.
4. Because of that — the first consequence, caused by line 3.
5. Because of that — the next consequence, caused by line 4.
6. Because of that — the pressure builds to a peak.
7. Until finally — the decisive act that resolves it.
8. And ever since then — states the change that remains.

Lines 4–6 are where most spines die, because each must be caused by the previous one, not merely follow it. If you want to fill in the eight lines right now, build them in the browser — that page owns the template; this one explains how to use it.

Which two lines do people get wrong?

Line 3 and the "Because of that" run.

Line 3 fails when it is a coincidence instead of a disruption. "But one day it rained" starts a weather report, not a story. The line has to break the routine from line 2 in a way that demands a response from the character in line 1. If nothing in line 3 calls the character to act, the spine has no engine.

The "Because of that" run fails when it is really "and then". "And then he travelled to Rome. And then he met the cardinal. And then the letter arrived." Nothing causes anything; it is a diary. The test for each line: does it exist because the line before it happened? If you can shuffle the three lines and the story still works, they were "and then" lines all along.

How is the spine different from a plot outline?

A plot outline lists events. The spine forces each event to be caused by the last — that is the whole constraint, and it is what makes the tool sharp.

The deletion test: delete a line and read the spine again. If the story still stands, the deleted line was a plot point, not a spine line. In a true spine, removing any "Because of that" makes the next line incomprehensible, because its cause is gone.

Can you use a spine on a true story?

Yes, and this is the useful part: the spine is a diagnostic. Map the facts you already have onto the eight lines. Where a line fills in, the story has that part. Where a line stays empty, you are missing a fact — and the fix is to find the fact, not to invent a line.

Here it worked on the opening of the story of the man who cut the rope, a true story sourced to Wikipedia, Elevator World, and ASME:

In the 1850s, factories needed machines that could lift heavy things up high. The lifting platforms were scary. Sometimes the rope broke, and the whole platform crashed down.

The spine, filled from the story's own facts:

1. Once upon a time — a mechanic named Elisha Otis works at a bedstead factory in Yonkers.
2. Every day — workers refuse the hoist because the rope can break.
3. But one day — [empty — see below]
4. Because of that — he builds a safety catch that grabs the rails.
5. Because of that — he takes it to a fair in New York in 1854.
6. Because of that — he rides a platform high above the crowd.
7. Until finally — he cuts the rope himself.
8. And ever since then — the platform drops a few inches, holds, and the crowd believes.

Line 3 is empty because the story does not have a single triggering day. The disruption is a slow fear — broken platforms, nervous workers — not one event you can put a date on. Two ways to fix it:

• Promote a platform crash into line 3. Clean spine, but it manufactures a specific day the sources do not give you.
• Move Otis's decision into line 3 — "But one day, Otis decided the hoist could be made safe" — and make line 4 the building of the catch.

The second is the one the story itself supports: the fear was general, but the decision was his and it caused everything after. This is the thing no template page tells you — a true story to map onto the spine will hand you the material, and the spine will show you exactly which part of it is missing. A gap is information, not failure.

What are the limits?

The spine flattens some stories, and pretending otherwise breaks them:

• Two protagonists — the spine wants one character to carry lines 1 and 7, and a double lead splits both.
• The slow reveal — a mystery's power comes from withholding, and the spine's chain of open consequences withholds nothing.
• Stories without a routine — line 2 needs an "every day" that then breaks. A story that starts mid-crisis has no routine to disrupt.

It suits anecdote and fable, which is most of what gets told out loud. For a whodunit or a two-hander, use it to check the middle and let the shape stay loose.

How do you go from spine to spoken story?

The spine is notes, not a script. Say the eight lines as eight sentences, out loud, labels included. That first pass sounds mechanical and should.

Then drop the labels and tell it. "Once upon a time" becomes "A village in India" or "Breakfast, Oxford, 1930" — the spine's job is done, and what is left is delivery: pace, pauses, the opening and the stop. Telling the finished spine out loud is a delivery problem, and how structure is scored shows what we check when the story is spoken rather than written.