Quick definition
This method borrows five iterative-design principles from tabletop game design and applies them to screen story development: prototype fast and ugly, cut by default when in doubt, rehearse the pitch through repetition, protect the story's core tension, and build in space for audience connection. The source is game designer Justin Gary's lessons from building the card game Ascension, remixed for screenwriters.
In one line: Ugly drafts are a feature, not a flaw — the value is in testing the idea, not presenting it perfectly.
Why polish-first drafting slows story development down
Polishing a draft before testing whether the underlying idea works wastes effort on execution the concept may not deserve. Game designers learned this the hard way with physical prototypes — cardboard and marker scribbles reveal whether a mechanic is fun long before expensive art assets would. The same logic applies to a first draft: treat it as disposable, not sacred.
The five lessons at a glance
| Lesson | In screenwriting terms |
|---|---|
| Prototype and iterate fast | Get ideas onto the page quickly, no polishing — every rough draft is a disposable test, not a presentation. |
| When in doubt, cut it out | Most story problems are solved by subtraction, not by adding more subplot or backstory. |
| Perfect your pitch through repetition | Rehearse a 30-second, 2-minute, and long-form version until the rhythm is second nature. |
| Know your core tension and protect it | Every story has a central engine — don't dilute it with clever detours. |
| Create space for community and connection | Build in the kind of details that make audiences want to talk to each other about the work. |
Cutting is usually the fix, not more material
The instinct under a story problem is often to add — another subplot, more backstory, a clever new turn of phrase. Most of the time, the actual fix is subtraction: if a scene, beat, or even a beloved line isn't serving tension, tone, or momentum, removing it usually strengthens what's left. Editing delivers its impact by taking away, not layering on.
Protect the core tension from clever detours
Every story runs on a central engine — survival vs. humanity, curiosity vs. danger, whatever the driving question is that keeps an audience reading or watching. Side mechanics and tonal detours that seem clever in isolation can dilute that engine if they don't serve it directly. Naming the core tension explicitly makes it easier to recognize when a scene is drifting away from it.
Pitch fluency comes from repetition, not memorization
Game designers pitch the same concept to playtesters, publishers, and players dozens of times, in different lengths, before it lands. The same applies to a story pitch: a 30-second hook for a stranger, a 2-minute version for a producer, a longer version for buyers. Testing the pitch repeatedly — recording it, reviewing it, adjusting — is what finds its rhythm, not writing a single polished script and reciting it.
Build in a reason for the audience to talk to each other
Connection doesn't require interactivity or a transmedia layer. It can be as simple as a cliffhanger that keeps friends texting, a character who sparks fan art, or a mystery that invites theory-crafting. The goal isn't only to entertain — it's to create something people want to discuss with each other after they've experienced it.
Iterative development checklist
- Is this draft still being treated as disposable, or has it become too precious to cut?
- When something isn't working, is the fix on my list an addition or a subtraction?
- Can I state this story's core tension in one sentence — and does every scene serve it?
- Have I pitched this out loud, in more than one length, more than once?
- Is there a detail here specific enough that two people could argue about it afterward?
Source note
This maintained reference page develops ideas first published in “Prototype Ugly, Cut Ruthlessly, Pitch Relentlessly” in Scribbler’s Toolbox on August 22, 2025. The original essay remains part of the editorial archive; this version is structured as a durable craft reference.
Related pages
- Story Development Learning Path — run this iteration loop inside the larger path from project alignment to market-facing pitch.
- How to Receive, Sort, and Apply Screenplay Notes — convert reader patterns into the focused, reversible prototype this method can test.
- How to Pitch a Movie or TV Series Without Reciting the Plot — the performance discipline that pairs with pitching through repetition.
- A Screenwriter’s Development Pipeline: From Concept to Market-Ready Draft — the fuller pipeline this iterative method plugs into at the drafting stage.
About the author
Jesse Alexander is a screenwriter, showrunner, and narrative designer whose work spans film, television, games, and transmedia storytelling. Scribbler’s Toolbox collects practical frameworks developed from professional story development and production.