chapters (8)
The Demo Nobody Remembers
The moment. You show the new feature. People nod. A week later nobody can describe what it does, and the project quietly loses priority.
What most people say
So this release adds bulk editing, improved filters, and a new export flow. You can now select multiple records, apply changes across them, and export in three formats.
Why it misfires. That's a feature list, and feature lists are unrepeatable. There's no one to root for and nothing at stake, so there's nothing for memory to hang on. People remember what happened to someone; a capability isn't an event.
The rewrite
Marta runs support. Every Monday she used to spend two hours re-tagging tickets one at a time - she'd put on a podcast because it was that dull. Last Monday she selected 400 tickets, changed them all at once, and was done before her coffee went cold. That's what shipped.
The move: one person, one moment. Pick a single named user and a single concrete moment in their week. Not "users can now…" but "Marta, last Monday." The feature list still exists - it just comes after, as detail.
Your turn
[Name] does [role]. Before, [specific painful moment]. Now, [same moment, changed].
Edge cases. No real user yet? Use a real internal person, or say plainly "here's the person we're building this for" - an honest hypothetical beats a fake anecdote, which people can smell.
This week. Before your next demo, write one sentence naming a person and a Monday. Open with it.