I joined a new team as a manager and after 3 years was kindly asked to step down and become an IC. While there are many external factors to blame, I decided to do an honest postmortem with myself so I thought about these things a lot. As a line manager a huge mistake you could make (especially if you’re joining a new team) is not being technical enough. You may not write code anymore, but you are expected to know the…
Mistakes as a new manager
111–120 of 157 posts
Re: Mistakes as a new manager
#112I joined a new team as a manager and after 3 years was kindly asked to step down and become an IC. While there are many external factors to blame, I decided to do an honest postmortem with myself so I thought about these things a lot. As a line manager a huge mistake you could make (especially if you’re joining a new team) is not being technical enough. You may not write code anymore, but you are expected to know the…
I'm an IC on a team full of seniors with strong domain knowledge that recently hired in an EM from the outside. In short, it was pretty bumpy and despite the guy being an ex engineer, his constant questions about how the system works were a huge drag. Maybe to him he was digging deep but to me it felt like my (and my teammates') work was blocked by his inability to grasp simple concepts. Like the time spent explainin…
Re: Mistakes as a new manager
#113The way to see this is that we’re all individual contributors, from the janitor to the CEO. Because if you’re not an individual, then what are you? And if you’re not contributing, then what are you doing there? When you manage a project or team, you’re just individually contributing in a different (though usually overlapping) way. Also, it’s helpful to remember, when delegating, that one reason you’re probably managi…
Re: Mistakes as a new manager
#114Earlier quoted context omitted.
Fully agree, quality is teams's effort and having a blameless culture where the team pushes for higher quality bar is essential. Chasing a single individual only makes sense when they have a track record of repeating the same thing multiple times - means they are not learning from their past mistakes.
Constantly pushing for higher quality is not healthy imo. You end up burned. I don’t want to be a high performer (I end up burned) and I don’t want to be a low performer either (end up fired). Something in between is something ICs shouldn’t be afraid of aiming to (unfortunately management doesn’t think like that and want to extract until the last drop of productivity from us)
Re: Mistakes as a new manager
#115Most of these are pretty accurate, but there's good news: giving a sh!t about your people will likely get you 80% of the way to being a good manager. If you genuinely care about them, their work and progression you're already aligned with the key aspects. You can learn & figure out the rest. It might be hard and very unpleasant at times, and stressful, but building the teams that build software is the most rewarding…
One of the most stand-out moments of leadership I've ever witnessed was my boss protecting me and a colleague from another manager on a different team. He put his foot down and drew a line about what was to be expected of us (among our other competing responsibilities). Fight for me and I'll fight for you.
Re: Mistakes as a new manager
#116This misses the single biggest mistake every new manager makes: avoiding hard conversations with your reports. If you start managing folks you were recently in the trenches with this can be VERY hard. These are your comrades after all! You want them to like you. It’s all very natural. Sadly it is the single biggest cause for dissatisfaction I’ve seen on a given team. Being unwilling to give honest, direct feedback re…
> I've noticed quality issues in your code recently... Why is it always the report who is the source of the problem and not the manager? How about "I've created a toxic work environment and put my reports under a lot of stress. And I have not given them any opportunities to grow and learn new skills. I am planning to do better..." Words that will never come from the mouth of a manager. Have a hard conversation with y…
Re: Mistakes as a new manager
#117I joined a new team as a manager and after 3 years was kindly asked to step down and become an IC. While there are many external factors to blame, I decided to do an honest postmortem with myself so I thought about these things a lot. As a line manager a huge mistake you could make (especially if you’re joining a new team) is not being technical enough. You may not write code anymore, but you are expected to know the…
I don't think that's the main goal for a manager (even technical). I'd say generally, the manager should understand why the team is building something, and the engineers should know how. The why includes who is going to use what was built, when do they need it, what trade-offs can be made, etc.
Re: Mistakes as a new manager
#118The way to see this is that we’re all individual contributors, from the janitor to the CEO. Because if you’re not an individual, then what are you? And if you’re not contributing, then what are you doing there? When you manage a project or team, you’re just individually contributing in a different (though usually overlapping) way. Also, it’s helpful to remember, when delegating, that one reason you’re probably managi…
The difference is in how your performance is judged. ICs are judged by their individual contributions, hence the name. Managers are judged by the performance of their team/department/organization/company. It's not enough to say, as a manager, "I personally ran the sprint meetings and did 1:1s and performance reviews so therefore I'm doing a good job."
The individual work managers do is much harder to tangibly measure. Things like establishing a culture, balancing your roadmap between one-off customer requests and internal production vision (and hacking in some AI crap to make your CEO happy), hiring the right people. Just doing the table stakes individual work of managing your direct reports' vacation time, promotions, and running team meetings is really only good enough for beginner, first-level line managers at bigger companies, where they just need people to execute established processes.
> Also, it’s helpful to remember, when delegating, that one reason you’re probably managing is that you either have tired of running your brain in fifth gear or, at your age, can’t.
ehhhhh. Management is a lot more reactive, that's true, but saying it requires less brainpower isn't true. As a manager you're constantly context switching. You don't just care about the codebase and solving one specific problem, you also care about sales and marketing, your customer support team, the budget for next year. You're getting slack messages from executives who need an update right now on your project, at the same time as an engineer needing to talk because their partner just filed for divorce and they need mental health days (and you need to support them while also figuring out how to rebalance their workload). It's a very different way of working that uses very different parts of your brain. But it's not just sitting in the executive bathroom and delegating work while you smoke a cigar.
Re: Mistakes as a new manager
#119Re: Mistakes as a new manager
#120This misses the single biggest mistake every new manager makes: avoiding hard conversations with your reports. If you start managing folks you were recently in the trenches with this can be VERY hard. These are your comrades after all! You want them to like you. It’s all very natural. Sadly it is the single biggest cause for dissatisfaction I’ve seen on a given team. Being unwilling to give honest, direct feedback re…