Hacker News new | past | comments | ask | show | jobs | submit login
Employees leave managers, not companies (alaisterlow.com)
625 points by kirkus on Feb 6, 2013 | hide | past | favorite | 257 comments

The problem here is that the modern company embodies a lot of the principles of medieval serfdom.

Serfs occupied a portion of land and owed a portion of their crops to the lord of the manor or their feudal lord. It was slavery in all but name.

The modern company is a kingdom. Managers are feudal lords. Managers can decide to hire (and fire) employees such that the employee is essentially beholden to that manager. Employment status is analagous to the land serfs worked.

The problem is that most companies have little internal mobility. If you don't get on with your manager the best thing for you and the company is to work for a different manager yet most companies make this exceedingly difficult.

At Google, individual engineers are far more empowered than that. There is a strong internal process for simply changing projects.

Also, most companies have performance feedback come solely from managers. Managers are an important source at Google but peer feedback carries a huge amount of weight.

So in many companies employees leave because they can't escape their feudal lord. I get it. The problem here is corporate feudalism.

Companies need to stop making it easier to move to a better team or getting a pay raise by leaving the company rather than moving within the company.

On a related note, some of the more effective companies I've worked for have had strong "up or out" cultures. Now, I know that this sounds harsh and draconian at first. And it conjures up images of political intrigue, heated power struggles, and corporate backstabbing. But truth be told, I've actually found those evils to be more prevalent in companies that don't cull their dead weight.

What happens is that these firms accumulate a vast, stagnant layer of middle and upper management types who have no incentive to work any harder, take new risks, or develop talented employees. Instead, they're simply cashing in on a safe paycheck, riding a pretty cushy high horse, and fiercely fending off anyone they perceive to be competition for their sweet gigs.

Compounding this problem is the fact that mobility slows to a crawl, because the queue is full. This breeds dissatisfaction with the young, ambitious types, while simultaneously breeding resentment among the older, entrenched types who adopt the grumbly "kids these days..." defensive mentality.

Now, there are plenty of ways to screw up the up-or-out system: bad KPIs and standards, inept evaluation processes, etc. But no system is perfect, and at least a system that forces honest dialogue with managers about their future advancement prospects is better than a system wherein lousy managers can overstay their welcome.

I agree that companies that don't cut the dead weight have tremendous amounts of very bad internal politicking, up-or-out organizations tend to have politics optimized around moving up...which is very rarely tied to any sort of work performance.

The U.S. military has a similar up-or-out policy (especially among the officer corps) and the result is (more often than not I'd say) yes men who latch onto a strong leader type and ride his coattails into a senior officer position. The result is poorly informed and advised leaders, and senior staff who spend their time figuring out if what they're doing will be approved "by the old man" instead of actually promoting the function of the organization, fight and win wars.

I'd argue that this problem exists in any large bureaucratic culture, and that its prevalence is often just as bad in non up-or-out environments.

The key difference between up-or-out and the alternative is that, in the alternative, a certain segment of the employee base plays the politics game, and a certain segment kicks back and stagnates in the middle, while the rest try to get ahead honestly. In up-or-out, at least the third category has a decent shot. In non-up-or-out, the people trying to work hard and advance on merit will run up against the entrenched slackocracy and the political Machiavellians.

It's almost like you're describing the dichotomy between military officers and civilian federal government jobs, where somebody can chill in a GS-13 position for 20 years and then retire.

False equivocation. The problems are not all of the same severity, and it is a fallacy to say they are "all the same" just because you use the same word, problems.

I didn't say that.

In my post, "problem" was referring to the parent post's "politics organized around moving up." My point is that most corporate cultures have elements of that focus on upward mobility. Obviously its prevalence varies from company to company. But I'd rather take a culture with an over-focus on upward mobility and potential for upward mobility than a culture with even a lesser focus on upward mobility, but less potential for it (due to all the dead weight).

I'm not holding "focus on upward mobility" equal in that assessment.

The problem there is that the US military usually has a very hard time evaluating actual effectiveness since it's not reasonable to start a war just to see how your employees do.

This means during prolonged periods of peacetime, a form of regulatory capture happens where the metrics used to evaluate promotion become decoupled from actual fitness of purpose.

Metrics used to evaluate fitness being detached from the actual purpose of a position is not only a characteristic of the military.

For example, since success in academics is usually the first requirement to even start in any position above the most menial, anyone who finds it difficult to toe the line and waste hours listening to someone drone on about a topic totally unrelated to their purpose in life, or enthusiastically embrace make-work homework assignments, will likely have a hard road, no matter how well qualified they might otherwise be.

well, I meant the military as an example, it's interesting that you bring up evaluation of fitness during peace vs. war time.

One could argue that the U.S. military in particular has had a tremendous opportunity this last decade or so to conduct exactly the kind of wartime evaluation you're talking about. But I wonder if the evaluation metrics are optimized towards peace-time?

Not a military member or veteran myself, but am friendly with quite a few present and former officers. The culture they describe sounds extremely political. Almost like being a career military officer is equivalent to being a career politician. To some extent, there's a hint of academy politics as well: people who publish, get cited, etc., move more quickly than people who don't. To another extent, there's classic politics: people who schmooze within the Beltway, know how to play the media game, etc., get ahead quicker than others.

In many respects, David Petraeus is the perfect embodiment of these political principles. He published, he politicked, he maximized his media exposure, and he hobnobbed within the right DC circles. I'm not qualified to judge whether or not he was as good a leader as many believe him to have been. But he was certainly a top-notch political operative.

(Other government agencies, e.g., the CIA, have very similar internal political incentives. The game is almost the same. This may explain, in part, the fluidity between military leadership and Agency leadership).

That sounds like a massive conflict of interest.

Usually a "senior" officer needs some command experience to make it beyond O-6. I know the Navy in particular, attaches qualifications to certain positions which would make it hard for yes-men to get promoted, even if they're on the CNO staff. For example, a CVN Carrier skipper, has to command a smaller ship, and be nuclear qualified, and usually a tour as carrier XO, before they get their command.

For the medical corps, above O-6, they usually have commanded at least one smaller facility, before they get an administrative flag assignment. More than a few have flamed-out at O-5 and O-6 commands.

In a carrier squadron, being XO or CO is preceded by being a department head. Maintenance department is a good one to get a command, but there are other departments.

The Army Medical Command had the problem with senior staff, where they were a large number of senior officers, O-8/O-9, involved in the Walter Reed scandal in 2007, were either fired or retired. Covering over issues with memos and paperwork up the chain-of-command by "yes men" didn't cut it.

The problem is that "command experience" doesn't mean that you did a good job at it. The impression I've got from friends who have observed this process first hand is that people get shuttled into a job to get "command experience", do a crappy job but everyone hunkers down and waits because they know they'll be gone to a better gig in 6 months so why rock the boat, and then the person gets promoted with their newfound "command experience".

Some of those same officers get relieved due to "poor command climate" one somewhat recent example; "[Navy Captain] was fired as commanding officer of Navy [a] Health Clinic after a survey found a poor command climate." Doesn't happen as much as it should, perhaps, but its not unknown.

The major difference is that the good leaders (whose coattails others want to ride on) should be able to distinguish capable subordinates from useless yes-men.

If they can't, they deserve to drown themselves. If they can, they will filter out most of the fakers, and collect a team that can get stuff done in real adversial situations - since a great commander with a sucky team will suffer, and an okay commander who is able to build a great team will get whatever achievements are possible.

I can see the benefit here of keeping people motivated to continually achieve more but it seems based on the assumption that everyone is capable of going all the way to the top.

In the worst case scenario, a large number of people go "up" to the point where they're no longer capable of doing the job they're in and then go "out" after a brief period of doing their job badly.

These people may well have been very competent at their previous level of authority and so the business as a whole loses out.

Additionally companies which state outright this is their policy often have quotas of people who should go "out" which I've seen, in particularly talented groups, lead to an almost random selection of people going out despite the entire group being so close together in ability than no meaningful distinctions can be made.

EDIT: re jonnathanson response below, agree completely that if up can mean a person is performing solidly and achieving good results while improving year on year then such a system can be very beneficial. My criticism is much more focussed on systems where up explicitly means moving through grades, especially where there are attempts to apply quotas to who goes up and who goes out.

"In the worst case scenario, a large number of people go "up" to the point where they're no longer capable of doing the job they're in and then go "out" after a brief period of doing their job badly."

AKA, "The Peter Principle."

http://en.wikipedia.org/wiki/Peter_Principle --

The Peter Principle is a belief that, in an organization where promotion is based on achievement, success, and merit, that organization's members will eventually be promoted beyond their level of ability. The principle is commonly phrased, "Employees tend to rise to their level of incompetence." In more formal parlance, the effect could be stated as: employees tend to be given more authority until they cannot continue to work competently. It was formulated by Laurence J. Peter and Raymond Hull in their 1969 book The Peter Principle, a humorous[1] treatise, which also introduced the "salutary science of hierarchiology".

Yes, but I see no proof that the Peter Principle is any more prevalent in up-or-out organizations than in other types of organizations. PP occurs in every large company.

Up-or-out is supposed to prevent the Peter Principle.

When the PP is active, people "rise to the level of their incompetence", and then stay there indefinitely. In Up-or-out, if you stop rising, then (after some suitable attempts to help you get unstuck) the company starts encouraging you to leave (with increasing vigour). They get the benefit of your knowledge at every level that you can operate at.

I think it depends on how we define "up." I think it's entirely fair to have a culture that encourages up-or-out, wherein "up" may mean professional advancement, or it may simply mean that the person is performing solidly and achieving good results, or improving year over year.

In this case, "up" means improvement more than it necessarily and literally means up the ladder.

I realize this reponse could be interpreted as a bit of a no-true-Scotsman reply, but honestly, it's intended to be a clarification of my original post.

I imagine it works best if there are at least some "up" paths which don't lead into management.

Interesting. What does 'up or out' do with senior engineers who don't want to start managing people? Do they leave the company?

At least at Microsoft, and I assume other primarily tech companies, there are level bands (job titles) above "senior developer" (principal, partner, technical fellow, distinguished engineer) that have nothing to do with management. Generally one can have a full career striving for technical fellow/distinguished engineer without stagnating (though not necessarily achieving it, tis a lofty accomplishment).

I know that HP Labs has a similar arrangement.

Same with IBM.

They go out, obviously. Up or out is only better than the very worst cultures. Given how maddeningly difficult it is to find competent people at any pay grade it seems extremely stupid to chuck everyone out after a while. It also implies a bias towards promoting from within, which is a great way to create cultural stagnation.

I once had a job interview at a small software consultant firm. 30 or 40 employees in 6 offices. They also had a demanding policy, probably not strict 'up or out' like at McKinsey or Deutsche Bank but they do fire people when they don't perform well enough. One of the guys who interviewed me was one of the 2 or 3 highest ranking people there and a technical person.

That was their deal: you start out as Junior Developer and when you are there for 5 or so years, you can decide whether you specialize into technical stuff or people stuff. From phone calls with recruiters I had the impression this is not an unusual model.

The only places I've ever heard of with a strong "up or out" culture are based on professional services.

Some companies have thresholds after which up or out is no longer the case. The logic being, below this level, your seniors are putting more work into you than you are producing (i.e. holding your hand, reviewing your work, generating new work for you to do, etc.). After you pass the threshold where you are a net contributor, you no longer have to go up if you don't want. Not sure how common this practice is.

Well, that's how Jack Welch managed GE back in his days. He made it pretty clear that in order to move up they either became a black belt or move out.

The biggest irony lies in the fact that in most traditional companies managers (people who manage developers) are usually the people who were never smart enough to make it as developers in the first place.

My company does this all the time. Didn't do well enough at the job interview or you're a total bozo and poor at understanding technical concepts/writing code? No problem! They'll appoint you as a project manager and you will get a team of developers to manage. At the same time, the brightest and the best engineers rarely get promoted because they are keeping their heads down and actually getting shit done. And there is little incentive for the company to promote such people because they lose a skilled and productive programmer if they do that (they don't care about anything except for how fast you can crank out code - one of the typical ailments of consulting companies).

