Chapter 5: The Writing Process: Planning, Drafting, Revising, and the Myth of the Perfect First Draft

"The first draft of anything is shit." — widely attributed to Ernest Hemingway

Chapter Overview

Here is a scene you may recognize. It is 11 p.m. The report is due tomorrow. You have a blank document open and a cursor blinking at the top of the page. You type a sentence. You read it back. It is bad, so you delete it. You type a slightly different sentence. You read it back. It is also bad, so you delete it too. Forty-five minutes pass and the page is still blank. You are not lazy and you are not stupid — you know this material cold. So why can't you write a single sentence you're willing to keep?

You can't keep a sentence because you are trying to write it and judge it in the same instant, and those are two different jobs that interfere with each other. Composing wants speed, momentum, and permission to be wrong. Judging wants to stop, scrutinize, and reject. Run them at the same time and they cancel out — the result is a blank page or, worse, a page you bled over for three hours that still isn't good. This chapter is about pulling those jobs apart. The professional writers you admire are not faster typists or more gifted stylists than you. They have a process: a set of distinct stages, done in order, where each stage is allowed to do its own job without the others getting in the way. That process is the single most teachable, most transferable, most immediately useful thing in this book.

In Chapter 1 you saw the book's central claim: writing is not the step where you record finished thoughts — writing is how the thoughts get finished. That claim has a direct consequence for how you should work. If the page is where thinking happens, then your first pass across the page is thinking-in-progress, and thinking-in-progress is messy by definition. The mess is not a failure of the draft. The mess is the point of the draft. By the end of this chapter you will be able to take any document this book asks you to write — a report, an email, a README, a proposal — and move it through a repeatable workflow that gets you from a blank page to a strong final draft without the 11 p.m. paralysis. This is the chapter that closes Part I, and it ties the philosophy of the first four chapters to the hands-on practice of everything that follows. The one idea to carry out of it is the chapter's threshold concept: revision is the work, not cleanup.

In this chapter, you will learn to:

• Run a document through five separate stages — plan, draft, revise, edit, proofread — instead of trying to do them all at once.
• Cure writer's block by giving yourself permission to write a bad first draft on purpose.
• Tell the difference between revising (the big structural moves) and editing (the surface polish), and stop skipping the one that matters most.
• Plan a real document with a purpose statement, an audience note, and an outline before you write a word of prose.
• Build a writing schedule with milestones and feedback points that survives contact with a real deadline.

📘 Business/Professional track: §5.1–5.4 and the Project Checkpoint are your core. The five-stage process maps directly onto emails, memos, and proposals — the work just gets shorter, not different. 📗 Software/CS track: the same process governs a README or a design doc; pay attention to §5.5 on managing projects, which is where docs die (started, never revised). 📕 Engineering/Science track: everything here applies, and §5.4 on revision vs. editing is the foundation for the deep techniques in Chapter 12.

5.1 Nobody Writes Well on the First Try

Let's start by killing a myth, because it is doing you real damage. The myth is that good writers sit down, think for a moment, and produce clean prose in one pass — and that your own ugly first attempts are evidence you're not a real writer. Both halves are false.

Watch what an experienced writer actually does. Anne Lamott, in Bird by Bird, devotes a whole chapter to what she calls "shitty first drafts," and her claim is blunt: nobody she knows, including the writers whose finished work looks effortless, gets it right the first time. The finished work looks effortless because of the drafts you never saw, not in spite of them. The polished article you admire had an embarrassing first version. The crisp two-paragraph email that landed perfectly was, in someone's drafts folder, a rambling six-paragraph mess that got cut in half. You are comparing your behind-the-scenes to everyone else's final cut, and that comparison is rigged.

This is so consistent across the writing-craft tradition that it functions as folk wisdom: all first drafts are bad. Treat that as a working assumption, not an insult. It is one of the most liberating sentences in this book, because it removes the impossible standard you've been holding yourself to. You are not failing when your first draft is bad. Your first draft is supposed to be bad. A bad first draft means the system is working: you got words out of your head and onto the page, where you can finally see them, fix them, and make them good.

