Policy Analysis Project: Diagnose, Propose, Persuade

Overview

Most people have opinions about policy. Almost no one can defend one rigorously. In this project you will take a single, real policy problem — local, state, or national — and treat it the way a professional analyst would: diagnose what is actually wrong, map who is affected and why the problem persists, design a concrete solution, attack your own solution harder than any critic would, and then stand in front of a real audience and make the case. This is not a debate-club exercise. The deliverable is a professional policy brief and a presentation good enough that the people who actually touch this issue would take it seriously.

The Deliverable

Two things, both judged by real-world standards:

1. A policy brief: 8-12 pages. The format real analysts use — an executive summary, a clear problem statement, a stakeholder and incentive map, an options analysis, a recommendation, an honest treatment of the strongest objection, and an implementation sketch. Cited. Tight. Written so a busy decision-maker could read the first page and know exactly what you are arguing.

2. A presentation to a relevant audience. Not your family at the kitchen table. A real audience with some connection to the issue: a city council public-comment session, a school board meeting, a nonprofit's board, a town hall, a local representative's staff, a community organization, or — at minimum — a panel of two or three adults with genuine expertise in the area who have agreed to question you hard. You present for 8-10 minutes and take questions.

"Done" looks like this: a stranger with authority over this issue reads your brief and says, "This person did their homework, and I now understand the tradeoff better than I did before." That is the bar. Not agreement — respect.

Materials & Tools

Project Phases

Phase 1: Plan — Choose and Diagnose (Weeks 1-2)

Choose a problem you can actually get your arms around. "Fix healthcare" is not a project; it is a lifetime. "Reduce the 45-minute average emergency response time in our county's rural northern district" is a project. Bias hard toward local and specific. Local issues have accessible data, reachable stakeholders, and a real audience you can actually present to. They are also where a motivated young person can have genuine impact, which national issues rarely offer.

Strong project shapes:

• A local ordinance, zoning rule, or permitting process that helps or hurts builders and small businesses
• A school district policy on something you have direct experience with
• A municipal budget tradeoff (the town can fund X or Y, not both)
• A regulation that affects an industry you know — food, construction, software
• A state-level issue with good public data where you can present to a representative's office

Then diagnose before you prescribe. This is the discipline most people skip, and skipping it is why most policy debate is useless. Spend real time separating three different things: the symptom (what people complain about), the problem (the underlying cause), and the politics (why the obvious fix has not already happened). Write a one-page problem statement that a smart person could not poke an immediate hole in. If your problem statement contains a solution smuggled inside it — "the problem is that we don't have enough X" — you have not diagnosed, you have pre-decided. Rewrite it.

A practical diagnostic tool: the "five whys." Take the complaint as people state it and ask why, then ask why of the answer, five times down. Emergency response is slow. Why? The nearest station is too far. Why? The county closed the northern station. Why? It cost too much to staff. Why? Call volume there did not justify a full crew. Why? The population is dispersed and aging, but funding is allocated by call volume, not by response-time risk. Five whys in, you have moved from a symptom anyone could name to a root cause — a funding formula that optimizes for the wrong thing — that almost no one has articulated. That root cause is your real problem statement, and it points toward solutions that treating the symptom never would.

By the end of Phase 1 you also need your audience lined up, at least tentatively. Send the emails. Make the calls. This takes longest, so start it first. Here is how to ask: keep it short, lead with respect for their time, state plainly that you are a student doing serious analysis of an issue they care about, and request a specific, small commitment — "ten minutes of public comment at your next meeting" or "thirty minutes for me to walk three of you through a brief." Most people say yes to a prepared, polite young person far more often than you expect, because most of what crosses their desk is neither prepared nor polite. The few who say no cost you nothing. Send five requests, not one, so a single decline does not stall the whole project.

Phase 2: Build — Map, Research, and Design (Weeks 3-6)

Milestone 1 — The stakeholder and incentive map. Every policy creates winners and losers, and the reason bad policy persists is almost always that someone benefits from it. Make a map: who is affected, how, and what each party wants. For each stakeholder, write their incentive in one honest sentence — not the noble version, the real one. The most important entry on the map is usually the group that benefits from the status quo, because they are who any real solution has to get past. If your map has no one defending the current situation, you have not looked hard enough.

