The Memo You Never Wrote

Somewhere around the third time I tried to hand a task to an AI agent and it came back wrong, I realised the problem wasn’t the agent.

The instructions I gave were vague. Not vague because I was being lazy — vague because I had never actually made the thing explicit. It existed in my head as a feeling, a preference, a cluster of half-formed criteria. I knew what I wanted when I saw it. I had never needed to describe it before.

That is how most decisions get made in a business.

Verbally. In meetings. In your head. On a call where everyone nods and walks out with slightly different interpretations. The experienced people just know. The culture carries it. Nobody writes it down because writing it down takes longer than just doing it, and doing it is usually faster than explaining it.

This works fine until you try to delegate to something that can’t read the room.

The instruction is the thinking

When you write a brief for an AI, you are forced into specificity in a way that briefing a person never requires. A person will fill in the gaps. They will ask clarifying questions. They will apply judgment shaped by weeks of working alongside you. An AI takes the instruction at face value and executes against it exactly as written.

So if your instruction is incomplete, the output reflects that incompleteness back at you in a way that is impossible to ignore.

This is uncomfortable. It is also, I have come to think, the most valuable thing about working this way.

Writing the instruction forces you to answer questions you had been deferring. What are we actually optimising for here? What does “good” mean in this context? What is the constraint I care about most? These are not questions I had been avoiding on purpose. They just never had to be answered before — because the person doing the work was good enough to intuit the answer.

The memo you never wrote is the thinking you never finished.

Externalisation as a forcing function

A founder I know runs a small consulting firm. She described the process of setting up Claude to handle a weekly client report as “accidentally becoming rigorous about what the report was even for.”

To get the agent to write the report correctly, she had to answer: What decisions does this report enable? Who reads it and what do they care about? What should change in the report when the project is on track versus off? She had been producing that report for two years. She had never asked those questions explicitly. She just knew.

Except she didn’t, quite. Once she wrote it down, she changed the report structure. And the clients noticed.

That is not an AI story. That is a thinking-clearly story. The AI was just the reason she finally had to do the work.

The discipline compounds

The first few times you write detailed context for an AI, it feels like overhead. You are used to just doing the thing, not explaining the thing. The explanation seems like a tax on execution.

But the explanation is execution. The moment you articulate a process clearly enough for an agent to follow it, you have also articulated it clearly enough to improve it, delegate it, or question whether it should exist at all.

Teams that have been doing this for a few months tend to describe something similar: they have documentation they never had before, not because someone went and wrote documentation, but because writing instructions for agents is, structurally, the same thing.

The decisions that used to live in one person’s head are now written down somewhere. Searchable. Refinable. Transferable.

What this changes

Most knowledge businesses run on tacit knowledge. The experienced people carry the process in their heads. When they leave, half the process leaves with them. Clients complain. Things fall through gaps that nobody noticed existed.

Working with AI doesn’t solve that problem automatically. But it creates the conditions for solving it, because you cannot fully delegate to something that requires explicit instructions without building a body of explicit instructions over time.

The memo you never wrote because you never needed to write it — you need to write it now.

That is not a burden. That is the thing becoming yours.