The Sector Speaks Fluent Avoidance

There is a phrase I keep encountering.

It appears on consulting firm websites, in conference keynotes, and in the opening paragraphs of sector reports. It appears in job descriptions, strategic plans, and board presentations. It is deployed with complete sincerity by people who have spent decades in this work and genuinely believe in what they are doing.

The phrase is some version of this: partnering with nonprofits to drive transformational change.

I have been trying, for years, to figure out what it means.

—

I should say this at the start: I have used this language. I have written it, spoken it, and put it in proposals. I know exactly what it feels like to reach for a phrase that sounds like a commitment and asks less of you than a commitment would. I am not writing from outside this problem. I am writing from inside it, which is the only place this argument can be made honestly.

—

The nonprofit sector has developed a professional language that is fluent, confident, and almost entirely hollow. It is not dishonest — that is the important thing to understand. The people who write campaign optimization and workload equity framework and strategies for keeping teams engaged in uncertain times are not trying to deceive anyone. They believe in the work. They are trying to help.

But the language they are using was designed — not consciously, not with malice, but structurally — to discuss the sector’s most serious problems without requiring anyone to be accountable for solving them.

That is a very specific kind of language. And the sector has become fluent in it.

—

Take transformational change.

Every consulting firm in the sector offers it. They partner with organizations to achieve it. They have case studies proving they delivered it. But ask what it means — specifically, measurably, in the life of an actual organization — and the answer dissolves into something about culture shifts and leadership alignment and stakeholder engagement.

Transformational change is a phrase that sounds like a destination and functions like a direction. You are always moving toward it. You never quite arrive. And because it is never precisely defined, it is never precisely undelivered.

The language protects everyone.

—

A leading executive search firm recently published a piece on strategies for keeping teams engaged in uncertain times.

Every strategy in it is correct. Communicate transparently. Build mutual trust. Give people meaningful work. Model work-life flexibility. All of it true. All of it written from a distance so careful that the person reading it — the ED running her fifth consecutive year with a team that is 30% understaffed, the development director carrying a $4 million goal with no support staff — will finish it and feel nothing. Because it is not written to her. It is written about her situation, from an altitude where the specific, uncomfortable, career-risking decision she actually needs to make has been replaced with a framework.

One of the strategies: Assign work that is challenging and mission-aligned.

What this means in practice: tell your program director her caseload is unreasonable before she tells you she is leaving. That is not a strategy. That is a conversation. And it is a conversation that requires someone to say something true to someone with power over their livelihood, in an underfunded organization, in a political moment that is already destabilizing everything.

No framework does that for you.

—

Here is what the language is actually doing.

When the sector says partner instead of hire, it diffuses accountability. Partners are alongside you. They share the journey. They are not responsible for the outcome the way a vendor is, the way an employee is, the way someone with skin in the game is.

When the sector says optimize strategy with appropriate ROI, it borrows the authority of the for-profit world and applies it to organizations running on the impossible labor of people who took a 30% pay cut to do work they believed in. The ROI of not burning out your communications director is not a metric anyone is measuring. But the language produces the feeling that someone is.

When the sector says workload equity instead of we are asking people to do too much and we know it, it creates the impression that the problem has been named and categorized and will therefore be addressed. Naming something in the language of a framework is not the same as fixing it. But it produces the same feeling of forward motion.

This is what the language is for. Not deception. Forward motion without displacement. The appearance of addressing something while the thing itself remains exactly where it was.

—

Sixty percent of nonprofit workers cite too much responsibility without enough support as the primary reason they are leaving. That figure has increased every year for three consecutive years of data collection.

The sector’s response has been to produce better language for describing it.

There are conferences about it now. Toolkits. Frameworks. Keynotes. An entire consulting economy organized around helping organizations talk about the problem more precisely while the problem gets worse.

I do not think the people producing this content are cynical. I think they are doing what the sector has trained them to do — which is to engage with a problem at the level of language because engagement at the level of language is what the sector funds, what it conferences about, what it puts on its website, what it calls thought leadership.

—

What would it cost the sector to say what it means?

It would cost someone a board meeting where they tell the board the revenue goal is not achievable with the current staff and the current budget and the current ask. It would cost a manager the discomfort of telling her team she is not going to email them at 9pm anymore and meaning it. It would cost a funder the admission that the reporting requirements they designed for accountability are consuming the staff capacity of every organization they fund.

These are not strategies. They are decisions. They are specific, uncomfortable, and they require someone to say something true to someone who has power over the outcome.

The language exists because decisions are hard and language is easier.

A framework that ends in a decision is not the problem. A framework that replaces one is.

—

I want to be precise about what I am arguing.

Someone will read this and ask for solutions. I want to address that directly.

The solutions are not the missing piece. The sector has solutions. It has published a few hundred just this month. It has toolkits and frameworks and keynote speakers who have spent years refining the answer. The missing piece is not knowledge. It is the willingness to make the specific, uncomfortable decision that the solution actually requires — and no framework makes that decision for you.

The sector does not have a language problem. It has a courage problem that it has been managing with language. The frameworks are not the disease. They are the symptom — evidence that something harder has been avoided.

The people inside these organizations know the difference. The ED who reads strategies for keeping teams engaged in uncertain times and recognizes nothing of her actual Monday morning knows the difference. The development director who sits through the culture change keynote and drives home thinking, but who is going to tell the board knows the difference?

They have known the difference for years.

They are also, at a rate of seventy percent, looking for a new job.

—

— Keira Haley | keirahaley.com

Trust the reader. Cut until it hurts. Earn the silence.

Fluent avoidance: speaking extensively, confidently, and professionally about serious problems in ways that avoid accountability for solving them.

Sources: Social Impact Staff Retention 2026, NonprofitStaff.org; Center for Effective Philanthropy, State of Nonprofits 2024