Audience Analysis for Policy Briefs

The Reader Determines the Brief

A policy brief is not a research paper. It exists to influence a specific decision-maker at a specific moment. The single most consequential choice you make as a writer is deciding who that reader is — because everything else flows from it. Tone, depth, structure, evidence type, and even page length all depend on who will read your brief and what they need from it.

A cabinet minister scanning briefs during a 15-minute car ride needs something fundamentally different from a parliamentary committee staffer who will brief their boss verbally. A municipal planning director wants implementation detail; a prime minister wants strategic options and tradeoffs. Writing for the wrong audience is the most common reason policy briefs fail to influence decisions.

Four Dimensions of Audience Analysis

Before drafting, profile your reader along four axes:

1. Technical knowledge. Does your reader understand the policy area, or are they a generalist? A health ministry official knows what QALY-adjusted cost-effectiveness means; a finance minister does not. Jargon that signals credibility to an expert signals laziness to a generalist.

2. Decision authority. Is your reader the final decision-maker, an advisor, or a gatekeeper? A gatekeeper (like a chief of staff) needs to be convinced your brief is worth passing up the chain. An advisor needs ammunition for the recommendation they will make verbally. The final decision-maker needs clear options with honest tradeoffs.

3. Time constraints. Senior officials rarely read more than two pages unprompted. Mid-level analysts may read ten. Knowing your reader's attention budget shapes your structure — front-load ruthlessly for time-poor readers, provide appendices for detail-hungry ones.

4. Political constraints. What positions has your reader already taken publicly? What constituencies do they answer to? A recommendation that ignores political feasibility will be dismissed regardless of its analytical merit.

Building a Reader Persona

Professional policy shops at organizations like the Brookings Institution and the OECD often create explicit reader personas before drafting. A persona is a short paragraph describing a composite reader: their role, what keeps them up at night, how they consume information, and what would make them act.

For example: 'Deputy Minister of Education, generalist background in law, manages a $2B budget, cares deeply about equity outcomes, reads briefs on a tablet during commutes, will ask about cost ' and implementation timeline within the first 30 seconds of any meeting.' This persona tells you: lead with equity impact, include a cost summary on page one, keep it under three pages, and make sure the implementation section has dates.

You do not need to write a formal persona every time. But spending two minutes answering 'Who is reading this and what do they need to decide?' before you outline saves hours of revision.