Study first
Review the ideas behind the questions
Review how research evidence changes a content decision before you start. Focus on the difference between a stakeholder request, a user need, an observation, a finding, and a next action.
Start with the user problem
A content brief is stronger when it starts from what people are trying to do, not from a format request or a stakeholder preference.
- Start by learning who the likely users are and what they need before deciding what to create.
- Treat opinions that do not come from users as assumptions that need research.
- A good user need should focus on the user's problem, not the team's preferred solution.
In Practice
Check the requested format
If a sales leader asks for a long guide, first ask what user problem the guide would solve and what evidence supports that need.
Use customer language
Research notes can show the words people use, which helps the brief avoid internal labels that readers would not search or recognize.
Common mistakes
Approving a content topic because the team likes it and then searching for evidence later.
Treat the topic as an assumption until research shows which user problem it solves.
Q&A
What makes a content user need stronger?
It is based on research evidence and describes the reader's problem instead of naming a preferred content format.
How should a team handle a stakeholder content idea with no user evidence?
Treat it as an assumption and test it through research before building the page around it.
Plan evidence before writing
Research planning keeps content work focused. The team should know what it needs to learn, who it needs to learn from, and which method can answer the question.
- Turn unfounded opinions into research questions before choosing content changes.
- Choose research methods based on what the team needs to learn and the project phase.
- Include a good variety of users when recruiting for a broad audience.
In Practice
Narrow the question
A vague goal like improve the blog is too broad; ask what readers need to decide, where they get stuck, or which draft choice needs proof.
Pick methods for the decision
Use interviews when the team needs to understand a task or problem, and usability testing when it needs to see whether people can use a draft.
Common mistakes
Running a large survey because it feels rigorous, even though the team needs to see where readers get stuck in a draft.
Choose an activity that can answer the specific content question with reliable evidence.
Q&A
When should research questions become more specific?
They should become more specific in later phases as the team focuses on user groups and parts of the experience.
What should a research plan show the content team?
It should show what each round will answer and how the evidence will help the team make decisions.
Turn notes into decisions
Synthesis should separate what people did or said from what the team thinks it means. Findings are useful when they lead to clearer priorities, content changes, or another research question.
- Capture observations as what people saw or heard before adding interpretation.
- Sort observations into patterns before writing findings.
- Research findings should help the team make design decisions, prioritize work, and refine user needs.
In Practice
Do not skip the observation step
A note like users are confused is weaker than the exact quote or behavior that showed the confusion.
Share while it can change the work
Findings should reach editors and stakeholders soon enough to change the brief, draft, roadmap, or next test.
Common mistakes
Turning one loud comment into a full rewrite without checking the wider pattern.
Group observations into themes, agree what they show, and then decide the content action.
Q&A
What should a finding include when shared with the team?
It should explain the essential facts, why they matter, and what happened with users.
What can findings become after analysis?
They can become design ideas, changes to test, new research questions, or new backlog details.