Your program is delivered reliably, but you cannot honestly say whether it is any good, or you have a nagging sense it could be better and no way to tell.
Reliable delivery of a mediocre experience is still mediocre, and consistency without quality just means you are consistently missing. This work builds the quality in: it defines what good delivery means for this program, opens a real channel to hear from the people you serve, sets a rhythm to review delivery honestly, and closes the loop by fixing what you find, so the program gets better on purpose rather than by luck. It is deliberately about delivery, not impact. It asks whether you are delivering the program well: with fidelity to the standard, in a way the people you serve experience as good, and in a way they complete rather than drift away from. It does not ask, and cannot answer, whether the program changes lives; that is the impact work, and this hands you there the moment your real question becomes proof of change. Use this if your program is delivered consistently but its quality is uneven or unknown. If delivery is not yet reliable, go to Standardize and Document Delivery first.
You cannot manage a quality you have not defined, and quality means something specific to each program. Name what good delivery looks like on three honest fronts, kept clearly distinct from whether lives changed: fidelity, is it delivered to the standard; experience, do the people served find it respectful, useful, and worth their time; and completion, do they stay through it rather than drift away. Then pick a small number of signals you will actually watch, chosen because they tell you something true, not because they are easy to count.
That is impact, outcomes rather than delivery, and it routes to the impact measurement work. Build the delivery-quality standard here for what you can see in the delivery itself, and take the change-in-lives question there, so you are not trying to prove impact with a delivery measure. This is a route, not a stop.
The people who receive your program know things about its quality that you cannot see from the inside, and in this sector they are usually the last to be asked, because they are not the ones paying. Create a way for them to tell you honestly how the program is for them, designed so it is safe, consensual, does not re-traumatize, does not punish honesty, and reaches those who struggle to speak up. Then decide when and how feedback is gathered as a normal part of delivery, not a special event, with consent and safety written in.
That is not quality-improvement input to log and trend; it is a safeguarding and possibly legal matter that must be acted on at once. Route it immediately to the relevant professional, your safeguarding process, and where required a nonprofit attorney or the authorities. Handle the person safety first, then the pattern. Where anyone is at risk, this takes precedence over the rest of this work.
Signals and feedback only improve a program if someone actually looks at them, together, on a regular basis. On a set rhythm, look together at the quality signals, the participant feedback, and whether delivery is holding to the standard, in a way that treats a problem as information rather than as blame. Check whether delivery has drifted from the standard, and whether any drift is a problem to correct or a genuine improvement to fold back into the standard.
Open the Delivery Quality Review →A review that names problems and changes nothing is worse than none, because it teaches the team that honesty is pointless. Turn each review into specific changes, to delivery or to the standard, with an owner and a date, and fold genuine improvements back into the delivery standard so the good change sticks. Then establish the continuing cycle of signal, feedback, review, and change as a permanent part of how the program runs.
If what the review keeps surfacing is the whole organization ability to find and fix problems, not just this one program, that broader mechanism lives in the operations and systems work, and it is worth building there so every program benefits. Build the delivery-specific loop here; route the organization-wide mechanism there. This is a route, not a stop.
Gathering feedback from people you serve can itself do harm if it is done carelessly: asking a person in crisis to relive it, pressing someone whose honest answer could cost them the service they depend on, or collecting sensitive information you cannot protect. Where your program serves a vulnerable population, design the feedback with consent, safety, and the person dignity first, and where you are unsure how to do that safely, bring in a professional who knows the field. And any feedback that reveals harm, abuse, or a safety failure is not data to trend; it is a duty to act, and it goes straight to the right professional and, where required, an attorney or the authorities. This framework helps you build the loop; it cannot make it safe for you, and safety here is not optional.
You can say, with evidence rather than hope, where your delivery is strong and where it is weak, and you can point to specific changes you made because the review or the people you serve told you to. The people who receive your program are heard as a matter of routine, and their honest feedback changes what you do. Delivery quality is trending up, or at least you would know if it were trending down, because you are watching.
Is your program now designed on purpose, delivered reliably whoever is on shift, and improving on a rhythm because you measure its quality and hear from the people you serve? If those three are true, you have done what this work sets out to do: you have turned the work from something that lived in one person head into a program the organization owns and keeps getting better. The honest next step is to prove it changes lives, which is the impact measurement work, the other half of your programs work.
And if you came to this in a crisis, one program on fire, and you have now steadied it, here is the honest next thing. Now that this is handled, it is worth stepping back to look at the whole organization rather than the one part that was burning. There is a short, whole-organization check-up waiting whenever you are ready. That is not a sales pitch and it is not a handoff to anyone; it is simply the next honest thing to look at, now that you are steady. The whole-organization check-up →