It's a very sad state of affairs. Makes me want to quit really.

Yes, and they get to give you lots of work then go home. Meetings and checklists for them. Plus, every now and then they get to explain how to do your job to you. It's kind of weird. I've been doing this for 20 years. I was wondering if anyone else noticed.

I know a huge bank that had problems that every developer they promoted, quit.

It was because their managment positions were so stressful and so communication heavy, that most developers were totally not suited for it, and just plainly quit.

Technical types tend to think that there's not much to the task or process of motivating and managing a team.

The people that promote individuals into management roles are often just as naive. The individuals are expected to develop new skills simply by virtue of having been promoted.

Maybe I'm arguing semantics, but to me project manager != manager. I have run both PM & dev teams, and often PM's are paid far less than dev's. In a lot of cases I wouldn't consider a move from being a dev to a PM to be a promotion in any sense.

A proper Manager who is coaching his staff, performing performance reviews, ensuring the team has all the resources needed to do their jobs as efficiently as possible, protecting the team from unnecessary bullshit meetings/interruptions, etc is a completely different story.

It's a fallacy to believe that good developers should make good managers and vice versa. I've had great managers that haven't written a line of production worthy code in their life, I've had horrible managers that were genius developers. Companies without a technical career path create bad managers because great developers that should go on to be Principle Engineers and Architects have no choice but to get into HR in order to advance their career even if they aren't fit for it.

You'd have to be a good developer who wants to be a good manager, or a good manager who is smart and cares enough about technology to absorb a lot and obsess about the details. I think the implication here is even if you have those traits the opportunity doesn't exist at most companies.

There are people saying this (more or less): leaders can be used in a any field, even a field they don't know.

Being a technical person, I used to doubt this too. But having seen to many bad managers in such a short time, I believe it's true. When you are senior enough, in a small company, you don't need a technical supervisor. You just need someone you can trust, who gives you political backup and who will evaluate you on your results.

The Peter Principle is a belief that, in an organization where promotion is based on achievement, success, and merit, that organization's members will eventually be promoted beyond their level of ability. The principle is commonly phrased, "Employees tend to rise to their level of incompetence." In more formal parlance, the effect could be stated as: employees tend to be given more authority until they cannot continue to work competently. It was formulated by Laurence J. Peter and Raymond Hull in their 1969 book The Peter Principle,


This should be required reading: http://books.google.com/books/about/The_Essential_Drucker.ht...

true, I've experienced that as well. The morons who wrote shitty code, made project managers.

So all it takes to be a manager at your company is to bomb the job interview? I could use a pay raise, which company do you work for?

sometimes gifted devs are horrible managers.

Speaking as a developer I have to say the arrogance in this post is very disturbing. It reeks of someone who has no idea what they're talking about and can't understand the challenges people other than developers face. To think that managers are people who aren't as smart as you are, or are people who couldn't hack it as a developer is ridiculous and naive and arrogant.

If your job is that shitty, and you're that smart and good, quit and find a better job.

And in fact the amount of shit that corporate developers are protected from is phenomenal. Getting shit out of the way of developers is the job of these managers.

Now of course, some companies are better or worse than others, some managers are better or worse than others and so on.

Personally I don't see myself a manager because I lack the social skills. In some days I barely remember to do minor things like sending out an email to my team at the end of the day or ask about the status of some roadblock.

Developers are supposed to be grateful that managers protect them from shit from even dumber and insane managers above them? Nope. Why not just fire those insane managers slinging shit everwhere.

It's not that black and white.

Ofttimes, what looks like meaningless corporate bullshit to a developer looks like valuable fertilizer to some other part of the organization, or to a regulatory body, or to something else that makes the company go. "looks like" phrasing was intentional here.

I was a damned good developer back in the day, and am working on being a good manager (of managers at this point). There is an insane amount of red tape that sprouts up over time in any large assembly of people. Some of it has some positive purpose somewhere; some of it has no evident purpose.

The best managers seek to protect their teams from unnecessary BS, but that doesn't necessarily mean eradicating it from the company. Shielding can be just as effective locally, at a tiny fraction of the cost.

Maybe we are talking about two different things. There's no qualms with stupid requirements, red tape, or regulations. The bullshit that I am talking about are the ethical lapses, the lying, the backstabbing, the disrespect, and the threats. There's no situation where that is legitimately valuable to some other part of the org. Anyone out there who thinks this is necessary or just part of the game needs to do an ethics check.

The parent might be arrogant, but he also happens to be right. A lot of managers are simply incompetent and not that smart.

In my experience, it's usually _not_ the line managers but the people above them. I've left several jobs, but almost always wasn't because of my immediate manager.

Nope. No way. I'm a developer who has worked with a lot of managers on group projects in many different business classes. I have had all sorts of problems in group projects because by and large the managers all want to do the project during work hours while I am coding and testing as fast as possible so I can get home by 8pm. So, I'm going to go ahead and say bullshit to "the challenges people other than developers face." Maybe you can explain the challenges? I can imagine the difficulty in two manager trying to out-bullshit each other. This does not constitute an inherent difficulty in the job, but is a difficulty in living with themselves. If managers are shitty to each other, its not because of the job description, its because they are shitty to other people.

I'm not a manager, I'm an engineer, but I'll speak up for the managers...

The challenge managers have to face is balancing competing priorities. If you're a manager, you have customers/users that you need to please to keep the money rolling in. You have an executive who often has very strong opinions about how to please those users. You have employees that each have their own career goals and interests, which may not necessarily be aligned with yours. You have cross-functional peers who you frequently need to rely on for favors, and yet often speak a totally different language from you. And you somehow have to make all of the above groups happy, or at least not totally pissed off at you, to keep the organization functioning.

I dunno what your job description is like, but mine (as a senior SWE at Google) is "Figure out how to make users happy". If you don't face similar ambiguities in your job description, it's because there's a manager somewhere up the org chart who did all the messy work of listening to what everybody else wanted and somehow harmonized it all into something halfway buildable. If you have a spec you're following, there was somebody out there who wrote it. If you're getting paid, it means somebody out there sold the product, and that usually requires listening to all the customers out there and figuring out what they want in common. None of these tasks do themselves.

That would be great except hat is not he real world. In the real world managers provide no value. Many are bold enough to admit to me that from the start they planned their careers around doing as little real work as possible and are focused only on ladder climbing and getting head count under them. My job description is wide open, I do all phases from conceiving of a project, to selling it to internal users, to coding and testing, to deploying and getting feedback. It's essentially intrapreneurship. I have never met a dev manager that understands software well enough to even begin to help in these regards. The ones that actually tried to organize development simply tried to dumb down the work to something they could understand like reports. As for the org knowing what they want, they want head count and exposure. I I could code these things I would be CEO.

The real world is a really broad place. If your manager doesn't add any value, quit and be CEO. I've done that before and I'll do it again if I find that I'm in a position where being part of an organization subtracts more value than it adds. For the moment, though, I've found that my manager and the rest of my organization adds a bunch of value in very subtle ways that I wouldn't get if I were out in my own startup.

> If your job is that shitty, and you're that smart and good, quit and find a better job.

That's the crux. If you really are that good, it shouldn't be too hard to leverage your skills somewhere better.

"At Google, individual engineers are far more empowered than that. There is a strong internal process for simply changing projects."

That assumes the Hogwarts Hat of random allocation doesn't land you with a stinker from the get-go. And I speak from personal experience that it occasionally does. If I had been able to change projects to something more relevant to my skills, I would still be there.

There have been far too many stories of arbitrary google managers both here and elsewhere to keep putting forth the story that if one goes to google, one can simply change projects if one doesn't like what they're doing.

Just one example from http://www.glassdoor.com/Reviews/Google-Reviews-E9079.htm

"For the most part, Google is held together by duct tape. Management quality is clearly below what's required for a company of this size. In a lot of cases managers are simply too junior and lack people skills."

Your prodigious propagandization of your paymaster is praiseworthy, but you don't need to take michaelochurch seriously to perceive this isn't a perfect picture of paradise.

I like the alliteration! Except that I feel a need to wipe my imaginary spittle from my face... ;-)

>I like the alliteration!

Good! If you really like words and want to get some copy edited you should check out http://www.edithero.com/

>The modern company is a kingdom. Managers are feudal lords. Managers can decide to hire (and fire) employees such that the employee is essentially beholden to that manager. Employment status is analagous to the land serfs worked.


It doesn't just hurt the employees, but the company (kingdom) as a whole. The managers (lords) concern themselves primarily with expanding their departments (fiefdoms), typically at the expense of other managers, rather than working to grow the company or improve the quality of life within it.

This leads to a mentality of collecting more rather than better staff, ass covering rather than innovating and all sorts of other bullshit.

Facebook has an explicit program (hackamonth) to avoid limiting internal mobility - https://www.facebook.com/notes/facebook-engineering/hackamon...

That is the theory at Google. And then there is the practice. Which varies across the organization, and can be influenced by the manager in a lot of ways.

Let's just say, I've heard rumor that my manager was asked to leave not too long after I was. And the circumstances of my leaving were not entirely unconnected.

Serfs occupied a portion of land and owed a portion of their crops to the lord of the manor or their feudal lord. It was slavery in all but name.

The most important point making it like slavery was the fact that serfs couldn't leave their fiefdom.

That's where the analogy to a modern corporation breaks down - employees can quit whenever they want.

That's where the analogy to a modern corporation breaks down - employees can quit whenever they want.

