Raising a Workplace Concern Without Triggering Formal Escalation

Someone keeps being handed work that isn't really part of their job. It comes from their manager, and on its own no single piece of it is a big deal. There's nothing to point to as a policy violation, nothing worth reporting, no clear line that's been crossed. It never rises to something HR would take on. And yet it keeps wearing on their focus and their mood, week after week.

It's a common spot to be in, and an uncomfortable one. The problem is real enough to keep nagging, but not big enough to formally write up. That leaves two obvious moves: say nothing and just carry it, or take it up the chain and risk turning a small irritation into an official dispute. Both come at a cost, and neither really deals with what's actually going on.

This post is about that gray area: the stretch before a concern becomes an official matter, and what it means to raise something there without turning it into more than it is.

The pre-escalation gap

Most organizations have clear channels for concerns that have already escalated, like HR intake, formal complaints, grievance procedures, reviews. These are built for matters that are serious and/or already on the record.

What organizations rarely have is a route for the smaller things: a concern that hasn't reached that point but isn't going away either. The recurring out-of-scope assignment is a good example. Raise it formally and you make it a bigger issue than it is. Raise it in a passing conversation and it tends to evaporate, leaving nothing behind to show it was ever said. It sits somewhere in between, with no natural fit.

That in-between space carries a real cost. SHRM found that 84% of U.S. workers say poorly trained managers create unnecessary work and stress (SHRM, 2020). Additionally, SHRM's report The High Cost of a Toxic Workplace Culture estimated that toxic workplace cultures cost U.S. employers $223 billion in turnover over five years (SHRM, 2019) Most of that strain never reaches a formal channel, because most of it never becomes serious enough to belong in one. It just quietly piles up instead.

Why the concern stays unspoken

Holding back here usually has little to do with the substance of the concern. It is about what raising it might cost, and the fear of what their response might be. When the other person is the direct manager - the one who hands out the work, writes the reviews, and sets the temperature of the week - the stakes change. Speaking up can feel almost indistinguishable from picking a fight. 

Amy C. Edmondson, the Novartis Professor of Leadership at Harvard Business School, names what's missing: “Psychological safety is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes.” Without that belief, concerns don't get aired. They get absorbed by the person holding them - which is exactly how the quiet pile-up happens. 

Edmondson's work in The Fearless Organization (Wiley, 2018) traces how the absence of that safety smothers precisely this kind of small, early signal. It stays unsaid not because it doesn't matter, but because there is no obvious way to say it, and saying it badly feels too risky to chance 

Tone is the variable, not content

Once a concern like this does get raised, what shapes where it goes is usually not the message itself but the way it arrives. The same point - that a run of assignments falls outside someone's actual role - can read as a calm clarification or as an accusation, depending on wording, timing, and tone. The content holds steady. Everything around it does not. 

That is what makes this so hard to do alone. Someone sitting on an unresolved concern is rarely calm about it, and writing and sending in that state is exactly where a small thing tips into a formal one - a line that comes out sharper than intended, a message fired off at the wrong moment. 

Where structure changes the delivery

A message like this rarely goes wrong on purpose. It goes wrong because it gets written and sent in a single motion, by someone who isn't calm about it, with nothing in between the urge to hit send and the words landing on the other end. The very things that decide how it's taken - tone, timing, sequence - are left to the worst possible moment to handle them.

What changes that isn't sharper wording. There's a more effective way to go about it - one that puts structure around the sending rather than the message: writing something and sending it as two separate steps, having the tone looked over before it reaches the other person, and spacing out a short exchange instead of letting it run open-ended. None of this touches what the concern is. It only shapes how it gets there.

Approached this way, saying something hard becomes a considered act rather than a reflex - done with care and a second set of eyes, rather than left to the moment it stings most. The concern still belongs to the person carrying it. What changes is only the way it arrives.

What it leaves untouched

Going about it this way keeps a concern its actual size. It doesn't turn the matter into a formal complaint, and it doesn't promise the assignments will stop or the situation will change. Whether the manager responds, and how, is still out of anyone's hands. The message having gone out in a calm, measured form is what has happened; what comes after is separate. Silence is as valid an outcome here as any reply.

Surfacing a concern at its actual scale

This middle ground is where most workplace concerns actually sit - too persistent to shrug off, not yet formal enough to file. The hard part is rarely deciding to speak. It's finding a way to say the thing at its true size and keep some control over how it lands.