Consider what the first draft is actually for. It is not for your reader — your reader will never see it. It is not for your boss, your professor, or your reviewers. The first draft has exactly one audience: you. Its job is to externalize the half-formed thoughts in your head so that you can look at them from the outside and discover what you actually think. (That's the Chapter 1 thesis in operation — writing as thinking, not transcription.) When you understand that the first draft is a private thinking tool with an audience of one, the pressure that causes writer's block evaporates. Of course it can be rough. Nobody's watching.

🔄 Check Your Understanding Your colleague says, "I'm a bad writer — look how rough my first drafts are." Using the idea from this section, what's wrong with her reasoning?

Answer

She's mistaking a universal feature of writing for a personal failing. Rough first drafts are what everyone produces, including excellent writers — the roughness is evidence the process is working, not that the writer is bad. What distinguishes strong writers is not cleaner first drafts; it's that they revise. She's judging her hidden first draft against other people's polished final drafts, which is not a fair comparison.

The cost of believing the myth

Believing in the perfect first draft is not a harmless little misconception. It produces three specific, expensive failures.

It causes writer's block. If you believe the words should come out right the first time, then every imperfect sentence feels like proof that you can't do this — so you freeze. The blank page is not a thinking problem; it's a permission problem. You haven't given yourself permission to be bad on the way to being good.

It causes the death-march draft. Some people don't freeze; they grind. They polish sentence one until it gleams before they'll allow themselves to write sentence two. This feels productive — look, every sentence is perfect! — but it's the slowest possible way to write, and it's brittle. When you discover in paragraph nine that the whole piece is structured wrong (and you will discover this, because you can't see the structure until it exists), every one of those gleaming sentences has to be torn out. You polished the furniture before checking whether the house was on fire.

It causes the unrevised submission. This is the most common and the most damaging. Because writing the first draft was so painful, you can't bear to look at it again, so you fix the typos and hit "send." First-draft-as-final-draft is why so much technical writing is mediocre: not because the writers lacked skill, but because they shipped the thinking-in-progress version and skipped the stage where it would have become good.

Here is the same idea shown three ways, so you can feel the difference the process makes. Imagine you need to explain, in a status email, why a project slipped two weeks.

THE FROZEN NON-DRAFT (what perfectionism produces):

[cursor blinking on a blank line]
[you've typed and deleted "I wanted to update you on..." four times]
[nothing has been written]
[it is now 40 minutes later]

You can't ship a blank page. Perfectionism didn't make the writing better — it prevented the writing. Now watch what happens when you give yourself permission to be bad:

THE FAST, MESSY FIRST DRAFT (write everything, judge nothing):

ok so the project is late. why. the API thing took way longer than
we thought because the vendor docs were wrong and we had to reverse
engineer the auth flow which was like 5 days of nobody's fault really.
also QA found a thing in the export that we had to fix. net net we are
2 weeks behind. new date is the 28th. i think we're fine after this,
the hard part is done. should i tell them the hard part is done? yes.
lead with that maybe. they care about: is it still happening (yes) and
when (28th) and is it going to slip again (no, here's why).

That is not a good email. It has lowercase sentences, a note-to-self in the middle of it, and a question the writer is asking themselves. It would be a small disaster if you sent it. But it took ninety seconds, it is complete, and — critically — it contains everything the real email needs, including a discovery the writer made while drafting: "lead with the hard part being done." Now there is something to revise. Watch:

THE REVISED DRAFT (now we do the real writing — restructure, cut, sharpen):

Subject: Project X update — back on track, new date Mar 28

Hi team,

Short version: the hard part is done, and we're targeting March 28.

We hit two delays. The vendor's API documentation was wrong, so we
spent about a week reverse-engineering their auth flow. Separately,
QA caught a bug in the data export, which we've since fixed. Together
those put us two weeks behind the original date.

I don't expect further slippage. Both issues were front-loaded
unknowns, and the remaining work is routine. I'll send a confirmation
the week of the 24th.

— Sam

Why the final version works: it leads with what the reader cares about most (still happening, new date), groups the two delays cleanly, and answers the unspoken question — will it slip again? — before anyone has to ask. None of that polish was possible from a blank page. It was only possible because there was a messy draft to react to. Draft fast, revise hard. That single phrase is the engine of this entire chapter, and you just watched it run.

💡 Tip: When you're stuck, lower the bar on purpose. Tell yourself, out loud if you have to: "I am now going to write the worst version of this." It works because it removes the standard that was freezing you. You can't fail to write a bad draft — and a bad draft is all you need to start.

5.2 The Five Stages — and Why Separating Them Works

The cure for almost every writing problem in this chapter is the same move: stop doing everything at once. Writing feels like one big undifferentiated task ("write the report"), and that framing is exactly what makes it overwhelming. In reality, finishing a document requires five different kinds of mental work, and several of them actively interfere with each other when you try to run them simultaneously. Separate them and each one becomes manageable.

Here are the five stages. Read them as five distinct jobs, each with a different goal, a different mindset, and a different question it answers.

The order matters and the separation matters even more. Look at what's really going on: stages 1–2 are about generating, and stages 3–5 are about judging. Generating and judging are opposite mental motions. Generating says "yes, and" — keep going, get it down, don't stop. Judging says "no, wait" — stop, look closer, reject what's weak. The reason a blank page is so hard is that you're trying to do both at once, and they cancel. Drafting with your editor switched on is like driving with one foot on the gas and one on the brake. The engine roars, the car barely moves, and you burn out.

🚪 Threshold Concept: Revision is the work, not cleanup. Before this chapter, you probably thought of writing like this: the real work is producing the words, and revision is a quick tidy-up at the end — fix typos, maybe smooth a sentence, done. After this chapter, the model flips. Producing the first draft is the easy, fast part. Revision is where the document actually becomes good. The first draft does not exist to be your final product; it exists to be changed. Once you internalize this, your whole relationship to writing changes: you stop fearing the blank page (because the draft is disposable), you stop polishing prematurely (because it's all going to be reworked anyway), and you start budgeting real time for the stage that matters. Writers who get this produce dramatically better work than writers who don't — not because they're more talented, but because they spend their effort where it pays off. This is a one-way door. Once you've seen writing this way, you can't unsee it.

Why doing all five at once causes writer's block

Let's make the mechanism concrete, because understanding why the separation works is what makes you actually do it.

When you try to draft and edit simultaneously, here's the loop you fall into. You write a few words. Your editor-brain immediately evaluates them and finds them lacking (of course it does — they're three words of a first draft). The negative judgment kills your momentum. You delete. You try again, slightly differently. Same verdict. Delete. Each cycle, the standard creeps up ("the last attempt was bad, so this one needs to be really good"), which makes the next attempt even more likely to be judged a failure. That's writer's block: not an absence of ideas, but a feedback loop in which the judging brain strangles the generating brain before it can produce anything to judge.

Now separate them. In the draft stage you make a deal with yourself: no judging allowed. The editor is benched. Anything that comes out, stays — for now. With the brake released, the words flow, because the only job is to get them down. The draft will be bad, and that is fine, because you have also scheduled a revise stage and an edit stage whose entire purpose is to fix bad drafts. You're not lowering your standards. You're deferring them to the stage where they belong. The editor isn't fired; the editor just isn't allowed in the room until there's a complete draft to work on.

This is the most important practical insight in the chapter, so let me state it as plainly as I can: writer's block is usually an editing impulse arriving during the drafting stage. The fix is not to think harder or wait for inspiration. The fix is to tell the editor, "Not yet. Your turn is coming. Sit down."

🧩 Productive Struggle Before you read the next paragraph, try to predict: of the five stages, which one do you think most people skip entirely, and which one do they spend too much time on relative to its value? Jot down your guess and your reasoning.

One useful way to think about it

Most people skip revision (stage 3) — they go straight from drafting to editing, fixing commas in sentences that should have been deleted or moved. And most people overspend on editing/proofreading (stages 4–5) relative to its payoff, because surface polish feels like progress and is psychologically safer than the harder structural questions revision forces you to face. The result is a beautifully proofread document that's organized all wrong. If your guess was different, that's fine — the point is that the stages are not equally valued by most writers, and the mismatch (skipping the high-value stage, over-investing in the low-value one) is exactly the problem this chapter is fixing.

You don't have to be rigid about it

A fair objection: real writing isn't this tidy. You're drafting and you realize the structure is wrong — do you really have to wait until the "revise stage" to fix it? No. The five stages are a discipline, not a prison. Two refinements keep them practical:

First, the stages loop. You might draft a section, revise it, draft the next, revise the whole thing, then loop back to draft a new section you realize is missing. The order is a default sequence, not a one-way conveyor belt. What matters is that at any given moment you know which job you're doing, and you're not trying to do two at once.

Second, capture without stopping. When you're drafting and a structural idea hits you ("this whole section should move to the end"), don't switch into revise-mode and start moving things — that breaks your drafting momentum. Instead, leave yourself a note in brackets — [MOVE THIS TO END] — and keep drafting. You've captured the insight without context-switching. When you reach the revise stage, your draft is already dotted with your own instructions.

🔍 Why Does This Work? Why does separating "generating" from "judging" actually unlock writing, when it seems like it should just slow you down by making you do two passes instead of one? Think about it before reading on.

The deep reason is cognitive load. Composing a sentence and evaluating a sentence are both demanding tasks, and running them together means your working memory is split — half of it generating, half of it critiquing — so neither runs well. It's like trying to brainstorm and fact-check in the same breath: the fact-checking shuts down the brainstorm. Separating them lets you bring full attention to one mode at a time. The "two passes" feel slower but are actually far faster, because a focused generating pass plus a focused judging pass beats an infinite loop of half-generating, half-judging that never completes. You're not adding work; you're removing a traffic jam.

[📍 Good stopping point — you've got the core model. The next sections go stage by stage.]

5.3 Stage 1 — Planning: Decide Before You Write

The biggest mistake new writers make is starting at the keyboard. Planning is the stage that prevents you from drafting confidently in the wrong direction for three pages before you realize it. It does not have to be elaborate. For a short email, planning is fifteen seconds of thought. For a thesis, it's weeks. But it always answers the same three questions, and it always happens before you draft.

The purpose statement: one sentence, before everything

Before you write anything, finish this sentence: "After reading this, the reader will ___." That blank is your purpose, and stating it in one sentence does more to focus a document than any other single habit.

Watch the difference vagueness makes:

❌ Vague purpose: "I'm writing a report about the database migration."

That's a topic, not a purpose. A topic tells you what the document is about; it tells you nothing about what it should do. With only a topic, you'll wander — you'll include everything you know about the migration because you have no test for what belongs.

✅ Sharp purpose: "After reading this, my manager will approve the three-day maintenance window I need to migrate the database, because she understands the risk of not migrating."

Why it's better: now you know your reader (your manager), your goal (approval of a specific request), and your argument (the risk of inaction). Every paragraph can be tested against that sentence: does this help her approve the window? The deep technical details of the migration script? Cut them — they don't serve the purpose. The one-line risk of staying on the old version? Front and center — it is the purpose. A sharp purpose statement is a decision-making machine. It tells you what to put in and, just as importantly, what to leave out.

✏️ Try This: Take any document you currently have to write. Before reading further, write its purpose as a single sentence in the form "After reading this, [reader] will [do/understand/decide] ___." If you can't finish the sentence, you've just learned something important: you don't yet know what the document is for, and no amount of drafting will fix that. Figure out the purpose first.

This is also where the threads of Part I converge. The purpose statement forces you to name your audience (Chapter 2) and gives you the test you'll apply for clarity (Chapter 3) — the "so what?" test in Chapter 3 is really just "does this sentence serve the purpose?" asked at sentence scale. Planning is where audience, clarity, and structure stop being separate lessons and become one decision.

The audience note: who reads this, and what do they know?

You met audience analysis in Chapter 2; in the planning stage you put it to work in thirty seconds. Jot down three things about your reader before you draft: what they already know (so you don't over-explain or under-explain), what they want from this document (the question they're really asking), and how they'll read it (start to finish? scan for one number? skim on a phone?). These three facts shape everything — your vocabulary, your structure, your length. The same migration report written for your manager (wants the risk and the cost) and for a fellow engineer (wants the rollback plan and the schema changes) are two different documents, and the planning stage is where you decide which one you're writing.

The outline: a map you can rearrange before it costs anything

An outline is a list of the points you'll make, in the order you'll make them — built before you write the prose. Its superpower is that it's cheap to change. Moving a bullet in an outline takes one second. Moving three polished paragraphs to a different section takes twenty minutes and breaks all the transitions. Outline first, and you do your structural experimentation when it's free.

Outlines come in different weights; match the weight to the document.

A LIGHT OUTLINE (for an email or a one-page memo) — three lines:
  - Lead: we're 2 weeks late, but the hard part is done. New date: 28th.
  - Why: vendor API docs were wrong (~1 wk); QA bug in export (fixed).
  - Reassure: no further slippage expected; confirmation coming the 24th.

A HEAVIER OUTLINE (for a report or proposal) — nested points:
  1. Problem: our database version goes end-of-life in 90 days
     - no more security patches after that date
     - one known unpatched vulnerability already
  2. Request: a 3-day maintenance window, weekend of the 14th
  3. Risk of NOT migrating (the real argument)
     - compliance exposure
     - cost of an incident vs. cost of the window
  4. The plan (brief — detail goes in an appendix)
     - tested rollback; staging dry-run already done
  5. What I need from you: approval by Friday

Notice the heavier outline already encodes a structural decision: the risk of not migrating comes before the technical plan, because that's the part the manager cares about. You made that call in the outline, where reversing it costs nothing — not in the draft, where it would cost you an afternoon.

Some people don't outline well in the abstract, and there's a legitimate alternative: talk it out. Explain what you're going to write to a colleague, or to a voice recorder, or to a rubber duck on your desk. Speaking forces linear order and exposes gaps ("wait, why does that part come first?") that you can't see while staring at a blank document. Then write down the order you just spoke. For many people, a five-minute spoken explanation is the outline, and it doubles as a check on whether you actually understand the thing — which, per Chapter 1, is the whole point.

🔄 Check Your Understanding Why is it cheaper to fix a structural problem in the outline stage than in the draft stage?

Answer

Because an outline is made of short, unpolished points. Moving or cutting a one-line bullet costs you nothing — no transitions break, no carefully crafted sentences get destroyed. In a draft, the same structural change means rewriting paragraphs, repairing the transitions between them, and re-checking the flow. You do your structural experiments when they're free (the outline) so you're not paying full price for them later (the draft). This is the same logic as "measure twice, cut once."

5.4 Stages 2–5 — Draft Fast, Then Revise Hard

With a plan in hand, the remaining four stages each get their turn. The single most important thing about them is that revision is not the same as editing, and confusing the two is why most documents stall at "okay" instead of reaching "good."

Stage 2 — Drafting: write fast, silence the critic

Drafting has one rule: keep your hands moving. You have a plan and an outline; now your only job is to convert that outline into prose as fast as you can, without stopping to evaluate, fix, or polish anything. Write the bad sentence. Leave the typo. Use a placeholder when you can't find the right word — [some better word for "thing" here] — and keep going. If you can't remember a number, write [NUMBER] and move on; you'll fill it in later. The goal of this stage is a complete bad draft, not a partial good one. A complete bad draft can be revised. A perfect first paragraph with nothing after it cannot.

The enemy here is the inner critic — the voice that reads each sentence as you write it and tells you it's not good enough. The inner critic is not your enemy in general; you'll need it desperately in stages 3–5. But during drafting it is poison, because its job (judging) is the opposite of this stage's job (generating). Bench it. Some concrete tactics for silencing it:

• Write to a timer. Set fifteen or twenty-five minutes and commit to writing without stopping until it goes off. The constraint makes hesitation feel expensive, which is exactly the point.
• Dim the screen or close your eyes. If you can't see what you've written, you can't edit it. Some writers literally turn the monitor brightness down to draft.
• Draft out of order. Nothing requires you to write the introduction first. Introductions are notoriously the hardest part to write because you don't yet know what you're introducing. Start with the section you understand best, build momentum, and write the intro last — when you finally know what the document says.
• Talk-to-text. If the keyboard freezes you, dictate. Speaking bypasses the editor for a lot of people. The transcript will be messy; that's a first draft, which is what you want.

If you remember one phrase from this section, make it Lamott's permission slip: the shitty first draft. You are allowed — encouraged, required — to write badly here. The badness is temporary and it's productive. Get it down.

Stage 3 — Revising: the big moves (this is the work)

Now switch hats completely. The generating brain is done; the judging brain takes over. Revising is re-seeing the whole document (that's literally what the word means: re + vision). You are no longer asking "is this sentence good?" — you're asking the big questions:

• Is the content right? Did I include what the reader needs? Did I include things they don't need that I should cut? Are there gaps — questions a reader will have that I never answered?
• Is the structure right? Is this in the order the reader needs (which, per Chapter 4, is usually not the order I discovered it in)? Does the most important point come early enough? Should these sections be reordered?
• Does it serve the purpose? Pull up your one-sentence purpose statement from the planning stage. Does the document accomplish it? Does every section earn its place against it?

Revising means making big moves: deleting whole paragraphs, merging two sections into one, moving the conclusion to the top, realizing you buried the lede and digging it out, discovering the document is missing an entire section and writing it. This is uncomfortable work, because it means admitting that real chunks of your draft are wrong, and tearing them out. That discomfort is exactly why people skip revision and jump to editing — fixing commas feels safe; deleting three paragraphs you spent an hour on feels like loss. But here's the truth that the threshold concept points at: the gains from revision dwarf the gains from editing. A document with the right content in the right order but a few clumsy sentences communicates. A document with beautiful sentences in the wrong order does not. Revise first. Always.

Stage 4 — Editing: the surface (sentence by sentence)

Now — and only now, with the structure settled — you sharpen at the sentence level. This is where everything from Chapter 3 comes in: cut the bloat, kill the nominalizations, prefer the strong verb, choose active voice unless passive earns its place, trim every sentence to the fewest words that carry the meaning. Editing is line-by-line craft. It matters enormously — but it matters after revision, because there is no point polishing a sentence you might delete. Editing a paragraph before you've decided whether the paragraph belongs is wasted labor, and it's worse than wasted: once a sentence is beautifully edited, you become attached to it, and that attachment makes you reluctant to cut it even when the structure demands it. Edit late so you don't fall in love with words you'll need to kill.

This is the distinction the whole chapter turns on, so let me draw it sharply:

If you take nothing else from §5.4, take this: revising changes what the document says and how it's organized; editing changes how each sentence reads. Do them in that order, in separate passes, and do not let yourself edit until the revising is genuinely done.

⚠️ Warning: The single most common process failure in technical writing is skipping revision and calling editing "revision." People run spell-check, fix a few sentences, and believe they've revised. They haven't — they've edited. If you never asked "is this the right content in the right order?", you didn't revise. The tell: if you didn't cut, move, or add anything substantial, you skipped the stage that matters.

Stage 5 — Proofreading: the final surface pass

Proofreading is the last, narrowest pass: catching the errors that survived everything else. Typos. A figure labeled "Figure 3" that's actually the second figure. A broken link. A number that says 2023 when you meant 2024. A "their" that should be "there." Proofreading is not editing — you're not improving sentences, you're checking for things that are broken. It deserves its own pass because the mindset is different: slow, literal, suspicious of every surface detail, reading what's actually on the page rather than what you meant to put there.

A few tactics that catch far more errors than re-reading on your screen:

• Read it aloud. Your ear catches what your eye skates over — a missing word, a sentence that doesn't end, a clumsy repetition. This is the single highest-yield proofreading technique.
• Change the format. Print it, or change the font, or paste it into a different app. Your brain has memorized the document in its current form and auto-corrects errors as it reads. Breaking the visual pattern forces you to actually see the words.
• Read it backwards, sentence by sentence. Start at the last sentence and move up. This strips away the meaning (which is what lets your brain autocomplete) and leaves only the mechanics, so typos pop.
• Get a fresh pair of eyes. You cannot fully proofread your own work, because you know what it's supposed to say. Someone seeing it cold will catch errors you're literally unable to see.

🔄 Check Your Understanding A teammate says, "I revised my report — I read through it twice and fixed all the typos and a bunch of awkward sentences." What stage did they actually do, and what did they skip?

Answer

They edited and proofread — they worked at the sentence and surface level (awkward sentences, typos). They did not revise: nothing in their description involves cutting, moving, or adding content, or questioning whether the structure serves the reader. The giveaway is that they changed how sentences read but never touched what the document says or the order it says it in. They skipped the highest-value stage and mislabeled the others as it — the exact failure the chapter warns about.

5.5 Managing a Real Writing Project: Deadlines, Milestones, and the Procrastination Trap

Knowing the five stages is not the same as finishing on time. A real document lives inside a deadline, and the deadline is where good intentions go to die. This section is about the project-management layer that sits on top of the writing process — the part that turns "I know how to write" into "I shipped it, and it was good."

Schedule backward from the deadline, and protect the revision time

The classic failure mode is to spend all your available time drafting, hit the deadline gasping, and submit an unrevised first draft. You ran out of road for the stage that mattered. The fix is to schedule backward from the deadline and reserve revision time first, before drafting can eat it.

A useful default split for a document of any size: spend roughly the first third of your time planning and researching, the middle third drafting, and the final third revising, editing, and proofreading. Most people instinctively allocate something like 5% / 90% / 5%, which is exactly backward — they under-plan, over-draft, and starve revision. If you do nothing else, protect the final third. Put it on the calendar as a hard block and defend it like a meeting you can't move.

EXAMPLE: a report due in 9 days. Schedule backward.

  Days 1–3   PLAN     audience note, purpose statement, outline, gather data
  Days 4–6   DRAFT    fast, ugly, complete — no editing allowed
  Day 7      REVISE   the big moves: structure, gaps, order. Send to a colleague.
  Day 8      (wait)   let it sit; incorporate the colleague's feedback
  Day 9 AM   EDIT     sentence-level, then PROOFREAD aloud. Submit by noon.

The "let it sit" on day 8 is not slack — it's a technique. A draft you set down for a day comes back looking different, because you've lost the memory of what you meant to say and can finally see what you actually said. That gap is where you catch the problems you were blind to while writing. Build the gap into the schedule on purpose; it's free quality.

Break a big document into milestones

A 30-page document is terrifying as a single task and manageable as a set of milestones. Don't plan to "write the report"; plan to finish the outline by Tuesday, draft sections 1–3 by Thursday, draft 4–6 by Saturday, and so on. Milestones do three things: they make a huge task feel finishable, they give you early warning if you're falling behind (you'll miss a milestone long before you'd miss the deadline), and they let you start the slow social processes — like sending a draft for feedback — early, instead of all at once at the end.

Build in feedback loops early

Feedback is part of the process, not an optional extra at the end, and the most common feedback mistake is asking for it too late. If you send your document for review the night before it's due, you can't act on what you hear — you'll get good advice you have no time to use. Send a draft for feedback after the revise stage, while there's still time to make changes. And tell your reviewer what kind of feedback you want: "Is the structure clear and does it answer the right questions?" gets you useful structural feedback, whereas a bare "thoughts?" gets you a list of comma fixes on paragraphs you might delete. Direct your reviewers to the stage you're actually in. (Chapter 12 goes deep on giving and receiving feedback well; for now, just get it early.)

Procrastination and perfectionism — same enemy, two faces

The two great threats to finishing are procrastination and perfectionism, and the surprising truth is that they're usually the same problem in different costumes. Both come from the gap between the perfect document in your head and the messy reality of the page. Perfectionism says I won't put it down until it's perfect, so nothing ships. Procrastination says I won't start until I can do it justice, so nothing starts. Both are the perfect first draft myth doing its damage — and both have the same cure.

The cure is to make the first action small enough that the perfectionism has nothing to grab onto. You cannot procrastinate on a task that takes two minutes. So shrink it: don't sit down to "write the report," sit down to "write the worst possible first sentence" or "rough out three bullet points." The standard is so low that the resistance evaporates, and once you've started, momentum carries you. This is the whole reason the draft stage exists with its permission to be bad: a bad draft is unblockable, because there's no quality bar to clear. The shitty-first-draft permission isn't just kinder to yourself — it's the single most effective anti-procrastination technique in writing, because it removes the standard that was causing the paralysis.

💡 Tip: When you catch yourself procrastinating on a writing task, the question to ask is not "why am I so lazy?" (you're not). The question is "what's the smallest piece of this I could do badly in the next five minutes?" Then do that. Starting badly beats not starting, every single time.

🪞 Learning Check-In Part I is ending. Before you move into the building blocks of Part II, take five minutes to reflect honestly on your current writing process — the one you actually use, not the one you wish you used: - When you write something important, do you separate stages, or do you draft-and-edit at once (the blank-page death spiral)? Which of the five stages do you skip? - Be honest: do you revise — making real structural changes — or do you just edit and proofread and call it revision? - When does writer's block hit you, and looking at §5.2, what's actually happening in those moments? - What's one specific change to your process you'll commit to on your next document? Write it down. (A written intention is far likelier to stick than a vague one.) This is the metacognitive habit the whole book is trying to build: noticing how you work, so you can change it deliberately. Part I gave you the philosophy — audience, clarity, structure, process. Part II makes you good at the craft. Knowing your own starting point is how you'll measure the distance you travel.

📐 Project Checkpoint

Throughout this book you're building a Communication Portfolio — seven professional documents (a technical report, a proposal, user docs, a data memo, an email chain, a presentation, and a blog post) that, by Chapter 40, become evidence of what you can do. Part I has given you the foundations: why writing matters (Ch 1), how to read your audience (Ch 2), how to write clearly (Ch 3), and how to structure for the reader (Ch 4). Now you put the process to work to plan your first piece.

This checkpoint: produce a complete plan for your first portfolio document — the technical report. Don't draft it yet. Plan it, using the three planning artifacts from §5.3:

1. Choose your topic. Pick something you genuinely know — a project you've done, a system you understand, an experiment you ran, a tool you've built. The report will explain it to a defined reader. (Writing is thinking: if you don't understand it well, the report will expose that — which is useful, but pick something you can actually explain.)

2. Write the purpose statement as a single sentence: "After reading this report, [my specific reader] will [understand / decide / be able to] ___." Name a real, specific reader, not "the general public."

3. Write the audience note — three lines: what your reader already knows, what they want from this report, and how they'll read it (cover to cover, or scanning for specifics).

4. Build the outline — the major sections in the order your reader needs them (lean on Chapter 4's structural thinking). A nested outline of five to nine points is plenty.

5. Make a schedule. Even if it's a personal project with no external deadline, give yourself one. Block time for plan / draft / revise / edit-proofread, with the revision time protected. Write the dates down.

Save all five artifacts in a file called portfolio/01-technical-report/PLAN.md. You'll draft from this plan in a later chapter, and when you do, you'll be drafting fast — because the hard thinking will already be done. Next checkpoint: you'll draft the report from this plan, deliberately writing a fast, bad first draft, then revising it hard — practicing on your own work exactly the workflow this chapter taught.

5.6 Common Mistakes & Practical Considerations

The five stages are simple to state and surprisingly hard to follow, because old habits fight back. Here are the mistakes that actually happen, and the "it depends" cases.

Editing while drafting (the big one). You know you shouldn't, and you'll do it anyway, because the impulse to fix the bad sentence you just wrote is strong. The fix is mechanical, not motivational: write to a timer, dim the screen, use placeholders, and physically resist the backspace key. Make the bad-draft rule a hard rule for a fixed time block, not a vague intention.

Skipping revision and calling editing "revision." Covered above, and worth repeating because it's the most consequential error in the chapter. If you didn't cut, move, or add something substantial, you didn't revise. Build a separate revise pass into every important document and ask the structural questions explicitly.

Over-planning to avoid drafting. The mirror image of the death-march draft: some people outline forever because outlining feels safe and drafting feels exposed. An outline that keeps getting more detailed is often procrastination wearing a productive disguise. The outline is done when it shows the shape; if you're adding sub-sub-sub-bullets, you're stalling. Start drafting.

Confusing "let it sit" with "leave it forever." The 24-hour gap is a tool with a time limit. Setting a draft aside for a day sharpens your eye; setting it aside for two weeks usually means it's quietly dying. Build the gap into the schedule deliberately, then come back on schedule.

Treating the process as one-size-fits-all. A two-line Slack message does not need a purpose statement and an outline. The five stages scale: for a tiny message, planning is a half-second of thought, drafting is one pass, revision is a quick reread, and editing is fixing one word. For a thesis, each stage is days or weeks. The skill is matching the weight of the process to the stakes of the document — not skipping stages, but right-sizing them. Don't bring a thesis process to an email, and don't bring an email process to a thesis.

"But I write better under pressure." A common belief, usually false. What feels like "I do my best work the night before" is really "I only do work the night before, so I have nothing to compare it to." Under deadline pressure you draft once and submit — you literally cannot revise, because there's no time. You're not writing better under pressure; you're skipping the stage that would have made it better, and calling the result your best because it's your only. Real time pressure happens, and §5.5's backward scheduling is how you protect against manufacturing it yourself.

The collaborative wrinkle. When several people write one document (Chapter 23's territory), the stages get socially complicated: one person's "done drafting" is another's "ready to edit," and editing someone's prose before the team has agreed on structure causes friction and wasted work. The same rule holds, just out loud: agree on the plan and the structure as a group before anyone polishes sentences, so nobody edits a paragraph that's about to be cut.

Frequently Asked Questions

How do I get over writer's block?

Writer's block is almost always an editing impulse arriving during the drafting stage — you're trying to write and judge at the same time, and the judging shuts down the writing. The cure is to separate them: give yourself explicit permission to write a bad first draft, set a timer, and keep your hands moving without fixing anything. Lower the bar on purpose — tell yourself "I'm going to write the worst version of this." You can't fail to write a bad draft, and a bad draft is all you need to start. The polishing happens later, in stages you've scheduled for exactly that purpose. See §5.1 and §5.2.

What's the difference between revising and editing?

Revising works on the whole document — content and structure. It means cutting sections, reordering, filling gaps, moving the main point earlier: the big moves that change what the document says and in what order. Editing works at the sentence and word level — clarity, concision, grammar, tone. The simplest test: revising changes what you said and how it's organized; editing changes how each sentence reads. Do them in that order and in separate passes, because polishing a sentence you might delete is wasted effort. Most writers skip revision and do only editing, which is why their documents are well-proofread but poorly organized. See §5.4.

How many drafts should I write?

For anything that matters, at least two: a fast first draft to get the content out, and a revised draft after you've stepped back and reworked the structure — plus an editing and a proofreading pass on top. There's no magic number; the right question isn't "how many drafts" but "have I actually revised, or did I just edit the first draft?" A short email might need one quick reread; a report needs a genuine revision pass; a thesis chapter might cycle through many. Match the number of passes to the stakes.

How long should I spend planning before I start writing?

It scales with the document, but a useful default is to spend roughly the first third of your total time on planning and research, the middle third drafting, and the final third revising and polishing. Most people massively under-invest in planning and then draft in circles because they never decided what they were trying to do. For a short email, planning is fifteen seconds (who's reading this, what do I want them to do). For a report, it's writing a purpose statement, an audience note, and an outline before any prose. The planning isn't lost time — it's what lets you draft fast and straight. See §5.3 and §5.5.

Isn't all this process overkill for short documents?

The process scales down; it doesn't disappear. For a two-line message, planning is a half-second ("what do I want them to do?"), drafting is one pass, and "revising" is a quick reread before you hit send. The point isn't to bring a five-stage ceremony to every sentence — it's to never skip a stage that the document's stakes require. The skill is right-sizing: a thesis gets weeks per stage; an email gets seconds. Mismatching in either direction (an email-sized process on a thesis, or a thesis-sized process on an email) is the actual mistake. See §5.6.

Chapter Summary

Key Takeaways

• Nobody writes well on the first try. All first drafts are bad — including those of the writers you admire. The roughness isn't a personal failing; it's how writing works. What separates strong writers is not cleaner first drafts but the willingness to revise.
• Writing is five distinct jobs, not one. Plan, draft, revise, edit, proofread. They use opposite mental modes — generating (plan, draft) versus judging (revise, edit, proofread) — and running them together is what causes writer's block.
• Revision is the work, not cleanup. The first draft exists to be changed. The biggest gains come from the structural moves of revision (cut, reorder, fill gaps), not from sentence polish — yet revision is the stage most people skip.
• Revising ≠ editing. Revising reworks content and structure; editing sharpens sentences. Do them in separate passes, revision first, so you don't polish words you'll end up cutting.
• Plan before you draft. A one-sentence purpose statement, a three-line audience note, and an outline turn a blank-page ordeal into a fast, directed draft.
• Protect your revision time. Schedule backward from the deadline, reserve the final third for revising and polishing, and get feedback early enough to use it.

Action Items

1. On your next important document, write a one-sentence purpose statement before you draft a word.
2. Draft it fast and bad on purpose — timer on, screen dimmed if you must, placeholders welcome, no backspacing.
3. After a complete draft, do a separate revision pass: ask "right content? right order?" and make at least one big move (cut, move, or add a section).
4. Only then edit sentences, and only then proofread aloud.
5. Build a 24-hour gap into your schedule before the final pass.

Common Mistakes

Decision Framework: which stage am I in?

Spaced Review

A few questions reaching back, to strengthen retention.

1. (From Chapter 3) Editing is where you apply Chapter 3's clarity tools. Name two of them — specific moves you'd make to a bloated sentence — and say which writing-process stage they belong to.
2. (From Chapter 1) Chapter 1 argued that writing is thinking, not transcription. How does the "write a bad first draft" advice in this chapter follow directly from that claim? What does a first draft do for your thinking?
3. (From Chapter 4, bridging) Chapter 4 said structure should serve the reader, organized how they read rather than how you discovered the material. Which stage of the writing process is where you actually fix bad structure — and why is it the wrong job for the drafting stage?

What's Next

You've finished Part I. You now have the philosophy — writing is thinking, audience drives everything, clarity and structure serve the reader — and the process that turns that philosophy into finished documents. Part II: The Building Blocks zooms in to the craft itself, starting with Chapter 6: Sentences That Work, where you'll learn the sentence-level techniques that the editing stage relies on — the twenty errors that plague technical writing and how to fix them. Everything in Part II lives inside the editing stage you met here. And when you reach Chapter 12: Editing and Revision, you'll go deep on the revision and editing techniques this chapter introduced — turning the "big moves" of revision into a repeatable, learnable craft. The process is the frame; the next several chapters fill it in.

Practice: Exercises · Quiz Go deeper: Case Study · Case Study 2 Review: Key Takeaways · Further Reading