Managing Up
“Managing up” has to be one of my least favorite business buzzword phrases, and the most condescending.
I’m grateful I don’t hear this phrase as much as I used to earlier in my career. The last time I heard someone use it, they were commenting on how little they thought about their direct supervisor’s ability. When you think about it, the phrase, and the idea behind it, is pretty insulting. The implication is that I know better than the person above me in the company organization chart and, essentially, have to do their job for them because they’re incapable of managing me. For one thing, it starts from a false premise, though one that a lot of technical people seem to buy into, namely that my work requires knowledge and abilities beyond the management layer above me. I’ve never found that to be actually true.
I prefer the term “managing expectations”. It’s more accurate and applicable to all levels of the org chart. It’s also something I do regularly. For instance, if I’m working on a project for someone, I want to make sure they know what’s involved and the kind of time that might take so they have some idea why I’ve set a delivery date. Or, more importantly, why the delivery date the stakeholder might expect is unreasonable. There are times, of course, that I find myself able to deliver well within the expected time, but, unfortunately, that’s much more unusual.
The other way I manage expectations is in what can be delivered at all. I will grant that to many the computer systems I work with on a regular basis are a bit like magic. Black boxes of mysterious abilities that miraculously produce information and reports when working correctly. Or, evil, possessed infernal machines that are blamed for keeping some other department from producing results when they aren’t working well. Obviously, my goal is to make sure the technology in my care is always working well, but that’s not always possible. And, when I’m asked by someone to produce something new, I want to give them an accurate idea of what precisely I’ll be able to deliver to them on whatever timetable is likely. Of course, like most technical people, I follow the lead of Montgomery Scott, Chief Engineer of the starship Enterprise and do my best to set expectations low so that when I am able to exceed them I seem like a miracle worker. Like the time I told someone I’d “do my best” to recover some of the more than three terabytes of engineering drawings that the previous IT person had lost to a cryptolocker virus, then found a decryption tool after everyone else had left early for a long holiday weekend that restored all the lost data.
Yes, I worked what seemed like a miracle, but before I did, I set the expectation that the data was going to be lost because the last tech hadn’t tested the backups. So, rather than “managing up”, manage expectations of what kind of results, and when those results, can be delivered. Everyone, not just your managers, will appreciate it more.
This post originally appeared on my LinkedIn profile.