Case Study 2 — The Brief That Recommended Nothing: Translating Research Into a Decision a Council Could Vote On

A contrasting scenario—Deep Dive. Where Case Study 1 was a business one-pager for executives who trust the author's judgment, this one moves to the policy world, where the reader is a non-expert who will vote on what they read and the author must translate research without distorting it. It shows the policy brief's defining failure—summarizing instead of recommending—and its ethical knife-edge: being clear and honest about uncertainty at the same time. Fictional but realistic; the data is illustrative, not a real study.

The setup

A city's data team finished an analysis: over two years, students in households without reliable home broadband completed homework and scored on standardized tests measurably below their connected peers, and the gap had widened during remote learning and not closed. About one in five students in the district lacked reliable home internet. A council member, deciding what to fund in the next budget cycle, asked the team for "a brief on the broadband-and-schools data."

The analyst wrote a careful, accurate brief. Here is how it ended:

Recent analysis of district data indicates a correlation between household broadband access and student academic outcomes. Students in households without reliable broadband demonstrated lower rates of homework completion and standardized test performance relative to peers with access. These findings are consistent with prior literature on the digital divide. Further research may be warranted to explore the mechanisms underlying this relationship.

The council member read it, set it down, and funded something else.

The diagnosis: a research summary masquerading as a policy brief

The brief wasn't wrong. Every sentence was accurate and appropriately cautious. But run it through the chapter's standard and it collapses—because it answered the analyst's question (what does the data show?) instead of the reader's (what should I do about it?).

The fatal phrase is the last one: "further research may be warranted." That is the academic reflex (Chapter 35's appropriate caution) imported into a genre that cannot use it. A council member can't fund "further research may be warranted." They can fund subsidies, or Wi-Fi, or nothing—and the brief pointed at none of those. It summarized the research and handed the hardest step, turning a correlation into a policy, to the reader least equipped to take it: a non-expert who isn't trained to know what a correlation does and doesn't license. This is Chapter 27's "finding with no 'so what?'"—at the scale of public policy, where the cost of the unmade decision falls on students.

There was a second, subtler failure lurking. The honest caution ("correlation," "further research") was real and important—the data genuinely couldn't prove that access caused the gap. But the analyst had let that honesty become an excuse not to recommend, when the right move was to recommend and design the recommendation around the uncertainty. Honesty about evidence and decisiveness about action are not opposites; the policy brief has to do both.

The rewrite: recommend, quantify, and design around the uncertainty

---

POLICY BRIEF · Closing the Student Connectivity Gap · For: City Council · [date]

Recommendation: Fund 1,200 home-broadband subsidies for low-income students in the next budget cycle, at an estimated $480K/year [est.], as a one-year program with a built-in evaluation.

The problem. Roughly 1 in 5 students in the district lacks reliable home internet. These students complete homework and score on standardized tests measurably below their connected peers—a gap that widened during remote learning and has not closed.

What the evidence shows (and doesn't). District data over two years shows a strong association between home access and academic outcomes, consistent with national research on the digital divide. The evidence that access drives the gap—rather than merely tracking other disadvantages—is strong but not definitive. That uncertainty is precisely why we recommend a structure that tests it (below).

The options: 1. Household subsidies — fastest, ~$480K/yr, reaches students immediately. (Recommended first.) 2. Public Wi-Fi expansion — broader reach, ~$1.2M capital, ~18-month build.

We recommend Option 1 now, with a one-year evaluation of academic outcomes, and a decision on Option 2 once we have local results. The main risk—subsidies reaching households that would have connected anyway—is mitigated by income-based eligibility.

Sources and the full analysis available on request.

---

What changed, and why each change matters:

• It leads with a specific, costed, authorizable recommendation—1,200 subsidies, $480K, next budget cycle. A council member can vote on that. ("Further research may be warranted" is gone.)
• The problem is quantified in plain terms (1 in 5 students), not "lower rates." The reader feels the scale.
• The uncertainty is kept—and made useful. "Strong but not definitive" is honest about the correlation, but instead of becoming a reason to do nothing, it becomes the justification for the program's design: a one-year evaluation that tests whether access drives the gap. The caveat is translated into policy, not buried and not used as an excuse.
• Real options with trade-offs (subsidies vs. Wi-Fi; speed vs. reach) respect that policymakers live in trade-offs—and a recommendation among them ("Option 1 first").
• The obvious risk is named with its mitigation (income-based eligibility), which builds trust rather than eroding it (Chapter 20's risk→mitigation, in a policy setting).

Why the honesty had to stay

It would have been easy to write a more persuasive brief by dropping the "strong but not definitive" line—claiming access plainly causes the gap and letting the recommendation ride on a clean causal story. That version would have been more compelling and dishonest: it would have led a council to act on a certainty the evidence didn't support. The honest move was harder and better: keep the decision-relevant uncertainty, and design the recommendation (a pilot with evaluation) so that the uncertainty is handled rather than hidden. This is the policy brief's ethical knife-edge, and the direct line to Chapter 38: translate and compress for the non-expert reader, yes—but never past the point where you've misled a decision-maker who is acting on your words and cannot check them against the study.

Note also what the rewrite did not do: it didn't drown the council in methodology. The single honest sentence about evidence ("strong but not definitive… that uncertainty is why we recommend a structure that tests it") was enough. Honesty about uncertainty doesn't require a statistics lecture; it requires one well-placed, plain-language caveat that changes how the reader should hold the recommendation.

The lesson

The first brief failed not because it was inaccurate but because it was inert—it summarized research for a reader who needed a decision. The rewrite recommended a specific, costed, authorizable action; quantified the stakes in plain terms; and kept the one caveat that mattered, turning it into the design of the program rather than an excuse to defer. A policy brief's job is not to inform a policymaker that a problem exists—it is to translate research into something they can vote on, honestly. The hardest part is doing both at once: being clear enough to act on and honest enough not to mislead. Summarizing is easy and safe; recommending honestly is the actual work.

Back to: Chapter 37 · Case Study 1 · Exercises · Key Takeaways