CLIENT: BirthBridge Africa (NGO)
GEOGRAPHY: Kano · Kaduna · Sokoto
DOMAIN: Maternal & Child Health
ENGAGEMENT TYPE: Data Strategy & Impact Reporting
Every month, BirthBridge's 140 community health workers completed paper registers tracking enrollments, antenatal visits, referrals, deliveries, and newborn follow-ups across 73 communities in Northern Nigeria. State coordinators transcribed these into Excel. The M&E officer consolidated them into a master file.
And then, when donor reporting season arrived, three weeks of manual effort produced a Word document that answered exactly one question: What did we do?
Not: did it work? Not: for whom? Not: where are we losing women between referral and delivery? Not: which state needs a different strategy entirely? Just a table of counts, a list of activities, and a set of numbers that no one could fully trust — because no one had a clear view of how they were derived.
That gap, between data collected and insight acted upon is exactly where this engagement began.
IF YOU RECOGNIZE THIS ORGANIZATION
You run a program that touches real lives. Your CHWs are doing meaningful work in hard places. But at the end of the year, your report reads like a receipt and not a story. You know the data holds more than you're getting out of it. You just don't have the system, the time, or the analytical infrastructure to unlock it.
Most data projects jump straight to visualisation. The dashboards get built, the charts get made, and then everyone realises the numbers mean different things to different people in the room. I take a different route.
Structure first. Story second.
Step 01 — Built a shared data language
Before touching the data, I designed a full data dictionary. 18 indicators across four program domains: Reach, Service Delivery, Outcomes, and Operations. Every metric was defined with a precise calculation, a data source, and a rationale for why it was chosen over alternatives. This became BirthBridge's first shared analytical reference: a document their M&E officer, program director, and donors could all point to and mean the same thing.
Step 02 — Structured the raw program data
The source data; a 4,100-row consolidated Excel file across three states, carried the hallmarks of paper-to-digital transcription: missing gestational ages, inconsistent referral coding, null values that needed to be distinguished from false values. Each cleaning decision was documented with its rationale, making the analytical process fully auditable.
Step 03 — Mined the data for the real story
Rather than reporting aggregate averages, I disaggregated performance across states, CHW cohorts, and program stages, revealing a 43-percentage-point gap in skilled birth attendance between Kano and Sokoto that the consolidated report had completely obscured. I traced the care continuum from enrollment to neonatal follow-up, surfacing where women were being lost and what questions the program needed to answer before the next cycle.
Step 04 — Turned findings into a decision-ready story
The final impact report was built around a deliberate narrative arc, not a data dump. An executive summary distilled thousands of data points into three things leadership needed to know. A care-continuum funnel made attrition visible in a way no table could. Strategic recommendations were rooted directly in the data, not imported from generic best-practice frameworks.
Gap in skilled birth attendance between Kano (67.9%) and Sokoto (24.7%) — hidden in the aggregate average
Women referred for facility delivery in 2024 who did not attend — the program's highest-leverage unanswered question
Neonatal follow-up completion rate — the sharpest drop in the entire care continuum
Some findings confirmed what leadership suspected. Others reframed how they understood their own program.
Structural inequity — not program design failure
Sokoto's underperformance could not be explained by CHW quality or training gaps alone. The data pointed to structural barriers such as: access, infrastructure, and community decision-making norms. Requiring a state-specific response strategy rather than a uniform program fix.
Early enrollment is the upstream lever
Only 26.4% of women enrolled before their second trimester. This single metric was upstream of almost every other outcome gap — more time in the program meant more ANC visits, better referral rates, and higher skilled birth attendance. Improving first-trimester enrollment would compound across the entire care continuum.
Data quality is a program management issue — not just an M&E problem
Sokoto's 60.8% data completeness rate meant the program was making resource and strategy decisions with an incomplete picture of its lowest-performing geography. Surfacing this in the report reframed data quality from a technical inconvenience to a leadership priority.
“An aggregate 51% skilled birth attendance rate tells you almost nothing. Disaggregated by state, it tells you that one part of your program is working and another is in crisis.”
This engagement produced four distinct outputs, each serving a different use case, and together forming a complete analytical infrastructure BirthBridge did not have before.
📖
Data Dictionary
18 indicators across 4 domians, each with a precise definition, calculation method, data source, and strategic rationale. BirthBridge's first shared analytical language.
🗂️
Structured Dataset
A clean, analysis-ready program dataset with full documentation of every transformation decision, making the data auditable, reproducible, and safe to hand to any future analyst.
📊
Impact Report
A narrative-driven, visually designed impact report answering three questions donors and leadership actually need: what changed, for whom, and what comes next.
📋
Methodology Note
A full audit trail of the analytical procress - cleaning decisions, metrics definitions, known limitations, and five concrete recommendations for improving data systems.
BirthBridge Africa is not an unusual organisation. Across the health NGO and health-tech landscape, there are hundreds of programs just like it: staffed by committed people, collecting more data than they know what to do with, and producing reports that describe activity rather than illuminate impact.
The gap is rarely a shortage of data. It's a shortage of the systems, structure, and analytical thinking needed to turn that data into something an executive director can act on, something a program officer can learn from, and something a donor can fund with confidence.
That is the gap I work in. Not as someone who makes charts — but as a Health Data Systems Strategist who builds the foundation that makes the charts mean something.
“The most important output of this engagement wasn't the report.
It was the first time BirthBridge's leadership, M&E officer, and program team were all looking at the same numbers — and meaning the same thing.”
If your organisation collects program data but struggles to turn it into decisions, funding arguments, or strategic clarity, that's exactly the problem I solve.
I work with health-focused NGOs and early-stage health-tech startups to build the data systems, analytical structure, and communication tools that transform messy impact data into decision-ready insight.
— GET IN TOUCH
Whether you have a specific data challenge or just want to explore how I can help, I'd love to hear from you.