What Leaders and Managers Can Learn from Save the Cat
Dana stood at the front of the all-hands with a slide titled "Reorg Rationale," full of boxes and arrows showing the new team structure. She'd rehearsed the logic twice: efficiency gains, clearer ownership, faster decisions. Twenty minutes in, hands stayed down and cameras stayed off. Later, her skip-level pulled her aside. "You told us what changes," he said, "but not why anyone should want it to." He was right — she'd cut the part of her notes about Marco, a support engineer who'd spent eight months bouncing tickets between three teams because no single owner existed, and who'd finally said in a survey that he no longer knew who to ask for help. That story was supposed to open the meeting. Instead it sat in her notes folder while people filed out already dreading the transition, having heard a plan but never met a reason.
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
Dana's slide is the common failure — leaders open a change announcement with the mechanics of what will differ, before anyone in the room has a reason to care that it changes at all. A memo that starts with new reporting lines, before naming the actual person or problem the change addresses, reads as bureaucracy rather than progress.
Before your next announcement, identify one real person whose daily work will visibly improve, and open with their situation in plain terms — what was hard, and what gets easier. Only move to structure and reporting lines once that person's situation has made the room care about the outcome.
Stories tend to share an underlying structural shape
Change communications often read as a list of decisions rather than a shape — what wasn't working, what was tried, what is changing, and what happens next. A team hearing only the decision, without the shape that led to it, tends to assume the decision was arbitrary or already fixed elsewhere.
Before your next team narrative, sketch four short beats: the strain everyone already feels, what you learned by looking closely at it, the change you're making because of that, and what you'll watch to know it's working. Deliver those beats in order, every time you retell the story.
Know your story's core idea in one clear sentence before building anything else
A leader who cannot state the reason for a change in one sentence tends to produce announcements that drift between several justifications at once, so different listeners walk away with different understandings of why it happened. Dana's own rationale slide mixed efficiency, ownership, and speed without picking one as the actual point.
Write one sentence naming the specific problem this change solves and for whom. Say that sentence to a colleague outside the initiative; if they cannot repeat back the core reason, revise the sentence before you touch the announcement, memo, or meeting agenda built on top of it.
Structure serves the idea, not the other way around
A polished change narrative cannot rescue a change that genuinely isn't needed or well thought through. Leaders sometimes reach for narrative technique to make a decision more palatable rather than more clear, and employees tend to sense the difference quickly. Use structure to help a real, defensible decision land the way it deserves to, not to dress up a decision that hasn't earned the room's trust on its own merits.
A tight one-sentence rationale can feel cold next to the human story that should open the announcement, and the four-beat shape can feel padded if you're eager to just state the decision. When time is short, keep the human opening and the one-sentence core, since together they carry most of the persuasive weight, and treat the fuller structural shape as something you can supply in follow-up conversations and documentation.
Name one thing, honestly
Whose specific situation, right now, would make your team believe your next change is worth the disruption, and have they actually appeared in your plan for announcing it?
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 naming the specific problem this change solves and for whom. Say that sentence to a colleague outside the initiative; if they cannot repeat back the core reason, revise the sentence before you touch the announcement, memo, or meeting agenda built on top of it.