You Already Told Us That

The questionnaire asks what visitors should do next. The project brief already says to request a callback.

Imagine you’re coordinating the next website draft for a customer. AI has helped produce a tidy set of questions. The wording is friendly. The questions are easy to answer. You could put them in front of the customer after a quick review.

Except the customer has already answered that first one. Their approved brief names the callback as the purpose of the page, and nothing in the current material contradicts it.

What would another answer let you do that the existing one doesn’t?

That’s worth asking before you make the customer start again.

The next stage still belongs to the same relationship

The observation behind this piece came from a request I rejected. I’d asked for an existing website to be used as a source. The questionnaire that followed asked questions that had already been answered in some form.

Our website draft and the questions we’ll work through are hypothetical.

If you’re the operations person carrying customer work from one stage to the next, you can recognize the decision. A standard request is ready on your side. Has it earned the customer’s time?

Here’s the thing. A new stage of your process does not earn you a new telling of what the customer already explained.

In The Professional Recipe, Context is the information about this particular situation. This customer. This work. This stage. It should change what you prepare and what you still need to ask.

Having the information somewhere doesn’t settle that. The question is whether you used it.

If another colleague is picking up this stage, they may need help finding the earlier decision. Give them that help before passing the question back to the customer. A change of person inside your team can explain why an answer was missed. It doesn’t automatically make the customer the right person to supply it again.

Use the answer before you ask the question.

Put the known answer to work

Stay with the callback instruction. In our example, it is an approved decision that still applies to this draft.

You can use it to give the proposed page a clear next action. You can make the draft reflect that purpose. You don’t need the customer to explain again why a callback matters before doing that work.

Removing the question is only half the move.

The answer needs to show up in what you bring back.

If the next draft still has no clear way to request a callback, you haven’t solved much by shortening the questionnaire. You’ve spared one repeated question while leaving the known instruction unused.

Look at the work beside the answer. Does the proposed page do what the brief asked? Can you point to the part shaped by that decision?

This gives the customer something useful to review. They can respond to the proposed work instead of rebuilding the starting point for you.

They may still change their mind. An existing answer gives you a basis for preparing the next draft, not a promise that the customer will never revise it.

Make confirmation specific

Now take a different question from the same hypothetical request: who should review the wording?

An earlier note says the office manager reviewed the previous round. It doesn’t establish who will review this draft. You need to know where the wording goes next, and that responsibility is still open.

That is a reason to confirm. The note’s age by itself isn’t.

You could ask, “How does your review process work?” That makes the customer explain the whole arrangement again.

Or you could ask, “Your office manager reviewed the wording last round. Are they reviewing this draft too?”

The second question tells the customer what you’re working from and what you still need to know. They can confirm it or correct the part that changed.

Asking again can be the right move. Make the reason visible.

Don’t turn that into a confirmation ritual for every known fact. If the current brief already names the reviewer for this round, use it. You don’t need a new reply merely because your standard questionnaire has a space for one.

The point is to resolve the actual uncertainty before it affects the work. A clear confirmation can do that without reopening everything around it.

Keep the question only the customer can answer

There is one more decision in our invented website draft. Should the opening put new-customer inquiries first, or requests from existing customers?

The callback instruction doesn’t answer that.

You know the next action the page should support. You don’t yet know which audience should get attention first. Filling that gap with whichever choice makes the draft easier would be a different mistake from asking too many questions.

Bring the customer the decision in a shape they can use. Show the proposed opening and identify the priority it assumes.

“This opening puts new inquiries first, with a separate place for existing-customer requests. Is that the priority you want?”

The customer might prefer the other priority. They might explain that both need equal prominence. Your proposed treatment gives them something concrete to respond to without claiming their decision is already settled.

You have done enough preparation to ask a useful question. You have also left room for the answer to change the work.

The difference is easy to miss. “What do you want your website to do?” invites another broad explanation. A question about the unresolved priority lets the customer make the choice still needed.

Don’t make them approve your whole memory

Here’s the thing. You can replace a questionnaire with a long brief and still give the customer the same job.

Pages of business facts. Every previous decision restated. A closing request to confirm that everything is correct before you’ll continue.

Sometimes a consequential change needs careful review. But if you’ve asked the customer to check every settled detail because you haven’t identified the uncertain ones, the document’s new title hasn’t changed the burden.

Use established answers to prepare the work. Point to the particular assumption or gap that needs attention. Let the rest support the draft without turning every line into a fresh approval request.

You should be able to explain why each remaining question belongs. It supports a decision, checks a real uncertainty, or asks for information the current work needs and the available sources don’t supply.

A shorter request isn’t automatically better. If every question has a sound reason, keep them. There is no prize for removing the question that would have prevented a wrong assumption.

Existing does not always mean current

Before you use an old answer, check what else you know now.

A public page may still carry wording that a newer approved decision changed. Two notes may disagree. The customer may have corrected something in the last review that your standard request hasn’t caught up with.

Don’t choose the convenient version because it lets you finish the draft. Bring the conflict to the person responsible for the work. If the answer remains unknown, keep that gap visible.

This doesn’t require a tour of every record your business has ever kept. Start with the relevant brief, current material and earlier answers already available for this job. Follow a conflict far enough to resolve it or name what needs clarification.

Does that make sense? Using what you know includes noticing when it no longer gives you a dependable answer.

Your Monday Move

Open one customer request you’re preparing and the relevant records you already use for that work.

For each question, find the answer if one exists. Decide whether you can apply it, need to confirm a specific uncertainty, or still need a decision from the customer.

Then look at the proposed work. Make sure the answers you’ve kept actually shape it. Removing a question while ignoring its answer leaves the next stage unfinished.

Keep the justified questions and put the request through your normal review process. You may have fewer questions. You may discover the work can proceed without another request. You may keep the same number with much clearer reasons.

When the next ordinary response arrives, notice whether it fills a genuine gap or corrects something you thought you knew. Carry that understanding into the next stage.

The customer can change the answer. They shouldn’t have to give it again just because your process turned a page.