I spent many hours creating a newsletter for the local recycling committee. I do this every month to help people better understand how to reduce and recycle. Our town has a unique system, with guidelines that don’t always apply elsewhere, so clear communication really matters.
After sharing the newsletter on Facebook, I received a response that wasn’t about the content, but about how it was distributed. It ended with the phrase: “just sayin’.”
For context: I already posted the newsletter on the Town website and on my own blog, Eastham Recycles. And I agree—distribution could be much, much better. But I am one person. I can improve it over time, but real expansion requires buy-in from the town and more volunteers to help.
The phrase “just sayin’” is often meant to sound casual or low-stakes. But in the context of feedback, it can land very differently. It hurts.
Instead of opening a dialogue, “just sayin’” often puts the person — me — who did the work into defensive mode. It delivers a judgment while also signaling that the commenter doesn’t plan to explain further, engage, or be part of a solution.
The issue isn’t that feedback was offered. Feedback about process, reach, or distribution can be valuable. The problem is that “just sayin’” strips feedback of context and responsibility. It turns what could be a conversation into a one-way remark, leaving the recipient to absorb it, interpret it, and decide what to do next—while ignoring the fact that they may have already tried.
In my case, distribution is shaped by real constraints: rules, time, and limited volunteer capacity. That context matters. But the larger point goes beyond this one newsletter. When feedback ignores constraints—especially in civic, creative, or volunteer work—it rarely feels helpful. It feels like criticism without a path forward.
What makes feedback productive isn’t just tone. It’s intention.
Does it invite discussion?
Does it acknowledge effort or limitations?
Does it offer a question, a suggestion, or a willingness to help?
“Just sayin’” does none of those things. It functions like a verbal shrug: I’ve said my piece without caring about any of the backgound. And once that happens, the work stops being collaborative.
Most people who create things—newsletters, programs, events, systems—are already carrying a lot. Thoughtful feedback helps carry the load. Casual, dismissive phrasing adds to it.
If you have an observation that could make something better, consider staying in the conversation long enough to make it useful. Ask a question. Share context. Offer help.
Because how feedback is delivered often determines whether it leads to improvement—or shuts it down.