Telling Your Impact Story: A Practical Guide to Credible Data Storytelling

Impact stories usually fall short in one of two ways: numbers with no meaning, or a story with no evidence

Impact stories usually fall short in one of two ways: they offer numbers with no explanation of what the numbers mean, or they offer a moving story with no evidence to show how typical it is. Both happen to organizations doing good work. Organizations doing meaningful work often know their programs are making a difference but struggle to demonstrate that difference, usually because the people who run the program are busy running it and the reporting comes at the end.

A report built only from numbers can be technically accurate and still leave a funder, a board, or a leadership team asking "So what?" A table showing how many people completed a program describes what was delivered. It doesn't say who those people were, what changed for them, or what the organization will do with what it learned.

A report built only from a story has the opposite problem. A single account can't show how many participants had a similar experience, and a story chosen because it's the most moving may describe the best outcome rather than the typical one. A reader who later learns that may begin to doubt the rest of the report.

The credible middle is what this guide is about. Reaching it depends less on writing talent than on choices made well before the writing starts: what your organization sets out to learn, what it collects, how honestly it describes the limits of its evidence, who each version of the story is for, and how the people in the story are treated. The sections that follow take those choices in order.

Communicating impact means answering six questions that an activity count leaves open

Communicating impact, rather than reporting activity, means answering six questions an activity count leaves open: who participated, what they experienced, what changed, why that change matters, what the organization learned, and what happens next. "We served 200 people" tells a reader the program was busy. It doesn't tell them any of those six things.

• 1
  Who participated?

  Who the program reached, who it didn't, and how much of the program people received.

• 2
  What did they experience?

  What taking part was like, including the barriers people ran into, in their own words where you have them.

• 3
  What changed?

  The short-term, intermediate, or long-term outcomes the evidence shows, and for which groups.

• 4
  Why does that change matter?

  What the change means for the people involved and for the goals the work was meant to serve.

• 5
  What did the organization learn?

  What worked, for whom, and under what conditions, and what didn't work as expected.

• 6
  What happens next?

  What the organization will continue, change, or stop as a result, and who is responsible for it.

Outputs still matter in this account. Counts of sessions, participants, and hours show what was delivered and to whom, and an outcome is hard to interpret without them. The difference is that an impact story puts each count next to its meaning instead of leaving the number to speak for itself.

The six questions apply in a business as much as in a nonprofit or a college. For example, a company that trained its new supervisors might report that 40 people completed the course, an illustrative figure. The impact story explains which teams those supervisors lead, what they said changed in how they handle difficult conversations, whether anything shifted on their teams, and what the company plans to do differently in the next round of training.

A report organized around these questions is also easier to read. How do I turn program data into a report my funder actually reads? shows how to put the most important findings first and explain what each one means.

One body of evidence can serve a board, a leadership team, a funder, accreditors, and a community

One body of evidence can serve a board, a leadership team, a funder, accreditors, and a community, as long as each version of the impact story is built around the question or decision that particular audience brings. Each of these audiences listens differently, and almost none of them wants the full report. The CDC's Program Evaluation Framework makes the same point in practical terms: it plans each message's format, channel, and timing, and says its style should be tailored to each audience.

What changes from one version to the next is the framing, the length, and the order. What should not change is the evidence. Use the same definitions and the same numbers in every version, so that a figure in the leadership summary matches the figure in the funder report and the accreditation narrative. When two versions disagree, the audience that notices may start to question both.

Each audience's first question also decides what comes first. A funder reviewing an annual report may want to know first whether the program reached the people it promised to serve. A leadership team in a business may want to know first whether the work is addressing the problem it was meant to address, such as turnover in one department or a skills gap on one team. A community meeting may want to know first what the program means for families like theirs. These are examples, and your own audiences may have different priorities.

Funders that need to tell a story across many grantees face a different problem, combining dozens of reports into something their own board can act on. How do I turn a mountain of grantee reports into insight for my board? covers that.

A right-sized annual report and findings shared during the year make an impact story more useful

A right-sized annual report, together with findings shared during the year, makes an impact story more useful, because the people who need the evidence receive it in a form and at a time they can act on. A long report delivered months after the work it describes may be complete and still arrive too late to change anything.

Start with what the annual report is for. Determine whether a funder, your board, or another commitment requires one, then identify who the report is meant for and what each of those readers needs from it. In many organizations the practical answer is to keep the report and change it: a shorter, more focused document, with the effort saved redirected into the updates, summaries, and conversations people will use. Nobody reads our annual report. Should we keep making it? works through that decision.

A better question than "what should go in the annual report?" is what your team needs to understand and what the people you report to need to know. That question usually leads to one full report, which holds the complete evidence and its methods, supported by a short summary, a briefing, or a presentation for each audience. The full report stays the reference that every shorter version draws from, which is also what keeps the numbers consistent across them.

Timing matters as much as format. Annual and final reports matter, but a project team should not have to wait until the end of a grant to learn something important. Findings shared during the year can become part of project meetings, planning conversations, and decisions about what to change while there's still time to change it. The CDC's framework describes planning how to communicate findings and updates throughout an evaluation.

The reporting calendar, the audiences, and the formats are worth planning at the start of an evaluation, alongside the questions and the data. An evaluator who knows from the beginning that the same evidence must reach a board in the spring, a funder in the summer, and participants in the fall can design data collection and analysis to serve all three, so the team isn't assembling three separate reports at the last minute.

A credible impact story combines evidence, context, and the experience of the people involved

A credible impact story isn't a matter of finding the right number or the most moving quotation. It comes from a series of choices: deciding what your organization needs to learn before collecting anything, answering the questions an activity count leaves open, pairing numbers with participants' accounts, naming what the evidence can't show, shaping each version for the audience that has to act on it, and treating the people in the story with care.

None of those choices requires a bigger report. Most of them require a smaller, clearer one, planned from the start with its audiences in mind, and a habit of sharing what the organization learns while there's still time to use it.

The difference between reporting activity and communicating impact is whether your reader can see who took part, what changed, why it matters, and what happens next.