We tend to measure efficiency at the wrong end of the pipe. The real test is not how little we spend, but how little we lose between the donor and the door.
When a funder asks us to be efficient, we reach for the easy lever: cut the budget line, trim the overhead, lower the unit cost. It feels responsible, and it satisfies the spreadsheet. But it answers a question that the people who depend on us are not really asking. The family waiting at the door does not need us to have spent less. They need what we promised to arrive whole, on time, and at the right quality. Those are not the same goal, and the gap between them is where a large share of our value quietly drains away.
What we count, and what we lose
Picture a single grant traveling from a donor commitment to a delivered service. It passes through proposal cycles, compliance checks, currency conversions, reporting formats that no two funders define the same way, approval layers, and re-budgeting requests. Each handoff is a place where time leaks, intent blurs, and a little more of the original purpose gets shaved off. Almost none of that shows up as waste in our financial reports. It shows up as process. We have built a sector that is rigorous about the cost of a sack of grain and nearly silent about the cost of moving it through ourselves.
That is the leak worth naming. Not fraud, not laziness, but friction we have learned to treat as normal. We tend to take the journey from intent to delivery as fixed and squeeze the delivery instead. So the cheapest looking proposal wins the bid, then quietly underperforms, and the result is still recorded as a budget success. Cheapness is easy to measure. Lost value is easy to miss.
Efficiency as protection, not subtraction
There is a more useful definition available to us. Efficiency is how much of what was promised reaches the people we serve, with their dignity and our staff’s judgment intact. By that measure, the most efficient choice is often not the cheapest one. Paying for the experienced coordinator who prevents a three month delay is efficient. Funding the unglamorous systems that let money move once instead of five times is efficient. Protecting frontline roles from the churn of short, heavily restricted cycles is efficient, because every handover we force is a tax we pay in lost context.
This definition also protects the people who carry the work. When efficiency means subtraction, the first thing trimmed is usually the human margin: the time to listen, the staff continuity, the slack that lets a team adapt when conditions shift. Quality then slips and pressure on people rises, and the cause is easy to overlook because it never appeared as a line item. A definition of efficiency that protects both the work and the workforce is not softer. It is more honest about where value is actually created and where it is lost.
We can begin this shift without waiting for permission. We can report the journey, not just the spend: how long money takes to move, how many hands it passes through, and how much of the original design survives to delivery. We can defend the lines that protect quality rather than apologize for them. And we can make the case to funders for fewer, longer, less fragmented commitments, showing them, in plain numbers, the friction that fragmented reporting creates.
Efficiency is not how light our footprint looks on paper. It is how much of our promise survives the trip from the donor to the door.