Why don’t non-profit research reports get read?

Non-profit research reports often go unread because they're written for an imagined academic audience rather than the program staff, funders, and community partners who would actually use the findings. Most reports prioritize methodological thoroughness and dense narrative over scannability, clear recommendations, and formats suited to how each audience works. When usability isn't built into the research process from the start, even strong findings end up sitting in a PDF that few people open.

What makes a research report usable?

A research report is usable when the people who need to act on it can find the information that matters to them, understand it without specialized training, and apply it to a real decision. That generally requires writing for specific audiences rather than everyone at once, leading with findings and recommendations instead of methodology, and offering formats beyond a long PDF, such as briefs, visuals, or short summaries tailored to each group.

Is unread research an ethical issue?

Yes. When community members, program staff, and partners give their time and stories to a research project, they do so with the implicit expectation that the findings will be used. Producing a report that almost no one reads means converting that generosity into a document that sits on a shelf, which is a failure of responsibility to the people who made the research possible, not only a missed communications opportunity.

How can non-profits make their research more useful?

Non-profits can make their research more useful by deciding who the audience is before writing begins, mapping how each audience will encounter and use the findings, and producing formats that fit those contexts. That might mean a short brief for funders, a visual summary for community partners, an internal tool for program staff, or a public-facing version for advocacy, all drawn from the same underlying research.

Research That Sits on a Shelf Fails the Communities It Studied

In the non-profit sector, an unread report is treated as a disappointment. It should be treated as a breach of trust. Every research project depends on the generosity of people who have very little reason to be generous: community members who sit for interviews, staff who carve hours out of overloaded weeks, partners who open their data and their networks. When the resulting report is downloaded a handful of times and then forgotten, that generosity has been spent on something that benefits almost no one.

The failure here isn’t a communications failure, though it’s almost always described that way. It’s ethical. Packaging findings in a format almost no one can use, after asking communities to make the research possible, is not a small thing.

This article makes the case that an unread report is not simply an inefficiency or a missed marketing opportunity. When communities give their time and stories to research, packaging the findings in a format almost no one can use is an ethical failure, not just a communications one. In the sections that follow, we will look at why so many reports end up unread, what organizations owe the people whose lives shaped the research, and how to start treating usability as a core part of ethical practice rather than a final polish.

The Responsibility We Owe to Participants

Every research project in the social impact space is built on the generosity of others. Community members sit down for interviews and share things they may never have told a stranger before. Program staff carve out hours from already overloaded weeks to fill in surveys or join focus groups. Partner organizations open their data, their networks, and sometimes their internal politics to scrutiny.

When a report doesn’t reach the people who could act on it, all of that generosity gets converted into a PDF that no one opens. The community members who participated don’t see their realities reflected back in ways that change how programs are run. The staff who contributed don’t see their input shape the next funding cycle. The findings that could’ve informed policy or practice stay locked inside a document written for an audience that wasn’t really there.

That’s the part that sits uncomfortably with us. When you ask people to share their time, their stories, and sometimes their pain, you’re making an implicit promise that what they offered will be put to use. A report that’s technically published but practically ignored breaks that promise, even if no one says so out loud.

How Usability Gets Overlooked

Most organizations don’t set out to produce an unusable report. The teams we work with are thoughtful, mission-driven, and genuinely invested in doing right by the communities they serve. What tends to happen is that so much energy goes into presenting the data thoroughly and accurately that there’s little left over to ask a different set of questions. Who’s going to read this? What decision are they trying to make? How will they encounter it, and in what format will it actually be useful to them?

Those questions often don’t come up until the report is already drafted, designed, and ready to ship. By then, it’s too late to restructure the document around how a frontline worker reads on their phone between client appointments, or how a funder skims for evidence of impact before a board meeting, or how a community partner wants to see their contributions acknowledged.

Usability gets overlooked, not dismissed. And the cost of that oversight shows up later, in the form of findings that never make it into practice.

What Usable Research Looks Like

Usable research starts with a different opening question. Instead of asking what we found, it asks who needs to know, and what they need it for. That change in perspective impacts almost everything downstream, from the structure of the document to the formats it gets packaged in.

