In 2017, I facilitated a focus group for participants involved in a leadership project. As part of the project, some participants received funding to implement small scaled engagement events in their local communities. One participant hosted an event to engage community members, and while the host anticipated over 100 attendees, the actual number was a quarter of that.

Based on the attendee numbers, the host shared that she didn’t think her event had been very successful because “not many people” attended.

At first glance, that conclusion made sense. We’re socialized to believe that attendance is the most visible measure of success. Fewer attendees could easily feel like a missed opportunity.

But as the conversation continued, a different story emerged.

The participants who attended remained engaged throughout the event. They asked thoughtful questions, contributed to meaningful discussions, and continued interacting after the session ended. What initially looked like a disappointing turnout became evidence of something much more valuable: The event still fostered genuine engagement.

That experience has stayed with me for years because it illustrates an important lesson about data: The numbers we collect don’t always tell the whole story.

Not All Data Serves the Same Purpose

One of the most helpful distinctions nonprofit staff can make is understanding the difference between learning data and accountability data.

Learning data helps organizations improve their work. It often answers questions such as:

• What contributed to this outcome?
• What surprised us?
• What resonated most with participants?
• What barriers did participants experience?
• What should we do differently next time?

Learning data informs decisions by helping organizations understand how to do their work better. It helps staff adapt programs, strengthen relationships, and continuously improve services.

Accountability data, on the other hand, demonstrates that activities occurred or that commitments were met. It asks different questions:

• How many people participated?
• How many workshops were delivered?
• How many community partners were contacted?
• Were program goals achieved?

This type of data is commonly shared with funders, boards, leadership, or other external stakeholders to demonstrate progress and responsible stewardship of resources. Ultimately, accountability data helps organizations demonstrate what they’ve accomplished.

Neither is more important than the other, as organizations need both. The difference lies in why the data is being collected and how it will be used.

The Same Data Can Serve Different Purposes

During this same project, participants completed monthly reports documenting their community engagement efforts. They were asked to report how many people they engaged, how they engaged them, and even how much time each interaction took. For example, if they emailed a potential community partner and received a response, they were expected to record the length of that interaction.

Does this make sense?

Perhaps those reporting requirements were tied to a funder’s expectations or an organizational reporting process. If so, they may have served an important accountability function.

But from a learning perspective, this wasn’t useful for participants.

If one participant contacted ten potential community partners but receives little response, and another participant consistently engaged three partners who became active collaborators over several months, if we focus only on the number of contacts or minutes spent engaging, we miss the quality of those relationships.

Learning data might instead explore:

• Which partnerships became stronger over time?
• What approaches generated meaningful engagement?
• What challenges prevented relationships from developing?
• What can participants learn from one another’s experiences?

Based, on the intention with the data, the same reporting process could have supported accountability, learning, or both.

Ask Yourself: Why Are We Collecting This?

It’s easy to collect data because a report requires it or because “we’ve always tracked it.”

But before adding another question to a survey or another column to a reporting template, it’s worth pausing to ask why the information is needed.

As you review your organization’s data collection practices, consider these questions:

• Who will use this information?
• What decision will this data help someone make?
• Is this primarily intended to demonstrate accountability or generate learning?
• If this number increases or decreases, what could be inferred and what action would we take?
• Does this information help us improve this program or service?
• Would participants find value in collecting or discussing this information?
• Are we measuring activity, or are we learning something meaningful about our work?
• Are we collecting this because it’s easy to measure, or because it’s useful?

Key Takeaway

Collecting more data doesn’t automatically lead to better programs or services.

When nonprofit staff understand the difference between data for learning and data for accountability, they can move beyond reporting activities and begin using data as a tool for reflection, decision-making, and continuous improvement.

The next time you’re asked to collect a new metric, start with a simple question: What are we hoping to learn, and who is this data ultimately serving?

Raise Your Voice: Does your organization prioritize collecting data for learning or for accountability? Share your thoughts in the comments section below.

Was this useful? Subscribe to the Raise Your Voice newsletter, and explore my consulting services.