If they like starving, yes. Being subject to Morton's fork doesn't make for a great day.

Software developers are currently in a pretty great place in this economy. Not everyone is. It's pretty important to remember that.

And it's also pretty important to remember there's life outside the US of A, where software developers are in a less rosy place.

Thats not exactly true, and I don't feel it breaks the analogy. Many, many people cannot simply up and leave. Sometimes people are locked in place due to family and lack of alternative employment in the given area.

Sounds like you don't have any ties to where you are and what you do. How is that working out for you? (genuine question)

Well then maybe sharecropping is a better analogy. Similar lack of agency but in theory you could leave.

Here we are still mucking about in the echoes of the late 19th century trying to make these outmoded models work, in education, in politics, in the workplace. There is too much inertia due to power dynamics and due to government control, things won't change until people start proving there are better ways.

Ok, what is the model you are envisioning then? There aren't many other structural models I'm aware of. Are you thinking modern companies should be more like Valve, perhaps, which are very flat instead of hierarchical? This works great for Valve, but they do cherry-pick veterans of their respective trades.

I know the "flat" model is enticing, but I have yet to see an example that handles greenhorns well.

If I had a sure fire management model that was objectively superior and worked in almost all circumstances I wouldn't be talking about the problem I'd be off making money with it or proselytizing.

I have many solid arguments as to why the current system, which really is rather feudal, is broken and could not possibly represent the apex of management systems. I also have a few good ideas about alternate systems. However, that would make for quite too long of a discussion here, so I'll save it for some other time/place.

Nevertheless, I will point out that if there is a solid trend as it relates to the impact of the progression of networking technology and software in general it is that both have a tendency toward disintermediation. And if there is one intermediary who is oh so very ripe for being kicked into the gutter it is certainly the middle manager. How do we get along without him/her? To my ears such a question has the ring of "how will we get along without cholera?"

So, here's some bullet points: greater individual autonomy/responsibility/return (e.g. profit sharing & equity); more peer relationships and fewer superior/insubordinate relationships (though not the absence of such), note carefully that this is not identical to a flatter hierarchy; more freelance-style and partnership relationships (whether across or within corporate boundaries); more reliance on leads instead of managers; more mentor/apprentice style relationships. In general the "employer/employee" relationship being closer to a partnership that both have entered into freely and with respect for the other party with the expectation of mutual benefit resulting rather than a coercive, unequal, and authoritarian bond that employment often imitates today.

What system do you think will work better, assuming we can overcome this inertia?

>Serfs occupied a portion of land and owed a portion of their crops to the lord of the manor or their feudal lord. It was slavery in all but name.

I guess it depends on your definition of slavery. Most serfs had some degree of autonomy and self-determination even if they were forced to pay tribute unfairly.

So that incites us to ask, how is it any different today, when we are also forced to pay a [quite hefty] tribute to the government simply for collecting money? We all have some form of autonomy, but the government has demonstration that only exists so long as we pay tribute and sacrifice the fruits of our labors. Same story as a serf, who would be granted a parcel and expected to pay a tribute to his lord or suffer serious infractions of basic rights to self-determination.

Yea, michaelochurch have talked about "open allocation" before.

So this is apparently less of a thing now, or at least it wasn't an issue for me. I negotiated an offer with Google last week, and I have a very good idea of which team I'm going to. I was given three options based on preferences and "matching my background to teams". Before accepting the offer, I was allowed to narrow this down to a single team.

I don't know if this is common now or only applies to people coming off of the industry track instead of the university track, but it was not at all what I'd been warned to expect.

So far everything about Google has been generally fantastic. I'm hoping it lives up to it once I'm inside.

This is exactly how my allocation went in mid-2010.

Mine as well. Early 2009.

I do suspect it has something to do with your employee bargaining power, which depends both on your past track record and on how many people are being hired relative to staffing needs. Managers bid on Nooglers, draft-style; if many teams are bidding on you, you have a lot of flexibility in where you end up, while if only one team bids you're basically stuck with them. michaelochurch was hired in 2011 IIRC, when Google notoriously overhired, and it could be that many of the other teams were flush with Nooglers and not looking for anyone else.

When I was hired, I had a list of five managers to interview with. During the first two weeks after I started, I talked with each of them and decided where I wanted to be placed. It was made clear to me that if I didn't like any of those five, I would get another list.

Just my experience; I started at the beginning of 2012.

> Serfs occupied a portion of land and owed a portion of their crops to the lord of the manor or their feudal lord. It was slavery in all but name.

Add in the ability to occasionally submit votes that are statistically irrelevant and you've got modern Western democracy.

This is a great post, but my experience with Google is that it doesn't empower individual engineers until they reach the Sr. SWE or Staff SWE levels. There's a Real Googler Line, which seems to be somewhere in the Senior SWE tier. If you're above it, you have independent credibility and you can change projects and as long as you're not a total flake about it, you get enough opportunities that you can find a place where you shine. If you're below the RGL, you get locked out by headcount limitations and your best hope is, after 18 months, to transfer to a slightly less bad project.

What you're discussing is the Credibility Drought. Companies define credibility so that only managers have it, in order to create an artificial scarcity that makes employees easier to control. That's what enables the managerial extortion that forces employees to serve local goals (the manager's own career) rather than the benefit of the company (or the growth of the individual).

Very few companies formally allow a manager to unilaterally fire. That's way too much of an HR/lawsuit risk. Instead, these closed-allocation dinosaur companies define credibility in such a limited way that managers can either support or not support the employee, and then if the person is not supported, that person's credibility is zero and the manager isn't firing that person. "The company" does it, after "careful review" of "objective" performance statistics. On top of this, they set tight headcount limits so that for anyone to get a good project requires a special favor, allowing the company to say "no" and appear consistent on the matter.

Google is aware enough of this problem to allow engineers at above a certain level to acquire independent credibility.

At Staff, you can pull a Yegge (quit your project in public) and be OK. If you're a SWE 3 and you try that, you're fucked.

So Google may be different from the full-on closed-allocation nightmare corporation, but you only if you either (a) start at a senior level, or (b) get on visible, desirable projects when you start, so you can get promotions quickly. The only time it isn't difficult to transfer to something better is immediately after a promotion (and there are some managers who withhold promotions to keep people captive; Google, to its credit, has a system that occasionally overrides managerial objections to promo).

The sad thing is that I don't doubt that Google is better than 95 percent of large corporations its size in terms of internal mobility, individual autonomy, and engineer-centric culture. It might be better than 98%. It's still pretty awful for a large percentage of people who work there, and the fact that it's so much better than most of what else is out there is a damnation of Corporate America, not an endorsement of Google.

I was a Senior Engineer with a manager who talked to me once on the day I joined the team, then forgot I existed for the next 3 months. If I had discreetly transferred without trying to repair this, I think I might have pulled it off.

But instead, I mistakenly emailed him, concerned that he was holding 1:1s with everyone else on the team except for me. He then hastily called a 1:1, apologized for forgetting my existence, and then immediately informed me that I was now behind on his expectations of my productivity.

My friends advised me to go to HR, so I did. Whereupon I found out he had already paid them a visit to inform them of me. At this point, the google immune system geared up to encourage me to leave of my own volition. I tried to get on to other teams. Friends in the company tried to get me onto their teams. These efforts were blocked.

Deciding this was a game not worth playing further, I left a month later when I got a compelling offer elsewhere.

Waste of 4 months IMO - but I also believe that if I had just been allocated to a more relevant team things would have turned out far better.

I don't think I would have let that go for three months. Did you try to contact him earlier? Did you have work in those three months? Were you checking in code?

This. After the first paper-work week, if I had a supervisor who didn't assign work to me, I would seek him out, if only to gauge his expectations.

Work was assigned to me the first day and I'm a very self-motivated independent worker when given a task. That trait had served me well right up to joining Google whereupon it flamed out because I probably put too much time into learning google's tool chain.

At the 3 month meeting, the manager openly admitted that while he managed two teams, he devoted most of his energy to the other one. So in his defense, he was overallocated. His other team was more interesting. But I think he already wanted me gone at that point so that wasn't an option.

What did you do for those 3 months, besides the first few days/weeks?

If you're asking whether I was productive, yes, I was, just not sufficiently so apparently.

My failing was explained to me that since I was a "Senior Engineer(tm)" I was supposed to arrive at google an expert in all their technologies so I could be a successful generalist and finish my starter project (in a brand new unfamiliar field to me) in <2 weeks. Whatever.

In contrast, I reached productivity <48 hours after starting my next gig, which did make use of my skills.

My failing was explained to me that since I was a "Senior Engineer(tm)" I was supposed to arrive at google an expert in all their technologies so I could be a successful generalist and finish my starter project (in a brand new unfamiliar field to me) in <2 weeks.

They make up those expectations after the fact, of course. Rather than have the decency to say, "I just don't like you, and don't want you on my team" your manager had to build an objective-looking "performance" case and it sounds like he was a total twat about it.

No one gets anything serious done in the first 2 weeks, and you're not expected to. That's what Codelabs (which are very good, and I wish more companies paid attention to that) are for.

One thing I disliked about the Google environment was that, because it's so hard to have a real accomplishment in your first year, whether you "succeed" depends on others' assessments (i.e. politics). I prefer to be in an environment where, after 3 weeks, I can reach the "so good they can't ignore you" state.

I like high-productivity environments better because I can prove, in the first month, that I'm actually worth a damn. Political issues always exist, but they're less threatening when you've already proven that you're good at what you do.

So what this implies to me is that the first year at Google is an additional hiring filter to weed out bad cultural fits who got past the previous hiring screen (which selects for walking encyclopedias of Comp Sci and recent Top Coder problems with a smattering of problem solving ability).

So they intentionally remove any element of choice in allocation, and throw people into the hopefully representative ensemble of all hiring teams at Google to test how one mixes with the average ideal spherical Googler. But if one ends up 2 sigma to the left of the mean, one is pretty much hosed. And that would likely have a 2-3% false rejection rate assuming this is a normal distribution and that most Google teams are sane. Not bad actually, but sucks for me.

Except that I don't think such a distribution is normal but more likely vastly oversamples the stinkers due to a twisted form of survivor bias because the stinkers have the highest departure rates, putting them constantly on the prowl for new meat oops I mean Nooglers (my small team lost several people during the short time I was on it and several Nooglers switched teams* hours before they would have started to avoid this allocation - I have a really funny photo of several sets of deflated welcome balloons next to what was supposed to be their desk after they had sat around for a couple weeks).

*The most important thing I learned at Google was that I should have secured my allocation before arriving as a condition of accepting employment. Failing that, one can sidestep the process on the first day if one has a friend on a team that is in need of people if one is insistent enough.

The problem of big companies. At some point they end up with people who suck like your manager. Small companies are much better at keeping their ethos and culture. This isn't to say that small companies are perfect though. It's just easier in small companies to know what you're getting into prior to making the leap.

This describes my son's experience at Google exactly. He is a computer engineer with strong software and chip level design experience. He sought and was offered a hardware design job at Google. When he got there he was given a job writing python scripts to manage hardware, not the same thing at all. When he tried to change jobs, he was told he had to wait 18 months, so he quit.

In all fairness, depending on his age, that's kind of how it goes. Hardware design is big money and long product cycles, you can't really just drop into a company and immediately starting masking out a new processor. Plus, computer engineers are (in my experience) pretty rare; you get a lot of electrical, and a lot of software. So they probably have a glut of coders, and a glut of semiconductor guys, but not a lot of 'bridge' people. If you can carve out a niche doing a bit of both, you become pretty valuable.

This is speaking as a comp eng. student who has gotten very little hands-on hardware experience. I've now worked two years doing pretty much exclusively software; the closest I got to real design was product verification and manufacturing support.

He is the 'bridge' person you speak of. He was only 30 but had about 15 years of professional software development experience. He spent 3 years at a startup developing highly parallel algorithms in C and implementing them in FPGAs resulting in commercial products. He said that in interviewing chip designers for his company that nearly all had no sense of algorithms. He felt that his software experience was a major strength in hardware design.

From what I understood from friends who are Googlers, is that 20% projects on other teams, can be rewarded with a transfer, sometimes sooner than later.

Google is one of the few companies where the 20% is a real thing for most people branch out, on either their own project, or another teams project.

As far as most companies, the side-project with other teams is simply not an option.

If you start at Google at a lower level (SWE 2 or SWE 3) your manager can unilaterally shut you down. If you get a bad "calibration score", which is set quarterly by the manager, peer feedback won't matter. No other team will want you, and you may face a PIP, which ends your career even if it doesn't get you fired.

Thus, your manager decides if you have 20% time or not.

There are good managers at Google who value 20% time and will encourage you to work cross-hierarchically with other teams or on personal side projects, and there are others who are absentee so you can pull that off furtively. If you get a hard-ass with a lot of project-specific ambition, you're not going to get away with 20% time.

Google inadvertently makes it worse by conflating project leadership with people management, which means that your boss is also held responsible for the performance of a specific project. That creates a huge conflict of interest, because the employee might be a better fit for another project, but the manager has to eat a loss on the project where he is.

If a team has direct evidence that you'd be valuable to them (i.e. you've 20%ed effectively on one of their projects), I can't imagine that they weight the calibration score more highly than that. People know what their own eyes tell them.

