Fast drafts expose the real problem: taste

Writing faster is having a moment.

There are sprints, timers, voice notes, ugly first drafts, and AI tools that can turn a few prompts into a page before your coffee cools. For writers who have spent years staring at a blank document, that speed can feel like a breakthrough.

Sometimes it is. A fast draft is better than an imaginary perfect one. Momentum helps you find the material you could not have planned from the outline.

But fast drafting has a useful side effect: it exposes the problem speed was hiding.

Once you can produce words quickly, the hard question is no longer how to make more of them. It is which ones deserve to stay.

That is a question of taste.

Speed solves a real but narrow problem

Many writers genuinely need help getting started. Perfectionism makes every sentence feel final. Self-editing interrupts the thought before it has a chance to develop. A rough draft can become so precious in the writer's mind that it never gets written at all.

Speed counters that. It gives you permission to make a mess. It lets you discover an example halfway through a paragraph or notice that your real argument is not the one you started with. It separates drafting from deciding.

That separation matters.

The mistake is assuming that faster production makes the whole writing process easier. It only makes one stage easier. It can even make the next stage harder, because now there is more material to judge.

You may have three openings instead of none. Ten plausible headings. A thousand words that are clean, grammatical, and almost entirely interchangeable with what anyone else could have written.

The blank page is gone. The editorial problem remains.

A draft is not an argument

This is especially obvious with AI-assisted drafting. A model can create a reasonable structure, list common advice, explain familiar terms, and keep adding polished paragraphs for as long as you ask it to.

What it cannot reliably do is know which observation is the reason the post should exist.

That choice requires context. It requires knowing what your reader has already heard, what you can actually support, what you care enough about to defend, and which detail makes the claim feel earned rather than assembled.

Consider two versions of a post about fast drafts. One says that writers should draft quickly, avoid perfectionism, and revise later. It is competent advice. It is also advice the reader has probably encountered many times.

The other says that fast drafts reveal a different bottleneck: once words are cheap, judgment becomes the scarce skill. That thought changes what belongs in the piece. It asks for examples about selection, not just productivity. It gives the conclusion somewhere specific to land.

The difference is not word count. It is taste.

Taste is not a mysterious gift

Calling it taste can sound vague or exclusionary, as if good writers are simply born with a private sense of what works. That is not useful.

Taste is a set of practical editorial judgments:

• Which claim is specific enough to be worth a reader's time?
• Which example proves the point instead of decorating it?
• Which sentence sounds polished but says nothing?
• Which familiar idea needs a sharper angle before you publish it?
• What can be removed without weakening the argument?

Those questions are learnable. They get easier with exposure to good work, with attention to real readers, and with feedback that names the actual problem in a draft.

They also take more than speed. A timer cannot tell you that the introduction promises too much. A generated outline cannot tell you that your strongest point appears once in paragraph seven and then disappears. Producing alternatives only helps if you can recognize the better one.

More output raises the bar for selection

When writing was slow, output often looked like the bottleneck. A person who could reliably finish an article each week had an advantage over someone who could not.

That advantage still matters. Publishing consistently is useful. But tools have changed the economics of competent text. A team can now create enough drafts, headlines, and social posts to fill a calendar with very little friction.

The new risk is mistaking abundance for quality.

If every idea becomes a draft and every draft becomes a publishable-looking page, someone still needs to decide what should not go out. That person protects the audience's attention. They protect the brand from saying the same thing everyone else is saying. They protect the writer from spending time improving a piece whose central thought was never strong enough.

Taste is not decoration at the end of the workflow. It is the filter that makes the workflow worth having.

Draft fast, then read with standards

There is no need to romanticize slow writing. Use the timer. Dictate the messy first pass. Let a tool help you surface possibilities. Get the raw material onto the page before you begin polishing it.

Then change jobs.

Read the draft as someone who did not write it. Ask what it is actually claiming. Find the paragraph that only repeats the setup. Circle the detail that makes the piece credible. Notice where the language becomes generic because the thought is still vague.

That is the part of writing that deserves more attention now.

Fast drafts are useful because they get you to the real work sooner. They reveal that writing is not mainly the ability to generate sentences. It is the ability to recognize which sentences carry a thought worth sharing.

In a world full of instant drafts, that ability is not less valuable.

It is the work.