3 ms·
I love this. But let me play a mild devil's advocate. Sometimes people move into management not because they want to necessarily progress in the company they're
by bane 13y ago
I love this. But let me play a mild devil's advocate. Sometimes people move into management not because they want to necessarily progress in the company they're in now, but because moving into management is an overall career advancement. Leaving a position with "manager" in your title makes it more likely you'll end up in one with "manager" in the title at your next job and be able to command a better position/pay combination.
- pixelmonkey 13y agoThis is a chicken & egg problem. If someone is moving into management as a form of "career advancement", the way I read that is, they think they should be paid more, but they don't think companies pay individual contributors with lots of experience more than they pay managers with lots of experience. That sucks. My belief is that management & compensation should be completely decoupled, so people wouldn't seek to do management for "career advancement", but because they actually enjoy management. For example, I hired a product manager last year and he really loves the work. It allows him to mix small engineering projects with product strategy, requirements elaboration, and his considerable people skills. But I don't see him as a "superior" to my other engineers -- he is just a contributor, like my other engineers. The "pay scale" for management should be similar to the pay scale for advanced individual work, in my opinion. Unfortunately, that's not the market we live in, so I can see why people would choose to seek management for "advancement" reasons, but this is just an unfortunate side effect of the market and ultimately causes a lot of talented contributors to do work they don't really love. Why? Essentially, for the money & prestige that needlessly comes with it.
- bane 13y agoActually, in the cases where I've done lots of hiring etc. It's quite often that good engineers make more than their managers. I think this is a good thing in some cases. I'm thinking of the recent Ask HN "What happens to older developers?" Which I answered in some detail here https://news.ycombinator.com/item?id=7373301 https://news.ycombinator.com/item?id=7373301 There's lots of reasons for wanting to get into management, and I've found that one of the main motivators is wanting to get out of direct code-slinging software development as the majority of their day and use their experience for the company good in different ways -- basically new challenges and all that...but keep a similar level of pay. And very few people these days want to stay at a single job for more than a few years. So for a very experienced developer, they may start to feel "trapped" in their career and may not even know it. Sorry, I don't want to be contradictory or make you defend what's obviously a working system for you guys. Just food for thought.
- pixelmonkey 13y agoNo need to apologize -- it was a healthy question & it's a strong point about motivations for management career move.
- gaius 13y agoRemember that there are two sides to every promotion: the promotee must also want it. So decisions on who gets promoted are made by people for whom getting promoted chimes with their value system.
- cwp 13y agoWell, there's another pattern that leads experienced developers into management. After a while, they realize that no matter how good they get, they can only write so much code each day. They can only increase their effectiveness by applying their experience to improving code that other people write. One route to that is by getting out of mainline production coding and going meta: designing new systems, programming languages, tools etc. Good work if you can get it, but prone to failure. Another route is to become a manager. There's plenty of demand for managers with technical ability, a clear route for advancement and much lower risk of failure.
- kingraoul3 13y agoTraditional business structures are predicated on the manager knowing more about the product & process than his/her employees - that's how he or she vet's and improves their work. The managers your describing sound more like PM's.
- mikeash 13y agoBut why should moving into management be an overall career advancement? Imagine a carpenter who sets his sights on working hard at carpentry and being a good carpenter so that he can eventually advance his career by becoming a plumber. Makes no sense, right? These are completely unrelated skills. Maybe plumbing pays more (reverse the roles if I got that wrong) but that doesn't make it an "advancement". Certainly one could make the move, but it's a lateral move, not a logical progression. Management is the same way. It's a different field. Yet somehow we have this idea that if you do well enough in some other field, "advancing" into management is a logical next step. It makes no sense.
- draugadrotten 13y ago> Management is the same way. It's a different field. Yet somehow we have this idea that if you do well enough in some other field, "advancing" into management is a logical next step. It makes no sense. It can make sense. A leader needs the respect of those she/he leads. It is easier to command respect when you are perceived as a technical expert or authority. Promoting the Dilberts to bosses is an attempt at giving the engineers what they say they want: bosses with Dilbert's engineering skills.
- bane 13y ago> Imagine a carpenter who sets his sights on working hard at carpentry and being a good carpenter so that he can eventually advance his career by becoming a plumber. The current way it works in trades like that is to move up to being a foreman or a site supervisor or similar. It's no different really. Ideally companies with management gaps want to move experienced tradesmen into these roles rather than put "management professionals" who wouldn't know a 2x4 from a band saw into them. Segregating out "management" as an entirely separate discipline makes a kind of sense, and it's why management is taught as a separate skill set with certificates and MBAs and all that. But I think the results have been mixed (90s Apple is given as a textbook example). For every professional manager who does a good job, I think it's possible to find somebody who moved into management who does as good or better because they understand the problem domain of their reports better. Wholly agree though that it's a separate set of skills, but I think those skills usually work best when layered on top of practical experience in the field.
- digikata 13y agoI think many otherwise technical people start moving into management because of a desire to have a bigger value impact in their company, but there is a poor breakdown of responsibilities between technical positions and management positions. Modern organizational structures (esp at big companies), usually puts in non-technical management in places where they take on higher-level responsibilities driving product and business. Think product managers, or high level sales directors, etc. Technical contributors' skills are treated as "too valuable" to waste on these management duties, but paradoxically, the opportunity for a technical person to contribute at a high level or early decision points ends up as something often held separate from the engineering career ladder (until you get very high up). I come across mentions of WWII era projects, designs of famous aircraft etc where the designs were incredibly well suited to the needs, and produced in incredibly short time-frames. Some of that is obviously the war-time focus, but I also notice that in many of those projects the lead position is not a non-technical manager, but a technical chief engineer where management functions must have been subservient. Unfortunately, there isn't a huge amount written about the organizational day-to-day project structures during WWII. I think at least some of the appeal of startups and smaller companies for technically oriented people is that division of responsibility is not as formalized and contributions can flow more easily between different domains. But again, startups are structured where technical founders are at the levers of control, and that's inverted from how many companies end up organized as they grow.
- pcorliss 13y agoI just read an interesting book about Lockheed's skunkworks program. It covers a bit of WWII, Korea, Vietnam, but mostly the post-Vietnam era. http://www.amazon.com/Skunk-Works-Personal-Memoir-Lockheed/dp/0316743003 http://www.amazon.com/Skunk-Works-Personal-Memoir-Lockheed/d...
- gatehouse 13y agoThat caliber of leadership and oversight requires immense skill, authority over capital allocation, AND trust from the next level up. Organizations that can maintain this are rare and typically have a brutal filtering process.