There's an escalation path if your manager is outright forbidding you from taking 20% time, and the manager can be disciplined by the Powers That Be for that.

Google also doesn't always conflate project leadership with people management (it depends on the team, and the org chart is explicitly setup so that this is not a given). There're pros and cons to both: if you're on a project where your manager is the tech lead, he'll know your work better (which can help you get promoted faster), but it also means that if you disagree with him on the technical direction of the project it can be harmful to your career. Out of my 4-year Google career, I've spent 2.5 years on teams where my manager was directly involved in the project, and 1.5 years basically doing my own thing or on loan to other teams with minimal involvement from my manager. I don't have a clear preference for one or the other, as I've found that my manager was always supportive of me as a person even when his primary responsibility was managing the project, and willing to let me move to another team when I'd outgrown his area of interest.

(It probably helped that I would work like hell to help my manager's project succeed first, and then transfer off once it launched. Most people are more inclined to help you succeed if you help them succeed.)

Has this been getting better or worse over the past couple of years?

Of the folks who I knew when I worked there and have been leaving, it seems to still be an issue. But a number of them were also somewhat off put by the evil/not-evil issues. In those cases they were definitely leaving the company and not the manager.

> What you're discussing is the Credibility Drought. Companies define credibility so that only managers have it, in order to create an artificial scarcity that makes employees easier to control. That's what enables the managerial extortion that forces employees to serve local goals (the manager's own career) rather than the benefit of the company (or the growth of the individual).

Seems what Valve does instead puts credibility on the open market. This makes sense, as that one term, credibility, actually encapsulates a complex panoply of things, and markets are good at regulation even when faced with complexity.

Valve starts you off with some basic credibility. You matter because you work there. You wouldn't have been hired if you weren't already credible. That's how it should be.

American corporatism is based on Original Sin (the so-called "Puritan work ethic"). If you're not "saved" by some rich institution (a job) then you're judged to be a leech and a failure. Most companies take advantage of this by continuing it into Credibility Scarcity-- you're worthless until told otherwise.

> Valve starts you off with some basic credibility. You matter because you work there. You wouldn't have been hired if you weren't already credible. That's how it should be.

I've worked for "startups" that don't do this. You start out as an "idiot." The manager has to look over your shoulder every 30 minutes, and gets worried because you are programming using "blocks." You're dictated to in terms of which libraries you use. All this total micromanagement, yet the manager knows so little about iPhone development, he has no idea what "delegates" are or that they're the most common pattern in the SDK.

I am considering leaving my job for this precise reason. I feel if I worked under anyone else I would enjoy what I am doing but currently it is impossible.

The problem is the guy has no managerial skills. Employee moral across the company is rock bottom. We get tasks day-to-day because he cannot plan ahead. We often drop projects to work on something else, only to drop them and work on what we was originally. Manager never sends final designs or when he does they later change anyway. (These are not tweaks, tweaks are understandable. This is the entire page layout) I could go on...

Why haven't I quit already? I am currently indispensable to the company I work for. I need to support my family. Not sure if I want to risk it on a new job in the current climate. The short term plan is to continue being miserable.

NOTE: I would go around my manager if I could. Unfortunately it is a team of 7 and its this guys company.

>I am currently indispensable to the company I work for.

That was me a few years ago.

I ended up putting up with it for an incredibly stressful 18 months and leaving anyway.

If I could do it all over again, I would have made a stand leveraging my indispensability. Either I succeed and effect change or fail and leave anyway.

>I need to support my family. Not sure if I want to risk it on a new job in the current climate.

Obviously, you'll want to find a new job before you quit, not the other way around. Less obviously, consider the impact of your "rock bottom" morale and apparently dead-end job on your family.

>The short term plan is to continue being miserable.

Short term plans have a way of becoming regrets without a long term plan.

> Less obviously, consider the impact of your "rock bottom" morale and apparently dead-end job on your family.

to add.....

When I was much younger I took my mother out to a movie. It was a comedy and a pretty good one at that (don't remember the name). We got to the parking lot and my mom said "This is the first time I've seen you smile in 6 months". Resumes went out the next day and a few recruiters I knew were called.

You might not notice the cost of a bad job, but the people around you will see the signs. I did love the "concept" of the job I was doing, but it was killing me and looking back, it took a while to actually recover. I knew I was frustrated, but not how far gone.

That's my story too, felt like leaving after a year but ended up staying for 18 months. Even got a decent pay rise, and managed to change things a little, but the enthusiasm faded quickly, it was a dead end.

The day I stepped up and tried to set everything straight was also the day I decided to quit. Fast-forward a few months, I'm earning 2x as much, and working with everything I wanted to.

I too thought I was indispensable, but the company you have in your head can be very different from the managers'.

>I too thought I was indispensable, but the company you have in your head can be very different from the managers'.

This is an important observation.

I'd wager a manager who doesn't recognize the way he/she is allowing if not creating a dysfunctional workplace doesn't recognize how/what makes it work in the first place.

The only thing that's indispensable to shitty managers is their own power/security.

I've heard that line of being indispensable to a company so many times. Turns out that it's not true. They'll find someone to replace you.

It's not even that. It's that they don't care. Most often they care more about power and process than results. It doesn't matter if you're "indispensable" to the company. A company will cut off its own nose to spite its face, and it will relish doing so. Sure, it may mean a huge setback for them, it may cost them millions even, but often they don't care. They'll just hire more people and apply enough effort to continue working.

The one thing that took me a long time to realize is that even when it comes to something like software if you throw enough half-assed labor at a problem there is a reasonable chance that eventually something of significant legitimate value can be created. No, it probably won't be as good as something created by a bunch of geniuses, but it can still end up being "good". When you play the long game or the big game you can afford to rely on half-assedness to work out in the end.

Software engineer job is not different from any other and I can't see any reason why it SHOULD be.

Oh, it's plenty different. First off, software is not one thing. It encompasses more orders of magnitude of difference than almost any other industry. At one end you might have throwaway fart apps or single serving joke websites and at the other end you might have spacecraft avionics or industrial systems control or banking systems, and in the middle there is a multi-dimensional realm of tremendous breadth and volume. Additionally, software construction is by its nature creative. Creating a million or a billion or even a trillion copies of a piece of software is a more or less trivial and heavily automated task. Software isn't like making cars or houses or bridges. When you make a bridge there is a lot of work that goes into design but most of the work is in implementation. In software the implementation (the actual running of the software) is automated, all of the development work and all of the so-called "implementation" work is in truth just design work on finer and finer scales.

The combination of all of these factors makes software a different sort of beast than a lot of other work. Now, as I said, that doesn't mean that you can't still attack it with brute force and obtain results, but software is actually one of the realms where that is one of the least effective strategies.

This is ridiculously arrogant. All of the arguments you make for software engineering being different can be applied to any other engineering discipline. Throwaway fart apps == single-use plate connections or custom fab bolts. Spacecraft avionics == spacecraft structural design. Etc, etc.

Your statement about design vs implementation shows that you're clearly outside of your knowledge space when talking about other disciplines. Depending on bridge span, length, and construction method, the man hours required for design can be much more than those required for construction.

Software is not really all that different from any other type of work. It even shares the trait that people that are part of the software sector think that their sector is somehow inherently different.

sigh Let's call off the angry accusation slinging straw man slap fight and just pencil in on the official forms that we did it, shall we?

I haven't said, nor do I mean to imply, that my dad is better than your dad, err, I mean, that software development is somehow on a higher plane or superior to other work. However, there is something that sets software apart from most other work in that it is almost entirely design work, even "construction" is design work. (Of course, there is often something that sets most genres of work apart from other genres too, every industry has its unique aspects.) A particular engineering task might require more man-hours in design than in construction but that is an edge case, and the ratio is unlikely to be higher than an order of magnitude, the norms still apply. And again, software sees a rather larger range of scale than almost any other industry. The difference in, say, the amount of data handled by a given piece of software can range from a single byte (or even a single bit) up to petabytes or higher (the LHC processes zettabytes of data per year). That's 21 orders of magnitude. The difference between the smallest features in a microchip and the longest superhighways on Earth is only 15 magnitudes, and those are considered to be hugely different industries.

The main point I wanted to get at though was that due to the primacy of design individual talent can often have an outsized impact on overall product quality or capability. You certainly see that in many other disciplines but not necessarily on the same scale. Because, again, it's not terribly rare to have a situation where a piece of software developed by a single developer is just generally better than one developed by a team working at a multi-billion dollar mega-corp. That's the equivalent of some guy building a Mach 10 plane in his garage that runs on solar power. You tend not to see extremes on such magnitudes outside of software.

Indeed, it's even a driving force in the industry, as the idea of being able to build some new or better product from nothing and scale up to a billion dollar company in a matter of years starting from only one or two founders is rather common in software and shockingly uncommon outside of it.

So your major point is that software is unique because it:

1. Spans N orders of magnitude in scale which is M orders of magnitude more than X sector.

2. A single individual can put out superb products while some teams put out mediocre products.

3. The possibility exists for companies to be created with J founders and reach a valuation of K in L years.

Sorry, but none of these are unique to software. They're just the same arguments for anything else with different values for the variables.

Again, your sector is not unique. Last time we thought software was a unique sector lead to the great "paradigm shift" (as Greenspan called it, I believe) of 2000. You might know it better as the dot-com bubble.

They're just the same arguments for anything else with different values for the variables.

That this makes two industries "equivalent" is an even more far-fetched claim than InclinedPlane's.

Being able to earn some money on the internet does not make you any smarter from any other profession. So it's just the internet what makes you feel so special. Good luck software engineering your bilion dollars without it.

I think in many cases people over-estimate their worth. Where I work I am the only real developer. I wrote and maintain all the products.

This makes me pretty indispensable. It also helps that before I arrived the guy in charge of the company had a bad time with at least 3 developers. If there is something I cannot do he tasks me to find someone and manage them so you know...

Obviously, guy could find someone else. Someone else could take the reigns of what I am doing. However transition time and the guys past experience with developers makes this very unlikely.

While I know nothing about you and your skills, this doesn't have to be always that simple. People who are "the only developer" in a company often get detached from the developer community, living in a kind of technology bubble they created. These people always solve the problems "their way", often obsolete, using inferior tools. They can write tons of code, when there's already a tool which does the trick just a google away. Again, I am not talking with you personally in mind, but simply being the sole programmer doesn't make one indispensable.

Please do not believe he is unaware of this situation and is not made nervous by it. Unless he is a fool - which he cannot be so much because he trusts you to get the job done :-)

He operates in a market for lemons, but one day it may be more comfortable for him to risk getting a Lemon Consulting firm than live with the stress of one guy who might leave and take the whole thing down with him.

Plenty of companies have a keystone developer that they don't replace/duplicate.

I think, as a general rule, people overestimate the value of their own skillsets/contributions and underestimate the skillsets/contributions of others. It is probably a Jedi mind trick to make ourselves feel more important/smarter/what have you. Luckily the free market for labor mostly exists (ignoring possibly shady deals between certain large tech companies) and people feeling undervalued can test that theory by shopping their skillset around. I think more people feel undervalued/underappreciated than pursue the "shopping around" angle. There are lots of reasons/excuses as to why, but protecting one's ego probably has a role, acknowledged or not.

Once I was the only "indispensable" developer too. Also under a bad managing owner. When I left I offered to help in time of a crisis. Never heard of him again.

Ask yourself this: do you get paid for the risk of you leaving? And ask yourself this: can your family enjoy you when you feel bad?

I think in many cases people over-estimate their worth. Where I work I am the only real developer. I wrote and maintain all the products.

I learned this lesson the hard way, long ago, in exactly that same situation -- it took two times -- by attempting to use leverage I didn't actually have but believed I did.

I hope most people are less dense than I was (hopefully "was" is the right word there), because no matter what percentage of the work you do or how deep and unique your knowledge of a system is, you can be replaced. It may not be easy or quick, but if you make yourself a nuisance, get on someone's bad side, or any of myriad things in and out of your control, you can and will end up on the chopping block, wondering what just happened.

As an anecdote to disprove that, I know of a number of small businesses that were doing decently that tanked shortly after a key employee resigned. It happens fairly often in small companies, especially in the case of a sales manager who maintains most of the personal relationships with clients.

Exactly; that's happened with me at 3-4 companies where bad management prompted me to leave and they died ugly deaths not too long after.

If I leave my company they would simply have to drop the system I basically made on my own.

Not saying it cannot be done, but it would lose them a ton of money. Yep, it's a double-edge sword because it puts a non-trivial amount of pressure over me. Even if they found someone with the rare combination of skills required, it would set them back years in the most optimistic scenario.

So yeah, "indispensable" people do exist. In the sense that you can lose big by parting ways with some people and not effectively replace them. Obviously life would go on, eh.

Poor managers allow individual employees to become indispensable.

It can work both ways. A brilliant employee who is hard to replace can add a lot of value to a company. If you insist on creating a process where developers are replaceable cogs in a machine the output you get will look like something that came out of said machine.

Managers should encourage employees to become highly valuable and at the same time manage the risk of those employees leaving some day - preferably mostly by creating the right environment for those employees to flourish.

what this means really is that there isn't a lot of collaboration and communication between employees. If one person holds instutionalized knowledge that isn't written down in a wiki or something, then they, or their manager is not doing their job right.

I don't agree with my boss a lot of time. Recently he brought up the concern that "what if" something happened to me? He has a solid concern, I told him that it would be and is wise to have another developer on par with my knowledge and skill set. He said he doesn't want me to leave (sometimes I question that, because I'm not his deisred "yes" man). I've been on the fence for a long time about whether to leave or not, because of him. I enjoy most everyone else and the product we build/sell and company. After thinking about this more I realized if we do hire someone to cover me while on vacation or if I have an accident... the social norm/aspect/idea of duty and obligation to help and support my fellow co-workers would be lighted on my shoulders... making it easier for me to leave!

Surely that does happen but it wasn't my case.

The option was basically not doing it. Since I made up for my cost it wasn't a bad idea I guess. Now if I get struck by lightning then they will lose future earnings but that's that. It's a big company and other parts of the company would continue just fine.

Not all resources are exchangeable, esp. when some niche research is involved.

The trick is to make people think you are indispensable.

I think more than often the real challenge is the knowledge, not the skills. IIRC there was a post linked HN about that problem, written by GitHub or Stripe maybe ?

Many times there exists the feeling that quitting your job makes you a traitor. Making employees feel indispensable feeds into the traitor concept, making them less inclined to leave. We hired a manager at one of my previous jobs who during a meeting literally told us to never mention any former employees!

Contracting, though I've never done it, sounds like a much healthier relationship between employer and employee. It does have it's own negative aspects though. I wish full-time jobs weren't such adversarial relationships where you're either with us or you're against us, if you quit.

I could put a monkey in someone's chair with the same job responsibilities. Doesn't mean I've replaced that person; I've simply found a way to occupy their space and assign their tasks.

I think people mean that in the current environment and configuration of the team, they are indispensable. And that of course, can be true. The team would not be able to function without them.

Of course a company can always find another fool to replace them.

Many smaller businesses work that way. They have a core group of often arrogant and unskilled old-timers that for one reason or another, cannot and will not be fired. I've seen this more than once, with clients and companies I've worked for.

The company cycles through talented new employees every other year. Once these employees are burnt out and move on to greener pastures, the company will find a new sucker to fill in their shoes. Rinse and repeat.

Usually it's just a case of understaffing and not being prepared for an employee leaving on short notice.

Ya, but at what cost?

I think you've outlined just how undervalued managerial skills actually are. I have seen many that have claimed that they can take up a manager's position yet can barely manage relationships with their friends.

I think that relationship skills are key to being a manager, in addition to all the other planning etc.

I'm not sure how approachable your manager is but it sounds like he needs help from you to bring moral up. A leader does not necessarily have to be a manager but of course, with everything, do at your own discretion.

I have tried. I set up project management software to try to get the team on the same page. Team liked it, manager scrapped it after 3 weeks.

I sent him a feature development blueprint which was well received but ignored.

Suggested he gave people more responsibilities, he did but then didn't like not being the conduit in which everything flowed so took all the responsibilities back.

Spent a day with him writing development goals for the next month. General goals for 3/6 months. This would get everyone on the page and stop priority switching. Trouble is he never stopped editing the document. Instead it just became a documented expression of his managerial style.

One day I got pissed off and wrote a pissy but constructive email about his managerial style. Again, fairly well received. He left alone for a week to complete the task I was on. Then everything went back to normal with random daily requests and project swapping.

I care for my work and want the company to succeed. I haven't been silent passenger :)

I definitely commend you for taking the effort :) If I had a company, I would love to have you on my side to help me point out my flaws.

Your manager needs a reality check to realize that while he's good at starting a company, he can't really manage it.

But as you've just said, it's all been wasted effort.

Sounds like the situation I found myself in. I stuck around because I felt I was indispensable and I felt a sense of loyalty. In the end, I got fired because the boss wanted to "change things up" since he wasn't getting things done as quickly as he wanted (mostly his fault for changing requirements). It took me less than 2 weeks to find a new job. There is no reason that you can't start looking for a new job while still working for your current company.

While I am not sure of your locale, here in New York the job market is booming with a great pick of companies to work for. Even then, you can always look without quitting beforehand. If a company is interested in you, they will be happy to interview you on off hours.

Well I was going to ask if you couldn't go over the manager, but by the time i clicked reply you'd added:

> its this guys company.

well… can't you try to find an other job for that? While working for the company? If he's the owner, I don't see why you'd care for being indispensable, it's not a case of an asshole manager in a great company it's a broken company.

Also, you probably aren't indispensable.

> well… can't you try to find an other job for that? While working for the company? If he's the owner, I don't see why you'd care for being indispensable, it's not a case of an asshole manager in a great company it's a broken company.

I am not leaving for 3 reasons.

1. I support my family with two young children. Partner doesn't work. As depressing as the job is I know it is secure for at least the next year if I want it.

2. I am concerned about the duration of any new job I take, especially in the current climate. I have friends who have lost their houses. If things were a bit rosier I would have gone already.

3. I am working on my own little side project which I hope to nurture into a full-time income. Trouble is work gets me so down I can barely look at a computer at the end of the day to push it along further.

> Also, you probably aren't indispensable.

I am currently essential to the smooth running of the companies products and systems. In my opinion that is as close as anyone can get to indispensable.

  > Trouble is work gets me so down I can barely look at a 
  computer at the end of the day to push it along further.
Please do not take this the wrong way (esp with my other post) but it sounds like work might not be the cause of you feeling down at the end of the day - have you considered that you may be suffering from a depression. Especially in SAD-central January.

I have been there, maybe I still am, but its just a thought and it may well be worth opening up to your doctor.

And remember free, over the Internet, psychological advice is worth every penny :-)

Can't speak for the GP, but this time last year I felt the same way about my situation and had for multiple years. Last April I finally got out of that job and my disposition changed noticeably. Multiple people noted such, and my desire to work on my side projects returned. I still have other underlying issues I am addressing, but the job was an acute trigger.

The economy isn't that bad for techies. If you're unhappy, find a new job and leave. Don't wait for some idealized future where your side project pays out. You're not indispensable.

It sounds like you're living in fear. Especially now, the job market in tech is booming.

I am concerned about the duration of any new job I take, especially in the current climate. I have friends who have lost their houses. If things were a bit rosier I would have gone already.

What do your friends do and where do you live? Even in a rather non-tech town I'm constantly getting calls. If I was willing to move to one of the cities within a 5 hour radius the calls go up even more. Techies who know wtf they are doing are in high demand. What I did when I left my previous stable, but soul crushing job 14 months ago was remember I had a stable job and I had time to look and pick and chose.

Nothing wrong with sending your resume around. The order of execution matters a lot. Get hired for a new job, then quit your current one.

In the worst case scenario, you still have your current job.

As others have pointed out there are a lot of excuses in this post and I don't really understand. The line about being indispensable has been address so I'll focus on "looking in this job climate".

Looking is fairly inexpensive and near risk free. Why wouldn't you just be casually looking until you found the right job?

I have a speech impediment, fairly low confidence and generally interview fairly badly. The thought of being dropped into a completely new work environment makes me a bit anxious. I worry that I will simply exchange my current set of problems for a new set of problems.

I am a quiet guy. I took the job because of the fairly low social requirements. I had low confidence with my speech at the time... I find it difficult to express the problem. I worry that a new job - if it has different social requirements - will be a shock to the system and I don't feel I have the support around to help me cope with that.

I want, probably need, a new job. I just have no idea about how to go about it to be honest and that puts me off looking.

I'll probably get flack for this, but have you considered seeing someone about the social anxiety? If you feel like it's limiting your career options, it might be worth seeing a counsellor just to discuss some strategies you can use. I know us developers can get hung up on independent research and solving our own problems, but some problems can be worked out a lot easier with another person, rather than googling.

HN gives a weird perspective on what employers expect of developers. I know lots of places where devs aren't expected to be social/growth hacking hustlers who have met the president, etc. Most places just want competent developers, and they're willing to accomodate a lot of the typical geek social anxiety.

All this to say, I know it's a scary prospect, but you can change your situation if you try. Whether that's getting some interviews, or seeing someone about your anxiety. Feel free to email me if you want to talk.

Yeah.. and I totally feel for this person. I see now it's not actually low cost at all for them. Working on social anxiety will help not just with job finding but also at making your next job fit with yourself much better.

Good luck.

Also you're a whiner.

"Graveyards are filled with indispensable men".

How about confronting the guy?

This is the one thing so many people fail to do, even though they don't want to leave. People don't suddenly stop being decent human beings incapable of change when they become managers or owners.

I've confronted people "above" me with their failures and have been confronted by people "below" me with mine. It hurts for a minute, but very rarely does that lead to escalation, and more often then not it at the very least a genuine attempt to change.

You will enjoy Quit[1] then!

I really suggest listening to (at least) episode 1 [2]

[1]: http://5by5.tv/quit

[2]: http://5by5.tv/quit/1

I could have written the first two paragraphs... Actually I also would have quitted already, but my situation is also uncomfortable for personal reasons.

Anyway, reading Dilbert.com helps ;)

