How to Write a Story With Someone Else

A workable co-writing process from the first conversation to a revision that still feels like both writers' work. Begin with the story and the reason for sharing it Writing a story with someone else works best when you agree what you are making before deciding who writes each scene. Describe the premise in a few sentences, the intended form and length, the readers you have in mind and what each person wants from the experience. One writer may want a polished novella while the other wants a playful experiment. Neither aim is wrong, but an unspoken mismatch will surface whenever time or quality decisions become difficult. Turn that conversation into a short working brief. Include the emotional promise of the story, subjects either writer does not want to handle, the likely finish point and what ‘finished’ means. Treat the brief as a starting agreement rather than a cage. Its purpose is to make assumptions visible, so a later change can be discussed instead of feeling like a betrayal of an invisible plan. Premise, form and approximate scope The experience each writer hopes to have Content boundaries and non-negotiable story promises A realistic definition of a complete draft Choose a co-writing model deliberately There is no single correct way to share a manuscript. Alternating scenes gives each writer a clear turn, but can create awkward hand-offs. Scene ownership lets the person closest to a viewpoint draft that material. Role ownership might put one writer on dialogue and another on structure, although both still need permission to question the whole. Fully shared drafting can be energising for short passages but tiring as a default. Choose the lightest model that makes responsibility clear, then test it on a chapter or short sequence. Record who drafts, who reviews and who makes the final call when a passage cannot satisfy both people. You can mix models: one person might own a viewpoint while either writer may draft shared action scenes. A model is useful only while it reduces uncertainty, so revisit it when the story or somebody's availability changes. Agree what each person may change Co-writing becomes tense when editing permissions are vague. Decide whether a partner may correct small errors directly, reshape a sentence, move a scene or alter a character decision without asking. A practical ladder is to allow silent correction of obvious slips, use suggestions for voice-level changes and require discussion for plot, theme or irreversible character choices. The boundary matters more than the particular ladder. Keep disagreements attached to the work rather than the writer. State the effect you are trying to create, identify what the current passage does for you as a reader and offer options. If you remain divided, preserve both versions briefly and test them against the agreed story promise. A designated decision-maker for that scene, a cooling-off period or a small trial with a neutral reader can prevent an argument becoming a contest of persistence. Keep voice and continuity coherent A shared story need not hide every difference between its writers. Distinct viewpoint voices can be an advantage. Readers do, however, need stable facts, motivations and tonal expectations. Maintain a compact continuity record for names, chronology, setting facts, character knowledge and unresolved promises. Update it after decisions, not after every passing suggestion, or it will become another draft to maintain. For voice, collect a few positive examples of how each narrator observes, speaks and avoids speaking. Read hand-off scenes aloud and look for sudden changes in distance, rhythm or attitude rather than merely different word choices. During revision, assign one pass to continuity and another to prose. Trying to solve plot, voice and punctuation simultaneously makes it hard to know whether an edit improves the shared story or simply makes it sound more like one partner. Use a humane communication rhythm Set a rhythm that matches real availability: perhaps a weekly check-in, a clear hand-off message and a longer review at the end of each section. Say where work lives, how versions are named and how quickly feedback is normally expected. Silence should not automatically mean approval. Make explicit confirmation the rule for important changes and build enough time for a partner to respond without being permanently on call. Plan for missed dates before they happen. Agree how to flag a delay, when work may be reassigned and how to pause without blame. Changing health, work or caring responsibilities are not a moral failure. A smaller scope, slower schedule or clean pause often protects both the relationship and the story better than repeated emergency promises. If one person must leave, discuss what material remains in the working draft and how their contribution will be credited before carrying on. Revise without erasing either writer Start revision by reading the complete draft and agreeing the largest problems. Make structural decisions before polishing sentences that may disappear. Divide passes by purpose—story logic, character development, continuity, voice and line clarity—and name the person coordinating each pass. Coordination is not ownership: substantial changes should still follow the permissions you agreed at the start. Finish with a retrospective. Note which hand-offs worked, where decisions stalled and whether either person felt unheard. Keep the practices that helped and change the rest before another project. If you want to observe a different project structure, public INK projects can be read without an account; active projects may accept written or visual submissions, and support or voting may be available where enabled. Selected submissions may become canon, but participation does not promise selection or any particular outcome.