Compassionate Nonprofit Leadership Is Operational Lubricant with Yerachmiel Stern [Episode 422]

Most nonprofit leaders I work with want to move faster, decide cleaner, and hold the standard. From the outside, that looks responsible. From the inside, something else is usually happening.

When a leader skips the relational work because it feels slow, the cost doesn't disappear. It moves. It shows up later as rework, attrition, board friction, and team members who go quiet in meetings because they have stopped expecting to be heard. The bill comes due downstream, where it is harder to trace.

The truth is, the time you spend being human with your team is not extra. It is the infrastructure that makes everything else faster.

I've been thinking a lot about this lately. I recently had a conversation about exactly this with Yerachmiel Stern, the executive director of Pesach Tikvah, and it was an important reminder to me that there are still many leaders out there who think compassion is “soft” and a “waste of time”. Those leaders are missing out on the important role compassion plays in a well run, highly effective organization.

The single most underrated piece of organizational design is the emotional state of the leader walking into the room.

Not the agenda. Not the org chart. The leader's tone.

When a leader walks in, regulated, warm, and present, the team's nervous system gets a signal: it's safe to think out loud here. Hard things can be named here. Mistakes can surface here without triggering self-protection. That signal is doing real operational work. It is shortening the time between a problem appearing and a problem getting solved.

When a leader walks in tight, transactional, or performatively calm, the team picks that up too. People stop volunteering information. Decisions move underground. The same problems take three meetings to surface that should have taken one.

In short:

• The leader's nervous system sets the team's nervous system.

• That isn't a vibe. It's a throughput metric.

• Information moves faster in a regulated room than a guarded one.

This is why "read the room" is not a soft skill. It is a leadership requirement. Before you open your mouth in a meeting, you are already leading.

One of the cleaner ways to diagnose whether a leader is operating from infrastructure or from extraction is to watch what happens when a team member brings a request that doesn't fit the existing rule.

The old reflex is to point at the rule. Policy says no. Budget says no. We don't do that here.

The infrastructure-minded leader asks a different question: 

“Is this rule still serving the outcome we actually want, or is it serving the convenience of saying no?”

Sometimes the answer is genuinely no, and the leader holds the line. Often the rule was set in a different context, the request is reasonable, and the cost of saying yes is much smaller than the goodwill you lose by reflexively saying no.

In short:

• Rules are tools, not identities.

• When the rule no longer serves the outcome, the rule is the problem.

• Saying yes when you can is a form of system maintenance.

This isn't about being a pushover. It is about staying connected to why the rule existed in the first place.

Conventional hiring asks: Have you done this exact job before? It optimizes for risk reduction. It also reliably under-selects for the people who would have been excellent in the role with a slightly different background.

Relational hiring asks a different question: what does this person actually want to do, and is that aligned with what we need done?

The shift sounds soft. It is not. It is one of the highest-leverage operational moves a CEO or executive director can make. People who are doing work that matches what they actually want to do produce more, stay longer, and require less management. People who are doing work they took because it was available produce less, leave sooner, and require constant supervision.

In short:

• Match the heart to the role.

• Heart-aligned hires need less management.

• Heart-misaligned hires cost twice: once in their tenure, once in the rehire.

You will not get this right every time. Nobody does. But shifting the question from "have you done this" to "do you want to do this" changes your hiring math permanently.

(For more on the underlying skill of leading with this kind of attunement, see)

The Power of Soft Skills for Nonprofit Leaders.

The harder version of this same principle shows up in firing.

Most leaders avoid letting someone go for too long. They tell themselves they are being compassionate. The person needs the job. The team is already stretched. The performance gap isn't catastrophic. We'll give it another quarter.

What is actually happening, in most of these situations, is that the person being kept in the wrong role already knows. Their nervous system knows. Their family knows. The team knows. Everyone is in a quiet, low-grade limbo that costs energy from every direction at once.

When the leader finally has the conversation, the most common response isn't anger. It's relief. Sometimes spoken, sometimes not. The person was waiting to be released from a fit that was never going to work, and they were too loyal, too scared, or too tired to release themselves.

I call this a compassionate release. The compassion is in the clarity, not in the delay.

In short:

• Limbo is more painful than a clean ending.

• Delay is a form of harm dressed up as kindness.

• Compassionate release ends the cost on both sides.

Holding someone in a misfit role isn't generosity. It's a tax everyone is paying, and the longest-paying account is the person you think you're protecting.

There is a version of nonprofit leadership that aims for "good enough." The reasoning sounds responsible. We don't have unlimited resources. We can't deliver gold-standard service to every client. We have to triage. We have to be realistic.

This framing adds risk.

The math isn't wrong. The framing is. It confuses two different things: what you can deliver structurally, and how you deliver what you have. Two organizations can offer the exact same baseline service, and one will feel like an extraordinary experience and the other will feel like a transaction. The difference isn't the budget. The difference is the personal touch wrapped around the delivery.

One line from my conversation with Yerachmiel stayed with me:

"If you give the clients that personal touch, the Ford could be better than the Cadillac."

What I appreciate about this framing is that it explains the mechanism. The personal touch is what converts a service into a relationship. The relationship is what produces retention, referrals, advocacy, and the willingness to come back when things get hard. None of that requires more money. All of it requires presence.

I had this experience recently in an emergency room. The equipment was advanced. The diagnostics were thorough. The most meaningful 30 seconds of the entire visit was a staff member taking a breath, asking how I was doing, and telling me my chair could recline. He delivered the most excellent service of the visit, and it cost him nothing.

That is the Ford becoming the Cadillac. The structure didn't change. The presence did.

The hardest piece of this for high-performing leaders to internalize is that the relational work, which feels slow, is what creates the speed.

I learned this with my own son, who is on the autism spectrum and has ADHD, dyslexia, dysgraphia, and anxiety. The clinicians who took an extra five minutes to let him regulate consistently finished on time. The clinicians who tried to muscle through and just hold him still consistently turned a 30-minute appointment into a two-hour event. Sometimes the visit had to be rescheduled at a different office entirely.

The "fast" approach was the slowest approach. The "slow" approach was actually the fastest one. The math is unambiguous once you start counting all the hours, not just the visible ones.

In short:

• The relational time isn't extra. It's structural.

• Skipping it doesn't save time. It moves the cost.

• Going slow at the start is what produces speed at the finish.

This same pattern shows up everywhere a nonprofit leader operates. With board members.

With staff. With donors. With clients. The minutes you invest in being a person before you are a transaction are the minutes that compound.

There is an older model of leadership that equates confidence with never apologizing, never being wrong, and never being visibly uncertain. It's still around, and it's slowly being retired for a good reason.

Confidence in a leadership role isn't the absence of mistakes. It is the willingness to absorb the final responsibility for the outcome, mistakes included. When the team trusts that the leader will carry the weight at the macro level, the leader is then free to be humble and openly learn at the everyday level. That doesn't subtract from authority. It deepens it.

People follow humans, not personas. (For more on this, see The Power of Vulnerability with Becca Pearce.)

When compassion is treated as infrastructure rather than personality, a few things shift.

What shifts:

• Meetings get shorter because information surfaces faster.

• Hiring gets cleaner because you're matching hearts to roles, not resumes to slots.

• Firing gets kinder because delay stops getting confused with mercy.

• Service quality goes up without the budget going up.

• The leader stops carrying the team's nervous system as a second job.

None of this is about being softer. It is about understanding what creates throughput in a human system, and building for it on purpose.

This isn't about doing less work.

It's about doing work that compounds.

Nonprofits can run on compassion and run on time.
They can hold high standards and hold their people.
They can deliver excellent service without spending more.

Not by pushing harder, but by building systems that treat human connection as the structural asset it actually is.