Three Things Nobody Wants to Talk About—But Everybody Is Dealing With

When Someone Is Making Your Workplace Unsafe

Workplace bullying is one of those topics that organizations prefer to handle quietly—which is exactly why it persists. In nonprofit environments especially, where the culture is built around shared mission and collaborative values, bullying creates a particular kind of dissonance. The gap between what the organization says it stands for and what’s actually being tolerated becomes impossible to ignore.

The first instinct is usually to document and wait—to build a record, stay professional, and hope the situation resolves itself. That approach has its place, but it has real limits. The longer a bullying dynamic goes unaddressed, the more it becomes the accepted reality, not just for the person experiencing it but for everyone watching. And people are always watching.

What actually moves things forward is combining documentation with deliberate escalation. That means keeping a specific, factual record—dates, behaviors, witnesses, impact on work—not necessarily to build a legal case, but to remove the ambiguity that these situations thrive on. Vague complaints are easy to dismiss. A clear pattern of documented incidents is much harder to ignore. Then escalate: to HR, to a senior leader, or if those channels aren’t working, through formal external channels.

But here’s the harder question that came up: what do you do when escalation doesn’t produce results? When HR is unresponsive, when leadership is unwilling to act, when the organization’s values and its actual behavior are visibly in conflict? That’s when clarity becomes the most important tool available—clarity about what you can and cannot change, and an honest assessment of whether this is an environment that’s capable of improving, or one that needs to be left.

When You’re Doing More but Getting Less

A different but equally frustrating situation: your responsibilities have expanded significantly, your scope has grown, you’re delivering results that didn’t exist in your original job description—and none of that has translated into a title change, a meaningful raise, or even formal acknowledgment that the role has changed.

This happens more often than organizations like to admit. The employee who absorbs additional responsibility is usually the capable, committed one—which makes them easy to rely on without formally recognizing the shift. And the employee often accepts it, at least initially, because they believe the recognition will eventually catch up. It usually doesn’t, not without a push.

What works is making the gap explicit rather than hoping it gets noticed. That means documenting the difference between the original role and the current one—not as a grievance, but as a factual description of what has changed and what that change is worth. It means asking for a direct conversation about growth and compensation, framed around the organization’s interests as much as your own: here is what I’m delivering, here is what that typically commands, here is what I need to stay fully engaged at this level. That framing shifts the conversation from personal advocacy to business case, which tends to land differently.

And then—the part people often skip—it means being genuinely honest about the answer you get. Sometimes the organization can’t move as fast as it should. Sometimes the budget really is constrained. But sometimes the answer, delivered clearly over repeated conversations, is actually the information you need to make a different decision about your future there.

When a Third of Your Emails Are Disappearing

Alongside those deeply human challenges, a more technical but equally urgent problem came up: email deliverability. Specifically, the situation where only one-third of emails are actually reaching inboxes—blocked, filtered, or bounced before anyone ever sees them—because of domain reputation issues with ISPs.

The revenue impact is immediate and easy to underestimate. Every campaign underperforms. Every appeal reaches a fraction of its intended audience. And the performance metrics that come back make it look like an engagement problem, when the actual problem is infrastructure. That’s a dangerous misdiagnosis, because it leads organizations to change their messaging and strategy when what they actually need to fix is their list and their sending behavior.

Email reputation is built slowly and damaged fast. The most common causes are high bounce rates from lists that haven’t been properly maintained, low engagement rates that signal to ISPs that recipients don’t want the mail, spam complaints that accumulate quietly until they cross a threshold, and sending volume that outpaces the domain’s established credibility. The path back starts with the list itself—scrubbing hard bounces, suppressing long-term non-openers, re-permissioning lapsed contacts before mailing them again. Most organizations resist this because the short-term list shrinkage feels like a step backward. But a smaller, cleaner list that actually reaches inboxes will generate more revenue than a larger, degraded one every time.

From there, the recovery is about patience and discipline: rebuilding sending reputation gradually by starting with the most engaged segments, monitoring deliverability metrics closely, and resisting the pressure to send at full volume before the domain can support it. In the meantime, maximizing revenue means leaning into the channels that are still working—direct mail to segments that can’t be reached digitally, SMS where permission exists, paid media to audiences that would otherwise be sitting in the email stream going nowhere.

What These Three Conversations Have in Common

Workplace bullying, career plateaus, and broken email infrastructure don’t have an obvious connection. But they share something important: in each case, the system that’s supposed to handle the problem—HR, organizational advancement, technical infrastructure—has failed to do what it’s designed to do. And the person left holding that failure is the one trying to do the actual work.

What helps in all three situations isn’t waiting for the system to fix itself. It’s getting specific about what the actual problem is, creating a clear record of the gap between what should be happening and what is, and being willing to make that gap visible—to leadership, to the organization, or at minimum to yourself. Because the first step toward fixing something broken is being willing to say, clearly and without flinching, that it’s broken.