The Shield
- Jun 26
- 3 min read
He took every hit for his team. He just never noticed what the hits were for.
Marcus ran the best-liked team in the company. Ask anyone on it and you'd hear the same word: protected.
When a project slipped, he took the heat in the leadership meeting. When a junior analyst sent a bad number to a client, he called the client himself, made it right, and never mentioned whose number it was. When the executive team came down hard on a missed quarter, he stood in front of his people and absorbed every bit of it.
His team adored him. And his team was stuck.
I saw it in the promotion data before I saw it anywhere else. Four years, and not one of his directs had been promoted out of the group. Not one. Other teams sent people up every cycle. His people stayed exactly where they were — comfortable, loyal, and quietly frozen in place.
Once I started looking, the mechanism was everywhere. Every time Marcus stepped in front of a consequence, he removed the one thing that would have grown the person standing behind him. The analyst never had to sit in the discomfort of explaining her mistake to the client, so she never built the muscle for it. The project lead never had to face the leadership team, so he never learned how. Marcus was so busy catching the arrows that nobody on his team ever learned to dodge.
So I asked him the obvious question. "You keep telling me you're protecting them. From what, exactly?"
He had the answer ready. The politics. Getting blamed for things that weren't fully their fault. The stuff he could handle and they shouldn't have to.
Then I asked the next one more slowly. "Or from watching them struggle in a way you'd have to sit there and feel?"
He didn't answer for a while.
That's the pattern, and it's a hard one to see because it wears such a flattering disguise. The shield looks like generosity. It's one of the most admired things a leader can do — take the hit, never throw your people under the bus, have everyone's back. And part of it is exactly that good. But underneath the admirable version there's usually a quieter one: a leader who can't tolerate the discomfort of watching someone they care about fail, and who has quietly confused that discomfort with the other person's wellbeing.
He wasn't protecting his team. He was protecting himself from having to watch them struggle.
And the cost lands on the people he cares about most. A shield that never comes down raises a team that never grows up. Judgment gets built by living with the results of your own calls — so they never built judgment. Resilience gets built by surviving the thing you were afraid of — so they never built resilience. Every hit Marcus absorbed was a rep he took away from someone who needed it.
So he tried something genuinely hard. The next time an analyst made a mistake with a stakeholder, he didn't make the call for her. He sat down with her, helped her prepare, and let her make it herself. He stayed in the room. He just didn't rescue.
By his own account, it was one of the most uncomfortable twenty minutes of his year. She stumbled. She recovered. She fixed it. And she walked out of that room a noticeably different professional than the one who'd walked in.
Within eighteen months, three of his directs were promoted. The team that had been frozen for four years started to move — not because Marcus got worse at protecting his people, but because he finally stopped.
Here's one thing to try. Think about the last time you stepped in to handle something on behalf of someone on your team. Then ask yourself honestly: did they need protecting, or did you need relief? The next time that same moment comes around, stay in the room — but let them make the call. Coach, don't catch.
Because when you take the hit for someone, it's worth knowing who you're really sparing. Them — or yourself?
Comments