Be the Shit Umbrella
How to protect your team and just LET THEM COOK
Every engineer has had the manager who just… let them work.
They weren’t absent. They weren’t checked out or hiding in their calendar. They were busy doing something upstream: absorbing the chaos, deflecting the politics, attending the meeting about the meeting so you didn’t have to. Maybe you didn’t fully appreciate it at the time. You just knew that somehow, in their team, the work felt possible.
The crude but accurate term for this is the “shit umbrella.” Your job as a manager is to stand between your team and the organizational weather so they can focus on what they were hired to do.
It sounds simple. It isn’t.
What the good ones actually do
The best managers I’ve worked with (and ones I’ve heard described by engineers who genuinely loved their teams) did three things simultaneously.
First, they asked what was blocking you and then went and removed it. Not “let me escalate that” followed by silence. Actually removed it. Called the person, cut through the process, got the answer. You’d mention a blocker on Monday and by Wednesday it was gone and you weren’t entirely sure how.
Second, they absorbed the political noise. The reorg rumors, the shifting priorities from three levels up, the exec who wanted a dashboard that would take six weeks to build for a meeting they’d forget about. None of it reached the team until it was real and relevant. They were in those rooms so you didn’t have to be.
Third, and this is the one that separates competent from great, they made it clear that the umbrella wasn’t unconditional. They’d tell you: if things start becoming a detriment to your work, loop me in and I’ll push back. They weren’t promising a fantasy world where nothing bad ever happened. They were promising that if the weather got bad enough to actually hurt you, they’d step in front of it.
A fellow Substacker Still Functional 🌻 described a manager like this as having a “shit cannon” - he didn’t just block what came from above, he fired it back. He cared about his people doing good work more than he cared about being easy to manage.
They pushed him out a few years later.
The trap: the hermetically sealed team
Here’s where people misread the pattern.
Some managers hear “shield the team” and interpret it as “shield the team from everything.” They create a bubble. The team has no idea why priorities shifted. They don’t know the company is having a rough quarter. They can’t see the strategic context for the work they’re doing. They just get tickets and ship code and wonder why nothing makes sense.
That’s not an umbrella. That’s a bunker. And bunkers breed helplessness.
When you over-shield, you rob people of the ability to self-advocate. You rob them of context they might actually need to make better technical decisions. You create a team that falls apart the moment you’re not there to intercept everything because they’ve never built the muscle to handle anything themselves.
Teams don’t need to be protected from reality. They need to be protected from waste:
wasted time,
wasted effort,
wasted emotional energy on things they can’t influence and didn’t ask for.
There’s a real difference between “I won’t tell you about the reorg because I don’t want you to worry” and “I’ll tell you the reorg is happening, here’s how it might affect us, and I’ll handle the fallout if it starts hurting our work.”
The first one is paternalism. The second one is leadership.
The calibration: what separates good from great
The best version of this pattern isn’t silence. It’s selective transparency with full energy absorption.
Let the information through. Absorb the chaos.
The manager that comes up most in conversations I have with happy engineers — the one people describe with something close to reverence — does exactly this.
He tells the team what’s going on.
He tells them how it might impact them.
He makes it clear that if it started being a detriment to their work, clue him in and he’d push back.
He doesn’’t shield them from everything, because that is a nearly impossible task. He trusts them to do their jobs, communicate their needs, and loop him in for support if things turned ridiculous.
The calibration question isn’t “should I tell my team about this?” It’s “does my team need to spend energy on this?”
If the answer is no, because
it’s political noise,
it’s someone else’s emergency,
it’s a fire drill that will be forgotten by Friday
you absorb it. You let it hit you instead of them. That’s the job.
If the answer is yes - if it’s real context they need to make good decisions, if it affects their work directly, if ignoring it would be worse than knowing about it, you share it. But you share it with the implicit promise: and I will handle the part of this that isn’t your job to handle.
That’s the whole skill. Information passes through. Chaos doesn’t.
The cost — and what it tells you
These managers often get pushed out. The one with the shit cannon? He “cared too much about his people and doing things right and not enough about what upper management wanted.” That’s almost a direct quote. And it’s a devastating one, not because of what it says about him, but because of what it says about the organization.
When your org ejects the people who protect teams from dysfunction, the dysfunction isn’t a bug. It’s the operating model. The company doesn’t have a management problem. It has a culture that punishes good management.
If you’re the shit umbrella and you’re getting punished for it, if saying “no” to protect your team’s focus is being read as “not a team player”, the signal isn’t that you’re doing your job wrong. The signal is that your org doesn’t actually want the job done well. They want compliance. They want noise passed downward without friction. They want managers who are funnels, not umbrellas.
That’s a culture diagnosis. And it’s one worth taking seriously, because it means the system is selecting against the people who make teams work.
The easiest way to evaluate a manager is to ask their team one question:
Does your manager let you focus on the work?
If the answer is yes, someone upstream is getting wet so you don’t have to. They’re in the rooms you don’t know about, having the conversations you’ll never hear, absorbing the energy that would otherwise land on your desk as yet another “quick sync” or “just checking in on priorities.”
That’s the job. Be the shit umbrella. Just make sure you’re shielding your team from waste, not from reality.
And if your org fires you for it, take that as the compliment it is.