Case Study 1: Breaking the Blank-Page Spiral

A composite, realistic scenario. The writer is fictional; the experience is universal.

The situation

Elena is a mechanical engineer, two years into her first job. She's good — she designs well, her analyses are sound, her teammates trust her numbers. Tonight she has to write a two-page summary recommending which of two suppliers her team should choose for a critical bearing component. The data is done. The decision is, in her head, obvious: Supplier B, despite costing more, because their tolerances are tighter and a failure here is expensive. Her manager needs the recommendation by 9 a.m.

It is now 9 p.m. Elena has had the document open for forty minutes. Here is what those forty minutes look like:

She types: "In order to determine the optimal supplier for the bearing assembly component, a comprehensive evaluation was performed across multiple criteria including but not limited to..." She stops. Reads it back. It sounds stiff and it's going nowhere. She deletes the whole line.

She types: "This memo summarizes our supplier evaluation." Too flat. Boring, she thinks. Delete.

She types: "After careful consideration of both suppliers..." No — careful consideration is filler, she can hear it. Delete.

Forty minutes. Three deleted sentences. A blank page. Elena is now convinced she's bad at writing, which is a strange thing to believe about yourself when you've just spent two weeks doing rigorous engineering analysis that nobody could fault. But the blank page feels like proof.

What's actually wrong

Elena's problem is not that she can't write. It's that she's doing two jobs at once and they're fighting. Every time she types a sentence, the editor in her head evaluates it instantly — stiff, boring, filler — and rejects it before she can write the next one. She is drafting and editing simultaneously, and the editing is strangling the drafting. This is the blank-page death spiral from §5.2: not an absence of ideas (she has the whole argument in her head), but a feedback loop where judgment kills generation.

The cruel part is that the standard keeps rising. Each rejected sentence makes the next one feel like it has to be even better to justify keeping it. By sentence three, she's effectively trying to write a perfect opening line on the first try — an impossible task that guarantees the freeze.

The intervention

Elena's deskmate, packing up to leave, glances at the blank screen and says something that sounds like nonsense: "Just write it badly. On purpose. I'm serious — write the worst version, don't fix anything, I'll see it tomorrow."

Elena is skeptical but desperate, so she tries it. She sets a timer for ten minutes and makes herself a rule: no backspace. Whatever comes out, stays. Here is what she produces:

ok recommendation is supplier B. why. B costs more, like 18% more per
unit, but their tolerance is +/- 0.005mm vs A's +/- 0.02mm which matters
a LOT for this bearing because [explain why - the load thing]. if this
bearing fails in the field its not a warranty swap its a whole assembly
teardown, way more expensive than the unit cost difference. A is cheaper
upfront but the risk isnt worth it. also B's lead time is actually better,
3 wks vs 5. so B wins on quality AND schedule, only loses on unit price,
and unit price is the thing that matters least here. manager cares about:
total cost of failure not unit cost, and hitting the launch. lead with
that. B. done.

It is, by any standard, a bad piece of writing. It has a note-to-self in brackets, no capital letters, and the word "thing" twice. But notice what just happened: in ten minutes, Elena went from a blank page to a complete argument. Everything the memo needs is in there — the recommendation, the reasoning, the cost-of-failure logic, the lead-time bonus, and even a discovery she made while writing: "manager cares about total cost of failure, not unit cost — lead with that." She didn't know she was going to frame it that way until the bad draft surfaced it. That's the Chapter 1 idea in action: the writing did the thinking.

The result

With a complete (terrible) draft in hand, the rest was almost easy, because now Elena was revising — reacting to existing words instead of summoning perfect ones from nothing. She spent twenty minutes restructuring (recommendation first, cost-of-failure logic second, the lead-time bonus third), filled in the bracketed [explain why], and cut the self-notes. Then ten minutes editing the sentences for the stiff, professional-but-clear tone her manager expected. Total time after the bad draft: about half an hour. She was done by 9:50 p.m. — having spent forty minutes producing nothing and fifty minutes producing a strong memo.

The memo her manager read the next morning opened: "Recommendation: Supplier B. They cost 18% more per unit, but that's the cheapest part of this decision." Her manager approved it in a two-line reply.

The lesson

Elena didn't get better at writing overnight. She changed when she let her editor into the room. The block wasn't a skill problem; it was a sequencing problem. The fix — permission to write badly, a timer, no backspace — cost nothing and took ten minutes, and it converted a paralyzing blank page into a draft she could shape.

The next time she had to write something hard, she didn't wait forty minutes for inspiration. She set a timer and wrote the worst version first, on purpose. That habit — draft fast, revise hard — is the difference between an engineer who dreads writing and one who just does it.

The takeaway in one line: Writer's block is the editor showing up during drafting. Send the editor away until there's a draft to edit, and the block dissolves.