Problem for me wasn't so much my manager. He did a good job, as far as he could. It was higher than him. But the last job I left was due to management.

Anecdotally, I spent 2 years at Microsoft (MSN division). I loved my manager to death, and telling him I was leaving felt kind of like breaking up with a long-term girlfriend. But MSN was a supremely depressing place to work because there was a palpable sense that nothing we did mattered, and Microsoft was simply running out the clock on those [hundreds of millions] of people who haven't figured out how to change their browser homepage away from msn.com. I left the company, not the person.

So while the lesson of this post -- that managing is important and a good manager can greatly increase employee retention -- is well taken, the headline is certainly overstated.

I think you are a lucky outlier. I've left all my jobs due to poor managers. If my manager doesn't even have the basic 'shit sandwhich' approach to telling me that I suck, then I tend to start looking for another job.

Also, broken promises in interviews - yeah, monk.e.boy, work here for a year and you'll be the head of your very own dev team. I've fallen for that one about 4 times. Then I leave and they ask 'Why-oh-why?' And I say 'Remember in my interview that you said X Y and Z and none of them happened?'

I think he may not be an outlier for Microsoft.

I've worked with a few people from Redmond who left not because of a crappy manager or an unpleasant team, but because their projects kept getting cancelled. It's hard to feel like you're working on something important if all of it gets scrapped before shipping two or three times in a row. Especially if this happens not due to any issue with the project, but due to political happenings miles above your head.

