When Nonprofit Language Starts Hiding Things

Nonprofit language can make a difficult day sound suspiciously tidy.

I am not talking about lying outright. Most of the time it is softer than that. A report uses “impact” where it should say “we made a limited offer.” A problem becomes a “challenge.” A person becomes a “success story” before anyone knows whether the help lasted. The words are not always false. They are often too smooth for the facts underneath them.

That bothers me because service is already hard enough without turning it into public relations.

People who give money or time deserve an honest account. So do the people receiving help. If a plan worked, say what worked. If it did not, say what failed and what will change. If the group does not know yet, that is an acceptable answer. It is better than filling the gap with a sentence that sounds responsible.

There is pressure to make every update reassuring. I understand that pressure. Reassurance makes people comfortable. It may even make fundraising easier. But comfort can become the priority, and then the organization starts editing reality for the reader.

The result is a strange kind of dishonesty. Nobody is technically deceived, but nobody is being told enough to understand what is happening.

Kasey’s Kitchen should resist that. We can say what we offered, what we learned, and what remains unfinished. We can avoid making someone’s hardship into a useful marketing image. We can avoid pretending that a difficult situation has a clean ending because a clean ending reads better.

Plain language is not cold. It can be respectful. “We do not know” can be respectful. “We cannot promise that” can be respectful. “This was not enough” can be respectful.

The alternative is language that makes everyone look better while making the situation harder to see.

I do not want to work around that kind of language. I want the words to be ordinary enough that someone can ask a fair question after reading them. What happened? Who was helped? What is still needed? What did we get wrong?

Those questions may not produce beautiful copy. They produce accountability.

That is more useful than beautiful copy.