Key Takeaways

The Call That Started This Article

I was on a call this week with a development leader at an organization I work with. She’d spent the previous week doing real work. Built a full growth campaign, mapped a budget to it, and designed a set of resources to bring new people into the organization’s orbit. It was good. It was ready.

As you can imagine, she was tired, not from the building but from the fighting.

Basically, every time her team proposed a way to reach more people, someone on the program side raised a reason it couldn’t be done. Things like the campaign might bring too much attention. It might strain the very thing the organization exists to protect. It might create a problem downstream. Each objection was reasonable on its face. Together, they formed a wall.

At one point, she said something I’ve heard, in different words, from dozens of nonprofit leaders: her organization puts up roadblock after roadblock about why it can’t do things, instead of asking how it could actually make them happen.

“We can’t do this. We can’t do that,”

She said:

“And it’s like, why can’t we?”

I told her what I’ll tell you. The objection on the table was not really about harm. The size and scope of what she was proposing was never going to cause the flood her colleagues feared. Something else was happening. And until she named it, she was going to keep losing the same argument every quarter.

This article is about that something else. If you’re a fundraiser or an executive director who feels like your hardest sell is not the donor but your own team, this one is for you.

Why Does the Program Team Keep Saying No?

Start with the generous reading, because it’s usually at least partly true. Program staff are closest to the cost of getting it wrong. They’re the ones who see the harm when an organization overpromises, overextends, or chases attention it can’t honor. Their caution is not random. It’s earned. A good program team is supposed to be the conscience in the room.

But caution that never resolves into a decision is not conscience. It’s paralysis wearing the costume of virtue. And three things are hiding underneath most program vetoes.

Why-We-Can’t Reflex

This is simply a cultural default. Some organizations have trained themselves, over years, to lead with the reasons something cannot work. It becomes the house style. A new idea enters the room, and the first five voices explain the obstacles. Nobody is being malicious. They’re being who the culture rewarded them for being.

The tell is that the objections arrive faster than the ideas. In a healthy organization, a proposal gets a fair hearing before it gets its critique. In a why-we-can’t culture, the critique is the hearing. The development leader on my call was not facing one bad actor. She was facing a reflex the whole organization had practiced until it was automatic.

Protection Instinct, Pointed at the Wrong Thing

This is what I’ve called elsewhere the protection instinct: the deeply human reflex to shield something we love from short-term discomfort, even when the long-term cost of shielding it is far worse. Program staff feel this about the mission the way a fundraiser feels it about a fragile donor relationship. The instinct is good. The aim is sometimes off. It’s the same protective reflex that keeps leaders from fundraising at all, convinced their discomfort is somehow ethical.

When a program leader blocks a growth campaign to protect the mission, ask the quiet question: protect the mission from what, exactly? Sometimes the answer is a genuine risk. Often the answer is change. Growth means more people, more visibility, more complexity, more that could go wrong. The protection instinct does not distinguish between “this will hurt the people we serve” and “this will make my job harder.” Both feel like threats to the thing being protected.

Comfort of the Status Quo

And the last one is the least flattering and the most common. Saying no is safe. Saying yes creates work. Every new initiative lands on someone’s plate, and the person whose plate it lands on has a powerful, mostly unconscious incentive to find the reason it should not happen. This is not villainy. It’s human nature operating inside a system with no slack in it. People who are already underwater do not welcome the tide.

Notice that none of these three are about the donors or the mission. They’re about culture, fear, and capacity. Which means the fix is not a better campaign. The fix is a better conversation.

What Is the Real Cost of the “Why We Can’t” Reflex?

It’s larger than a single stalled campaign, and most leaders never add it up.

There’s the obvious cost: the revenue you never raised because the idea died in committee. The sector keeps growing, total giving keeps reaching new highs, and the organizations stuck under their own ceilings are not stuck because the money disappeared. They’re stuck because they keep voting against the things that would have reached it. The strategies that actually move revenue almost always require doing something the organization hasn’t done before — which is exactly what the reflex kills.

Then there’s the cost almost nobody names: your best fundraiser. A development leader who has to win an internal war before she can even start the real work does not last. She spends her energy on persuasion instead of cultivation. She watches good ideas get strangled. And one day she takes that energy somewhere it’ll be welcomed, which is how organizations lose the exact people they most needed to keep. I’ve written before about the mindset shift that pulls nonprofit leaders out of burnout, and this is one of the purest forms of it: the slow exhaustion of fighting your own side.

And there’s a third cost, subtler still. A culture that always says no teaches its boldest people to stop proposing. After enough vetoes, the ideas simply stop coming. The organization mistakes the silence for peace. It is not peace. It’s surrender.

How Do You Break the Reflex Without Steamrolling Your Team?

You don’t win this by overruling the program team. Override them, and you confirm every fear they had about fundraising running roughshod over the mission. You win it by changing the shape of the conversation. Here’s how.

1. Separate the Real Risk From the Reflex

