AI & Technology
The Invisible Handshake
Writing a thing badly is how you find out you never understood it; a clean first draft hides that.
2026-09-161 min read
Drafting has always done two jobs at once, and only one of them is producing text. The other is diagnostic. Sentences fail in specific ways - a claim you cannot finish, a transition that will not hold, a paragraph that keeps restating its own first line - and each failure is information about where your understanding runs out. A model that writes fluently on the first pass removes every one of those signals. The page comes back smooth, and smoothness is indistinguishable, from the outside, from having thought it through.
Leonid Rozenblit and Frank Keil named the relevant failure the illusion of explanatory depth: people rate their understanding of ordinary mechanisms highly, then find the rating was inflated the moment they are asked to write out how the thing actually works. The rating does not fall because they learned something new. It falls because explaining is the first point at which the gap becomes visible to them. A generated draft arrives on the far side of that test, with the gap intact and unmarked. Whoever sends it on - usually its nominal author - then carries a confidence calibrated to prose quality rather than to anything they know.
The cost lands later, and somewhere else. It arrives when a question is asked that the draft never had to answer: in a review, from a client, or from the engineer who has to build the thing. What looks at that moment like a failure of the model is usually a rehearsal that never happened.
Key insights
A first draft is a test instrument, and a fluent one returns no reading.
Explaining something in writing is the point where an inflated sense of understanding becomes visible, and generated text arrives past that point.
Smooth prose and understood material produce the same surface, which is why the substitution is so hard to notice from the inside.
Why it matters
Confidence calibrated to how good the prose sounds is confidence in the wrong signal, and it fails in the room where the question finally gets asked.
A team that never sees its own bad first drafts has lost the one routine diagnostic it had for shallow understanding.
Use this tomorrow
1Take the last AI-assisted document you sent, and without reopening it write down the three claims it rests on; count how many you can state the reasoning for.
2Before your next generated draft goes to anyone, write two questions you would ask if someone else had sent it to you, then count how many of the two the draft already answers.
Go deeper
The generation effect in memory research is the companion finding: material you produce yourself is retained better than the same material read passively. Between the two effects, composing does double duty - it exposes what you do not understand and it fixes what you do. Delegating composition gives up both at once, which is why the loss is larger than the time saved makes it look. It also explains why editing the output is not a substitute: editing operates on what is present, and the thing you needed was the discovery of what is absent.
Measurement makes this worse in a specific way. A team that tracks output in documents, tickets, or drafts per week is measuring the half of drafting that was never the valuable half, and that number improves fastest exactly when the diagnostic half is being skipped. A group can post its best quarter on that metric while its actual grasp of the work erodes, and nothing on the dashboard will disagree. The uncomfortable counter-metric is simpler than it sounds: how often does a question in a review turn out to be unanswerable by the person who sent the document.