Milestone 2 — The evidence base. Gather the real numbers. Government data portals, agency reports, budget documents, academic studies, and — where you can get them — interviews with people who live inside the issue. A ten-minute conversation with someone who actually administers the policy is worth more than ten hours of reading op-eds. Cite everything. Distinguish hard data from estimates from opinion, and never launder one into another. If a number is shaky, say so; an honest "the best available estimate is X, but it is contested" is stronger than false confidence.

Treat your sources with the suspicion of an investigator, not the gratitude of someone who found something that agrees with them. For every number you plan to use, ask three questions. Who produced this, and what did they want to be true? A figure from an industry trade group, an advocacy nonprofit, or a political campaign is not worthless, but it was produced by someone with a stake, and you must know which way their thumb was on the scale. How was it measured? A statistic about "crime" means nothing until you know whether it counts reported incidents, arrests, or convictions — three wildly different numbers. Compared to what? A figure with no baseline is a magic trick; "spending rose by $2 million" is meaningless until you know whether that is a rounding error or a doubling. The most persuasive thing in your entire brief will not be the cleverness of your argument; it will be the evident care with which you handled the evidence. Decision-makers are surrounded by people pushing motivated numbers. The young analyst who visibly checked their own sources, disclosed the weak ones, and refused to overclaim will stand out precisely because that rigor is so rare.

Milestone 3 — The options analysis and recommendation. Real analysts do not present a single answer; they present options with tradeoffs and then recommend one. Lay out three to four genuine alternatives — including "do nothing," which is always an option and often the one to beat. For each, state the cost, the benefit, who it helps and hurts, and the implementation difficulty. Then make your recommendation and defend why it beats the others. A recommendation that has not survived comparison to real alternatives is just your first idea wearing a suit.

A discipline that separates real analysis from advocacy: each of your options must be a genuine option, not a strawman built to make your favorite look good. The cheap version of this milestone presents one real proposal flanked by two obviously terrible ones, so the conclusion is rigged before the reader starts. Anyone serious will see through it instantly and stop trusting you. The honest version presents alternatives that a smart person might actually prefer, and then wins the argument on the merits. Build a simple comparison table — options down the side, and across the top the criteria that actually matter for this problem: cost, time to implement, who bears the burden, political feasibility, and reversibility. Reversibility deserves special weight: an option you can undo if it fails is worth more than an equally good option you cannot, because it lets you learn from a mistake instead of being trapped by it. Score each option honestly, even where the scoring hurts your preferred answer. If your recommendation still wins after honest scoring, you have a real case. If it does not, you have learned something more valuable than a tidy conclusion: you were about to recommend the wrong thing, and the table caught it.

Phase 3: Test & Refine — Steelman the Opposition

Before you write the final brief, do the single hardest and most important thing in this project: build the strongest possible case against your own recommendation. Not a strawman you can knock over — the version the smartest, best-informed opponent would actually make. Write it out at full strength. If you cannot make the opposing case compellingly, you do not understand the issue well enough to recommend anything.

Then handle it honestly in the brief. Sometimes steelmanning the opposition will reveal that your solution is wrong, or partial, or has a cost you were ignoring. When that happens, change your recommendation. Changing your mind in response to the strongest counterargument is not weakness; it is the entire point of analysis as opposed to advocacy. A brief that engages and survives the best objection is ten times more persuasive than one that pretends no objection exists.

Test the brief itself, too. Hand it to someone unfamiliar with the issue and watch where they get confused, where they stop believing you, where the argument sags. Revise until a busy stranger could read the executive summary and correctly state your recommendation and your single best reason for it.

Phase 4: Present

Deliver to your real audience. Eight to ten minutes, then questions. Some hard-won rules for the room:

