A content calendar has an empty slot. Someone suggests a trend report. Someone else wants a product comparison. Neither suggestion explains what the buyer needs.
Customer interviews give the editorial team a different starting point: a person trying to complete a task with incomplete information.
The useful output is a question with evidence behind it. A transcript alone does not tell a writer what to build.
Use the workflow below to move from a research question to a bounded article brief. The worked example is fictional throughout.
Start with one decision you need to understand
Write the research question before the invitation. Keep it narrow enough that an interview can produce relevant examples.
For this exercise, a fictional team sells reporting software. Its question is: what information do operations managers need before choosing a reporting approach?
That leaves room for answers involving spreadsheets, outside help, or keeping the current process. The research question does not assume a software purchase.
Define the decision boundary too. This round examines evaluation before purchase. It does not investigate installation, renewals, or every problem with reporting.
Choose participants for relevant experience. An operations manager who recently evaluated an approach fits this question better than someone with a matching title alone.
Include people who reached different outcomes. A buyer, a nonbuyer, and someone who postponed the decision can expose different missing information.
Those are proposed selection criteria for this exercise. GOV.UK's interview guidance recommends researching current or likely users and preparing a discussion guide.
Avoid describing the invitation as a chance to explain why your product is better. That introduces the answer before the conversation starts.
Record who the round excludes. If all participants already know your company, the notes cannot explain the experience of people outside that group.
Set the permission boundary before taking notes
Explain the purpose, participants, note-taking method, intended audience, and storage arrangements before collecting information. Let people decline questions or end the session.
Separate participation, recording, and publication permissions in your working record. Agreement to discuss a task does not establish permission to publish a quotation.
Use a plain record with fields for participant code, permitted collection method, internal access, agreed uses, and review or deletion date.
Keep contact details outside the editorial notes. Give the writer a reviewed observation summary instead of the recruitment list or full recording. Remove identifying details before sharing it.
For this workflow, keep quotation publication disabled by default. If a quotation becomes useful, request separate permission for the exact wording and attribution.
Record the response rather than inferring agreement from a friendly conversation. If publication permission is absent, keep the quotation out of public copy.
These are proposed editorial controls, not a statement of universal legal requirements. Follow the organization's applicable privacy process before gathering real material.
The GOV.UK interview guide calls for informed consent and secure storage of collected personal data. Its guidance addresses government service research.
Do not request confidential screens or files to make an interview feel concrete. A participant can describe the sequence without exposing another person's information.
Ask about a recent task
A discussion guide keeps the conversation connected to the research question. Treat it as a route through the task, with room for useful detours.
The following prompts are an original guide for the fictional reporting example. They are questions to ask, not quotations from participants.
- What reporting task did you last need to change?
- What happened immediately before you started looking for another approach?
- Walk through the first thing you did.
- Which approaches did you consider, including keeping the current one?
- What information did you look for before comparing those approaches?
- Where did you find an answer, and where did you remain uncertain?
- Who else needed information before the decision could proceed?
- What did you eventually choose, and what remained unresolved?
Follow the sequence with neutral requests for detail. Ask what happened next, what a term means, or which information changed the decision.
Avoid asking whether a readiness checklist would have helped. First establish what the participant needed; a preferred format can wait.
If someone describes an ideal process, ask for the most recent occasion when the task occurred. Keep the account tied to an event.
Before closing, summarize your understanding and invite corrections. Do not turn an uncertain answer into agreement by repeating it confidently.
GOV.UK recommends open, neutral questions and real examples. The specific reporting prompts above are an editorial adaptation.
Keep observations separate from interpretations
Create one observation per note. Preserve enough context to explain the task without carrying identifying detail into the editorial workspace.
The following table contains synthetic notes, not research findings. No interviews occurred, and none of the statements describes a real customer.
| Synthetic note | Observation | Possible interpretation |
|---|---|---|
| Participant A lists required source files before comparing approaches. | A documents input requirements first. | Input readiness may shape evaluation. |
| Participant B postpones comparison until a colleague identifies the report owner. | B needs an ownership decision before proceeding. | Ownership may be an earlier dependency. |
| Participant C continues using a spreadsheet after reviewing a vendor guide. | C chooses the existing approach. | A new tool may be unnecessary for this task. |
The observation column stays close to the invented account. The interpretation column contains tentative explanations that require further checking.
Do not replace A's observation with a claim that buyers want automation. That sentence inserts a product preference the note never establishes.
Give each note a stable reference within the restricted research record. In the fictional example, references A1, B1, and C1 are enough.
A writer's brief can cite those references without containing personal details. Keep any mapping back to identifiable source material under the agreed access controls.
GOV.UK's analysis guidance separates observations, grouped themes, findings, and actions. The table applies that distinction to content planning.
Turn the notes into a question worth answering
Group A1 and B1 under a tentative theme: prerequisites before comparing reporting approaches. Keep C1 beside that group as a boundary on the conclusion.
The theme does not mean every buyer needs the same checklist. It suggests a question to investigate: what should a team establish before evaluating reporting options?
Write the buyer question in task language. For this example: how do we know whether our reporting process needs a new tool?
That question allows an answer that recommends keeping the current setup. A useful article must leave that outcome available.
Translate the theme through explicit steps:
- Observation: A lists inputs; B needs an owner; C keeps the spreadsheet.
- Theme: evaluation depends on understanding the current process.
- Buyer question: what should we check before comparing reporting approaches?
- Content candidate: a readiness guide with inputs, ownership, and reasons to defer a purchase.
- Evidence gap: whether other relevant participants encounter the same dependency remains unknown.
The final line belongs in the brief. Without it, a small research round can harden into an unsupported statement about the whole market.
Treat the proposed article as a response to the question, then use buyer-journey mapping to place it among existing pages.
Write a brief a writer can challenge
An actionable brief names the reader, decision, evidence, exclusions, and required answer. It also tells the writer where the evidence ends.
Here is the fictional reporting brief produced by the notes above.
| Brief field | Proposed entry |
|---|---|
| Reader | Operations manager evaluating a change to recurring reporting. |
| Task | Establish prerequisites before comparing approaches. |
| Working title | What to Check Before Replacing Your Reporting Spreadsheet. |
| Main question | Do we understand the inputs, owner, and failure well enough to choose another approach? |
| Evidence | Synthetic observations A1, B1, and C1 illustrate the workflow only. |
| Required sections | Current task, input inventory, ownership, comparison criteria, and reasons to defer. |
| Verification | A reporting specialist checks the proposed assessment questions. |
| Exclusions | No product superiority claims, customer quotations, demand estimates, or promised business results. |
In a real brief, replace synthetic references with permitted research evidence. Keep the distinction visible while the exercise remains fictional.
Specify what the opening must answer. Here, the opening should explain how to describe the current reporting problem before choosing software.
Specify what completion looks like for the reader. A useful result is a written inventory of inputs, ownership, constraints, and unresolved questions.
Do not require the writer to conclude that a new purchase is necessary. Let the assessment produce an honest decision to wait.
Send the brief through the team's editorial workflow. Assign review of evidence and review of subject accuracy as explicit responsibilities.
Keep contradictions in the handoff
Reserve a field for observations that challenge the proposed angle. A brief without that field can become a collection of supporting anecdotes.
In the fictional example, C1 prevents the outline from treating replacement as the default. The article needs criteria for retaining the existing spreadsheet.
Suppose another synthetic participant compares tools before identifying any internal owner. Keep that sequence too, with the conditions that made it possible.
The next research question becomes more precise: when does ownership block evaluation, and when can evaluation proceed without resolving it first?
Do not settle the disagreement by counting isolated comments. Ask whether participants describe the same task, constraints, decision authority, and stage.
If the accounts concern different situations, narrow the article's audience or split the candidate. If the evidence stays unclear, hold the conclusion.
Invite a colleague to challenge the proposed theme before drafting. Ask them which observation supports each section and which evidence the outline ignores.
Keep uncertainty attached to the claim it limits. A general disclaimer at the bottom does little when the opening overstates what the research established.
Check existing answers and search demand separately
Search the content inventory for the task and its component questions. Read the existing pages before assigning a new URL.
An existing comparison may already answer the main question but omit prerequisites. That finding could justify a later revision rather than another competing article.
For a new piece, state its distinct job in one sentence. The fictional readiness guide helps establish the current process before tool comparison begins.
Check that internal links lead to the next useful question. Avoid linking every mention of reporting to the same sales destination.
Interview language supplies candidate phrasing. It does not measure how often people search, how search results behave, or whether a page can attract relevant readers.
Keep those questions in a separate keyword research process. Record the date and source of any demand evidence used in prioritization.
If demand is unknown, label it unknown. A guide can still serve an existing buyer conversation without a fabricated monthly search estimate.
GOV.UK's user-needs guidance treats needs as evidence-based descriptions of user problems. The publication decision remains the editorial team's responsibility.
Before drafting, check the chain once more: relevant task, neutral account, bounded observation, tentative theme, answerable question, distinct brief.
Keep the evidence attached to the question.
Sources
- GOV.UK: Using in-depth interviews, checked October 28, 2026. Interview preparation and neutral questioning.
- GOV.UK: Analyse a research session, checked October 28, 2026. Observations, themes, findings, and actions.
- GOV.UK: Learning about users and their needs, checked October 28, 2026. Evidence-based needs and user problems.