Weeks after the project ended, I could barely remember the coverage statistics. What stayed with me was a conversation that exposed how much our data had failed to tell us.
We had gathered with parents, community leaders, and health workers to understand why vaccine uptake remained lower than expected in some communities. On paper, the challenge seemed straightforward. We knew where coverage was lagging, which communities needed greater attention, and how progress compared with our targets.
Parents described hearing rumors long before they heard from health workers. Community leaders said engagement came too late. Health workers spoke about the difficulty of rebuilding confidence once misinformation had spread.
None of these experiences appeared in the monitoring reports. They emerged only because people were given the space to share what they had lived through.
I left that meeting with an uncomfortable thought: we often trust what we can measure and overlook what people are trying to tell us.
That experience points to a broader lesson about storytelling for impact in development work. Data and stories should not compete with each other. Data shows us patterns at scale. Stories help us understand the people, choices, fears, and relationships behind them.
Stories are another form of evidence. They reveal context, assumptions, and realities that numbers alone cannot capture. They sit alonside data, and help us interpret it.
The most valuable insights are often hidden in everyday experiences: a teacher who continues showing up despite difficult conditions, a health worker helping families navigate new systems, or an entrepreneur creating opportunities where few seem to exist.
These experiences may never attract headlines, yet they often reveal more about how systems succeed or fail than any performance indicator.
The longer I work in development communications, the more convinced I become that strategic storytelling is as much a decision-making tool as a communications one.
Too often, stories are treated as evidence collected after a program ends. Yet stories in development communication can do far more. They can reveal blind spots, highlight emerging risks, and help organizations make better decisions before, during, and after implementation.
When we fail to listen to people’s experiences, we miss context and warning signs, along with local knowledge that could improve program design and delivery. We risk building solutions around assumptions rather than understanding.
Much of what we needed to understand the gap was already being said in those communities before we asked. Are we listening carefully enough to the stories people are telling?
The voices we never hear are the missing pieces of progress itself.
This belief sits at the heart of the work my firm, Iwà Consulting does with development programs and private institutions, building the systems and listening mechanisms that bring community voices into decisions. If your organization is trying to surface the insights hidden behind the numbers, I’d welcome the conversation.
