Audience and Message Research

Reader Needs Map

Connect real audience situations, questions, barriers, decisions, and evidence to the information, sequence, format, and maintenance each content experience requires.

Free editable Markdown · Content strategists, UX researchers, and editorial teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Reader situation

Need ID: [Durable identifier]
Reader group: [Specific but not needlessly personal]
Situation and trigger: [What is happening now?]
Desired progress: [What are they trying to understand, decide, or do?]
Material constraints: [Time, device, language, access, knowledge, risk, or another]
Current behavior: [Where they look or what they do]
Barrier: [What prevents progress?]
Consequence of failure: [Why this matters]

Evidence and confidence

Evidence sources: [Interview IDs, support theme, query set, observation, or policy]
Evidence date: [YYYY-MM-DD or range]
Pattern observed: [What repeats across sources?]
Contradiction: [Evidence that does not fit]
Assumption: [What is inferred rather than known?]
Confidence: [High / Medium / Low, with reason]
Validation action: [Research needed and owner]

Stated preference is distinguished from observed behavior.
The need is not based on one unverified anecdote.
Missing or excluded audiences are documented.

Content requirement

Question to answer: [Use reader language where appropriate]
Minimum information: [Facts or steps required]
Required proof: [Source, example, demonstration, or limitation]
Sequence: [Order that supports the task]
Vocabulary: [Terms to use, define, or avoid]
Format and access: [Page, tool, download, audio, language, or another]
Next action: [Appropriate reader step]
Risk or review: [Accuracy, accessibility, privacy, or specialist need]

Coverage and outcome

Current content: [URL or None]
Coverage gap: [Missing, unclear, outdated, duplicated, or inaccessible]
Action: [Keep / Improve / Combine / Create / Retire]
Priority rationale: [Evidence, harm, reach, effort, or dependency]
Success signal: [Observable behavior or feedback]
Maintenance owner: [Role]
Review trigger: [Date or change event]

How to use this template

Gather research and operational evidence, then list distinct reader situations without assuming a particular content solution.
Write each need as a trigger, desired progress, decision or task, and material constraint.
Link evidence, label confidence, and separate confirmed patterns from assumptions and stakeholder requests.
Define the information, proof, sequence, language, format, accessibility, and next action needed for each situation.
Map current coverage, choose a content action, assign maintenance, and schedule validation of weak or changing needs.

Frame needs as progress in context

“Needs information about pricing” names a topic, not a need. Write the situation, trigger, decision, and constraint: “A team lead estimating next quarter’s budget needs to identify recurring and usage-based costs before requesting approval.” The same pricing page may also serve an existing customer checking an unexpected charge, whose evidence and next step differ. Avoid embedding the solution in the need statement. “Needs a video” may conceal the actual need to compare a process while away from a desk. Format should follow from context, access, and complexity.

Trace every requirement to evidence

Attach interview notes, support themes, search queries, task observations, analytics, policy requirements, or expert knowledge to each need. Mark source strength and date. Behavioral evidence and stated preferences can disagree; preserve both rather than selecting the convenient one. Distinguish an established pattern from a plausible assumption and give assumptions an owner and validation plan. If a loud stakeholder request lacks reader evidence, record it as a stakeholder need rather than relabeling it. This makes prioritization honest and reveals where additional research has the highest value.

Translate the map into content decisions

For each need, specify the minimum information, required proof, sequence, vocabulary, format, accessibility considerations, and next action. Identify content that already serves it, then decide whether to keep, improve, combine, create, or retire. A map is not a license to create one page per need; several compatible needs may belong in one coherent experience, while one broad page may need task-specific branches. Define how success will be observed and who keeps time-sensitive details current. Revisit the map when language, policy, product behavior, or audience conditions change.

See the fields in context

Fictional example: workshop cancellation

Pinebridge Learning Hall and its reservation process are invented.

Situation: A parent learns on the morning of a fictional workshop that their child is ill.
Need: Determine whether cancellation is possible and what action preserves any credit before the session begins.
Evidence: Three fictional support summaries show readers searched for “cancel class today,” while the page used “attendance amendment.”
Requirement: Put the deadline, exact action, confirmation signal, and credit limitation together in plain language.
Outcome signal: Fewer support contacts asking whether a submitted cancellation was received.

Frequently asked questions

Is a reader need the same as a search keyword?

No. A query can provide evidence about vocabulary and intent, but the need includes the situation, decision, constraints, and consequence. Different needs can use similar words, and one need can produce many queries.

Should every mapped need become a new page?

No. Choose the information architecture that supports coherent tasks. Combine compatible needs, improve an existing page, add a tool or contextual message, or retire duplication. Creating many thin pages can make the experience and maintenance worse.

How should confidence be rated?

Explain the evidence behind the label. Consider recency, source diversity, relevance to the target situation, observed behavior, sample gaps, and contradictions. Do not present a low-confidence assumption as a proven reader truth.

When should the map be updated?

Review it when research, support patterns, terminology, product behavior, policy, or audience conditions change, as well as on a sensible regular schedule. Time-sensitive needs require event-based triggers and named owners.