8 ms·
So at one point I took on a management job, stepping up from a (lead) developer. I felt like the whole thing was kind of a train wreck and I am still slowly ana
by IgorPartola 13y ago
So at one point I took on a management job, stepping up from a (lead) developer. I felt like the whole thing was kind of a train wreck and I am still slowly analyzing the black box recordings from it. This was my first time having direct reports that were not one or two interns and managing a team of seven other highly intelligent people was quite a chore in itself. What bugged me is that I could never tell if the problem was the environment or something I was doing. I tried to be fair. I mentored people when I could help. I tried to not be overbearing when I had nothing to add. I present challenging problems to the people who I thought would find them interesting. I advocated for my guys to the upper management, trying to improve working conditions. I insisted on being flexible, discarding what was slowing us down, and adopting what was good. None of that seemed to help: my dev team learned to resent me for delivering the bad news (for example the dev team was the fallback for doing data entry for weeks on end when nobody else could handle it and we had no time to finish better data entry tools because of it), and my boss(es) learned to resent me for not delivering what they expected.
I know that there were quite a few problems above me. Lack of leadership carries far and wide and there was a disconnect between what the products did and what the management thought it did. Lack of money (think lack of compensation, lack of tools, lack of time for anything but immediate returns) did not help either. I do keep questioning whether I was doing all the wrong things or if I was put in a situation designed for me to fail, or perhaps both.
After I left I understand the company hired three different people to replace me: a manager, a dev lead, and a support engineer. I suppose that's some kind of a sign that I was trying to do too many things at once. Most of the engineering team also left after I did. The least I could do is give them the great recommendations they all deserved so all of them moved onto exciting new pastures. However, I cannot help but feel like I failed at this task that I felt sure I could tackle and I don't understand why.
Please excuse the rant. These types of topics always trigger those same feelings in me.
Edit: now I work as a developer on 2-3 person teams. I have no reports. I get to be productive again! I can write code that doesn't have to suck to compensate for poorly chosen deadlines. This is good for the soul. I do miss leading a team though; not managing but really leading. One of my proudest moments was when I was allowed to follow a system of estimates and sprints I put together and for 8 weeks my team delivered on schedule and exactly what was promised. That was one of my more joyful moments.
- bane 13y agowelcome to low/mid-level management. You get squeezed from the top and bottom. Everybody will hate you, so you just try and hit deadlines. It also sounds like a typical story where the larger organization was trying to keep management lean, without realizing that it really did take multiple people to do the job. One place I worked at ground through three managers in 6 months (with 120 people under them) before finally getting the clue and hiring a proper team of 7 to do the job. It's not uncommon at all and it really is the upper management's responsibility to properly staff their low/mid management teams.
- rpwilcox 13y agoHow common is 600% turnover in management? I know turnover in engineering is usually high (if people are moving around every 18 months to 2 years)... but 600%?
- kevingadd 13y agoI've seen turnover that bad at past employers. In some cases it continued for years after I left. I think it depends on the company, not necessarily averages.
- marrs 13y agoDitto for a place where I used to work. Unfortunately for me and my colleagues, the reason for the high turnover was that they kept hiring good dev managers who all quickly identified the projects' major problems and set about trying to solve them. This had the unfortunate side effect of revealing the incompetence of the TD, so they had to go quickly.
- Consultant32452 13y agoTD? Technical Director?
- bane 13y agoI think more common than you can believe. low/mid level management is incredibly stressful and hard to build a proper support framework around and hard to do if that framework isn't there. After you asked, I spent a bit of time thinking of similar situations (high low/mid turnover) and I can think of 2 or 3 other instances I know of personally. Anecdotal I know, but there it is.