The Meeting Where I Lost My Temper, and What It Cost

Week eleven of a data centre migration, Thursday, ten past three. A storage engineer on the call said the validation runs hadn't started yet. I said, in front of nine people, "Are you actually doing this job or just attending the meetings about it?"

Nobody said anything. We moved to the next agenda item. I remember thinking I'd been firm but fair.

Here's what I didn't understand at ten past three on a Thursday.

That engineer stopped volunteering information. Not dramatically. He still turned up, still did good work, still answered questions. But he only answered the exact question asked, and he never again said the thing you most need people to say, which is "I'm not sure this is going to land."

Worse, everyone else on that call learned something too. They learned what happens when you bring bad news into this room while I'm under pressure. So the next slip, which was in the network team and had nothing to do with him, reached me about three weeks after the people doing the work knew about it. By then the mitigation options had gone from four to one, and the one was expensive.

Nine seconds of temper. Three weeks of blindness. That's the exchange rate, and it's terrible.

The part that still bothers me is that I never got a bill I could read. Nobody complained. HR wasn't involved. There was no moment where someone said "you damaged that." The cost showed up later, disguised as bad luck and other people's poor communication, which is exactly how this cost always shows up.

I've thought about that Thursday a lot, and what I've concluded is that the storage validation had almost nothing to do with it.

At nine the next morning I had a steering group where I was going to have to say the migration was tracking two weeks late. I'd been awake since four. I'd already rehearsed the conversation eleven times in the shower and I still didn't have a good answer for the finance director. I walked into that three o'clock call already holding a bad meeting, and the first person who handed me more bad news got it.

That's the mechanism, and once you see it in yourself you see it everywhere. Your temper almost never fires at the thing in front of you. It fires at the thing you're scared of, and the thing in front of you just happens to be standing in the wrong place at the wrong time.

Which means the useful question after you've snapped is not "was I right about the validation runs". You were probably right about the validation runs. The useful question is: what was I actually afraid of an hour before that, and who did I make pay for it.

Mine, consistently, is exposure. Being about to be seen not having control of something I said I had control of. Yours might be being made to look stupid in front of a peer, or being ignored, or having your technical judgement questioned by someone who hasn't earned the right. Learn which one is yours and you get about a ten-second warning before it happens, which is enough.

I did apologise, but I did it badly, and I did it four days later, which made it worse. What I said was something like "sorry about Thursday, it'd been a rough week."

Notice what that sentence does. It offers my stress as the explanation, which quietly makes my stress his problem. It doesn't name what I actually did. And "sorry if that came across wrong" is the same trick in a different coat, because it makes the injury a matter of his interpretation.

Here's the version that works, and it takes about twenty seconds.

Name the behaviour, precisely. "On Thursday I asked whether you were actually doing your job, in front of the whole call." Say the effect without asking them to reassure you about it. "That was unfair and it wasn't about you." Say what you'll do differently, concretely. "If I've got a concern about progress I'll raise it with you directly before the call, not in it." Then stop talking. Do not explain the pressure you were under. Do not ask whether you're forgiven, because that hands them the job of managing your guilt, and they've already done enough work in this conversation.

Then, and this is the bit people skip, repair it in the room where it happened. One line at the top of the next call. "I was sharp with Dan last week and that was out of order, it wasn't a fair reflection of his work." Ten seconds. It does more for how much bad news reaches you than any amount of saying your door is always open.

The version of this I'd give my younger self is blunt. Once you're leading, your mood is no longer personal information. It's an input to other people's decisions about what to tell you.

A 26-person support function at a betting and gaming operator I worked near had a lead who was, by every technical measure, excellent. He was also visibly tense every Wednesday, because Wednesday was the executive review. Over about a year the team quietly reorganised itself around that: nobody raised risks on a Wednesday. They'd sit on something until Thursday morning. Not policy, nobody wrote it down, it just became how the team worked. When an incident finally landed on a Tuesday night, mid-fixture, the delay in telling him was eleven hours, and eleven hours of an unreported production problem is a real number with real money attached.

He wasn't a bad leader. He was an unmanaged one. There's a difference, and the fix is not personality transplantation. It's noticing that Wednesday is a thing, and doing something structural about it, like moving your own prep to Tuesday afternoon so you don't walk in loaded.

If you've been sharp with someone in the last month and you haven't repaired it properly, book fifteen minutes with them on Monday and do the twenty-second version above. Name the behaviour, no "but", one concrete change, then stop.

If there's genuinely nobody, then take the other half of it: look at your calendar for the meeting you're most tense about this week, and find out what you do in the hour after it. That hour is where your team is paying for your stress, and you're the only person who can take it back off them.