• Lead with the problem and the recommendation, not the background. Decision-makers are busy. Tell them what you want and why in the first ninety seconds, then earn the rest.
• Bring a one-page leave-behind. Most of your audience will not remember your slides. A tight one-pager that states the problem, the recommendation, and the three strongest supporting facts will outlive the room.
• Welcome the hostile question. When someone challenges you — and at a real venue, someone will — that is the project working. Answer the question they asked, concede the points that are fair, hold the ground that is defensible, and never bluff a number you do not have. "I don't know, but I can find out" is a completely acceptable and respectable answer.
• Record it if you can. Watching yourself field questions is uncomfortable and enormously instructive.

What a Strong Brief Actually Looks Like

To anchor the standard, here is the skeleton of a brief that would earn respect, using the rural emergency-response example. The executive summary, half a page, states the whole argument: "Emergency response times in the northern district average 45 minutes, more than double the county standard, because the county allocates fire and EMS funding by call volume rather than by response-time risk. This brief recommends adding a single weighting factor to the existing funding formula, at an estimated annual cost of $X, which would justify a staffed first-responder presence in the north without new bureaucracy." A decision-maker who reads only that paragraph already knows the problem, the cause, the fix, and the cost.

The body then earns each claim. The problem statement traces the five-whys chain to the funding formula. The stakeholder map names the county budget office (wants to control costs and avoid setting precedents), the northern residents (want faster response and feel forgotten), the existing stations in the populous south (quietly do not want their funding reallocated — the status-quo defenders), and the elected commissioners (want to help without raising taxes or angering the south). The options analysis compares doing nothing, building a new station (expensive, slow, politically hard), reallocating the formula (cheaper, faster, fought by the south), and a volunteer-responder program (cheapest, least reliable). The recommendation picks the formula change and defends why it beats the others on the comparison table. The steelman section gives the south's strongest objection full voice — "every dollar moved north is a dollar of slower response somewhere that has more total emergencies" — and answers it honestly with the response-time-risk data rather than dismissing it. That structure, executed with real numbers and real citations, is the difference between a student exercise and a document a commissioner would actually carry into a meeting.

Success Criteria

• The problem statement separates symptom, cause, and politics, and contains no smuggled-in solution
• The stakeholder map names at least one party that benefits from the status quo and states each party's real incentive honestly
• The brief presents three or more genuine options, including "do nothing," each with tradeoffs
• The brief contains a full-strength steelman of the strongest objection, honestly addressed
• Every factual claim is cited, and data, estimates, and opinion are clearly distinguished
• The presentation was delivered to a real, relevant audience — not just family — and the student fielded unscripted questions
• The student can state their recommendation and its single strongest justification in under thirty seconds, from memory

Common Pitfalls

• Choosing too big a problem. The number-one project killer. National issues have no accessible data, no reachable stakeholders, and no audience you can present to. Go local, go specific, and you can actually finish — and possibly affect something real.
• Advocating instead of analyzing. If you picked the issue because you already "know the answer," you will skip the diagnosis and steelman, and the work will be worthless. The tell is that your brief has no honest tradeoffs in it. Real policy always has tradeoffs; a brief with none is propaganda.
• Mistaking sources for evidence. Twenty op-eds that agree with you are not evidence; they are an echo. One government dataset, one budget line, one interview with someone inside the system outweighs a stack of opinion pieces.
• Skipping the audience until the end. Securing a real venue takes weeks of emails and follow-ups. Students who leave it to the final week end up presenting to their parents, which defeats the purpose. Start the outreach in Phase 1.

Extensions

• Turn the brief into action. If your recommendation is sound and local, do not stop at the presentation. File the public comment. Request the follow-up meeting. Organize others around it. A policy analysis that changes an actual decision is a capstone-worthy achievement and a genuine portfolio piece.
• Write the op-ed version. Compress your brief into a 700-word op-ed and submit it to a local paper or a relevant publication. Translating rigorous analysis into persuasive public prose is its own discipline, and a published piece carries real weight.
• Run the opposing analysis. As a separate exercise, write the brief that recommends the opposite of what you concluded, at full strength. Being able to argue both sides convincingly is the mark of someone who truly understands an issue rather than merely holding a position on it.
• Brief a real official. Take what you built to a member of your city council, school board, or representative's staff and ask for fifteen minutes to walk them through it. Most local officials will meet a serious, prepared young person — and you will learn how policy actually gets made, which is messier and more human than any brief can capture.