4 ms·
I happen to be an expert (read: flailing desperately to do this work right) at the moment, and I thought a lot like you a year plus ago. Oh God... How that vi
by salawat 5y ago
I happen to be an expert (read: flailing desperately to do this work right) at the moment, and I thought a lot like you a year plus ago.
Oh God... How that view has changed. As a manager, if you're actually trying to make your team's lives easier, it's bloody hard work. I started out as the first IC and sort of had my role take shape from there.
I know where the skeletons are, and spend a great deal of time making sure my people know about them before falling victim to them. I'm often troubleshooting cross-team problems, and either localizing the nebulous stuff to a particular team, or getting the best teams to work together to resolve the issue in the same room, talking, and understanding each other. I'm sanity checking requirements, auditing everyone's meetings, to make sure important things propagate beyond team's silos.
I'm constantly switching between an understanding of work about 3 weeks minimum ahead of everyone else, and now, trying to figure out if divergences from what's planned is just statistical noise or something to worry about.
Then there is the HR side. Everyone has their own bucket of stuff, and it's my job to help make sure they have the tools they need to overcome it. Sometimes this means looking up weird jurisdictional things, rewriting a job description, shuffling around work, book or resource recommendations, or sometimes long after hours calls or the occasional emergency interference running. There's also making the hard calls on whether someone's forseeable future is going to be upset or not. I'm not jaded enough to just not care anymore, so I always try to make sure if a hard call has to be made, I can make sure everyone involved leaves with something in the sense of a possible new direction. That's not part of my JD but something I just feel like should be done and I'll continue to do until a really unlucky streak of bad hires beats it out of me I guess. I hope by that time I won't need to do this anymore.
The way I see it, I'm sacrificing my ability to shut up and engineer the stuff I like (software) to make sure my teams can concentrate on just doing what they are best at, and I'm context switching too much to do reliably anymore. The fact is, all these "odd-jobs" have to get done to ensure the organization runs and someone has to do it... Might as well be the one who knows the org best until I've got others trained up and confident enough to do the same.
Re: Expensive proxies
I try to act as the anti-proxy. When I see bad communication, I try to get people circled around in the same room looking at the same things. My goal is not to say X has it all wrong to Y, and Z, but getting X, Y, and Z all saying the same thing about the same thing.
Sometimes you have to unlearn organizational habits to come to terms with what's actually going on. My higher ups may share your sentiment of that making me an "expensive proxy" but after the second or third projectt that has to get redone, eh, the grumbling quiets down.
Haven't been fired yet! So there's that!