Writing as thinking: The cognitive tool we are outsourcing before we understand it

In 2019, at Freshworks, I wrote the single worst product brief of my career. I had been asked to build the case for a new feature direction that would require pulling engineers from two active projects. I sat with a blank document for an hour. I typed a paragraph, deleted it, typed another, deleted that, and produced four pages that read like a man arguing with himself. My manager read it the next morning and said, very gently, "I think you are still figuring out what you believe." He was right.

But here is the part I did not understand until much later. By the time I finished that miserable draft, I understood the problem differently than when I started. The brief was terrible. The thinking it forced was not. Somewhere around the third deleted paragraph, I realised my original framing was backwards. The feature I wanted to propose was solving a symptom, not a cause. I would not have seen that if I had not been forced to put my reasoning into sentences that refused to cooperate.

I did not sit down knowing what I thought and then write it down. I sat down confused, and the act of writing showed me what my confusion was actually about.

The ordinary world

For most of my career, writing was just overhead. Product briefs, strategy documents, design rationales, meeting pre-reads. Nobody called these cognitive activities. They were the paperwork that surrounded the real work of building products.

But it was never just paperwork. The thinking happens invisibly, embedded inside the act of composing sentences. You start a brief believing you understand the problem. By the third paragraph, you discover a gap in your reasoning that was not visible until you tried to explain it to an imaginary reader. That discovery is the work. The document is just the residue.

I call this the first-draft tax. It is the cognitive cost of forcing yourself to turn vague intuitions into specific, ordered sentences. It is slow. It is uncomfortable. It is occasionally humbling when you realise that your confident opinion evaporates the moment you try to write it down. But the tax is where the thinking happens. Skip the tax, skip the thinking.

The call that sounds like a gift

AI writing tools are now offering to eliminate the first-draft tax entirely. Describe your product direction in three sentences, receive a polished brief in thirty seconds. The output reads like it was written by someone who understood the problem thoroughly.

But the person who prompted the brief did not go through the cognitive process that writing forces. They received clarity without earning it.

I tested this myself earlier this year. Instead of writing a brief from scratch, I described a product concept to an AI tool and asked it to generate one. The result was impressive. Clear problem statement, logical flow, reasonable assumptions. But when I sat with the document, something felt wrong. Not factually wrong. Epistemically wrong. The brief was articulate about a problem I had not yet fully understood. It had the shape of finished thinking without any thinking having been done.

I have started calling this borrowed clarity: the appearance of having thought something through without the actual process of thinking it through. The document looks like understanding. But nobody did the understanding. It is a receipt for a meal nobody cooked.

The ordeal

At Adobe, I worked with a product manager named Kavitha who wrote every first draft by hand, in a notebook, before typing anything. Her colleagues found this eccentric, even performatively old-fashioned, like insisting on a quill pen. But her briefs were consistently the sharpest in the organisation. When I asked her why, she said something that has stayed with me since: "If I cannot explain it without a backspace key, I do not understand it yet."

That line contains the whole argument.

Writing is not the recording of thoughts already formed. It is the process by which thoughts become formed. The resistance of the blank page, the requirement to choose one word over another, the need to put ideas in sequence, these are not obstacles to thinking. They are thinking. And they are precisely the elements that AI-generated first drafts eliminate.

I have started noticing the difference in briefs I review. The ones written from scratch, even when rougher, contain genuine insight somewhere in the middle. A paragraph where the author clearly worked through a contradiction or arrived at something unexpected. The AI-assisted briefs are smoother but flatter. The author prompted, reviewed, approved. But they did not wrestle.

The first-draft tax is not a bug in the writing process. It is the feature.

What to protect

I am not arguing that AI has no place in product writing. That would be absurd, and I limit myself to one absurd position per quarter. AI is excellent for editing, restructuring, and turning a rough draft into something presentable. But there is a critical distinction between using AI to improve thinking you have already done and using AI to replace thinking you have not done. The first is a tool. The second is a shortcut that produces documents without producing understanding.

Product work is, at its core, a thinking discipline. The brief is not the deliverable. The understanding is the deliverable. The brief is the mechanism by which understanding gets produced. When we outsource the mechanism, we risk outsourcing the understanding along with it.

I mentor junior PMs, and I give them a specific instruction: write your first draft without AI. Sit with the blank page and struggle. Let the struggle reveal what you do not yet understand. Only after you have a draft that represents your own thinking should you use AI to sharpen or polish it.

Some of them look at me the way you might look at someone recommending you churn your own butter. I understand the reaction. But the ones who follow it consistently report the same thing: they did not realise how much of their thinking was happening during the writing. They thought the thinking came first and the writing came second. It does not.

That is the first-draft tax doing its job.

The return

There is a version of this that sounds like technological conservatism, like arguing that calculators will rot your arithmetic. But the analogy does not hold. Calculators automate computation, which is mechanical. Writing is the process by which ambiguous, half-formed ideas get forced into clarity through the friction of language. There is no mechanical step to skip. The effort is the product.

I think about that brief at Freshworks, the one that took ninety minutes and read like an argument with myself. If I had prompted an AI tool with the same information, I would have received a polished document in seconds. But I would not have discovered that my framing was backwards. I would have had a document. I would not have had understanding.

The convenience is genuine. The speed is real. But the question product teams have not yet thought to ask is: what are we losing when we stop paying the first-draft tax? The answer is not polish or craft. It is the thinking itself.

Writing has always been the cheapest cognitive tool available to anyone who works with ideas. It requires no software, no facilitator, no meeting room. Just a willingness to sit with a blank page and let it show you what you do not know.

The strange thing about outsourcing that process is that you do not notice what you have lost until much later, when a decision fails and you trace it back to a brief that sounded clear but was never thought through.