At least, this is what I've been told. I've never worked for them myself.

It's quite simple: believe it when you see it, no matter who it is making you promises. The bigger the promise, the more quietly skeptical you must be.

Those people filling you with hope may genuinely want to make something happen, or may be cynically telling you what you want to hear. Either way, their words don't mean a thing until they've made them fact.

Ideally your manager would leave, and take you along to the new company. Such situations do exist --- and they're immensely valuable, when you hire a manager to hire his team. Elite CEOs often work like this - they have a "legal guy", a cohort of CxOs, etc. who they bring along when hired.

My thoughts exactly. A good manager can make a difficult company bearable, and vice versa.

> But MSN was a supremely depressing place to work because there was a palpable sense that nothing we did mattered, and Microsoft was simply running out the clock on those [hundreds of millions] of people who haven't figured out how to change their browser homepage away from msn.com.

I worked for a company that did content creation for MSN. The amount of pageviews on MSN sounds daunting, but the ad revenue was not on par with the pageviews.

I spent 5 years as a full time consultant building 'Human Capital Management' software for enterprise companies. I learned many things about enterprise dynamics in those 5 years, but my biggest takeaway analytically is that performance management is backwards. The people actually doing the work are graded by their managers, and in very few cases are managers formally reviewed by their employees. I can't speak for small companies, but enterprises would do much better if the employees had a formal process to get a manager on some sort of performance track - without the fear of going above their head in an informal process.

I think regularly scheduled (annual? bi-annual?) skip-level meetings would be a good approach to this. A skip-level meeting is one where the employee meets with his boss's boss.

BTW, the skip-level concept is something I gleaned from the Manager Tools podcast. I highly recommend it for anyone interested in learning how to manage better (or even, just, understand organizational behavior).


Semco in Brazil does (or used to) performance reviews of management by peers and subordinates. I found the book wrote by the company's "CEO"/owner fascinating: "Maverick: The Success Story Behind the World's Most Unusual Workplace", not sure why I don't see it mentioned often in HN/startup sites.

I like the concept of putting managers on some sort of performance track. That is an interesting idea. I wonder what organizations would look like if this was allowed to happen.

The reality is that managers are performance managed, just what their teams think isn't normally one of the metrics because many organisations by and large don't care that much.

Speaking as a manager you'd be surprised (actually scrub that, you wouldn't) how often when I raise concerns the team has the instruction comes back "screw what the team thinks or wants, just do X" (where X flies in the face of what the team want and best practice but supports what the screaming customer and short term revenue demands).

Organisations that genuinely care about the staff I don't think would change much, those who don't won't ever do it so it's kind of moot.

I imagine that the org structure would flatten out a bit, and the stereotypical 'office space' managers would be shaking in their boots. The employees of these organisations would feel empowered and generally be happier - but I won't speculate on whether that would improve productivity for the company (though I have seen research that says it would).

>I wonder what organizations would look like if this was allowed to happen.

Probably microscopic shitstorms, not large ones because only a minority is affected. But in the long run it would probably change everything in organizations with management problems. I think hiring policies would also change a lot.

How would you handle employee review in such a case? Managers could no longer review employees, it would cause too much gaming the system in either retaliatory or you scratch my back I'll scratch yours sort of rigging. Not that I disagree with you.

I would do periodic organization culture assessments by an outside and professional firm. Things like, who is respected, who is hated, who is consider incapable, who people enjoy working with. etc.

As a consultant I worked for several large IT organizations, and I got to see a lot of very toxic people. Some were really high up, some middle managers. They were assholes with everybody but I bet they were very nice to their own bosses, and worked very hard at masking their incompetence. Those people can really screw the organizational culture.

In my opinion the reviewing needs to be led and executed by HR. (Or by a manager that is at least one level higher - but forget that, those folks don't have time anyway)

That HR doesn't understand what you are doing is a bad excuse, depending on the job you might be the only person knowing exactly what you are doing. Anyway, I feel like the manager doing the review is absolutely unfair - at least not in a sufficiently large organization.

>it would cause too much gaming the system in either retaliatory

This is already the case. When your manager does the review, your review is limited by the manager.

Are you of the opinion that there is an acceptable level of gaming the system today?

You might be interested in this similar concept:


Do note, that most big companies claiming they do 360 degree feedback don't. It is much like a lot of companies claiming they do "agile".

I really like this idea, the peer review system in valve is probably the closest to the best system I have heard of.

I've left two organisations (BBC and Sony) and neither time did I have any problem with my direct manager in fact in both cases I liked them although I did have a lack of faith the top management and the direction of at least my area of the organisation.

In the BBC case (amongst other issues) my department was earmarked to be moved to Manchester (about 200 miles away) in about 4 years. I was clear (for family reasons) that I wouldn't be moving so staying would have felt like a personal dead end to me (although later the BBC's plan changed and much of the department moved into London instead which might have been OK but the lack of thought through initial decision was a really bad sign about the senior management).

At Sony it was a general lack of faith that the management had enough capability that Sony could become a profitable, viable, mass market electronics company again. That made me happy to leave to see what I could do on my own and be home to take and collect my son from school.

Odd... I've never even worked at any one company for 2 years, so... making work plans based on what someone decides will probably happen in 4 years is simply incomprehensible to me.

The few companies I've worked at have taught me that for the most part, companies can't do much real planning beyond 6 mos to a year at most - the stuff we considered important in 2006 was often irrelevant by 2007 because of changes in the market conditions, competition, etc. Planning out moves that far ahead is probably necessary in some situations, but I've seen enough of those 'long term plans' have to change anyway that I don't actually believe many of them.

Agreed. I feel like it's more of an exercise to have some sort of vision but in reality, it's really difficult to predict what the environment will be like in 4 years.

Looking at what I have learnt just 2 years ago, some of it is already starting to get irrelevant!

Fair point but it was an R&D environment with a lot of accumulated experience and slightly slow moving and in some ways I was ready for a change anyway wanting to work more directly on products that reach consumers hands. The way the change plan was announced/managed also led me to conclude the overall BBC organisation didn't value the R&D function in general and the lack of care from the top was a factor in me departing.

