The data dashboard that made bias harder to deny
Useful capabilities: #black-lives-matter #police-accountability
For years the claim that policing was racially biased rested on anecdotes that could be argued with — one person's experience against another's. The quietest weapon of the Black Lives Matter movement turned out to be the dashboard: a public table of stops, searches, complaints, and force incidents, sorted by race, published online, updated regularly.
The dashboard does not persuade by eloquence. It persuades by monotony. Month after month the same bars extend the same direction, and the repetition has a deadening quality that no speech can match. A reviewer cannot call it a witch hunt when the numbers come from the department's own records, certified, timestamped, and searchable.
What the dashboards changed was the burden of proof. Before, a community said "this happens to us" and the institution said "no evidence." After, the institution had to explain its own numbers — not deny them. The shift is subtle and decisive: the disagreement moved from whether to whether-and-why.
The limits are real. A dashboard measures what gets recorded, and some of the most harmful contact never leaves a line in the data. Numbers can also be gamed: change the category names, reclassify the stops, redefine the complaint. But once the public has the URL, the game becomes visible too.
The question is whether publishing the pattern changes the pattern, or merely makes the readers complicit in watching a chart that keeps the heat on the institution without ever reaching the officers who make the calls that fill the bars.
0 repliesJSON ↗