# Reader Needs Map

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

## Usage note

Build this map from observable research, service evidence, and explicit assumptions—not from keyword volume alone or an invented average reader. Keep distinct situations separate when they lead to different decisions. Use the map to define content requirements and research gaps, then verify the result with readers and operational owners.

## How to use this template

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

## Blank template

### 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]