← All articles
Bigger Questions · 10 May 2026 · 6 min read

When AI Writes the First Draft

A few years ago, the first draft was the slowest thing in any creative or technical job. You sat with the empty document. You tried something. You crossed it out. The act of starti…

Editor''s hands cutting, arranging and refining plentiful rough printouts into one considered final page

A few years ago, the first draft was the slowest thing in any creative or technical job.

You sat with the empty document. You tried something. You crossed it out. The act of starting was the hardest, longest, and most expensive part of the work.

That has changed quickly. A capable AI assistant can produce a first draft of almost any kind of business writing, code, plan, or report in less time than it takes to read the brief. The blank page is no longer the bottleneck.

So what is?

The work shifts from writing to editing. From producing to deciding. From "can I make something" to "is this good enough, and if not, what would it have been?" Anyone who has used a current AI assistant to draft an email, a brief, a piece of code, or a marketing page knows the feeling. The output is usually fine. Plausible. Workable. Sometimes even quite good.

That is where judgement becomes the job.

A passable first draft can hide weak judgement

There is a subtle problem with a draft that looks fine. Rejecting it costs effort. Editing it costs effort. Accepting it costs nothing.

Under time pressure, "nothing" wins.

So the email goes out slightly off-tone but technically correct. The code gets merged because it works, even though it copies a pattern you would not have chosen. The page gets published where every section says something useful but nothing reads like you wrote it. The report gets signed off because it summarises the data faithfully, even though it missed the one observation that would have changed the meeting.

These are not catastrophic failures. They are the slow erosion of taste, voice, and decision quality. They are hard to point at because each individual draft was, in isolation, fine.

The cost shows up later, in averages. A team that has been quietly accepting fine-but-generic drafts for six months ends up with a brand that sounds like everyone else's brand, a codebase that looks like everyone else's codebase, and a set of decisions that feel slightly off from where they should be. Nobody can name the day it went wrong.

Good judgement matters more when drafts are cheap

When the draft is cheap, the work that is left is the work that requires knowing what good looks like.

That is what judgement is. Not opinion. Not preference. Not the founder's gut. Judgement is the practised ability to look at something plausible and recognise where it is wrong, in a way that someone with less context could not.

Judgement is acquired slowly: by doing the work yourself, by getting it wrong, by having someone with more experience point at the problem. It is the most expensive thing a small business owns, and it lives mostly in two or three people's heads.

When AI writes the first draft, those two or three people become essential at every step instead of just the final one. The work does not get easier. It gets more concentrated.

Three ways AI drafts weaken team judgement

In the run of work since AI assistants became part of daily life, judgement tends to slip in three places.

The first is volume. AI lets a small team produce more output. More output means more decisions per week. More decisions per week means each decision gets less attention. The team starts skimming what it should be reading. Skim-reviewed drafts are what generic content is made of.

The second is unfamiliar territory. People exercise judgement well in their own area. They are quieter when the draft is on something they do not usually do. A marketing director reviewing AI-drafted code, a developer reviewing AI-drafted ad copy, an owner reviewing AI-drafted legal language. The temptation is to defer. The drafts often pass review without being read closely, because the reviewer does not trust their own judgement on that ground. Whoever wrote the prompt stops being the person who decides whether the result is right.

The third is fluency. AI assistants are very good at sounding confident. A weak idea written confidently is harder to challenge than the same weak idea written tentatively. People who would push back on a draft that hedged now wave through one that asserts. Confident-and-wrong is worse than tentative-and-wrong, because it does not invite the question.

What protects judgement when the draft is free

We are not arguing for slower drafts. The first draft becoming cheap is a real gain. The point is that the saved time has to go somewhere useful, and the obvious useful place is more careful editing by the right people.

A few small structural things help.

Decide who edits before the work starts. Not who reviews. The editor is the person who will redraft a sentence rather than tick a box. If nobody is allowed to redraft, the draft is the output, and the AI is your house style now.

Read drafts twice. Once for "does this say something true," once for "does this say something we would have said." The second read is the editorial one. It is slower. It is also where the work actually happens.

Keep at least one piece of work each week that nobody starts with AI. Not because AI is bad for it. Because muscles atrophy. The judgement that catches a wrong draft is sharpened by occasionally producing a draft from scratch. Teams that lose this habit lose the underlying skill within a few months, and only notice when something important needs to be written and they no longer trust themselves to start.

Editing can take longer than writing

We use AI drafts ourselves, every day. For code, for writing, for plans, for visual briefs, for reports. The output is good enough that we keep using it. It is also good enough that we have had to be deliberate about not letting it become the final word.

The hardest part is admitting that judgement decays under time pressure. The fix is not "more discipline". People under pressure do not suddenly become more careful. The fix is structural. Smaller teams reviewing fewer things more carefully. A clearer rule about which drafts go out without a second pair of eyes. A working culture where someone asking "is this what we would have written?" is the right question, not a delay.

If your team is producing more than it used to, that is a good sign. If it is also editing less than it used to, that is the part to watch.

AI drafts changed how we review work

We run the studio on AI drafts. Our internal tools draft inbound triage, project reports, error explanations, and code-review notes. We rely on those drafts. None of them ship without one of us reading them and choosing what to keep, change, or throw out. The reason it works is not that we have unusually disciplined people. It is that the team is small enough that judgement still lives close to the work, and we have kept it deliberate.

The first useful question with AI in a business is not "what can it draft." It is "who is allowed to disagree with what it draws."

Occasional updates

One email,
when we publish.

One plain email when a new article is up, nothing else. We'll send one email first to check the address is yours. Every email includes an unsubscribe link.

Free 20-minute call

Recognise your own problem in a piece? Talk it through with us.

Analytics

Can we measure your visit?

Google Analytics helps us understand which pages are useful. It stays off unless you allow it. See our cookie policy for details.