I agree that employees might leave managers.

But I disagree that people don't leave companies.

First, there are some companies that kinda act on their own, they are very old, and people just obey tradition and old rules and policies. This sometimes the managers can fight hard against, and several will fail anyway.

Sometimes, the company is in a field that make the employee leave, I know for example many IT people that after they realised how banks operate, they felt bad about it and quit.

Sometimes the company itself is having problems, like being sued, or going bankrupt...

So no, sometimes the fault is of the company.

But sometimes.

Asshat managers can make people go away too.

I agree. I've left sometimes for bad managers, sometimes for bad company. Oh, and once it was both. Honestly, it was so sweet when the guy asked what they could do to keep me and I answered "don't bother" with a giant smile.

Very good managers might shine in a bad environment and very bad ones disrupt a good environment. Most though just reflect the organisational culture.

Exactly, and it is very hard sometimes to deviate from that culture, it requires exceptional individuals.

Unfortunately it is seemly easier to be excepcional toward the bad than toward the good.

When my dad left one of his previous jobs, in which he was a manager of about 10-15 people; 3 of his team quit within the week. One of them told him that he was the best manager he'd ever worked under, and that he couldn't face working in that company with anyone else.

If I ever end up in a management position, that's the sort of manager I want to be.

Wow...what aspect of your dad's management attributed to this?

As far as I know he's very fair; he shared work out between himself and others evenly, trusted them to do the work, and made sure everyone was doing their share. He always tried to shield his team from the managerial crap from above. He also never got involved in office politics, and is generally quiet and softly spoken (I differ a little from him there).

I think a lot of people resent managers because they seem to do less of the actual work than those they manage. My dad always works hard at whatever he does, and he expected the same of his team. Now he's retired, part of me really wants to try doing some projects with him. He has a real interest in building web apps that I'd love to collaborate on.

This article unfortunately resonates on a personal level. This is why I believe I enjoy consulting so much. On a short term basis I can put up with ignorance, credit taking, silent treatment etc (All the qualities respondents mentioned in the survey). For a long term career I'm not sure I could last.

I'm curious if anyone has any stories of how they overcame a Manager that was not their Champion? I have been thinking about this a lot. In my short time at large corporations it seems you really need someone on your side to move up the ladder a bit.

Yeah, but companies pay mortgages, not managers.

In other words, I could be working for the most awesome, charismatic manager in the world but if I'm being paid significantly below Market Rate, I'd still leave.

I offer a corollary, "Employees follow leaders, not managers."

At one time I considered leaving a company I believed strongly in, due to an immediate manager with which I didn't work well. However, I looked higher in the organization to the leader(ship) I believed in and decided to stay. I'm glad I did, because the management problem rectified itself soon enough and now I follow good leaders and learn from a great mentor.

I think there is a tidal change in software at the moment - imagine the Venn diagram of remote working technologies, continuous integration technologies and a willingness to shed middle manager white collar jobs like never before.

As we can enable people to work from home, because we can see the code they wrote today up and working on the CI server, we can do away with needing a boss to telll them what to do and watch if they do it - in fact we can pass the autonomy many bosses have down the line - and I hope see a world where the developer says - I have done this cool thing and it has improved our bottom line because I measured this change.

A culture of Continuous Integration, testing changes for business KPIs allows us to let go of the middle rank of supervision, and allows us to change the working conditions now the supervision is unnecessary

For me the best solution is to stay small - keep the organisation under the dunbar number. That way a competant CEO can manage the politics personally, and guide the culture effectively.

But if you are going to grow, you need one of these proxy solutions.

To me there are two outstanding solutions:

1. Free Labour Market 2. "add or out"

1. Google-like - have projects and allow engineers to move around to join different projects, and adjust via funding. THis is trying to create an internal job market, and may or may not be effective but its a response to Dunbars number problem.

2. "add or out" - add measurable value, or the worst performing 10% leave. This forces a culture of testing and measuring value, and whilst it is subject to being gamed, it might be workable.

The world would be a very different place if the government did not provide corporate protection to any organization with more than 150 employees (Dunbar number).

Is (1) what happens at Google? I always thought they used forced allocation as opposed to Valve's open allocation.

Please, correct me if I'm wrong.

I think a lot of people at Microsoft would disagree about #2's efficacy...

I've had fantastic managers at terrible companies. In each case, I left because of the company, not because of the manager.

Yeh this doesn't apply to all situations. What made the company terrible?

Really ineffective performance measurement standards and incentives. When there is no reward for going above and beyond or penalty for simply coasting by, you're essentially creating a haven for shitty employees.

Best way to handle this? Get rid of management. Flat hierarchy. Just to make sure to hire really smart engineers. Code it, test it, ship it. If two forces opposite each other, put it in a hackathon and gain votes.

Do you think there might be practical issues that you're not considering, or don't have exposure to, which might explain why such a vanishing percentage of companies work the way you're saying is obvious? Is it because no-one else is smart enough to have thought of this?

Holy fuck that is an arrogant comment.

Yeah, non-tech companies who produce actual products/services can't really do that, but then they are also not really that relevant since nobody here works for them (outside of IT departments, which could be run as suggested).

No the real reason for almost any stupid thing done in corporate environments is politics. Everybody is a peer and results only environments threaten those who have accumulated power under the old system and who couldn't cut in the new system -- which is basically all managers.

So of course this only happens when somebody with enough political capital to institute it does so -- typically the owner.

Add to that that it is extremely unorthodox and that very few people have previous exposure to systems like that.

And you get the few companies that do this, and do well by it.

Well thank you good sir!

There multiple companies that do flat hierarchies. Most famous one is Valve. You got an interesting project, try convincing others to join you.

If the manager does not provide direction, ask for it. If they still do not provide direction, set your own. The grass always looks greener on the other side. Sometimes, you are the problem, not the manager.

Reminds me of the story about the traveler and the new city. He left because he thought the people there were horrible. Upon arriving at the gate of the new city, he asked a man sitting by the gate, "How are the people here in this city?" To which the sitting man replied, "How were they in the city you came from?" "Oh... they were horrible, mean people."

"You'll find them the same here."

On the day I put in my notice for my last job I found out that my immediate manager had put in his notice as well the day before, much for the same reasons I did. I liked working for the guy so quitting felt bad. Basically choices made by upper management made the working environment not so good and we had decided to move on. Turns out we weren't the only ones, within three weeks five out of six of the web team left and gutted the department.

Nice to see this discussion on HN. Back in early 2000, when I worked at Walmart's home office in Bentonville, we had a speaker come and talk to ISD about this exact topic. That was the main line that stuck with me, "Employees leave managers, not companies". It's probably not the case 100% of the time for causing the loss of an employee, but having a good manager makes all the world of a difference in an employee's happiness.

I had an MBA roommate once and frequently read her books on management culture. I've never actually seen what was used in those books put into practice, but my experience is relatively small (once a manager).

The books talked about the Organizational Cultural Assessment Index (OCAI) and a manager capabilities assessment test (cannot remember the name). Anyone out there used these?

These seemed like reasonable, standard approaches to improving the workplace.

Things like OCAI really don't work that well in practice. The main benefit you get from them is actually asking the questions, not in the results of the 'test' or anything like that. People (and organizational culture) is too diverse and complex to understand with a few simple charts. Beware snake oil salesmen trying to sell you quick and easy 'fixes' for people or culture. Always.

Culture is incredibly hard to change once it is engrained, and is going to take real work and real sacrifice, not simple questionnaires. You should look at changing company culture in the same way as looking as getting a smoker to stop smoking. It's not as easy as 'presenting an argument'.

Yes, culture change is hard.

The OCAI is a tool, like the Myers-Briggs. The book I read [1] treated it as a start for diagnosing your organizational culture, then provided a framework for accomplishing cultural change. I believe it's extraordinarily dangerous to approach (organizational) change without treating it as a process with defined goals.

BTW, I am a former smoker, and quitting was pretty hard. I'd chalk that up to changing my environment (I stopped hanging out with smokers).

[1] http://www.amazon.com/Diagnosing-Changing-Organizational-Cul...

I've never left a company because of my managers, in fact my managers were almost always one of the reasons that I stayed as long as I did. The true reasons, at least in my case, for leaving was always the lack of freedom to make my own decisions and the companies' support for "non project related" work. In fact, my manager did as much as he could to support my endeavors, everything within his realm of power at least.

This issue stems, in my experience, from the top of an individual department or location (if it's a franchise). The top level management in large companies couldn't possibly supervise all their department managers at the same time. So things fly by under the radar that shouldn't because they don't have stringent enough criteria for employee satisfaction and manager competency.

I recall this happening when I used to work at P.F. Chang's (the restaurant chain).

We had a general manager who was absolutely loathsome to work with. We frequently ran out of the kinds of food you'd be embarrassed to lack at a Chinese restaurant (read: white and brown rice, lettuce, etc). However, he had a stellar reputation and history with "corporate" and had even won awards within the company.

The reasons this happened were twofold: 1. he was the general manager, and in the eyes of corporate he was just saving money (they never saw the restaurant descend into chaos and dysfunction due to lack of ingredients), and 2. he was honestly kind of a dick. Unless you were above him on the pay scale he would respond to suggestions with, "I'll take that under advisement."

There was a book in the late 1990's, "First Break All the Rules: What the world's greatest managers do differently" which was the write-up of a Gallup study about manager effectiveness. One of its conclusions is the point made in this article almost verbatim, that people leave their managers not their jobs or companies. One of the most powerful sections for the book for me was the opening chapter where they explain their assessment methodology. They compiled it down to a catalog of 12 questions and they found that if these questions were answered positively it correlated with high employee performance, good financial results, good retention, etc. The rest of the book dives into more detail on the reasons for this, one being that each employee's talent is different and managers should try to align talents with business need, focusing on employee strengths rather than weaknesses.

Here's the Amazon link: http://www.amazon.com/First-Break-All-Rules-Differently/dp/0...

According to this meta-analysis, employees dont leave managers nor do they leave companies.

They leave (maybe) because of the job.

Estimated true score correlation Job Fit - Tenure: 0.18 Company Fit - Tenure: 0.03 Group Fit - Tenure: 0.06 Supervisor Fit - Tenure: 0.09


Seems like there are a lot of war stories on this thread. I disagree with the article based on my personal statistics. When I have decided to move on, in all but one case it has been that either we weren't shipping or the overall product path got stale (beyond the control of day to day engineers).

I like working on things and I like working on things people use. If we aren't shipping, I have to ask why. Periods of development are certainly reasonable but at the end of the day you have to ship.

Where I have moved on due to management? An alpha presence who treated everyone under him as a contractor, yet we weren't hourly, and we weren't compensated for following up on inane decisions. I ended up stepping up, guiding two mis-managed resources, and pushing back on some very dumb decisions (a few were backed by the CTO). However, at the end of the day, when I stepped back anded look at the energy I put in and what I was getting out, it was time to leave.

Decisions to leave are complex.

Very timely read for me. I work in a successful company with lots of challenges and room for expansion, I am a key member of the team and work very long hours (which would be better spent on my own side project).

My current manager has done all of the listed reasons-for-leaving in the article at one point or another - I'm not the only one this happens to; it happens to all who work with him, however I'm the only one who has to report directly to him.

It's a sad situation because the guy is a good guy, he's just difficult to work with and as a result I'm currently looking at my options - if I can help it, I would prefer to stay at the company.

I understand it can be difficult for a manager to be direct with their team, but it's something I know a lot of good people appreciate - honest, direct feedback. You don't want to feel like you're being "handled" or used as a crutch for the manager's own self-actualisation. It's the whole golden-goose scenario - you don't want to kill it.

edit: typos :)

