top of page

Why Many NGO Reports Are Ignored (And How to Fix That)

  • Writer: Donfelix Ochieng
    Donfelix Ochieng
  • Jan 20
  • 3 min read

Communication, clarity, storytelling

You've just handed in a report—pages of hard-earned data, a transparent methodology, and polished tables. You're proud—but a week later, no one mentions it. No feedback. No actions. It sits in a folder, unopened.

If this sounds familiar, you're not alone.

Across the development sector, organizations produce thousands of reports every year—evaluations, baselines, impact assessments, and situation analyses. But so many of these reports never influence decisions. They end up in archives instead of shaping strategy.

So why does this happen? And how do we fix it?

Let's unpack this without jargon.

 

research communication

1. The Problem: Reports That Don't Get Read

The most straightforward answer is this: many NGO reports are not written for their real audience.

You might have spent weeks cleaning data, running analyses, and drafting summaries—but the intended users (decision-makers, programme managers, partners, and communities) often don't read them. Why?

A few common reasons:

  • Dense language and technical jargon

  • No clear answers to real questions

  • Lack of actionable recommendations

  • Buried insights in long documents

Even the Harvard Business Review notes that "the way information is communicated affects whether it is used"—not just what the information says. The point isn't just to inform but to influence.

 

2. Why It Matters: Reports Should Lead to Decisions

A report that doesn't inform a decision is like a map no one uses—detailed but irrelevant.

For NGOs, ignored reports have real consequences:

  • Programmes repeat the same mistakes

  • Donors see little value in evidence

  • Communities feel unheard

  • Opportunities for improvement are lost

The OECD frames this well in their "Bridging Research and Policy Practice" work: "Data and evidence must be communicated in ways that are timely, accessible, and relevant to be useful." Reports that are too long, too technical, or poorly structured fail this test.

 

3. A Better Way: Make Your Report Usable

Think of a report as a conversation—not a deposit of information. The audience should feel guided, not overwhelmed.

Here are practical ways to make that happen:

 

a) Start with the Most Important Thing

Don't bury the lead.

Begin with a short executive summary that answers the key questions:

  • What did we set out to learn?

  • What did we find?

  • What should happen next?

This aligns with best practices, which emphasize front-loaded insights so busy readers can immediately grasp the report's value.

 

b) Use Plain Language

Write like you're explaining it to a thoughtful colleague—not a textbook.

Avoid heavy terms like "ameliorate" or "operationalize." These don't add meaning and often block understanding.


writing on well by William Zinsser

c) Tell a Story with Your Data

People remember stories, not tables. Narrative gives context.

Here's a trusted structure:

  1. Problem or question

  2. What we did

  3. What we found

  4. What it means

  5. What we recommend

This mirrors what communication researcher William Zinsser calls "clarity through simplicity."  When your reader can follow the narrative, the insights stick.

 

d) Visuals That Explain—Not Just Decorate

Charts and graphs should do one thing: make understanding faster.

Avoid complex infographics that require a page-long legend. Instead:

  • Use clear labels

  • Show trends, not raw clutter

  • Annotate key points

A single good chart can replace several paragraphs.

 

e) Include Practical Recommendations

A report should answer not just what was found, but also what should happen next.

Recommendations should be:

  • Specific: "Train 20 community volunteers..."

  • Actionable: "Use existing budget lines..."

  • Linked to evidence: "Because 65% of women reported …"

Decision-makers don't use reports; they use answers.

 

4. A Real Example (Simplified)

An NGO conducted a midline survey for a youth skills programme. The 50-page report covered enrollment numbers, attendance, facilitator performance, and satisfaction.

Problem: Decision-makers didn't act. They said it was "too long" and "not clear enough."

Here's what will be fixed next time:

  • 2-page front-loaded summary

  • Key charts with arrows and labels

  • Practical recommendations tied to budgets

  • A short slideshow version for managers

Outcome: The programme adjusted its scheduling and facilitator support based on precise, timely, and actionable insights.

 

5. Takeaway: Reports Are for Action, Not Just Archives

A good report informs. An excellent report changes minds and actions.

When we think of reports as communication tools—not just academic exercises—the way we write, structure, and present them changes.

At the end of the day, evidence isn't robust because it's accurate. It's powerful because it's understood, trusted, and used.

And that's how reports go from being ignored…to being influential.

Comments


© 2026 TechMedMind. All rights reserved.

bottom of page