Elementum

The Program Delivery Diagnostic.

Something about your program is not holding, but you cannot yet name which thing.

Program trouble comes in three shapes that need completely different work: the program was never really designed, so there is nothing solid to deliver reliably; it is understood but delivered inconsistently, so quality rides on who is working; or it is delivered consistently but nobody manages its quality, so you are guessing whether it helps. This sorts out which one you have, confirms a design-and-delivery problem is really what you are facing rather than an impact, mission, systems, or staffing problem in disguise, and hands you a plan. It is a sorting instrument, not a fix. It will not design or repair your program. It takes about three hours, which you can spread across sittings, and it asks for an honest look at how your program actually runs on an ordinary day, not how it runs in the brochure.

Step 1

Picture your programs and how delivery actually goes

You cannot judge a delivery problem without seeing what you run, who each program is for, and how consistently it actually happens on an ordinary day. List each program or service, who it is meant to serve, and what it is meant to change for them, in the plainest words you have, and where you cannot say cleanly, mark it, because that gap is data. Then note honestly whether each is delivered the same way whoever is working, whether it depends on one or two key people, and whether you can tell if it is landing.

Who: you or your program director, with the frontline staff and volunteers who actually deliver the work, because they know how it really goes. Produces: a clear picture of what you run, who it serves and what it is meant to change, and an honest read of how consistently each program is actually delivered.

Open the Program and Delivery Snapshot →

Step 2

Confirm it is a design-and-delivery problem, and route out what is not

Before you locate your stage, make sure you are in the right place, because the most costly mistake here is doing delivery work on a problem that was never a delivery problem. Sort your problem honestly.

The trouble with your program is really:

The program itself: never really designed, delivered inconsistently, or you cannot tell if it is any good Whether the program actually works and how to prove it Whether this program should exist at all, or which to keep, stop, or start Your back-office workflows, technology, or data, not the program delivery itself You simply do not have enough people or money to deliver it

Produces: confirmation that your problem is really program design and delivery, and a single named finding placing your program on the lowest rung that is not yet solid: design, standardize, or quality. This front-gate and ladder is the Program Problem Sorter and Delivery Stage Locator.

If the honest problem is too few people or too little money

Stop before you build a delivery system for work you cannot staff. Route the staffing question to the staffing work, the volunteer question to volunteer engagement, and the money question to the funding work. Documenting a delivery model your team has no capacity to run would waste the effort and demoralize the people who cannot keep up. Come back once the capacity question has an honest answer. This is a route, not a stop.

Step 3

Prioritize and sequence into your plan

Turn the finding into an ordered plan that names your first guide and follows the order this work actually goes: design, then standardize, then quality. Where more than one rung is shaky, sequence them in that order, because you cannot standardize what you have not designed, or manage the quality of what you have not standardized. Add anything Step 2 surfaced, and give the first guide a real start date.

Who: you or your program director, with the staff who will do the work with you. Produces: a one-page plan naming your first guide, what follows, and when you start, with any work that belongs elsewhere named and routed.

Open the Prioritized Program Plan →

When to call a real person

If your program operates in a licensed or regulated service, clinical care, childcare, education, housing, food, or any work with a professional standard of practice, then how it is designed and delivered is bound by rules that sit outside this framework: licensing, accreditation, mandated reporting, safety codes, credentialing, and a duty of care to the people you serve. This can help you see and organize the delivery. It cannot tell you what the law and your license require, and getting that wrong can harm a participant and end a program. Where your program touches any of these lines, bring in the relevant regulator, licensing body, or a nonprofit attorney, and treat their requirements as fixed points your design must meet. This is the most serious edge in this work.

How you will know it worked

You can say, in one plain sentence, whether your work is to design the program, to make its delivery reliable, or to manage its quality, or whether the honest answer is that your real problem lives in another part of the work. You have a written plan with a first guide and a date. And you have looked honestly at the gap between the program as imagined and the program as delivered, rather than judging it by the brochure.

If you arrived here in a crisis and have now steadied

Once the immediate problem is handled, it is worth stepping back to look at the whole organization, not just the part that was on fire. There is a short whole-organization check-up waiting when you are ready. That is not a sales pitch. It is the next honest thing to look at. The whole-organization check-up →

You can always go back to the overview or start over from the welcome page.