This is just one of many, MANY stories I can share about a manager I once worked under, who I will call “Trevor”. I worked as an engineer in a broadcast facility. We would often need to do upgrades to one important system or another, and some of these, such as main power, were handled by third-party specialist contractors. They provided a combined Risk Assessment – Method Statement (RAMS) document that any relevant stakeholder in the company (basically any manager whose team could be affected) had to read and give the thumbs up to before the job could proceed.
One such job was scheduled for a Friday night, and muggins here was the late shift that day. The first I heard about it was when the manager of the control room stopped by to ask if I was up to speed with the event, even though I was on a completely different team. I had to matter-of-factly tell him that my own manager hadn’t even mentioned this job to me, let alone asked if I was okay with it.
Normally, I would finish a Friday late shift at 10:00 pm, but this maintenance job wouldn’t even start until 11:00 pm, and it would go on until at least three or four in the morning. So, not only would I lose what was left of my Friday evening, but I would be losing my Saturday morning, as well. Great when you’ve got a young family at home!
I went up to my manager’s desk in the middle of the open-plan office — two floors above the engineering team he was supposed to be running — and asked him about this upcoming overnight work. How come he hadn’t asked me about it? Didn’t he think that he should have at least let me know?
Well, Trevor didn’t like being spoken to like this by a mere mortal such as me, and certainly not in earshot of all the other managers he liked to try and impress. I got dragged into an empty meeting room where he tried to rant at me some more. The only argument he seemed to have, which he repeated over and over again, was that at some point there had been an email, and in that email was an attachment containing the Risk Assessment, and at the bottom of the last page of this Risk Assessment under the heading “Resources” was my name. So, basically, his logic was that I needed to read every line in every document in every email that landed in our shared inbox, just in case my name was in there somewhere. And if my name was there, I had to assume that my work pattern had automatically changed, and he didn’t need to do anything more because it was all my responsibility — so there.
The fact that this was utterly bonkers, the complete opposite of good management, not to mention just plain inconsiderate didn’t seem to occur to him, but at this point in my time working under him, I was not surprised. It also completely contradicted a previous edict he had once issued after we’d adjusted our shift pattern at the last minute to deal with a problem, only to be raked over the coals for not consulting him first!
The one other thing I got out of this incident was that during our argument, I accused him of not dealing with my upcoming leave request, something he was well known for not doing. I wanted a week off for my fortieth birthday and had put this into the system nine months earlier. “I was just dealing with that!” he barked at me, which basically meant that he had utterly forgotten about it until I mentioned it. This was proven the next day, when we found out that he had rung up a colleague at our other site, practically pleading with him to cover my leave later that month.