The document has everything. Outputs delivered. Outcomes measured. Disaggregated data. Tidy charts. A methodology section no one will read. It's comprehensive. It's rigorous. It's exactly what the funder asked for.

And it will move no one.

This is the gap we see again and again in the sector: organizations that are meticulous about evidence and bewildered about why their communications don't land. The report is done. Why isn't anyone paying attention?

Because a report isn't a story. And the sector has gotten very good at one while neglecting the other.

Reports answer questions. Stories raise stakes.

A report says: here's what we did, here's what happened, here's how we know. It's organized around accountability. It assumes a reader who needs to verify, who's checking your work.

A story says: here's what was at risk, here's what changed, here's why it matters. It's organized around meaning. It assumes a reader who wants to care, who's looking for a reason to stay engaged.

Both are necessary. But they serve different functions, and treating them as interchangeable is where organizations get stuck.

The funder report is not your annual communication to supporters. The program evaluation is not your case study. The data dashboard is not your impact narrative. Each has a job to do, and expecting one document to do all the jobs usually means it does none of them well.

The curse of completeness

Here's a pattern we see constantly: an organization has rich, compelling material—transformative participant journeys, unexpected insights, hard-won lessons—and they bury it in a comprehensive document designed to prove they did everything they said they would.

Completeness is the enemy of resonance. A story that tries to include everything includes nothing memorable. The reader drowns in information and surfaces with no clear impression.

Good storytelling is fundamentally about selection. What do you leave out? What details carry the weight of the whole? What single moment crystallizes the change you're trying to describe?

This is craft, not instinct. It requires editing with a machete, not a scalpel. And it requires someone in the room who's willing to say: "Yes, that's accurate, but it's not interesting. Cut it."

Characters, not categories

The sector has a habit of talking about people in aggregate. "Participants." "Clients." "Community members." "Youth facing barriers." The language is precise and respectful and completely abstract.

Stories need characters. Not case studies—characters. People with names and particularities, with contradictions and texture, with wants that drive them and obstacles that block them.

This doesn't mean every communication needs a first-person testimonial. It means the reader should come away with a felt sense of a human being, not a demographic category. It means writing that trusts specific detail to do the work that generalization cannot.

One woman who almost gave up but didn't will stay with your reader longer than a hundred "program participants who demonstrated improved outcomes." Not because the data doesn't matter, but because the data doesn't move.

Tension is not optional

A story without tension is a summary. Things happened, then other things happened, and now here we are.

Tension is what creates forward momentum. It's the gap between what is and what could be—between the problem as it exists and the future the work is trying to bring about. It's uncertainty, struggle, risk. It's the possibility of failure.

Organizations are often reluctant to foreground tension in their communications. It feels like admitting weakness, inviting scrutiny, undermining confidence in the work. But the opposite is true. A story that acknowledges difficulty is more credible, not less. It signals honesty. It creates room for the reader to root for something.

The work you do exists because something is broken. Don't skip past that brokenness in your rush to prove you fixed it.

Audience is everything

The most common mistake in impact communications is writing for everyone. The second most common mistake is writing for funders when you're trying to reach someone else.

Different audiences need different things. A program officer evaluating your grant performance needs evidence of accountability. A potential donor needs to feel moved by possibility. A peer organization needs to see your methodology. A board member needs confidence that things are on track. A participant needs to see themselves reflected with dignity.

One document cannot do all of this. And pretending it can leads to muddled communications that speak to no one in particular.

Before you write anything, ask: Who is this for? What do they already know? What do they care about? What do we want them to feel, and then do, after reading this?

If you can't answer those questions clearly, you're not ready to write.

The integration question

None of this means data doesn't matter. The best impact communications braid evidence and narrative together—using story to make data meaningful and data to make story credible.

A number without context is noise. "We served 847 people" lands differently than "We served 847 people—triple what we'd planned, because word spread through the community faster than we could keep up."

A story without evidence is anecdote. A single powerful testimonial gains weight when it's situated within a pattern: "Maria's experience reflects what we heard across dozens of interviews."

The integration is the craft. Not data or story, but data in service of story, story grounded in data. Each doing what the other cannot.