A customer-problem content decision map is a short planning record that connects a real audience problem to the task the person is trying to complete, the evidence you have, the most useful content job and the next sensible action. It helps a small business choose what to create next without treating every keyword, comment or idea as equally important.
A long topic list can feel productive while hiding the decision that matters: which problem deserves attention now? One request may be frequent but poorly matched to your offer. Another may be commercially relevant but supported by only one vague comment. A third may be important to customers yet better solved by improving a service page than publishing another article.
The map in this guide gives each problem a clear place, evidence and priority. It fits inside the broader content marketing system for a small business, but focuses on the step that happens before a brief or calendar: deciding which customer problem the content should help solve.
What a customer-problem content map contains
The map is not a persona document or a catalogue of everything customers might care about. It is a decision tool. Each row or card should answer six questions:
- Who: which recognisable audience group has the problem?
- Problem: what obstacle, uncertainty or risk are they experiencing?
- Task: what are they trying to do when the problem appears?
- Evidence: where did you observe it, and how strong is that signal?
- Content job: should the content help them discover, understand, compare, decide or act?
- Next step: what useful action should become easier after they read?
This structure prevents an editorial team from jumping from “people ask about pricing” to “write a pricing article.” The real task could be estimating total cost, comparing plans, understanding renewal terms or deciding whether the product fits a particular workflow. Those needs require different content.
Start with evidence, not a brainstorming session
Begin with places where customers already reveal friction. Useful sources include sales questions, support tickets, search queries that lead to your site, form responses, product reviews, call notes, community discussions and objections recorded during onboarding. The GOV.UK content guidance recommends learning who users are, what they are trying to do, how they currently do it and which frustrations they experience. It also advises reviewing existing evidence rather than inventing a need to justify content that already exists.
Keep the evidence close to the problem statement. Record the source, date, approximate frequency and exact language where appropriate. Remove personal data. A note such as “three onboarding calls in September asked which files must be ready before setup” is more useful than “customers need onboarding content.”
Search data can strengthen the picture, but it is not the whole picture. A high-volume phrase may describe a broad audience you do not serve. A low-volume question may still matter if it repeatedly delays a valuable buying or implementation decision. This is where buyer intent can matter more than raw traffic.
Rewrite every problem as a task
A useful problem statement describes what the person is trying to achieve, not the content format you want to publish. “Needs a webinar” is a proposed solution. “Needs to compare setup approaches before committing staff time” describes a task.
Use this sentence:
As a [specific audience], I need to [complete a task or make a decision], so that I can [reach an outcome or avoid a consequence].
The wording is adapted from the user-need pattern used in GOV.UK content design. It forces you to name a person, an action and a reason. If you cannot complete the sentence without guessing, the problem is not ready for the map. Collect better evidence first.
Group related problems without flattening them
Several observations may belong to one problem family. Questions about monthly limits, extra charges and renewal dates can sit under “predict the real cost before buying.” Grouping them reduces duplicate articles, but do not merge distinct tasks merely because they share a keyword.
- Merge observations when the same person is trying to make the same decision.
- Keep them separate when the audience, decision stage or required answer changes.
- Mark contradictions instead of averaging them away; different customer groups may need different pages.
- Link existing content to the problem before proposing something new.
This check is important because Google’s current people-first guidance asks whether content serves an intended audience, helps someone achieve a goal and adds substantial value. Producing another page is not automatically the answer. Updating, consolidating or linking an existing page may serve the need better.
Score the problem before choosing a topic
Use a simple zero-to-two score across four dimensions. The aim is not mathematical certainty. It is to expose why one problem is being prioritised.
- Evidence strength: zero means assumption; one means an isolated or indirect signal; two means repeated, recent or corroborated evidence.
- Reader consequence: zero means mild curiosity; one means delay or confusion; two means a meaningful cost, risk or blocked decision.
- Business fit: zero means outside your focus; one means adjacent; two means directly connected to your expertise, service or customer journey.
- Content advantage: zero means a page already answers it well; one means a useful improvement is possible; two means you can provide a clearer method, example or evidence that is genuinely missing.
Add the four scores, then review the reasoning. A total of six to eight is a strong candidate for the next content brief. Four or five usually needs more evidence or narrower scope. Zero to three normally belongs in the parking area, a support response or a product improvement backlog rather than the publishing calendar.
Do not let the score hide judgement. A serious legal, safety or financial question may deserve expert review even if it is rare. A commercially attractive topic should not outrank a better-supported need merely because it offers an easy call to action.
Choose the content job and acceptance test
Before selecting a format, decide what the content must help the reader do. A discovery article frames an unfamiliar problem. An explanatory guide clarifies a process. A comparison helps evaluate options. A checklist supports action. A troubleshooting page helps diagnose a failure.
Then write an acceptance test. For example: “After reading, a first-time buyer can list the three cost components, identify which plan information is still missing and prepare two questions for the vendor.” This is more useful than “the article should rank for pricing software.” It gives the writer and reviewer a shared definition of usefulness.
Hypothetical example: a bookkeeping firm
Imagine a small bookkeeping firm. This example is fictional; it does not report real customer research or business results.
The firm records five recent enquiries from owners who sent documents late because they did not know what to prepare each month. The first idea is “write about bookkeeping organisation.” That is too broad. The map produces a sharper record:
- Who: owners of small service businesses handling their own monthly records.
- Problem: documents arrive late or incomplete, creating avoidable follow-up.
- Task: prepare the correct records before the monthly deadline.
- Evidence: five recent enquiry or onboarding questions plus repeated support reminders.
- Content job: action support.
- Acceptance test: the reader can assemble a monthly folder, identify missing items and know when to ask for help.
The resulting content might be “A monthly bookkeeping document checklist for service businesses.” The map also shows what not to claim. The firm cannot promise that the checklist prevents every delay or satisfies every tax requirement. The article should state its scope, jurisdictional limits and when professional advice is needed.
Copyable customer-problem map
Audience: [specific group]
Observed problem: [their words, without personal data]
Task and outcome: [what they need to do, and why]
Evidence: [source, date, frequency and confidence]
Current content: [none, update, consolidate or link]
Content job: [discover, understand, compare, decide, act or troubleshoot]
Acceptance test: [what the reader can do afterward]
Priority score: [evidence + consequence + business fit + content advantage]
Next decision: [create, update, combine, research further or do not publish]
You can also use this compact review prompt with an AI assistant after removing private customer data:
Review these anonymised customer observations. Group only observations that describe the same audience, task and decision stage. For each group, state the problem, evidence strength, likely content job, missing evidence, existing-content check and a cautious next action. Do not invent prevalence, customer quotes or business results.
Treat the output as a draft for human review. The assistant cannot know whether your notes are representative, whether another team owns the problem or whether publishing is the best solution.
Run a 20-minute decision meeting
A small team can maintain the map without turning it into another large system:
- Add new evidence before the meeting, not new topic ideas.
- Review one high-scoring problem and the page that already comes closest to solving it.
- Choose one action: create, update, combine, research further or decline.
- Name an owner and acceptance test.
- Set a recheck date for volatile evidence or unresolved assumptions.
Keep rejected ideas in the record with a short reason. That prevents the same weak topic from returning every month and gives you a useful history when new evidence appears.
Common mistakes that weaken the map
- Counting mentions without context: ten mentions may come from one unusual incident.
- Starting with the product: a topic built to justify an offer can misrepresent the reader’s real task.
- Equating search volume with importance: volume estimates do not show fit, urgency or whether you can add value.
- Mixing journey stages: beginners and ready-to-buy readers may use similar words but need different answers.
- Skipping the existing-page check: unnecessary new URLs can fragment useful information.
- Leaving evidence undated: product, market and customer conditions change.
The U.S. Small Business Administration describes market research as a way to understand customers and reduce risk. For a content team, the same principle applies: evidence improves the decision, but it does not eliminate uncertainty. Record what you know, what you inferred and what still needs checking.
Reader Q&A
What is a customer-problem content decision map?
It is a planning record that connects an audience problem to the task the person is trying to complete, the evidence behind the problem, the job the content should perform and the next editorial decision. It helps teams prioritise needs instead of publishing from an undifferentiated idea list.
How many customer problems should the map contain?
Include as many evidenced problems as you can maintain, but keep the active decision view small. A small business might review the five to ten strongest current records and archive weak, solved or outdated entries with a reason.
Can keyword research replace customer evidence?
No. Keyword research can show how people search and can help test language or discover related questions. It does not prove that the searcher matches your audience, that the problem is important to your customers or that a new article is the right solution.
What if only one customer mentions a problem?
Record it as an isolated signal rather than treating it as a common need. Check other evidence, assess the consequence and decide whether a direct response, further research, a product change or content is the proportionate next step.
Should every high-scoring problem become a new article?
No. The best action may be updating an existing article, improving a service page, adding a checklist, clarifying onboarding, combining overlapping pages or deciding not to publish. The map supports the decision; it does not prescribe a format.
How often should the content decision map be reviewed?
Review active priorities on a regular editorial rhythm, such as weekly or monthly, and recheck volatile evidence before creating the brief. Also update the map when customer questions, products, regulations or business priorities materially change.
Choose the next problem, not the next format
A useful content plan starts with evidence of a real task. Build one problem record, check the page that already comes closest, score the opportunity and write an acceptance test. Only then decide whether the answer should be an article, checklist, comparison, email, video, service-page improvement or no new content at all.
That discipline gives a small team fewer topics, stronger reasons and a clearer link between customer help and business learning.
