4 ms·
It’s a meh from me - either is bad. If you are in a highly complex and professional field (in the traditional sense of the word) single axis optimization hollow
by klabb3 2y ago
It’s a meh from me - either is bad. If you are in a highly complex and professional field (in the traditional sense of the word) single axis optimization hollows out the whole craft. Engineering is delicate and constant battling of tradeoffs, and decision consequences are often delayed by longer than average tenure, let alone a 6 month perf cycle. The more you McKinsey the process, the more mediocre and incoherent the results.
- Arainach 2y agoYou get what you measure. You can't hire smart motivated people and then be surprised when they figure out to optimize for their rewards. If you want a team that lands stable customer-loved products, make THAT your performance review. Turns out that's hard to do objectively and consistently.
- lupire 2y agoAccording to your other comment, then, a company that "lands stable customer-loved products" would be a "hotbed of nepotism" that people shouldn't work for.
- Arainach 2y agoNonsense - you can have documented metrics which are known and tied to performance. For example: * Require features to be launched for a period of time rather than in development or shoved out the door a week before perf * Have metrics for customer satisfaction and oncall pages be incorporated Etc.
- aprdm 2y agoNonsense were a lot of your replies in my experience :), this "measure everything" is very much another cargo cult. Software engineering is complex, people are complex, thinking you can come with a true metric and who doesn't have it doesn't know what they're doing is the nonsense in my world view. Have excited engineers, pay them well, have them work on something that is aligned with their career & deliver value to their customers, they don't really need much more than that. All the rest is simply trying to "processi-ze" what is a human
- klabb3 2y ago> You can't hire smart motivated people and then be surprised when they figure out to optimize for their rewards. Never said that. I don’t have a solution. Well I have a partial solution, but not complete: Reward all team members equally for the performance of the team, or even the company. For instance: the pie is divided into 3 pieces: company, team, and individual performance. Candy is given out based on performance of both. It doesn’t fix the hackable metrics issue, but when people collaborate the side effects are better than when they think of their own promotions, and worse when they’re competing against their direct peers for a fixed bucket of candy per team. Such incentives are directly opposing collaboration between the very people that need to collaborate the most.