Earlier quoted context omitted.
I always feel there is an alterior motive when managers ask me these sorts of questions. Like the GP post, I'm rarely honest; I tell them what I think they want to hear. This has been learned over years where being honest resulted in the manager getting defensive, a lecture about "getting with the program" or at best an attempt to pursuade me to see it their way. Rarely have I ever had critical feedback accepted and…
I am a manager, but when I was an IC, I held your view. I learned that giving even softened feedback resulted in being at best ignored for a week, at worst, becoming a marked man. I resolved to change this for my team. Ask for feedback broadly, and about projects, not me per say. Peoples end up commenting on the project/ sprint, and they feel safer. Much of what they talk about however, I have power over, so I view i…
Some mistakes I made as a new manager
91–100 of 156 posts
Re: Some mistakes I made as a new manager
#92> I asked people for feedback. I found that if I just asked “do you have any feedback for me?” people often wouldn’t, but if I asked more granular questions—“was that meeting useful?”—I would usually learn a lot from it. This part is good. I think generally as engineers, a manager simply asking "do you have feedback for me" just feels like a trap. I don't know man, there's plenty of things you do that annoy me but li…
Re: Some mistakes I made as a new manager
#93I had worked at my first software company for around five years when our lead developer left for greener pastures. Soon thereafter as the most senior developer on staff I had a meeting with the owner of the company and his assistant talking about the need to interview people to fill the lead position and it was kind of half floated “I don’t suppose you would want it” and I champed at the bit. I was young and desperate for what I saw as career advancement. They agreed and drew up a new contract.
I moved out of the bullpen and into the office. Pretty quickly started trying to fix things I saw as “wrong” with our process by laying down decrees.
One of the biggest being trying to get people to use version control (git) - it was 2009 and it was frankly still “acceptable” not to use version control. I had a lunch-and-learn where I taught everyone how to set up and use git. They didn’t understand the why. We had nightly backups, isn’t that good enough? I tried incentivizing them with a literal weekly “whoever has the most commits by the end of week gets a gift card“ and the same very green junior dev won it every week because she was the only one who bothered.
At this same time a developer I had considered a friend was vastly underperforming. Prior to my time as lead, his desk had been moved to be in public view to try to keep him on task, it had not worked. He would mess around all day every day and when due dates rolled around he would turn in half completed rush jobs. He was already on notice when I took over. After a talk with the owner it was very clear we were trying to get rid of him. I had to be the one to place my friend on an improvement plan he was fully expected to fail. It was very difficult for me emotionally. A couple days later we were both working late and I called him into my office and I basically told him on the low down that the owner was gunning for him and he should start looking for a new gig. He was gone very shortly thereafter and I thankfully never had fire him.
Around the same time as this, a developer told another developer a joke with exceedingly mild sexual innuendo - something not at all out of place in an episode of Rocky and Bullwinkle hidden for the parents. Well a third developer overheard the joke and put in a formal complaint and after bouncing off our HR person I was tasked with formally reprimanding the joke teller and the intended joke recipient. Joy.
This entire time I am doing a very poor job of delegating, working 10 hour days and weekends and falling further and further behind. Hardest I have ever worked in my life, even to this day. And then my yearly review comes due. The owner’s assistant conducts it. It is the first negative review of my career, I am not getting enough done.
I am working harder than ever, being put into positions I hate, and being told I am not doing enough. I went from loving my job to hating it. My stress level reaches 9001 and something in me just breaks, I get the worst headache of my life followed by what I would describe as jolts of “face lightning” followed by numbness and facial weakness. I go to the ER.
They suspect stroke and do a CT scan, but find nothing. I end up getting diagnosed with stress induced trigeminal neuralgia and put on a drug to relieve apparent inflammation of my nerves.
I had a former colleague who regularly tried to recruit me to whatever gig he was working at the time. Literally the next day I text him asking if he’s looking for a developer. He is, he sets me up with an interview with his boss. Within a week of the negative review and the trip to the ER I am putting in my two week notice.
As one final insult, the owner points out that in my contract I had agreed to three weeks notice. I had planned to take a week off between jobs, but that’s gone I guess.
And that’s why in the last 14 years since, I’ve made zero new attempts to become a manager again. I am a firmly believe I was not built for the task. I just want to build cool things.
Re: Some mistakes I made as a new manager
#94Wow. the level of mistrust and fear shown by reactions here is ... at least I am not alone :-) We (most of us) live in democracies with clear rules of law and strong defence of individual rights. But we work in feudal hierarchies with arbitrary rules and love by whim of the powerful. I think that's the first thing to chnage rather than hoping the training middle management to be "better communicators" will improve th…
Re: Some mistakes I made as a new manager
#95Earlier quoted context omitted.
I found it difficult when working with American companies, as they can be purified by positivity. A saving grace of software work is the retrospective, those were at least a moment of honesty. While I do appreciate the upbeat attitude, I found it made people hide small issues to not ruin the vibe, and anyone with major concerns with approach risks getting backbenched.
I have also been really confused by this. It reminds me a bit of a clunky, modified, but also less extreme version of face saving in Eastern cultures.
We have a bit of it in Australia but it isn't as hard to pierce the veil. A robust system of banter takes the edge off I guess.
Re: Some mistakes I made as a new manager
#96> ANGSTING INSTEAD OF ASKING This is a great way of describing one of my biggest peeves in the office: So many unnecessary conflicts/dramas can be avoided by simple and honest communication. There’s a related dysfunction where managers are (wrongly) convinced that they must answer every question in the most positive and upbeat way possible. I had to leave a company once because my manager was frustrated with many peo…
Communication isn't enough. If neither side is willing to compromise then knowing what everyone is thinking doesn't help, and often makes things worse. There has to be a culture of openness and willingness to change in order to avoid drama.
Re: Some mistakes I made as a new manager
#97I'm a new manager and am facing a conundrum over a supposed super star who joined my team but, at least from what I can tell, is far and away the least productive member of my team. Any ideas?
Talk to them and figure out what's different between your team and their previous team. You might be able to change things to get more from them. If not, let them move on to another team where they can be better.
Re: Some mistakes I made as a new manager
#98I've been managing teams for 16 years, I think it's actually really beneficial to stay hands on in lead or director roles. After that it's usually not possible given the work load. It improves team alignment, you can evaluate people's work better, understand their issues better and help level them up. Some of the companies that promoted the hands-off style of management, like Twilio are currently really struggling. D…
I was a director with 3 sr. managers reporting into me. They had 4-5 ICs. I found being hands-on pretty much impossible even with fewer than 20 people.
Is 4 reports common in the US? How do companies survive with so much management?
Re: Some mistakes I made as a new manager
#99Earlier quoted context omitted.
I was a director with 3 sr. managers reporting into me. They had 4-5 ICs. I found being hands-on pretty much impossible even with fewer than 20 people.
Honest question, I come from an industrial background where you have Work Package Manager in charge of the work of roughly 10 persons but not their actual manager with all the bureaucracy associated and an actual manager with less than 25 reports don’t exist. Is 4 reports common in the US? How do companies survive with so much management?
Re: Some mistakes I made as a new manager
#100> I asked people for feedback. I found that if I just asked “do you have any feedback for me?” people often wouldn’t, but if I asked more granular questions—“was that meeting useful?”—I would usually learn a lot from it. This part is good. I think generally as engineers, a manager simply asking "do you have feedback for me" just feels like a trap. I don't know man, there's plenty of things you do that annoy me but li…