When an objection lands, don’t argue with it. Size it. Ask the person to put a number, a scale, or a concrete scenario on the harm they’re worried about. “Help me understand the actual exposure here. If this campaign works exactly as planned, how many more people are we talking about, and what specifically breaks?”

Most of the time, the honest answer reveals that the feared harm is wildly out of proportion to the actual scale of what you’re proposing. A modest campaign is not going to overwhelm anything. Naming the real numbers shrinks the imagined catastrophe back down to a manageable tradeoff. And a tradeoff is something an organization can decide. A catastrophe is something it can only fear.

2. Name the Tradeoff Out Loud

Every choice has a cost on both sides. The program team is fluent in the cost of acting. They’re often blind to the cost of not acting, because that cost is invisible: the donors you never met, the revenue you never raised, the programs you couldn’t fund because you stayed small to stay safe.

Your job as a leader is to put both costs on the same table. “If we do this, here’s the risk we’re accepting. If we don’t, here’s the revenue and reach we’re giving up, and here’s what that means for the people we serve next year.” When both costs are visible, the conversation stops being about whether to take a risk and starts being about which risk you’d rather carry. That’s the conversation that actually moves an organization. It’s the same forward-leaning posture that separated the organizations that grew during a downturn from the ones that sank waiting for the storm to pass.

3. Make “How Can We” the Required Next Sentence

Install a simple rule, and model it relentlessly. Anyone is allowed to raise a concern. But the concern has to be followed by an attempt at a path. “I’m worried about X. Here’s how we might do it anyway.” You’re not banning objections. You’re banning the dead-end objection — the one that drops a wall and walks away.

This single norm changes a culture faster than almost anything else, because it converts the program team’s expertise from a brake into a steering wheel. The same person who knows all the reasons it could go wrong is exactly the person best equipped to design the version that goes right. You’re not silencing the caution. You’re putting it to work.

4. Be Directive When the Moment Calls for It

There’s a time for consensus and a time for a decision. If you’ve sized the risk, named the tradeoff, and invited the path, and the reflex is still just a reflex, then leadership means choosing. Kindly, clearly, and with the reasoning visible: “I hear the concern, I’ve weighed it, and we’re going to move forward, because the cost of staying still is the greater risk to the mission.” Said with respect, that is not steamrolling. That’s the job — and it’s the same kind of ownership we keep coming back to in the CEO’s role in fundraising.

FAQ´s

How do I know whether my program team has a real objection or just a reflex?

Listen for whether the objection comes with a path. A real concern from a serious colleague usually arrives as “I’m worried about this, and here’s what we’d need to do it safely.” A reflex arrives as a flat “we can’t,” with no door attached. When you ask someone to size the risk, and they can’t put any concrete shape on the harm they fear, you’re almost certainly looking at a reflex rather than a reason.

Isn’t it dangerous to push past program staff who understand the mission better than I do?

It would be if pushing past them were the move. It’s not. The move is to make the program team’s knowledge part of the design instead of a veto over it. Their expertise is real, and you need it. What you can’t afford is to let legitimate expertise harden into an automatic no. Bring them in early, ask them to help you find the safe version, and reserve the directive call for the cases where caution has clearly tipped into paralysis.

What if the executive director is the one with the “why we can’t” reflex?

Then the work is harder and more important, because culture flows downhill from leadership. Start by making the cost of inaction visible in terms the ED already cares about: revenue, reach, the programs that go unfunded. Leaders who default to no are often responding to a history of being burned, and they change when they can see, concretely, that the bigger danger now is standing still. If the pattern is organization-wide and rooted at the top, that’s its own decision the leadership has been avoiding — a separate but related problem.

How does this connect to revenue diversification and growth?

Directly. Every growth strategy worth having — new audiences, new channels, new campaigns — requires the organization to do something it hasn’t done before. An organization governed by the why-we-can’t reflex cannot diversify, because diversification is nothing but a series of new things. If your revenue has been flat for years and your ideas keep dying internally, the flat revenue and the dying ideas are the same problem.

My team says we don’t have the capacity to take on anything new. Is that a real objection?

It’s the most real of all, and it deserves a real answer rather than a guilt trip. Sometimes the honest move is to stop doing something old so you can do the new thing well, or to fund the capacity — a contractor, added hours — rather than pretend the work will happen for free. What you can’t do is let “we have no capacity” quietly become the permanent reason the organization never grows, because an organization that never grows never gets the capacity either. That loop only breaks on purpose.

Wrapping Up

The hardest sale in fundraising is often not the donor. It’s the colleague down the hall who loves the mission so much they won’t let it move.

You’re not going to fix that by caring more or arguing harder. You fix it by changing the question the organization asks. Not

“what could go wrong,”

Asked as a way to stop. But

“how could we make this work,”

Asked as a way to start. The caution stays. The expertise stays. Only the default changes — from a wall to a door.

Basically, the next time someone tells you it can’t be done, don’t deflate. Ask them to size the risk. Put both costs on the table. And require the next sentence to be a path, not a period.

Stop asking permission to grow. Start leading the conversation about how.

Is Your Fundraising Strategy Built for the World You’re Actually In?