Shield Fatigue, Part Two

The other day, I wrote a note about coming up with a term to describe some of what I’ve been feeling at work. That term was Shield Fatigue. In that note, I promised I’d come back with more — especially since I was still digesting the fact that I’d finally found a word, a label, that helped explain something a lot of people I’ve talked to could sense but couldn’t quite put their finger on.

So, as promised, here’s a bit more — with one big caveat I’ll get to at the end. If you missed the original note and have no idea what I’m talking about, you can go back and read it, but here’s the short version: Shield Fatigue is the term I came up with to try to name a very specific kind of exhaustion — the kind that comes from standing permanently as the mediator between two groups. For a manager, that’s leadership generating demands from above, and your team absorbing them below. In practice, that means mediating between the two: arguing about capacity, say, and softening the blow on the way down.

The plan for this post is to first clear up what Shield Fatigue is not, then show what it is, and finally walk through a few real situations to illustrate it.

Let’s start with some feedback I got from people who read the original note. A number of you pointed out that what I was describing sounded a lot like empathy fatigue, or compassion fatigue. What I learned is that empathy fatigue is about feeling depleted from absorbing other people’s emotional pain. It’s entirely about feelings, and from what I can tell, it runs in one direction: from you, toward the person who’s struggling. It’s well documented, especially among therapists, nurses, and caregivers, and the literature is full of remedies — mostly centered on boundaries and self-care.

Shield Fatigue, on the other hand, isn’t primarily about emotional depletion. It’s more structural, and it isn’t one-directional. The strain doesn’t come from caring too much about one person who’s struggling. It comes from being the permanent joint between two parties who are both fully engaged, both right from where they stand — but who also have misaligned expectations that you’re now expected to reconcile, over and over, with no clean resolution in sight.

A cleaner way to put it: empathy fatigue runs on a single axis, down in one direction. Shield Fatigue runs on two axes at once — up and down, simultaneously. You can experience Shield Fatigue with zero empathy fatigue, because nobody’s necessarily falling apart. Everybody could be doing their job well, and you’d still feel ground down by the position you’re standing in.

This is also why some of the advice I got in response to the original note — things like avoiding the empathy trap, or “stop rescuing people” — while genuinely good advice, doesn’t really apply here. That advice assumes someone isn’t owning their part, and that you’re stepping in to rescue them. Shield Fatigue assumes the opposite: that everyone is owning their part, doing their job right. The pain isn’t a gap in accountability. It’s the mediation itself.

It’s also distinct from burnout. Burnout is mostly about the volume of exhaustion. Shield Fatigue is about the role itself — you could be perfectly well rested and still feel it the moment you’re put back in the middle of that situation.

With that distinction in mind, here are a few examples — lightly modified to be a bit more abstracted from specifics, but hopefully still recognizable.

Do more, with less: From above, leadership is pressuring you to increase output while your resources have shrunk. That’s coming from above. From below, you might have one or two — or several — people who, for genuine personal reasons, need to decelerate for a while. They need a breather. Both of these are legitimate. Leadership asking for more isn’t necessarily a nefarious request, or people being oblivious to the situation. And someone asking for a breather, whether for personal reasons or work-related ones, is just as legitimate. But you’re the one who has to hold the line — protecting the person below while simultaneously trying to help leadership above — and there’s no slack left for you to trade with.

No matter how long you’ve been doing this job, the standard management tools don’t really help, because you can’t plan for this. Succession planning, capacity models, resourcing spreadsheets — they all assume a steady-state human. Someone who doesn’t have emotions, doesn’t get sick, doesn’t need a break. There’s no cell in the spreadsheet for “this valued engineer needs six weeks at 60%, for reasons that are none of the org’s business.”

For all purposes, the plan says that this engineer can deliver X, but the actual human, this month, can only deliver less than X. That shortfall doesn’t disappear. Leadership above is still expecting X. They were PROMISED X by the plan. So the difference lands on you, the shock absorber between a commitment made above and a reality below.

The “optional” task that isn’t: From above, leadership wants something completed 100% — a survey, some training, signing up for something. In theory, it’s something that would benefit everyone. In practice, the real payoff is a compliance number: proof that the whole team completed the thing and is therefore fully compliant. But leadership won’t declare it mandatory. They want the metric without owning the mandate. So the word that comes down is “optional,” but the enforcement gets delegated to you, the line manager. Which puts you in the position of coming up with the talking points, manufacturing the reasoning, and being the one who has to nudge and pester people — weekly, sometimes daily — until the officially optional task hits 100%.

If you’re someone who’s always championed autonomy and freedom, the way I try to, the people who report to you trust you specifically because they believe you wouldn’t hound them over something optional. So the moment you’re put in the position of enforcing it, it spends the exact trust that makes you effective — in service of a mandate that its actual owners won’t put their name to. That’s the fatigue: being the enforcer of things leadership won’t take ownership of.

Rewarding the firefighters: And the last example is when you end up rewarding the firefighters by very quietly, discreetly taxing everyone else. Leadership makes a decision that goes badly, then asks engineers to pull all-nighters for weeks to hit a goal they’d been warned, repeatedly, couldn’t be hit without burning people out. To reward those firefighters, leadership then creates an additional compensation pool — which, in practice, is funded by shrinking the pool available for everyone else. So the engineers who weren’t pulled into the dumpster fire, who were working just as hard keeping the actual lights on, get the short end of the stick through no fault of their own. They did nothing wrong except not being near the fire that leadership started in the first place. And now you, the manager, are the one who has to communicate and defend the allocation — which you probably find very hard to defend. Once again, you’re standing between a decision you didn’t make and people you know are being shortchanged.

In every one of these examples, leadership either makes or avoids a decision, and then declines to fully own it. The ownership gap lands on you, the manager — to broker it, to sell it, to enforce it, to the very people who trust you specifically because you don’t do those things.

None of these are “someone isn’t pulling their weight” problems, or empathy-trap problems, or “there’s just too much work” burnout problems. These are position problems. If you took someone out of the middle of that situation, the problem should, in theory, evaporate — and if it doesn’t go away even after you’ve been out of that position for a while, then no amount of self-care is going to fix it. That’s why these things are so hard to plan for. They’re situational, relational, and born of decisions made above you that you can’t predict. There’s no playbook, because each one is a fresh collision between top-down expectations and a specific human underneath them.

When I first wrote about this, I promised a plan, and I’ve been working on one — building on the inversion model from my last note, asking not what I need to do, but what I should stop doing. But honestly, what I’ve landed on so far feels a little too specific to my particular role and situation to generalize. I’m not confident it applies across the board, and I’d rather not dress up a personal coping tactic as advice. So my plan is to sit with this a little longer before I claim to have something worth sharing. This post is just the diagnosis, a little sharper than before — the prescription is still cooking.

After spending some time trying to articulate these feelings and pin down what was causing them, I can tell you that I’m now pretty confident Shield Fatigue is it. I’m still not sure what to do about it, and I’d rather tell you that honestly than sell you a fix I don’t trust yet. Once I’ve spent more time thinking it through — and trying a few things myself — if I land on something that doesn’t feel too specific to my role, I’ll be glad to share it.

Let me know if this is something you’d be interested in hearing more about. And, as always, I’d love your feedback and thoughts.