In practice, usable research tends to share a few characteristics. It’s built with specific audiences in mind, not a generic “stakeholder.” It’s available in more than one format, because a fifty-page PDF and a one-page summary card serve different readers. It uses language that frontline staff and community members can actually engage with, rather than language calibrated for an academic reviewer who isn’t reading it anyway. And it makes the path from finding to action as short as possible, so the people who could use the work don’t have to translate it themselves.

None of this means dumbing down the research. Rigour and usability aren’t in competition. A well-designed brief, a clear visual summary, or a short video walkthrough can carry the same evidentiary weight as a long report, and reach far more of the people who need it.

Where to Start

If you’re sitting with a report that’s about to be published, or one that’s already out in the world and not getting the traction you hoped for, the most useful thing you can do is pause and ask who it’s really for. Not in the abstract, but specifically. Name the people. Picture how they’ll encounter it. Think about what they need to do after they read it, and whether the current format makes that easy or hard.

That’s the work we’ll be digging into at our upcoming Wunder Webinar, Stop Writing Reports No One Uses, on June 17, 2026. In thirty minutes, Doaa Abou Hussein will walk through how to spot when a research product is heading toward the shelf, how to choose formats that make findings easier to use, and how to advocate for non-traditional outputs that actually reach the people they’re meant to serve. Every attendee will also receive a usable research checklist they can apply to any report, deck, or summary to test whether it’s likely to land.

The research your organization produces deserves to be used. So do the stories, time, and trust that went into making it possible.

import { injectHsEmbed } from ‘https://thirdwunder.com/wp-content/plugins/hubspot-content-embed/build/hsEmbedInjector.js’; const elementId = “hs-embed-client-inject-214172525192-0530”; const embedDomain = “https://21237790.hs-sites.com/_hcms/embed/214172525192”; const embedId = 214172525192; const options = { sendCurrentUTKAsParam: true }; injectHsEmbed(embedId, embedDomain, elementId, options).catch((err) => { // If the embed fails for some reason, just completely hide it console.error(‘HubSpot Content embed injection error:’, err); document.getElementById(elementId).style.height = 0; document.getElementById(elementId).style.minHeight = 0; })

FAQ

Why don’t non-profit research reports get read?

Non-profit research reports often go unread because they’re written for an imagined academic audience rather than the program staff, funders, and community partners who would actually use the findings. Most reports prioritize methodological thoroughness and dense narrative over scannability, clear recommendations, and formats suited to how each audience works. When usability isn’t built into the research process from the start, even strong findings end up sitting in a PDF that few people open.
What makes a research report usable?

A research report is usable when the people who need to act on it can find the information that matters to them, understand it without specialized training, and apply it to a real decision. That generally requires writing for specific audiences rather than everyone at once, leading with findings and recommendations instead of methodology, and offering formats beyond a long PDF, such as briefs, visuals, or short summaries tailored to each group.
Is unread research an ethical issue?

Yes. When community members, program staff, and partners give their time and stories to a research project, they do so with the implicit expectation that the findings will be used. Producing a report that almost no one reads means converting that generosity into a document that sits on a shelf, which is a failure of responsibility to the people who made the research possible, not only a missed communications opportunity.
How can non-profits make their research more useful?

Non-profits can make their research more useful by deciding who the audience is before writing begins, mapping how each audience will encounter and use the findings, and producing formats that fit those contexts. That might mean a short brief for funders, a visual summary for community partners, an internal tool for program staff, or a public-facing version for advocacy, all drawn from the same underlying research.

Table of Contents

Research That Sits on a Shelf Fails the Communities It Studied

The Responsibility We Owe to Participants

How to Turn Your Annual Report Into a Full Year of Social Media Content / 7 mins read

How Community Data Is Powering Smarter Social Services in Quebec / 4 mins read

How Usability Gets Overlooked

What Usable Research Looks Like

Where to Start

Elizabeth Holloway

Why Your AI Content Strategy Depends on Infrastructure, Not Prompts

The Organizations Making Pride Real All Year Round

Where Non-Profit Teams Should Start with AI Adoption

Stop Writing Reports No One Uses

Earning Attention Through Human-Centred Video Storytelling

How to Build a Team That Leads Itself