I would not wish a petty/spiteful manager on anyone. I was in a similar situation in my last company: personal problems between my manager and I forced my departure.

In my situation the terrible fact was that my manager's inability to separate his personal and professional life caused the top four of my hierarchy of needs to be threatened (it's hard to be creative and solve problems when you're in a very shitty situation).

At the very end of my tenure, instead of talking about and trying to resolve our personal differences, he chose to go hyper-managerial on me (in manner and communication), making it clear that this was how my day-to-day was going to be from then on.

I loved working with my coworkers and almost everything else about working there, but I found it no longer mattered when I sat next to someone who will only communicate with me in writing with HR cc'd.

There is one thing that is overlooked here. There is as much pathology at the managerial level as is at the subordinate level. We can all say we have shitty bosses. Lets face it, there are shitty workers among us too.

It is easy to complain about managers, but "craving credit" and "silent treatment" happen asymmetrically because the average worker is an order of magnitude different than his cube mate.

Going from a concrete project/goal focused position with expectations to managing those people is a much harder proposition.

I hated managing people. As a manager, you expect the same things from your crew as you would yourself. Instead you hear every excuse, tragedy and jealous rant for attention, rather than just getting the work done.

You try to "nurture" and "empathize" but in the end, workers run the whole gamut from narcissist to kaamchor to subservient drone.

How far up the chain do you have to go before managers become come companies? At a certain point a company is defined by its management, just as to consumers a company is defined by its products. Anecdotally I have never quit a job primarily because of my direct manager.

This has been true of almost every single company I've ever worked for. It's also worth noting that Companies are reflective of the management constituency because they control the levers; bad managers usually mean bad companies.

When your company is small, your manager practically is your company. I'm a junior developer at a rather dysfunctional small company with really shoddy engineering standards. Here, due to the small number of employees, the manager and senior engineer practically are the company. Our senior dev has a cracker jack box cs degree, and has been stuck in his own bubble for the past decade writing horrible code. I also found out my company was sued by a customer 10 years ago because they thought our products and services suck. Good times.

At my former place of employment -- I won't bore you with the "consolidation" memo and the unannounced reshuffling of titles and the change to generic job descriptions in the name of "flexibility." After the reorganization, I had to work for a smug, platitudinous, self-important, patronizing, repulsive know-nothing. I left within a couple months of the reorganization. In just about every case I've left jobs because I detested my boss. I tend to dislike bosses in general, unless they are exceptionally intelligent.

From the article:-

"The key to being able to keep the good employees is not so much the salary you offer them or even the actual work, it is more about how you manage them and how they feel working under you as their manager. "

Personally I don't think there is a key, instead it's a case of all of the above. You can't keep an underpaid employee happy. You can't keep a bored employee happy. You can't keep an employee happy when you don't treat them well. I've left companies for all 3 of these reasons, it only takes one reason.

I had exactly this issue at a well known British telecommunications company, I had a personality clash with my (newly promoted) manager and leaving was impossible because the manager did not want to see a diminished headcount. I manouevered myself out by working almost all of my time on some other manager's project and it got to the point where the argument that I may as well report to, and be appraised by this other manager was unarguable.

Personally, I have observed this becoming more of an issue related to the times that we live in. Let's face it, America has been so ingrained with the survival of the fittest mentality for so long that finally it is sinking in.

Until people start valuing others more in society I do not feel that this will change. Behaviors flow out of beliefs. When the beliefs change then people change. Loving our neighbor as ourself is not a cherished value right now.

This article sounds like a recap of Hertzberg's Two-Factor theory which is basically the application of Maslow's hierarchy of needs to the corporate world.

See: http://www.businessballs.com/herzbergmotivationdiagram.pdf See: http://en.wikipedia.org/wiki/Two-factor_theory

That was a great article. One issue that came to mind is how to interview for these skills when hiring managers. The more I think about this, the more I realize this is not something you can truly screen for during an interview. Reference checks are important, but they will have to be more comprehensive and less "self-selected" referrals (which would almost be very positive about a given candidate).

I'm sure that this happens a lot, but it isn't my experience.

I lost my first job when 2/3 of the company way laid off.

I left my second job for manangerial reasons, but that was more that my position was an experiment and when the manager who'd created it left the person who took over didn't know how to manage me.

The company after that I left because we were bought out and I wouldn't sign the new, draconian NDA.

A (good) manager's primary tasks are: 1) Make sure your team knows what to do and has what they need to do it. 2) Be a buffer between them and anything that distracts them from #1. 3) Be a resource to help them develop. All 3 require good communication.

Every job I've quit has ultimately been because of a deficiency in one of those 3 things that led to conflict.

I'm sure this is true, but I believe that the root cause of the management practices that result in this situation is the byproduct of company direction and culture. As an example, if the direction of the company is primarily to maintain a headcount, then there is only so many mental games a manager can play to retain it's ambitious employees.

I'm coming a bit late, so don't expect many to see this... but I worked at a company and had several friends leave for other jobs, but they were sad to part with their managers. They left mostly because the direction of the company as a whole wasn't satisfying them, which is a function of management, but usually not your immediate manager.

Which is why employee satisfaction surveys rarely ask the right questions or if they do they are interpreted in such a way that the managers who are the problem are not declared as such. I learned real quick to not be amazed at how such a survey can be turned upside down to blame the employees or a select group of them.

I have often thought that tech companies should pay more attention to how movies / tv series are managed then MBA programs. I get the feeling the Producer / Director / Show Runner model might work better for software. Support might complicate things though.

I would not down-play salary that much. I am not sure if it applies to all sectors, but at least in my limited experience more you ask for - better you are treated and better technology you work with. Because otherwise it will be to expensive to keep you.

I suspect Valve has a good way of dealing with this. There, manager is a role, and people can decide if you are good enough at that role to merit working with you in that capacity, or not. They get to vote with their feet, without leaving the company.

Even without reading the article i couldn't agree more. Currently i'm in the position where i like my colleagues and the company, but the management is BAD ( i could write 3 pages long explanation but i won't ). Well sorry , iQuit.

What in this instance defines bad management?

Perhaps its unusual but every company I have worked for this could be sorted out with a quiet word with upper management or HR. A little disruption moving people between teams is well worth averting a potential clashes

We usually don't like our managers for one reason or another unless we ourselves become one and someone else replace us. This has been happening for centuries. Point is why don't we learn lessons from past mistakes?

Either the boss is incompetent and so that boss makes work intolerable for the employee, or the employee is incompetent and the boss makes work intolerable for the employee. It's often hard to tell.

you developers have no idea how good you have it.

Choose your boss? yes, by accepting a job offer. Move to a different team? Again, by choosing a company.

Move internally? Yes, if you don't mind a firestorm that burns bridges, and moving to a job that won't use the skills I was hired for.

I'm the only one -- or at best, one of a handful of people -- who can do my job at my nonprofit. Does that give me more power? Heck no. Best I can do is threaten to quit, and if the boss and I don't get along, then they probably are just aching to hire in someone else.

I love working for my supervisor, manager, and director.

My company sucks, pay is sub par, benefits suck, policy sucks, forced overtime sucks....

If I leave I'll be leaving my company, not my manager. and the company is HUGE

This is so true, so so true. Not neessarly "managers" per say, but people involved in "decision" making that affects you.

For me; the people doing the UX, the people doing product, and etc.

A bad manager is going to hire a bad manager, and if you follow the organization chart to the top it stops being a bad manager, it becomes the company mantra.

That is a well known (decades+) fact - employees join companies based on their global reputation but leave mostly based on their direct supervisor quality.

I've left because of managers. I've left because of the company.

When a company cuts my salary by 30% while jacking up my benefits payments by 300%, it's usually time to leave.

But, on to the article at hand.

As a manager now, those statistics at the end really kind of tick me off. It feels very one-sided and the following text is just me rambling on... somewhat trolling.

39%: Their supervisor failed to keep promises

How many of these employees fail to keep theirs? How many of these broken promises were based on things promised to the manager? How much of it was in their control? When kept at this simplistic level, this one seems like a third-grade problem.

37%: Their supervisor failed to give credit when due

This perception of credit and recognition is one sticking point in our team right now, especially with the people born after 1980. They want credit and recognition for every single thing they do. If they manage to successfully eat a meal without choking on a bone, they want public recognition for it. The older guys on the team, we sit down and do the work because it is our job. That's what we're here to do. The old guys can sit around and come up with ideas and realize that together as a team we designed something. The team gets credit. No one person gets the credit. The kids, if they have one key idea at any point in a process, they want to be held up high. Oh and damn if their idea comes early in the discussion and is never used directly but expanded upon and changed, hell they think they were the sole party responsible for all ideas and all further ideas were stolen.

31%: Their supervisor gave them the “silent treatment” in the past year.

Yes, I do this. I usually do this when I am trying to decide what to do with spoiled or "entitled" employees. If I have asked somebody to quit looking at StupidVideos.com for 3 hours a day and they persist while their projects back up, I'm going to be silent for a while while I try and come up with a plan. I'm not going to sit and try to motivate them. Motivating geeks is a pain-in-the-ass. I'm not allowed to fire anybody or put them on disciplinary action w/out months of paperwork, especially when they know how to talk to HR and convince them that they are doing the best that they can.

27%: Their supervisor made negative comments about them to other employees or managers.

Agreed, this one is bad no matter how you slice it.

24%: Their supervisor invaded their privacy.

Again, if you're looking at Facebook and not getting your work done, you need to get over it.

23%: Their supervisor blames others to cover up mistakes or minimize embarrassment.

Yeah, this happens. Sucks. Lucky for my team, when I lie my eye twitches so there is a built-in lie detector. :-)

"The significant problems we have cannot be solved at the same level of thinking with which we created them." --Einstein

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact