Executive coaching for nonprofit leadership teams is the same fundamental work as anywhere else, helping a senior team tell the truth, own commitments, and lead together, with one big difference: at a mission-driven organization, the cost of a struggling leadership team is counted in people who needed you and got less. That changes the stakes and it should change the work.
This is for executive directors and nonprofit CEOs who have a talented, devoted senior team that somehow can't get out of its own way, and who feel the particular guilt of knowing it.
Why do nonprofit leadership teams struggle differently?
The dysfunction wears nicer clothes.
At a company, leadership conflict tends to show up as politics and turf. At a mission-driven organization, it shows up as politeness. Your people took pay cuts to be here. They came for the mission, they genuinely care about each other, and somewhere along the way, being kind got tangled up with never saying the hard thing. The VP of Programs and the VP of Finance can sit through a whole budget meeting radiating warmth and leave with the same unresolved disagreement they've carried for two years, because surfacing it would feel like a betrayal of the culture.
I've come to think of it as mission shield: the way "we're all here for the same reason" gets used to close conversations that needed to stay open. Of course we're aligned, we both care about the families we serve. Meanwhile programs and finance haven't honestly negotiated a budget in three cycles, and the gap between them is quietly shaping what services get delivered.
There's also a structural difference companies don't have: the board. Nonprofit executive teams perform for an audience in a way corporate teams don't, and I've watched strategic retreats collapse because the senior team couldn't be honest with board members in the room. The team needs a place to tell the truth that isn't a performance, and many nonprofit teams have literally never had one.
What does leadership team dysfunction cost a nonprofit?
Not margin. Mission.
The program that didn't launch because two departments couldn't agree on staffing, that's families who didn't get served, and everyone on your team can put faces to the abstraction. The talented program director who left, exhausted by the unspoken tension, took years of community relationships out the door with her. Grant opportunities have application windows, and a leadership team that decides slowly misses them the same way a company misses a market.
And there's a cost specific to your world: your people's devotion is the organization's main asset, and unresolved leadership friction spends it down. Staff who took pay cuts for the mission will forgive low salaries for years. What wears them out is watching the leadership team model the opposite of the values on the wall.
Is spending on the leadership team taking money from the mission?
This is the question that keeps executive directors from getting help, so it deserves a straight answer: the leadership team is the instrument the mission gets delivered through, and you're allowed to maintain the instrument.
You already accept this logic everywhere else. Nobody calls the development director's salary a diversion from the mission, because fundraising capacity is mission capacity. A senior team that can decide quickly, tell each other the truth, and stop relitigating the same conflicts delivers more service with the same budget. The honest framing for your board isn't about leadership as a luxury. It's that the team's current patterns are already costing program delivery, you can name where, and this is what fixing the leak costs.
What I'd never tell you is that the tension should go away. It shouldn't. The discomfort of spending on yourselves is part of what keeps mission organizations honest. Spend anyway, carefully, the way you'd repair a roof.
What does the work actually look like at a nonprofit?
Like it does anywhere, with the mission in the room as a working tool instead of a shield.
One organization I worked with, a workforce development nonprofit, had a programs-versus-finance standoff that everyone described as a personality difference. It wasn't. It was an honest disagreement about risk that had never once been had openly. The early work was trust: the ED went first, telling her team about a program decision she'd gotten wrong and what it had cost the people they serve, out loud, with the number of families attached. The room changed. Within a few months the programs and finance leads had the actual argument, the one about how much risk a budget should carry when real people depend on the services, and it was hard and warm at the same time, which mission teams are surprisingly good at once it's safe. The budget that came out was one both of them owned, and the next two cycles didn't reopen it. Trust made the argument possible, the argument made the ownership real. Mission teams move through the Six Shifts the same way companies do, usually faster, because the caring was never the missing piece.
Where this leaves you
Your team's devotion is real. It was never the problem. The problem is that somewhere along the way, your team started protecting each other from the truth instead of trusting each other with it, and the people paying for that arrangement are the ones the mission exists for.
One place to start: at your next senior team meeting, ask what conversation this team avoids best. Mission teams usually know immediately, and the fact that everyone laughs before anyone answers will tell you the answer is close to the surface, waiting for somebody to make it safe.