October 10, 2026
The Routine I Run Before Any New Program Gets Written Down
By Jodie Kluver
A Draft I Never Skip
Before a new program goes anywhere near a grant application or a board packet, I write one page nobody else sees. It is not a logic model and it is not a budget. It is a list of who has not been in the room while we were designing this.
That page is the whole routine. It takes fifteen minutes. I have been doing some version of it for most of my career, across arts organizations, literacy programs, and public administration classrooms, and it catches things that a strategic plan never will.
Why a List, Not a Meeting
Meetings are where ideas get polished. Lists are where they get checked. If I wait until a meeting to ask who is missing, the people already in the room answer for me, and they tend to answer that everyone important is already there. A list I write alone, before I talk to anyone, forces a different kind of honesty.
I ask three questions on that page:
- Who uses this program the way we are describing it, and who actually told me so.
- Who is affected by this program but will never apply for it, serve on its committee, or answer a survey about it.
- Whose objection would I find most annoying to hear right now.
That third one matters most. The people whose input is most inconvenient are usually the ones whose input would change the design.
What This Catches That Governance Does Not
Boards ask good questions about money and risk. They rarely ask who was consulted and who was assumed. A program can pass every financial review and still be built entirely around the preferences of the staff who designed it, the funders who liked the idea, and the handful of participants who show up to everything.
I have watched well-run organizations build a program around the loudest, most available voices in a community and call that community engagement. It is not wrong, exactly. It is just incomplete, and incomplete has a way of showing up later as low enrollment, quiet attrition, or a grant renewal nobody can explain confidently.
The list does not fix that by itself. What it does is make the gap visible before the program is funded, staffed, and announced. A gap you can see is a gap you can still do something about. A gap you discover at year two is a gap you have to explain.
Informal Networks Count Too
Part of what I look for on that page is the informal association nobody put on an org chart: the parent group that meets at the coffee shop, the retirees who carpool to the senior center, the group chat that already exists for the exact population I am trying to reach. Formal partners are easy to list. Informal ones take more thought, because nobody sends them a meeting invite and nobody expects to be asked.
I have found that these informal networks often know more about what will or will not work than any formal partner does, simply because they talk to each other without an agenda. Leaving them off the page is the most common gap I find, including in my own early drafts.
How to Start This Without Overhauling Anything
You do not need a new process to try this. You need one page and fifteen minutes, done before the next idea gets presented to anyone else.
Write down who you consulted. Write down who you assumed. Write down the one group whose feedback you are least looking forward to hearing. Then decide, on purpose, whether you are going to go find them before the design is finished or after.
Either answer can be right, depending on timeline and resources. What I do not think is right is skipping the question and discovering the gap by accident, three months into a program that is harder to change than a page would have been.
The page costs almost nothing. That is most of why it earns its place. The routines that survive in a busy organization are rarely the elaborate ones. They are the small ones that keep getting done because they take less time than the problem they prevent.