The request is never the whole story
“We need more blog posts” is a request.
“Make the form easier” is a request.
Neither tells me what is actually wrong.
I have learned to treat a brief as the start of a diagnosis, not a set of instructions. The thing you ask for is usually the most visible part of the problem. It is not always the part worth fixing.
You might ask for more articles because leads have slowed down. But the real issue could be that your services page never explains who you help. You might ask for a shorter form because people abandon it. But the real issue could be that they should not have to complete that form at all.
Writing before you understand the need is expensive guesswork.
A government example: “make the form easier” vs. “I shouldn’t need the form”
Here is a realistic version of a pattern I saw often in public-sector work.
A service team had a form for people reporting a change of address. It asked for their name, old address, new address, reference number, date of move and contact details. People complained that it was too long and confusing.
The obvious response was to simplify the wording and remove a few fields.
That would have made a bad process slightly less irritating.
A better question was: why are people filling this in at all?
In this case, the organisation already held most of the information. The user had logged in. Their name, reference number and current address were known. Asking them to type it all again added friction without helping anyone make a decision.
The real need was not a friendlier form. It was a service that showed the details it already held, asked for the one thing that had changed, and confirmed what would happen next.
That distinction changes the work completely. If I only respond to the request, I rewrite labels. If I understand the need, I can challenge the process behind the page.
The best content work often removes content rather than producing more of it.
That is why I do not start with copy. I start with the moment the reader is in, what they are trying to do, and what is stopping them.
A business example: “we need more blog posts”
A business owner once described a familiar problem to me. Their website had steady traffic but too few enquiries. Their conclusion was immediate: “We need more blog posts.”
They had a list of topics ready. “How much does it cost?” “What should I look for?” “Common mistakes.” They wanted a regular publishing schedule.
The business sold a specialist service. It was not a casual purchase. Prospects usually arrived after a bad experience with a cheaper provider, or when an existing arrangement had failed.
I looked at the site before discussing article ideas.
The homepage led with broad language about quality and expertise. The services page listed what the business did, but not how projects worked, what a typical engagement involved, or what made the business a better fit for someone who had been burned before. There was no example of a completed project. There was no explanation of how pricing decisions were made.
Publishing more articles would have brought more people into the same unresolved journey.
What they were actually missing
They were not missing topics. They were missing the information that turned interest into confidence.
The first job was to rebuild the core pages around the questions prospects were already asking in sales calls:
- What problem do you solve that another provider has not?
- What will I get, and what will I need to do?
- How do you decide what this costs?
- How will I know this is the right fit before I commit?
Only then did blog content make sense. Articles could answer early-stage questions and bring in people who did not yet know how to describe their problem. But those articles had somewhere useful to send them.
The owner had asked for more blog posts. What they needed was a clearer route from “I think this might help” to “I understand why I should contact them.”
Those are different jobs.
Why this connects to why people buy, not just what they say
This is the same idea I explore in the Why We Buy series.
What people say they want and what drives their behaviour can be different things.
Someone may say they want more choice. Then they leave a page because it gives them six similar options and no help choosing. Someone may say price matters most. Then they choose the more expensive option because its process feels clearer and less risky.
That is the gap between a considered answer and the quick judgement people make in the moment. Your reader may tell you they want “more information”. What they may actually need is reassurance that they will not make an expensive mistake.
That is why a content request should not be treated as research.
When someone says, “We need more blog posts,” I do not assume they have diagnosed the problem. They may be right. But I want to see what people do on the site, where sales conversations stall, and which questions keep coming up before I decide.
Your customers are not trying to mislead you. They are describing the solution they can see. Your job is to find the problem underneath it.
The one question that separates a brief from a need
The question I come back to is:
What is the reader trying to get done before they ask for this?
Ask it when a client says they need a new landing page. Ask it when your team wants to rewrite a form. Ask it when someone proposes a content calendar because traffic has dipped.
For example, a reader asking for a downloadable pricing guide may be trying to avoid an awkward sales call. A reader asking for more case studies may be trying to prove to their manager that choosing you is safe. A reader abandoning a contact form may not object to the form itself. They may not know what will happen after they press submit.
The request tells you where to look. The question tells you what to investigate.
How to find the real need before you write a word
I look for evidence from the point where people get stuck.
That might mean reading enquiry emails and noting the questions that repeat. It might mean listening to sales calls. It might mean watching someone use a page and seeing them hesitate over a phrase you assumed was obvious.
If you are working with a strategist, give them more than the requested deliverable. Show them the messages from customers. Tell them where prospects disappear. Let them hear the version of the problem you get when someone is frustrated, uncertain or close to buying.
Then ask a few direct questions:
- What is happening just before people ask for this?
- What are they trying to decide or avoid?
- What information do they already have?
- If we fixed this request perfectly, what problem could still remain?
The answer may still be “write more blog posts”. Sometimes the request is right.
But it should be the conclusion of the work, not the place you start.
