How to Plan a Collaborative Story

Create a shared story brief and decision process that gives collaborators direction without planning away every surprise. Write the smallest useful story brief Start with a one-page brief containing the premise, intended audience, format, approximate scale and emotional destination. Add boundaries around tone or subject matter and identify what the story is promising: perhaps a mystery will be solved, a relationship will change or a journey will cost something meaningful. A brief gives proposals a common test. It should not settle every scene before contributors have room to think. Separate non-negotiables from preferences. If the hopeful ending is essential, label it; if a coastal setting is merely today's favourite, say so. Too many fixed details turn collaborators into implementers, while no constraints force every person to guess what belongs. Review the list together and ask whether each fixed point creates useful direction. Remove rules that exist only because nobody has questioned them. Map a flexible arc and meaningful openings Sketch major changes rather than a chain of compulsory events. Mark the starting pressure, likely turning points and possible ending conditions. Between them, identify questions contributors may answer: what makes the alliance fail, which cost is paid, or what new truth changes the goal? Open questions invite invention while preserving the direction readers need. Contribution points should affect the story rather than decorate it. Define what information is available at each point, what must remain consistent and what kinds of addition would be useful. Leave room for an unexpected proposal to alter later plans. If every accepted idea requires rewriting an enormous outline, the plan is too brittle; if nothing can be assessed against it, the plan is too vague. Assign responsibilities without making silos Name who coordinates the outline, continuity, character voice, visual material and final assembly. Coordination means keeping a question moving, not owning every idea in that area. Give each role a clear remit, a backup when somebody is absent and a point at which a decision returns to the whole group. Small teams may combine roles, but should still name the hat a person is wearing. Avoid dividing the story so completely that no one sees its whole shape. Build regular cross-reviews around transitions and consequences. A worldbuilding decision can alter character motivation; an illustration can reveal pacing or design problems in prose. Shared checkpoints let specialists challenge assumptions before their separate pieces become expensive to reconnect. Define how proposals become decisions Write down how an idea is proposed, discussed, accepted, revised or declined. Consensus can suit foundational choices but stall minor ones. A scene owner may decide local details after hearing objections, while the group reserves shared approval for premise, ending and irreversible character turns. Set a reasonable discussion window and explain what happens if somebody is unavailable; silence should not be mistaken for enthusiastic consent. Record accepted decisions with a short reason. The reason helps later contributors understand the purpose and suggest a better way to meet it. Keep unaccepted possibilities in a separate parking area, not mixed into canon notes. This distinction prevents an attractive brainstorm from quietly becoming a fact that half the team never approved. Maintain a living continuity record Track only facts that future work needs: chronology, locations, character knowledge, established rules, unresolved promises and the current status of decisions. Link to the source scene where possible. A concise record that people consult is more valuable than an encyclopaedia nobody can update. Give one person responsibility for spotting gaps, while allowing everyone to propose corrections. Schedule continuity checks at natural milestones. Look forwards as well as backwards: which promises still need payment, and which constraints will shape the next contribution? When facts conflict, first ask whether the difference can be meaningful perspective. If not, choose the version that best supports established story pressure, record the resolution and update affected work deliberately. Re-plan when the draft teaches you something A collaborative plan should change when the actual story becomes more interesting or more honest. At each milestone, compare the draft with its promises, not every early prediction. Preserve decisions that still create value, revise those blocking the emerging work and communicate the consequences before somebody drafts from an obsolete plan. Version the brief so old notes cannot masquerade as current instructions. Public INK projects offer examples of premises developing through staged contributions. Active projects may accept written or visual submissions; readers and contributors may support or vote where those options are enabled, and selected submissions may become canon. Browse to understand possible structures, not to assume acceptance. The planning method in this guide stands on its own whether you use a platform, shared documents or paper on a table. Run a planning review before drafting Ask each collaborator to explain the premise, the next major change and their own responsibility without reading the brief aloud. Differences reveal ambiguous language early. Walk one possible scene from proposal through approval, drafting, continuity checking and revision. If nobody knows who responds at a step, add a decision rather than more story detail. Confirm where the current brief and records live, and archive duplicates that could cause avoidable mistakes. Finally, test the plan for creative room. Each person should be able to name at least one consequential choice they are genuinely free to shape. Also test it for resilience: what happens if a scene fails, a contributor pauses or an accepted idea changes the intended ending? A useful plan supports the next decision and a reasonable change of course. Once it does those jobs, drafting will teach you more than another layer of prediction.