Before You Add a Second Program

There's a certain sparkle that comes into a board meeting when expansion is on the table. A new program, a second site, a population nobody else is serving well: the idea arrives dressed in mission language, and it photographs beautifully. Growth is our sector's default compliment (look how much more they're doing), and so the conversation tilts toward yes before it has fairly begun.

Let me say first that some second programs are exactly right, and some of the best organizational chapters I've watched began with one. This is not an argument against growing. It's an argument that an idea this consequential deserves better questions than momentum usually allows, and I'd offer six.

Is the first program sturdy without your full attention? A second program changes the first one's life, the way a second child changes the first one's. Before adding, it's worth asking whether program one can run a full season without leadership heroics: without the ED personally patching schedules, without the founder's weekend rescues. If the honest answer is no, the choice on the table isn't really "one program or two." It's "one sturdy program or two wobbly ones," and almost nobody, put that way, picks the second.

Where is the demand actually coming from? Three forces regularly masquerade as community need: a funder's interest, a team's restlessness, and an actual community asking. All three are real, and only the third is a mandate. A program built because an RFP appeared will live on the funder's calendar, not the community's. One built because talented staff were bored will last as long as the boredom would have. It's a clarifying exercise to finish this sentence truthfully: we are considering this because ______. Whatever fills the blank should be something you'd say out loud to the people you serve.

What does it share with what you already do? Call this the adjacency test. A strong second program usually borrows something substantial from the first: the same population served in a new way, the same staff skills applied to a new group, the same building, systems, or relationships put to fuller use. The more it shares, the more your existing strength carries it. A program that shares nothing (new population, new skills, new infrastructure, new funders) isn't really a second program. It's a second organization wearing your name, and it will demand a second organization's worth of everything.

Who runs it, by name, and what stops? New work is done by specific humans, not by the org in the abstract, and in small organizations the default human is whoever is already fullest. If the plan cannot name the person (and describe what comes off their plate to make room), the plan isn't finished. Something always makes room; the only question is whether you choose it or it chooses itself.

What's the smallest honest pilot? Between "no" and "full launch" sits a wide, underused middle: one cohort, one site, one season, run at a scale real enough to teach you something and small enough to end without drama. Pilots convert arguments into evidence. They also protect the sparkle, in a way: an idea proven small earns its expansion, while an idea launched large has to survive its own learning curve in public.

And the question I'd treat as close to non-negotiable: what would tell us to stop? Decide, before the launch, what result by what date would mean winding it down, and write it in the minutes. This feels pessimistic and is precisely the opposite; it's what makes the yes safe to give. Exit criteria set in advance are a gift from your present board to your future one, because two years in, the program will have staff, stories, and sunk costs, and no one will be able to see it clearly. The organizations that get reputations for trying bold things are, on inspection, usually the ones that also know how to end things kindly. The permission machine and the stopping machine are the same machine.

If the idea clears all six, then congratulations are in order, and honestly, so is the growth. Adjacent, demanded, named, piloted, and endable is about as good as a second program's beginnings get.

One last thought, since "growth" so often gets defined as width. Depth is growth too. Serving the same people more completely, more durably, with a sturdier organization behind the serving, expands the mission every bit as much as a new banner does, and it never dilutes. Whichever direction your organization chooses, I hope the addition makes the first thing stronger, and not merely the whole thing bigger.