Stop Building Reports Nobody Reads (Build This Instead)
If your monthly report takes three hours to build and four minutes to skim, the problem isn’t the report. The problem is that you’re building reports nobody reads because they were designed to display data, not answer questions. A dashboard that lists everything you track is a filing cabinet with charts on the front. What your team actually needs is something that ends a debate, sharpens a decision, or kills an assumption. The shift is small to describe and uncomfortable to implement: stop showing what you have, and start answering what people are arguing about.
What question did your team argue about last meeting?
Before you build anything, ask the team what they argued about in their last meeting. Not what they want to see. Not what looks important. What did they actually disagree about, in real time, with stakes attached?
That’s your dashboard.
The 14-tab spreadsheet someone inherited in 2019 is not your dashboard. The template a consultant sold you in 2022 is not your dashboard. The funder report you cut and paste every quarter is not your dashboard. Those are artifacts. They describe activity. They don’t resolve disagreement.
A useful diagnostic: if the answer to what would change if this number went up or down is nothing, you’re tracking something nobody is using to decide anything.
Reports describe. Answers decide.
A good output ends with, “So we should…”, not “As you can see…”.
That single sentence is the cleanest way I know to test whether a report is doing its job. If you finish reading and you’re informed but not pointed at a choice, you’ve read a description. Descriptions are useful, but they’re a poor substitute for an answer.
Compare the two:
Descriptive: Program attendance was 412 this quarter, up 8% from last quarter.
Answering: Program attendance is up 8%, driven entirely by the Tuesday evening slot. Saturday morning has dropped three quarters in a row. We should either fix Saturday or move that capacity to Tuesday.
The data underneath both is identical. The work the report is doing is completely different. The first one tells you what happened. The second one tells you what to do about it.
If your monthly report is full of the first kind and nothing of the second, that’s why nobody opens it.
Why nonprofits build reports nobody reads
Reporting in nonprofits often gets built for funders first and staff second. That ordering quietly distorts everything downstream.
Funders need justification: proof that money was spent on the mission, proof that activity happened, proof that outcomes were measured. Those documents are designed to defend. They’re written to a specific audience with a specific question, and the question is usually some version of did you do what you said you’d do.
That’s a fine document. It’s just not the same document as one designed to help your program director decide whether to keep running the Saturday session.
When the funder document becomes the internal document by default, the people who could act on the data end up reading a report engineered to justify, not to inform. They skim it, file it, and make decisions the old way: by gut, by what was loudest in the last meeting, by what the longest-tenured person remembers from 2018.
The data is there. It’s just pointed at the wrong audience.
How do you replace the monthly report?
Stop thinking in documents. Start thinking in questions.
Replace your monthly report with a running list of live questions the team is actually trying to answer. Each question gets one view. When the question is answered or stops mattering, the view retires.
Here’s what that looks like in practice:
Capture the questions. At the end of every leadership meeting, write down what the team disagreed about or wasn’t sure about. Those go on the list.
Rank by stakes. Which question, if answered, would change a decision in the next 30 days? Start there.
Build one view per question. Not a dashboard with 12 charts. One view, one question, one clear read.
Set an expiration date. Every view gets reviewed quarterly. If nobody has referenced it, retire it. If the question has been settled, retire it.
Add new questions as they surface. The list is alive. It grows and shrinks with the work.
This sounds simple because it is. The difficult part isn’t the building. It’s letting yourself stop tracking things that aren’t tied to a decision.
What changes when you stop building reports nobody reads?
Three things, in roughly this order.
First, you build fewer charts. A lot fewer. The 14 tabs collapse into four or five views, because most of what was on those tabs was never tied to a choice anyone was making.
Second, the meetings get shorter. When the data points at a decision, the conversation moves from let’s review the numbers to let’s pick the option. That’s a different meeting, and it ends an hour earlier.
Third, and this is the quiet one: you notice how much of your tracking was performative. Tracking that existed because tracking felt responsible. Tracking that nobody used, nobody questioned, and nobody would have missed if it disappeared. Letting go of it feels uncomfortable at first, the way clearing out a closet always does. Then it feels like relief.
The mission gets more of your attention. The team makes faster decisions. The data finally earns its keep.
That’s the whole shift. Build for the question, not the audit. Retire what isn’t being used. Trust that fewer, sharper outputs will move the work forward more than a comprehensive report nobody reads.
Frequently asked questions
How is this different from a regular dashboard?
A regular dashboard shows metrics. A question-led dashboard shows the answer to a specific decision the team is trying to make. The difference is purpose: one is built to be comprehensive, the other is built to be useful. Comprehensive isn’t a substitute for useful.
What do we do about funder reporting?
Keep it. Funder reports serve a real purpose and have a real audience. The point isn’t to stop producing them. The point is to stop assuming they’re also the right document for internal decisions. They’re two different jobs that deserve two different outputs.
How many questions should be on the live list?
Fewer than you think. Most small nonprofits can run on five to eight active questions at a time. If the list grows past ten, you’re probably mixing strategic questions with operational noise. Split them, or cut the noise.
What if our team doesn’t know what they’re arguing about?
That’s its own diagnostic. If the team can’t name a disagreement or an open question, either the work is on autopilot (worth examining) or the meetings aren’t surfacing the real decisions (also worth examining). Either way, that’s the more important conversation to have first.
Do we need new software for this?
Almost never. Most teams already have the data and the tools. What’s missing is the question. A spreadsheet pointed at the right question beats a dashboard pointed at nothing.
If this kind of thinking is useful, the Meaningful Insights SubStack goes deeper into how small nonprofits can turn data into decisions without hiring an analytics team. Subscribe to for more notes on what to track, what to retire, and how to make your data earn its keep.