Articles • Aurora Pioneer

Overhead view of cocktail book, financial charts, and red pencil on desk.

2025-12-16 · Seasonal offers

What local authority budget data can and cannot tell you about strategic intent

The most common mistake analysts make when they open a local authority's statement of accounts is treating spending totals as a map of what the organisation actually cares about. A children's services directorate absorbs 38% of net expenditure, so children must be the priority — that is the logic, and it costs people real money when they act on it. Commissioners use this reasoning to benchmark councils against each other. Consultants use it to advise on restructuring. Think-tanks use it to rank authorities by apparent ambition. The forty-three-authority longitudinal study we carried out at Aurora Pioneer, tracking published accounts from 2016-17 through 2022-23, kept running into the wreckage that reasoning leaves behind. Spending shares shift for reasons that have almost nothing to do with political will, and the accounts, on their own, cannot tell you which reason applies. Read more →

2025-10-19

When a data audit is the right first step before a strategy refresh

Most strategy refreshes begin with a blank slide deck and a room full of confident opinions. The trouble is that the opinions are usually built on numbers no one has checked since the last strategy cycle, which could be three years ago or could be seven. In the projects Aurora Pioneer has worked through over the past two years, the single most common source of bad strategy is not poor thinking — it is unexamined data that has quietly gone stale while everyone assumed it was fine. A data audit, run before the first workshop, changes the starting conditions of the whole exercise. This piece explains when that audit is genuinely worth the time and what it most reliably turns up.

2025-07-27

The difference between a rapid evidence assessment and a proper systematic review

If someone hands you a research brief and a six-week deadline in the same breath, do you actually know which kind of evidence review you are commissioning? Most project leads say yes, then describe a rapid evidence assessment when they mean a systematic review, or the other way around. The confusion is understandable: both involve searching literature, screening studies, and producing a synthesis document, and both get called "the evidence base" in board papers. But the differences between them are not cosmetic. They determine how far you can trust the answer you get back, and whether that answer will survive scrutiny from a policy audience, a funder, or a regulator. This piece maps those differences honestly, including the parts that most methodology guides quietly skip over.

2025-03-10

How to tell whether an evidence review has actually reviewed the evidence

A policy team receives a systematic review. It has a DOI, a university logo on the cover page, and a references section that runs to four pages. Someone marks it "evidence base confirmed" and the briefing moves forward. This happens dozens of times a year across government departments, quangos, and commissioning bodies — and it is one of the most quietly consequential shortcuts in public policy. When Aurora Pioneer spent several months quality-assessing seventy-one systematic reviews produced in a single intervention field, the finding that kept surfacing was not that the reviews were fraudulent or even careless. It was that the gap between what a review claimed to do and what it had actually done was almost never visible from the abstract alone. The five questions in this article are designed to close that gap, in plain language, before a review gets cited in a briefing, a funding decision, or a parliamentary submission.

2025-01-29

Designing a programme evaluation that funders and practitioners will both actually read

Most evaluation reports land in inboxes and stay there. The funder finds the executive summary too thin, the practitioner finds the methodology section impenetrable, and the whole document quietly fails at both jobs it was hired to do. At Aurora Pioneer we have spent the past several years building evaluation frameworks for programmes ranging from early childhood literacy pilots to municipal employment schemes, and the pattern we keep finding is the same: the problem is not the quality of the findings. The problem is that the report was designed as a single document for a composite reader who does not actually exist. What follows is a behind-the-scenes account of how we restructure that process so the evaluation genuinely serves both audiences, without hiding the complexity from either.

News & Announcements