The Myth of the First Draft
"Just finish the first draft" assumes writing is linear. It's not: the writing process is exploratory, and your tools should reflect that.
“Just get the first draft done.”
It’s the most common piece of writing advice out there. “Power through, don’t edit as you go, get words on the page and fix them later.”
The problem is that writing doesn’t actually work like that.
The linear fallacy
The “first draft” model treats writing as if the hard part is execution, as if you already know what you want to say and you just need to, well, say it.
But anyone who’s written anything serious knows the opposite is true. You discover what you’re trying to say by writing. The act of putting a sentence down changes what the next sentence should be. A paragraph you write on page four can retroactively invalidate your thesis on page one.
Writing is really a search through possibility space, not a pipeline. And yet, every tool we use (Google Docs, Word, Notion, even plain text files) enforces the pipeline model. One document, one cursor, one sequence of words from top to bottom. Want to try a different direction? Copy-paste into a new doc. Or worse, delete what you had and hope you remember it later. Or scroll through “version history” hoping you’ll find what you need before it becomes a waste of time.
When the tool enforces linearity, linearity is what you get.
Exploration vs. commitment
What actually happens when experienced writers write is that they hold multiple possibilities in their heads simultaneously. This paragraph could go here, or maybe it belongs later. This argument works if I frame it this way, but there’s a stronger version if I restructure the whole piece. Good writers are constantly branching: they just have to do it mentally because their tools don’t support it.
The “just finish the first draft” advice is really saying: stop exploring and commit to a path. Sometimes that’s fine, and sometimes you do need to ship. But the advice has been elevated into a philosophy of writing itself, and that’s where it breaks down.
What if you didn’t have to choose?
The real unlock isn’t writing faster or forcing yourself through a linear draft. It’s being able to explore multiple paths at once without losing any of them. This matters especially for writing that demands precision: college application essays, short fiction, anything where every sentence carries weight.
Imagine being able to write a sentence, and then forking it into two or three different versions in parallel. Not as separate documents you have to juggle, but as branches of the same piece, visible and navigable, the way a developer might branch code.
That’s what I’m building with Quillium: a writing tool where exploration is a first-class operation rather than a workaround. You can fork any sentence or paragraph, follow divergent paths, and converge when you’re ready—or not. Every version stays alive, and nothing gets lost to the delete key.
The real advice
Here’s better advice than “just finish the first draft”: write more than one first draft. Explore the possibility space. Follow the thread that surprises you, not just the first one you found.
And if your current tool makes that hard—if it forces you into a single linear sequence and punishes you for changing your mind—maybe the tool is the problem.
I’m building Quillium for writers who think this way. If that sounds like you, join the waitlist.