Discussion about this post

User's avatar
Alasdair Mackintosh's avatar

Imagine one of those space warfare games where you have to assemble a fleet, and you have a certain number of points to spend. Do you want that Rigellian Battlecruiser at 1000 points? Or do you only have the budget for a handful of Denebian escorts at 50 points each? Hold that thought...

Your peers should have a reasonably good idea of how valuable you actually are. They review your code, they see you help fix problems (or fail to), they see you volunteer to fix unglamourous bugs (or decline to). There should be some way of capturing this. Written peer feedback is mostly meaningless, as you pointed out, but I wonder if there is some way of deriving a numerical score for a person, based on the (anonymous) marks that their peers give them, and weighted by some metric of how closely they collaborate. Your final total reflects some weighted average of how well they people you work with appreciate what you are doing. This total affects promotion and compensation, but it also determines your price on the internal market. A manager looking for new team members can get you by paying a cost based on your current rating. (This means that people who are overlooked by the system, and rated lower than they should be, may turn out to be a potential bargain for someone else.)

I can think of all kinds of objections to this, of course. It smells a bit like stack ranking. It's probably open to gaming and manipulation. And people may not like being reduced to a number (although that's what compensation is, really.) But at the same time, I think we need to solve the problem of the kind of peer reviews you describe, where everyone is just basically nice. Their ought to be some kind of cost to the ratings that you give out. Overrating or underrating someone should have some kind of consequence.

Expand full comment
Ramius's avatar

Talking about the anxiety aspect of performance reviews, I found this paper quite interesting: https://www.researchgate.net/profile/Ofer-Sharone-2/publication/292499150_Engineering_overwork_Bell-curve_management_at_a_high-tech_firm/links/5cd039ef458515712e95ab3b/Engineering-overwork-Bell-curve-management-at-a-high-tech-firm.pdf

It explains long work hours in the case study as a result of performance reviews and other management practices that create anxiety about professional competence. Even if you don’t agree with all of the conclusions I found it fascinating to read a sociologist’s analysis of something I’ve lived through.

Expand full comment
12 more comments...

No posts