Quick definition
A strong project kickoff gets eight layers of questions on the table before drafting starts — content, audience, stakeholders, creative direction, emotional impact, production constraints, resources, and distribution — run inside a room culture that protects momentum and morale. Misalignment that doesn't surface on day one doesn't disappear. It just waits for a more expensive moment to surface later.
In one line: Ask the boring questions before the room gets attached to an answer.
Why the first meeting matters more than it looks like it does
Everyone wants to get to the fun part — the pitching, the world, the characters. But a room that skips straight to brainstorming is quietly making a dozen unexamined assumptions about audience, budget, platform, and stakeholder expectations, and every one of those assumptions has to get resolved eventually. The only choice is whether they get resolved cheaply on day one or expensively in week twelve.
Start with what the room already loves
Before touching the actual project, open by talking about the games, movies, or shows the room loves that live in the same space as what you're about to build. What resonated? What got everyone hooked? What made those things stand out? Sharing what you love about existing work gets a room on the same creative page fast, and it surfaces the specific energy everyone is secretly hoping to recreate — which is far more useful to name explicitly than to leave assumed.
Run the room with Post-its, not just talk
Post-it notes during brainstorming keep a session flexible and legible at the same time. Everyone writes their own ideas and hands them to a leader, who places them on a whiteboard — which makes it easy to move ideas around, cluster similar ones, and watch patterns emerge as the conversation evolves. That visible structure keeps the process dynamic without losing organization, and it sets the table for the decisions that come later. A guiding principle or stated value for the session helps the room evaluate ideas without spiraling into an indecision loop.
The eight-layer kickoff checklist
| Layer | Core questions |
|---|---|
| Content Definition | What am I making, what genre is it, and who's the audience? |
| Audience & Market | What does this audience expect from this kind of content? What comparable projects exist, and what can we bring that's unique? |
| Stakeholder Expectations | What do the people employing us expect, what are their success metrics, and how will the finished work actually get measured? |
| Creative Direction | What key scenes or moments do we want to see? Which characters get dramatically challenged? Where can we push against expected tropes? |
| Emotional & Narrative Impact | How should the audience feel afterward? What themes are relevant? What might they say about it once it's over? |
| Production Constraints | What's the deadline, the budget, and the milestone schedule across development through post? |
| Resources & Team | What team, collaborators, or specialized tools does this actually require? |
| Distribution & Platforms | Where does this get released, and how does that platform change how it should be crafted? |
The Metaphorical Refrigerator
Storytelling works a lot like filling a refrigerator with ingredients you'll cook with later. Every scene, prop, line of dialogue, and worldbuilding detail is an ingredient going into the fridge — available to be pulled out and combined into a narrative "meal" whenever the story needs one. This keeps development flexible instead of rigid, because the story doesn't have to move in only the one direction it was originally outlined to move in.
The discipline that makes the metaphor useful is checking the fridge before generating something new. When a character or story hits a wall, ask what they're facing, what's already known, and whether something already established earlier can inform the choice in front of them — before manufacturing a new element to solve the problem. Reaching for a fresh ingredient before checking what's already stocked is how stories accumulate contradictions and orphaned threads.
And when a room genuinely runs out of ingredients for a character or arc, that's not a failure of imagination — it's usually a signal. It often means that character's arc, or the story itself, has reached its natural completion, and the room is trying to force one more meal out of a fridge that's already empty.
Conflict is the only thing that makes a story interesting
Every story decision needs to introduce conflict or consequence — physical, emotional, or rhetorical. A story is only as interesting as the friction between a character's intention and the obstacles in front of it, and that friction is what actually tests a character's willpower and the viability of their goals. Even at epic scale, keep the conflict tethered to a relatable, grounded emotional struggle — scale without a grounded dramatic question underneath it reads as spectacle, not story. Meaning, in the same spirit, isn't a worldbuilding fun fact — it's something a character has learned about themselves by going through the difficulty the story put in front of them, which is exactly why characters need room to make mistakes, feel pain, and fail.
Let misaligned ideas run their course
Not every idea a room generates will align with the project's stated principles, and that's fine — pushing every misaligned idea out the moment it appears protects the plan but costs the room its momentum and morale. A more durable approach: let an idea continue even after you've quietly clocked that it's off-target, and trust that a natural touchpoint later in the process will make the misalignment clear to everyone, not just to you. Killing ideas too early teaches a room to stop offering them.
Room habits worth setting on day one
- Active listening — full attention to whoever's speaking, which builds the trust a room needs before people will offer half-formed ideas out loud.
- "Yes, and…" brainstorming — build on what's offered instead of dismissing it outright, so the room stays in generation mode instead of critique mode.
- Constructive feedback, strengths first — specific and actionable, and it starts with what's working before it gets to what isn't.
- Ground rules, stated out loud — clear guidelines for respectful, inclusive dialogue so everyone knows what's expected before they need to rely on it.
- A safe space for raw ideas — writers need to be able to share unpolished thinking without it being held against them later.
- Diverse perspectives, actually valued — a room of one kind of voice will default to groupthink no matter how good its process is.
Try it on your next kickoff
- Open with what the room loves before opening the project file.
- Run the eight-layer checklist out loud, even the boring production-constraint questions.
- Check the fridge before generating a brand-new story element.
- Let at least one misaligned idea breathe instead of correcting it in the room.
- Name the room's ground rules instead of assuming everyone already knows them.
Source note
This reference page is adapted from an internal Scribbler’s Toolbox teaching document, Best Practices at Project Start — a maintained development-process guide rather than a dated Substack essay. It's presented here in the same durable, citeable format as the site's other craft references.
Related pages
- Story Development Learning Path — move from kickoff through prototype, draft, feedback, pitch, and diagnosis in a defined order.
- How to Receive, Sort, and Apply Screenplay Notes — preserve the room's shared goals when feedback turns into revision decisions.
- A Screenwriter's Development Pipeline: From Concept to Market-Ready Draft — what happens after the kickoff session, once a project starts moving toward a draft.
- How to Pitch a Movie or TV Series Without Reciting the Plot — the stakeholder-facing counterpart to this checklist's internal Audience and Stakeholder Expectations questions.
- Prototype Ugly, Cut Ruthlessly, Pitch Relentlessly: An Iterative Story Development Method — a companion method for what to do with the ingredients this checklist helps a room generate.
- How to Give Screenplay Notes: A Guide to Constructive Feedback — a fuller treatment of the constructive-feedback habit this checklist asks a room to set on day one.
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.