Skip to main content

2. Audience & Stakeholder Analysis

Tier: All Tiers | Part: Foundation

The Four Developer Personas​

Junior Developer​

Needs step-by-step guidance, relies on code examples. Needs: Getting started guides, tutorials.

Senior Backend Engineer​

Scans reference docs quickly, wants complete parameter tables. Needs: Full reference docs, OpenAPI specs.

DevOps / Integration Engineer​

Focused on reliability, webhooks, rate limits. Needs: Conceptual docs, architecture overviews.

Startup CTO​

Evaluating the API. Needs: Overview pages, capability summaries.

Audience Analysis Template​

## Audience Analysis — [Project Name]

### Primary Audience
- Who are they?
- What is their technical level?
- What do they want to accomplish?

### Secondary Audience
- Who else reads these docs?

### Stakeholders
- Who reviews documentation?
- Who approves it?

### Content Implications
- What documentation types are needed?
- What code languages for examples?

NotiFlow Example​

Primary: Junior to mid-level developers integrating messaging. Code languages: JavaScript (primary), Python (secondary) Priority: Getting started guide + authentication docs

Checklist​

  • Primary developer persona identified
  • All stakeholders mapped
  • Audience analysis template completed
  • Code languages confirmed