What Creators and Innovators Can Learn from Save the Cat
Theo's product demo video opened with a slow pan across his app's settings menu, narrating each toggle in order: notifications, themes, export formats, sync options. By the ninety-second mark, the view count graph on his dashboard showed what it always showed for videos like this — a steep drop right after the first few seconds. His editor, watching the analytics with him, finally said what she'd been thinking for weeks: "Nobody has ever opened a video because they wanted to see a settings menu." Buried in Theo's notes was a two-sentence story about the actual reason he'd built the export feature — a user who'd lost a semester of research notes when a competing app locked her files in a format nothing else could read. That story had never made it into a single video. Theo scrapped the settings pan, opened his next draft with the lost-research story instead, and watched the same graph hold steady for the first time in months.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Give your audience an early, concrete reason to root for your protagonist
Theo's settings-menu opening is the common failure — creators lead with what the thing does mechanically, before giving a viewer any person or moment to actually care about. A product page that opens with a feature list, before describing whose specific problem it solves, tends to lose visitors before they reach the list's third item.
Before publishing your next demo or page, write a two-sentence story about one real person's specific frustration that your work addresses. Open with that story, on screen or on the page, before any feature explanation appears.
Stories tend to share an underlying structural shape
Product narratives often unfold as a feature-by-feature tour rather than a shape with a real problem, an attempt, and a resolution, so a viewer has no throughline connecting one moment to the next. A walkthrough that jumps between unrelated features in the order they appear in a menu, rather than in the order a problem actually gets solved, is hard to follow even for an interested viewer.
Before recording or drafting your next piece, outline the shape first: the frustration, the attempted workaround that didn't fully work, and what your solution actually changes. Only add specific features once that shape is set, and drop any that don't serve it.
Know your story's core idea in one clear sentence before building anything else
A creator who cannot state their project's core idea in one sentence tends to produce content that explains everything and clarifies nothing, because every viewer question feels equally important to answer. Theo's early drafts drifted between four different value propositions depending on which day he recorded them.
Write one sentence stating what your work lets someone do that they couldn't do before, and for whom. Read that sentence before drafting any new video, page, or pitch, and cut whatever doesn't visibly serve it.
Structure serves the idea, not the other way around
A compelling narrative structure cannot rescue a product or piece of work that doesn't actually solve a real problem. Some creators become skilled at story technique and use it to generate attention for something genuinely undercooked underneath. Use these tools to help a real, useful idea reach the people who need it faster, not to manufacture interest in something that isn't ready yet.
A punchy origin story can crowd out the fuller shape of problem, attempt, and resolution in a short format, and a properly paced structure can feel slow next to the instant hook attention spans now demand. When you're limited to a few seconds, keep the human opening and the one-sentence core, since together they carry most of the weight, and save the fuller shape for longer formats where there's room to build it out properly.
Name one thing, honestly
What's the specific person and frustration behind your current project that you've never actually said out loud in anything you've published?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Write one sentence stating what your work lets someone do that they couldn't do before, and for whom. Read that sentence before drafting any new video, page, or pitch, and cut whatever doesn't visibly serve it.