How to Write Faster Without Sacrificing Quality

Writing faster doesn't mean typing faster. I type around 85 WPM, which is decent but not exceptional. Yet I consistently produce more written output than colleagues who type 100+ WPM. The difference is everything that happens before and after the typing.

Why Most People Write Slowly

It's rarely a typing speed problem. Watch someone compose an email and you'll see the real bottlenecks:

1. Staring at the blank page wondering how to start
2. Editing while drafting — writing a sentence, deleting half of it, rewriting, deleting again
3. Searching for the right word instead of using a good-enough word and moving on
4. Re-reading the whole thing after every paragraph
5. Second-guessing tone — "Is this too formal? Too casual?"

Each of these behaviors individually seems small. Together, they turn a 5-minute email into a 20-minute ordeal.

The Separation Principle

The single most effective technique I've found: separate drafting from editing. These are two different cognitive tasks, and switching between them constantly is what kills your speed.

During Drafting:

• Write forward only. Don't go back.
• Use placeholder brackets for anything you're not sure about: [check exact number], [insert client name], [rephrase this later]
• Accept imperfect sentences. They'll get fixed in editing.
• Don't worry about paragraph structure. Just get the ideas down.

During Editing:

• Now go back and clean up
• Fill in placeholders
• Fix awkward phrasing
• Check tone and formatting
• Cut anything that doesn't earn its place

This feels wrong at first. You'll want to fix that typo you just made. Resist. The context switch from "generating ideas" to "polishing text" costs more time than you realize.

Pre-Built Structures

The blank page is the enemy. When you start with a structure, you skip the hardest part: figuring out what to say.

I maintain text expansion snippets for every type of writing I do regularly:

Email Structures

;email-update expands to:

Hi [name],

>

Quick update on [topic]:

>

What happened: [summary]

>

What's next: [next steps]

>

What I need from you: [ask, or "Nothing for now"]

>

[sign-off]

I fill in the brackets and I'm done. No staring at a blank compose window.

Document Structures

;doc-proposal gives me:

Background: [Why are we doing this]

>

Proposal: [What we should do]

>

Impact: [What changes and for whom]

>

Timeline: [When this happens]

>

Open questions: [What we still need to figure out]

Slack Message Structures

;slack-request expands to:

Hey [name] — I need [what you need], ideally by [when]. Context: [brief background]. Let me know if that timeline works or if you need anything from me first.

Every one of these saves me from the "how do I start this" paralysis.

The Good-Enough Vocabulary

Perfectionism about word choice is a massive time sink. Here's a liberating truth: in professional writing, clarity beats cleverness every single time.

Instead of spending 30 seconds searching for the perfect word:

• Use the first clear word that comes to mind
• If it's not quite right, bracket it: [better word for 'implement'] and move on
• During editing, you'll either find the right word instantly (because you're in editing mode now) or realize the original word was fine

Voice-to-Text as a First Draft Tool

For longer pieces of writing, I sometimes dictate a rough first draft. Speaking is typically 3-4x faster than typing, and for getting ideas out of your head, it works surprisingly well.

The output is messy — run-on sentences, tangents, filler words. That's fine. It's a draft. The editing pass cleans it up, and you've cut your drafting time by 60%.

Writing Speed by Type

Different types of writing have different optimization strategies:

Emails (target: under 2 minutes each)

• Use snippets for everything routine
• Keep to 5 sentences or fewer when possible
• One topic per email. Always.

Slack/Chat Messages (target: under 30 seconds)

• Front-load the ask or information
• Use snippets for common responses
• Skip greetings in thread replies

Documentation (target: outline in 5 min, draft in 20 min)

• Start with bullet points, expand into prose
• Use your doc structure snippets
• Write the introduction last (you'll know what to introduce after writing the body)

Reports (target: 30-45 min for a weekly report)

• Keep a running log during the week (snippet: ;weeklog)
• On report day, organize the log into your report template
• Most of the "writing" is actually just organizing notes you already captured

The Weekly Writing Review

Every Friday, I spend 10 minutes reviewing what I wrote that week:

• Were there any new patterns I should create snippets for?
• Did I struggle with any particular type of writing?
• What took longer than it should have?

This review has led to me creating snippets I never would have thought of proactively. Last month I noticed I was writing the same "here's how to access the shared drive" instructions in Slack three times a week. A 30-second snippet creation fixed that permanently.

Speed Benchmarks

After a few months of practicing these techniques, here's where I landed:

Writing Type	Before	After
Standard email reply	4-5 minutes	45 seconds
Weekly status report	35 minutes	12 minutes
Meeting notes	Real-time + 10 min cleanup	Real-time + 3 min
Slack response	1-2 minutes	15-30 seconds
Blog post draft	3 hours	90 minutes

The biggest gains came from snippets and the separation principle. Everything else was polish.

Writing faster isn't about rushing. It's about eliminating the friction between having a thought and getting it on the screen.