Live data from Hacker News

Google Engineering Management Mistakes

docs.google.com

41–50 of 136 posts

Re: Google Engineering Management Mistakes

#41

What is a "Peer bonus structure"? I appears in #3 Recognition, "Peer bonus structure was very well done, but not widely used inside engineering."

You can give a peer bonus of $200 to any individual with their manager's approval (which is very easy to get). They encourage giving peer bonuses for when someone goes the extra mile on something, but very few engineers initiate giving a peer bonus. After tax, it's about $100, hence the "I can poop $100" bit.

Re: Google Engineering Management Mistakes

#42
"The sum of money just appeared in my bank account, but was so insulting low that I felt devalued. If a manager had just talked to me about how much my work was appreciated, it would have been better than money."

This is true at a certain threshold. Appreciation is immeasurably better than an demoralizing, insultingly-sized bonus. However on the other end, if you go above and beyond normal expectations and save or earn the company millions of dollars, a "thank you" from your boss on the company newsletter is not going to cut it.

Re: Google Engineering Management Mistakes

#43
post #23

Earlier quoted context omitted.

It does seem asinine. Although frankly I can't think of many ways that seem much better. Do you always just give everyone on your team the exact same bonus?

In certain companies, bonuses are dependent on three factors: company success, team success, and individual success, based on targets agreed upon at a certain point in time. To me, that seems a lot more fair than implicitly believing all members of a team are of equal levels of skill, productivity, etc.

It is obviously true that people should be compensated for company, team, and individual success.

It does not follow that the way to do that is a rigid, formal cycle of performance reviews and ranking.

Re: Google Engineering Management Mistakes

#44
It's funny how you could take "Google" out of that slide and put "Apple" in it and it would be almost word-for-word applicable. Or maybe it's not funny.

Too, I recognize that this author of this presentation spent time to make it public, and sharing this sort of information is always welcome, so moaning about the format might seem a little rich. But in the glorious tradition of the internet, I'ma gonna bitch about it anyway. I really really hate this new fad of posting these Powerpoint-style slide decks. I would always prefer to read prose, even inexpert prose, than through yet another comically inept link on scribd or google docs.

Moaning off. Thanks again to the author.

Re: Google Engineering Management Mistakes

#45
post #43
post #23

Earlier quoted context omitted.

In certain companies, bonuses are dependent on three factors: company success, team success, and individual success, based on targets agreed upon at a certain point in time. To me, that seems a lot more fair than implicitly believing all members of a team are of equal levels of skill, productivity, etc.

It is obviously true that people should be compensated for company, team, and individual success. It does not follow that the way to do that is a rigid, formal cycle of performance reviews and ranking.

No, of course not. I did not mean to imply that.

Re: Google Engineering Management Mistakes

#46
post #12

Earlier quoted context omitted.

That's one option. Not giving bonuses at all is another option. Tying incentive comp to business events (recruitment, customer acquisition, an A/B test and minor feature change that produces a 1% uplift, etc) is another option. Anything has to be better than going out of your way to stratify an otherwise well-functioning team.

I just have a hard time believing incentives don't work. For example, if I lost all of my stock options today and was told I'd never get another raise or bonus, except CoL, I'd quit on the spot. In fact I'd argue, if there were no financial incentives, most HNers wouldn't do startups. I know everyone likes to say they do it to change the world and the passion of something or other. But in reality I've yet to see many…

Losing all of your stock options or having something else taken away is not a negative case for incentives, it's an example of a disincentive, which also has an effect. They aren't the same thing, and you can tell because you don't know how well you'd be working if you never had the options in the first place (and hadn't been denied them or otherwise been treated unfairly).

One of the reasons you don't see many founders take a $50k/yr salary is that very few of them are truly confident of success. I once heard an aphorism, "don't trust a founder who won't put their own money into the company." It's a little pointed and unrealistic, but you get the idea. In an industry driven by a mythology of becoming the next big thing (parallels to the equally one-in-a-million mindset in the music industry), no founder can afford, professionally and with regard to reputation, to treat themselves as anything but a foregone success, and that attitude requires "competitive compensation." This means they want to be paid as much as other unsure founders.

The "low-salary superboss" is a product of already-successful companies.

Re: Google Engineering Management Mistakes

#47

Earlier quoted context omitted.

"Stack ranking means that if you have a group of 20 people, during each performance review cycle the group manager is expected to rank them from 1 to 20, and the company distributes bonuses and promotions accordingly. That just seems completely asinine." Worse, there is often an associated ideal distribution ("the curve") with fixed ratios for "exceeds expectations", "below expectations" and so on and managers are un…

I was in a place that decided to give out bonuses to my team (consisting of 3 members and a leader) in the following way: 1. Allocate fixed amount to give out per team 2. Have team leader's manager determine how that pie would be shared between team leader and us 3 team members. 3. NOT have 360° feedback 4. Incorporate team leader feedback on team's performance into this decision I'm not sure what type of HR schmuck…

It sounds like your manager actually suffered a bout of insanity or was a thief.

Re: Google Engineering Management Mistakes

#48
post #15
post #5

Earlier quoted context omitted.

I had to look up "stack ranking" just now, so, for the benefit of the class: Stack ranking means that if you have a group of 20 people, during each performance review cycle the group manager is expected to rank them from 1 to 20, and the company distributes bonuses and promotions accordingly. That just seems completely asinine.

I once worked at company that employed a lot of hourly wage type people. One exec wanted to stack rank each group of wage employees each month and fire the bottom 25%. I tried to explain to him the negative morale effect that would lead to lower performance across the board, the fact any employes who were decent would just leave on their own, and there is a significant training cost for each new employee that he was…

This is what Jack Welch did at GE in the 80s, firing 10% of management every year. It's not universally derided as an HR/Management policy. I mean, it's pretty much the entire premise of the TV show "The Apprentice," no?

Pro: http://www.cogmap.com/blog/2009/11/12/force-ranking-to-fire-...

Con: http://www.missionmindedmanagement.com/where-jack-welch-got-...

Re: Google Engineering Management Mistakes

#49
post #34

Earlier quoted context omitted.

Career ladders are wishful thinking and an easy way to undervalue contributions. They imply that professional development largely occurs along a single axis rather than multiple ones. Who's worth more, Peter Norvig or Marissa Mayer? What about an overachieving SWE I vs an mailing-it-in SWE III?

Additionally, poorly structured career ladders can to lead to "Promotion Until Incompetence", where people are repeatedly promoted until they are unable to warrant another promotion. Thus, everyone is stuck at a level of mild incompetence.

AKA "The Peter Principle."

Re: Google Engineering Management Mistakes

#50
post #46

Earlier quoted context omitted.

I just have a hard time believing incentives don't work. For example, if I lost all of my stock options today and was told I'd never get another raise or bonus, except CoL, I'd quit on the spot. In fact I'd argue, if there were no financial incentives, most HNers wouldn't do startups. I know everyone likes to say they do it to change the world and the passion of something or other. But in reality I've yet to see many…

Losing all of your stock options or having something else taken away is not a negative case for incentives, it's an example of a disincentive , which also has an effect. They aren't the same thing, and you can tell because you don't know how well you'd be working if you never had the options in the first place (and hadn't been denied them or otherwise been treated unfairly). One of the reasons you don't see many foun…

Well I think I'd also turn down most jobs that said, "We'll pay $150k/year with no further financial incentives ever". Unless my goal was simply to to do as little work as humanly possible, yet still collect a check, I'd be hardpressed to work there. And if I did, despite non-financial that exist in the world, I really don't think you could get me to work more than 40 hours per week.
Post reply on HN