The Only Copy

Why your team can follow every instruction and still move further from what the client needs.

Two colleagues in office clothes reach out open hands across a gap toward a woman with round glasses seated at a desk, who holds one blue sheet of paper. The words being available sit above the colleagues, and the words the only copy sit beside the woman.

It's Tuesday, and SEO wants to know what to optimize for. You answer from memory of the discovery call, explaining which searches matter to the client and why.

Content asks what tone to use. You give them a shorter version of what the client sounded like.

PPC asks for the target CPA. You give the target.

I made that week up.

Each question gives you a small proof that you were on the call and the teams still need you.

You heard what the client stressed, what they passed over, and why the work mattered enough to hire someone.

You have a good reason to keep answering. A quick reply lets the team get on with the work.

Sending them back to a brief would feel unhelpful if the answer is already in your head. So you answer, and each team gets what it asked for.

Each answer is true. Each also holds a little less than the call.

SEO gets a direction, content gets a tone, and PPC gets a target. The reasons that joined those answers together stay with you, waiting for the next person to ask.

By Thursday in that week, the client's priority has moved. The SEO answer was right on Tuesday; now it points toward work that matters less.

The SEO answer was right on Tuesday; now it points toward work that matters less.

The SEO answer was right on Tuesday; now it points toward work that matters less. Dots, in order: the blue flag, the signpost, the bare stake, the team member.

Click a numbered dot to see what it stands for. Start with 1.

The team has your answer, but not enough of the reason to question it. An answer built for the room it was given in can work well there and fail when the room changes.

The other teams hold their own small versions of the client. Content can use the right tone while saying the wrong thing. PPC can hit an agreed target after its purpose has changed.

Nobody has to be careless for the work to drift. Each team can follow your instructions and still move further from what the client needs.

Now take yourself out of that week. The teams can wait for you and risk missing the date. Or they can guess what you would have said and risk missing the target.

The work has not stopped needing the client's reasons. It has stopped being able to reach them. All those answers have one source, and that source is away.

The only copy

You call it being available. You know the client, so of course people come to you. From inside, being available feels like being the person who knows.

But being available does not make the client's intent available. It makes you available to explain it again.

You are the only copy.

The fact sits in one place and the decision in another. The person deciding may know that you know, but still cannot act without borrowing your memory.

So you become the switchboard. Every question routes through you, even when someone else could have answered it with the same context. Your usefulness grows with the number of people who cannot move without you.

That is a hard kind of usefulness to give up. If the team can answer without you, you lose a daily sign that you matter. The calls and questions have been proof that the relationship is yours to hold.

The wish to protect that relationship is real. So is the comfort of being needed. Both can keep the client's reasons in your head long after they could have helped someone else.

What a page can hold

The client did hire a person, not a document. They trust your judgment, including the parts that do not fit neatly into a page. You cannot file that trust and assume the relationship has moved with it.

A document can even make things worse. Once it exists, everyone can act as though the transfer happened. A brief written once and filed may hide the gap better than an honest admission that someone needs to ask.

A document can even make things worse.

A document can even make things worse. Dots, in order: the paper floor, the two colleagues, the blue pit.

Click a numbered dot to see what it stands for. Start with 1.

That is a reason to test the page, not to leave the intent unwritten. The page need not hold the whole relationship. It needs to hold the client's question clearly enough for someone who was not in discovery to use it.

That person must be able to choose work for a reason the client would recognize. If they cannot, a polished paragraph has not done the job.

The page can also be wrong. Instead of defending it because it captured what the client meant before, check it against what the client means now. Your judgment still matters, but it can go toward that check instead of repeating the same answer.

The question beneath the request

So what goes on the page?

A brief might say, "Write 10 blog posts." That tells a team what to make. A Story Anchor is a short written page that holds the client's reason, keeping it close enough to guide a choice when the brief no longer fits.

The team can now judge a proposed post against the question.

The team can now judge a proposed post against the question. Dots, in order: the stack of pages, the colleague adding a page, the blue board, the page held up.

Click a numbered dot to see what it stands for. Start with 1.

I use Barbara Minto's Situation, Complication, Question, Answer. She developed those four parts to open a document with the reader on common ground. Using them to hold a client's problem for people outside the call is my adaptation.

For the SEO team in that week, the Situation is the request to improve search visibility. The Complication is that more visibility does not, by itself, mean reaching people who might buy. The Question becomes which searches will put the client in front of those people.

The Answer is a direction for the work: build visibility for searches that show an intent to buy. The team can now judge a proposed post against the question, rather than count it toward the ten.

That answer is still something to check with the client. Their definition of success belongs beside it, along with what is out of scope. The target CPA and the tone can sit beside the reasons behind them.

The destination needs words too. In Working Backwards, Bryar and Carr describe Amazon teams writing a press release and FAQ before building a product. The press release is less than one page and describes the product as the customer would meet it; the FAQ runs five pages or less.

On their site, they write, "A great PR defines a valuable destination." The value is in agreeing where the work is meant to arrive before spending effort getting there.

Writing about AWS, Bryar and Carr say the team spent more than a year writing and revising its PR/FAQs before building. Readers across Amazon could then reach the same understanding of the product plan from those documents.

For the anchor, I use a short paragraph written as though the client has arrived. In that week, it describes the client being found by people who might buy, not merely appearing higher in search. The client gets to check whether that is the destination they meant.

That paragraph cannot stay fixed while the client moves. Bryar and Carr describe the PR/FAQ as a living document, changed after approval. A Story Anchor needs the same permission to change.

So Thursday's shift goes onto the page, along with what it changes about the work. SEO can see the new priority and the reason, without waiting for you to repeat a call.

It is the same Tuesday, and SEO is asking again what to optimize for.

Content still needs a tone, and PPC still needs a target CPA. The questions have not vanished.

This time, each team can find an answer and see why it belongs to this client. SEO can tell whether a new topic serves the question. Content can understand what its tone needs to carry.

PPC can judge the target against the client's definition of success. A choice that falls outside the page still needs a conversation. The difference is that every choice no longer needs the person who remembers discovery.

You can be away while the team keeps making choices you would recognize. When you return, the useful conversation is about what changed or what the page could not answer. It does not have to begin with what the client wanted.

You can leave the room without taking the client with you.

I write down what clients ask, and what I find they were asking underneath.

Part of A Certain Answer, a series about checking not just whether a message was sent, but whether it reached someone and was understood.