Live data from Hacker News

Ask HN: How does your company do performance reviews?

news.ycombinator.com

11–20 of 100 posts

Re: Ask HN: How does your company do performance reviews?

#11
post #9

My company uses quarterly reviews. Here are the metrics my company uses to review each developer: 1. We have an in-house developed tool that tracks git and mercurial commits and calculates the test coverage and code quality for each individual developer. 2. We use jira to track the number of points each developer burns (points are shared between developer, reviewer and QA). We also track the number of bugs each devel…

"one of my colleagues and friend was "forced" to quit the company because he scored really low on the jira burn rate metric" This sounds totally insane. I Cannot believe this happens in real world.

It sounds like justification for a decision made for less quantitative reasons.

Managers don't say, "So let's see who's the worst performer... it's Tom! Weird, he seems to be one of my best developers. Oh, well! The metrics say he's the worst. Off to fire Tom!"

Re: Ask HN: How does your company do performance reviews?

#12
post #2

A related question: Should you do them? They don't seem useful in tiny companies, where you can just see how everyone is doing, apart from informal "What is worrying you" conversations. How big a company you have to be for them to be useful/necessary?

It's hard not to have some sort of review process if you want to be able to fire someone. If anyone challenges their dismissal for performance reasons, you'll want a record of the "conversations" (1) you had. This is why a lot of review processes include some sort of sign-off by the parties involved.

(1) Scare quotes around "conversations" because I've never seen management approach an underperforming employee and then realize that they had a big part in that. Conversations tend to be more two-way than that.

Re: Ask HN: How does your company do performance reviews?

#13
post #9

Earlier quoted context omitted.

"one of my colleagues and friend was "forced" to quit the company because he scored really low on the jira burn rate metric" This sounds totally insane. I Cannot believe this happens in real world.

It sounds like justification for a decision made for less quantitative reasons. Managers don't say, "So let's see who's the worst performer... it's Tom! Weird, he seems to be one of my best developers. Oh, well! The metrics say he's the worst. Off to fire Tom!"

Not in general, but I'm sure there are some that might.

Re: Ask HN: How does your company do performance reviews?

#14
post #2

A related question: Should you do them? They don't seem useful in tiny companies, where you can just see how everyone is doing, apart from informal "What is worrying you" conversations. How big a company you have to be for them to be useful/necessary?

It's hard not to have some sort of review process if you want to be able to fire someone. If anyone challenges their dismissal for performance reasons, you'll want a record of the "conversations" (1) you had. This is why a lot of review processes include some sort of sign-off by the parties involved. (1) Scare quotes around "conversations" because I've never seen management approach an underperforming employee and th…

In our situation, which is a relatively small company, it's used to keep people energized, focused and well... happy. Without it, we had regular team meetings where people talked about frustrations they had (and it exploded at times).

I don't think having it around as way to fire someone is the right approach.

Re: Ask HN: How does your company do performance reviews?

#15
post #9

My company uses quarterly reviews. Here are the metrics my company uses to review each developer: 1. We have an in-house developed tool that tracks git and mercurial commits and calculates the test coverage and code quality for each individual developer. 2. We use jira to track the number of points each developer burns (points are shared between developer, reviewer and QA). We also track the number of bugs each devel…

"one of my colleagues and friend was "forced" to quit the company because he scored really low on the jira burn rate metric" This sounds totally insane. I Cannot believe this happens in real world.

"[manager] didn't want to assume any blame for this"

This happens depressingly often.

"6 monts working on the equivalent of 2 weeks of estimation points"

It's really the fault of the manager for not changing something after the first 3 weeks of this.

Re: Ask HN: How does your company do performance reviews?

#16

Earlier quoted context omitted.

It's hard not to have some sort of review process if you want to be able to fire someone. If anyone challenges their dismissal for performance reasons, you'll want a record of the "conversations" (1) you had. This is why a lot of review processes include some sort of sign-off by the parties involved. (1) Scare quotes around "conversations" because I've never seen management approach an underperforming employee and th…

In our situation, which is a relatively small company, it's used to keep people energized, focused and well... happy. Without it, we had regular team meetings where people talked about frustrations they had (and it exploded at times). I don't think having it around as way to fire someone is the right approach.

I'm a huge fan of more informal one-on-one meetings. To the point where I will consider a move if I'm not getting enough time with my management. I don't consider those "performance reviews" though.

Re: Ask HN: How does your company do performance reviews?

#17
Large company, performance is based almost entirely on feedback from peers and those you report to with check-ins every 6 months. Overall score from 1-5 with a 3 being "meets expectations" and the most common rating by far.

The problem is that the feedback from superiors seems to be weighted much higher so the peer feedback is almost useless so don't bother mentoring or helping someone get back in front of their tasking. This leads to a lot of I'm-working-so-hard theatrics instead of actually being efficient/effective and delivering product.

Combine this with "suggested targets" (quotas) for the number of people in each 1-5 bin, you end up with the usual stack ranking problem that getting on the shittiest project (and keeping it that way to ward off competition) and making it damn clear to your manager that they can't live without you is the best strategy.

Re: Ask HN: How does your company do performance reviews?

#18
Yes; we have quarterly "check-in" reviews and a larger yearly review where salary is considered. The process consists of peer and self reviews. We used to have a rating system as well where in the yearly review you would get a certain rating out of five options depending on how you did. The rating portion was removed a couple of years ago.

Re: Ask HN: How does your company do performance reviews?

#19

My company uses quarterly reviews. Here are the metrics my company uses to review each developer: 1. We have an in-house developed tool that tracks git and mercurial commits and calculates the test coverage and code quality for each individual developer. 2. We use jira to track the number of points each developer burns (points are shared between developer, reviewer and QA). We also track the number of bugs each devel…

That sounds like a terrible process. With that kind of process I wouldn't want to work there. It's a great example of how developers are treated as second class grunt workers.

Re: Ask HN: How does your company do performance reviews?

#20
Oh don't get me started.

Fairly big (>1000 devs) company. Performance reviews are twice a year.

In theory: before each cycle, an employee and a manager meet to discuss manager's expectations. If an employee "exceeds expectations" he or she gets a good rating. The rating is then approved and bonus and compensation is determined.

In practice: the rating is kind of determined by how employee's work contributed towards "important goals" of the company. This contributes to a deluge of half-assed work pushed into production just before the evaluation begins. Also it of course depends on performance of the other devs. The existence of the curve was never officially acknowledged but it is an open secret that it indeed exists.

The evaluation process is extremely opaque and shrouded in mystery. An employee (and his or her manager too) can never be certain that enough work was done for a particular rating as they are subject to correction at the highest levels of hierarchy (rumor has it that the CTO himself approves the final ratings of all developers above certain level). The process is also extremely long (easily exceeds 1.5 months) and taxing for line managers who have to defend their subordinates' ratings against cuts.

The meetings between an employee and a manager are very awkward. In theory the manager should discuss career prospects and deliver valuable feedback, but what is the point of delivering feedback on something that happened 5 months ago? Why would you wait for so long to do it? So everyone just goes through the motions during these meetings as quickly as possible.

The whole process is very inefficient. Frankly, it stinks. (Personally, I've fared fairly well so it is not an instance of sour grapes). My opinion it that the only reason it exists is because it provides the potential of almost authoritarian control and ample micromanagement opportunities.

I wonder, are my experience and feelings somehow special or is it a common thing in our industry?

Post reply on HN