Every good delivery manager is a shit umbrella

It's 9:04 on a Tuesday. Somewhere in the building, a HiPPO has just found out your team shipped something without asking them. They found out the worst possible way: a colleague congratulated them on it.

You moved around them, because their sign-off meant 3 weeks and a steering committee with biscuits. The wall came down. Now the dust is drifting towards the people who did the work.

Cue the hushed voice and the cello.

Here, on the fourth floor, we find one of the open-plan office's least understood creatures: the delivery manager. Note the lanyard. Note the laptop with 31 tabs open. She has sensed the HiPPO before the team has. Slowly, she rises from her desk and places herself between the herd and the danger. She will not run. Running would expose the young.

The creature has one call, and it never changes: "Sorry. That was my call."

Say it whether it was strictly your call or not, and say it before anyone can type an engineer's name into the chat. Most "lessons learned" sessions are a hunt for a name, with sandwiches. Get yours on the plate first.

Then let them shout. Think submarine film: destroyer overhead, depth charges coming down, the crew staring at the ceiling. You run silent. Don't defend the work. What's on the table is whether they still matter, and every clever point about deployment frequency (how often you put changes live) or cycle time (days from idea to live) is a torpedo fired straight up. Nobody mid-barrage has ever stopped and said, "Ah, good point about the cycle time."

When they've run out of charges, ask one question: "What would have made this OK for you?" The answer is nearly always small. They wanted to know first. They wanted not to hear it from their own boss, in the lift. Write it down where they can see you doing it.

If the anger lands on you, it stops with you. If it lands on the developer who wrote the code, it spreads into the private sums every engineer does about whether going fast is worth a bollocking. Teams that get shouted at learn to ask permission. Give it a fortnight and the hammer might as well never have swung.

No film crew has ever recorded a delivery manager receiving a thank-you card in the wild.

The lessonTake the backlash yourself, so the team keeps the nerve to move fast.

Why it works

Teams that feel safe try the risky option. Teams that don't spend their energy covering their arses. Nobody was ever made to feel safe by a poster in a kitchen. They feel safe after they've watched someone stand up.

Two rules keep the umbrella honest.

First, the team hears what the stakeholder wants, never how loudly they said it.

Second, taking the blame is a loan, and you pay it back. Next time, go to that stakeholder early. Bring them a small win (lesson 24). If all you ever do is absorb, you're a punchbag with a lanyard.

It costs you something. But venting is about the work and over in ten minutes. Bullying is about a person and doesn't stop when the meeting does. Sit through the first. End the conversation on the second, and write down what was said. Even this hardy species needs shelter: a peer, a boss who knows what you're doing and why, or a pub with a reliable quiz night.