Rhimes Writing Process

Why your first draft always looks like it was written by committee

I spent three years trying to produce coherent long-form content without falling into the same structural traps. The breakthrough came when I stopped treating writing as a linear process and started mapping it as a series of revision passes. This isn't about talent or vocabulary. It's about separating the act of creation from the act of editing so thoroughly that each pass has a single, non-negotiable job. Most writers I talk to do everything at once. They compose a sentence, critique it immediately, rewrite it, second-guess the word choice, and move on. The result reads like a patchwork of competing voices. Your readers can feel the hesitation. The process I describe below fixes that by enforcing strict phase separation.

Getting started with Rhimes Writing Process

The Rhimes Writing Process breaks composition into four distinct passes. The first pass is pure dump. You write without stopping, without backspacing, without looking at what you've already produced. The goal isn't quality. The goal is volume. I usually hit 800 to 1,200 words in a single sitting, and most of it is garbage. That's the point. Pass two introduces structure. You take that raw material and carve it into sections with working headings. No polishing yet. Just organization. I keep my headings deliberately ugly because they're internal navigation aids, not reader-facing content. "This part explains X but needs more evidence" stays until pass three. Pass three is where most people fail. You edit for logic and flow only. Every sentence must survive a single test: does the next paragraph actually follow from this one? If not, you rewrite or cut. No word choice decisions. No tone adjustments. Just causal chain verification. This pass usually takes longer than you expect because human reasoning is full of hidden assumptions that don't hold up under scrutiny.

Pass four handles language. Now you care about rhythm, precision, and clarity. You read each sentence aloud. If you stumble, you rewrite. If you can replace three words with one without losing meaning, you do it. This is the only pass where beauty matters.

The edge case that broke me for two weeks

I encountered a specific problem with a client project last year that exposed a flaw in the basic Rhimes Writing Process framework. The issue involved technical documentation for an API where the dependency graph had circular references. My first draft was logically coherent but technically misleading because I wrote about the modules in alphabetical order rather than dependency order. The workaround was adding a fifth pass specifically for technical content: verify that every concept is introduced only after all its prerequisites have been defined. I built a quick dependency checker script that flagged out-of-order references. This added about 20 minutes to the process but eliminated an entire class of errors that would have required a complete rewrite later. Not all content needs this extra pass. Fiction, opinion pieces, and narrative non-fiction work fine with the original four. The dependency check matters primarily for technical writing where concepts build on each other in non-linear ways.

What beginners consistently get wrong

The biggest mistake is merging passes. Writers think they can edit for logic and language simultaneously. They can't. Each cognitive mode uses different neural pathways, and switching between them creates what I call revision drift. You end up with paragraphs that are grammatically perfect but logically incoherent, or vice versa. A second common pitfall is spending too long on pass one. The dump phase should feel uncomfortable. If you're producing polished prose on the first pass, you're being too careful. The raw material needs to be messy. I time my dumps at 20 minutes for short pieces and 45 minutes for long ones. Going longer doesn't increase quality. It increases the chance you'll start self-editing mid-stream and defeat the purpose entirely. There's also a misconception that the Rhimes Writing Process works the same way for every writer. It doesn't. Some people need three dump phases before they have enough material. Others can structure on the fly and barely need pass two. The framework is rigid, but the time allocation is flexible. Start with the defaults I describe here and adjust after you've done five complete cycles.

When this approach fails

The Rhimes Writing Process is not universal. It assumes you have time for multiple passes. If you're producing content under deadline pressure, the overhead of four separate drafts may be prohibitive. In those cases, a hybrid approach works better: dump, then structure and edit in a single pass. You lose some coherence, but you gain speed. The method also struggles with highly collaborative content. When multiple people contribute, the phase separation becomes difficult to enforce. I've seen teams try to apply this to group projects and end up with conflicting revision histories that took longer to reconcile than the original content. For those situations, I recommend using version control with clear commit messages for each phase. Document which pass each version represents. This doesn't solve the coordination problem, but it makes the chaos traceable.

Measuring whether it's working

You'll know the Rhimes Writing Process is taking effect when your revision time decreases relative to your drafting time. Initially, pass three and four will dominate. After a dozen cycles, you should spend roughly 30 percent of your total time on passes three and four combined. If you're still doing heavy language work in pass four, you leaked editing into earlier passes. Another signal is reader feedback. Coherent writing produces a specific kind of response. Readers finish your content without feeling like they had to re-read paragraphs to understand them. They may disagree with your conclusions, but they won't question whether they understood your argument. That distinction matters more than you think. I track my own progress by measuring time per word across passes. My current average is 8 minutes per 1,000 words for pass one, 12 minutes per 1,000 words for pass two, 20 minutes per 1,000 words for pass three, and 15 minutes per 1,000 words for pass four. These numbers vary by content type. Technical writing skews heavier on pass three. Narrative writing skews heavier on pass four.

A note on tools

Software doesn't replace discipline, but the right tools reduce friction. I use a simple text editor with no formatting capabilities for pass one. The lack of styling forces you to focus on content. For passes two through four, I switch to a word processor with outlining features. The outline view makes structural problems visible immediately. Version control is essential. Commit after each pass. Label commits clearly: "pass one dump", "pass two structure", "pass three logic", "pass four language". This creates a recovery path if you merge phases accidentally and need to restart a clean pass. Some writers prefer specialized apps. I've tried them. They don't improve the fundamental process. They change the interface. If a tool helps you stay in the right cognitive mode, use it. If it adds steps, abandon it. The Rhimes Writing Process is about mental discipline, not software configuration.