Audience analysis is the process of determining who the reader is, what they know, what they need, and what they’re trying to do — before writing a word. In technical writing, audience analysis is not preliminary research but the foundation that every structural and stylistic decision rests on.

Karen Schriver identified three approaches to audience analysis, each with different reliability [@schriver1997]:

  1. Classification-based — the writer categorizes readers by demographics, role, or expertise level (“engineers with 3+ years of experience,” “new users,” “administrators”). This is the most common approach and the least reliable, because categories obscure the variation within them. Not all “new users” know the same things or want the same outcomes.

  2. Intuition-based — the writer imagines the reader and predicts what they’ll understand, where they’ll struggle, and what they’ll need. This is better than classification because it engages with specific reading situations, but Schriver’s research found that writers systematically overestimate reader comprehension. The writer who knows the material cannot reliably simulate the experience of someone who doesn’t.

  3. Feedback-based — the writer tests the document with real readers and revises based on observed difficulties. Think-aloud protocols, usability testing, and protocol-aided audience analysis are feedback-based methods. Schriver’s research showed this approach consistently outperforms the others because it replaces the writer’s assumptions with evidence.

Linda Flower framed the underlying problem: writers naturally produce writer-based prose — text organized around their own discovery process rather than the reader’s needs [@flowerhayes1981]. Audience analysis is the corrective: it forces the writer to ask “what does the reader need, and in what order?” rather than “what do I know, and how did I learn it?”

In practice, most technical writing projects combine all three approaches: classification to define the initial audience, intuition to draft, and feedback to revise. The key insight is that the first two are starting points, not endpoints — only feedback reveals whether the writing actually works.

  • audience — the general writing concept that audience analysis operationalizes
  • usability testing — the most rigorous form of feedback-based audience analysis
  • writer-based prose — what audience analysis corrects
  • task analysis — the companion process: determining what the reader is trying to do