5 ms·
The purpose of metrics is to be something to game. Now you do need don't to anything illegal policies in place, and you might have a [unwritten] moral code of
by bluGill 5y ago
The purpose of metrics is to be something to game.
Now you do need don't to anything illegal policies in place, and you might have a [unwritten] moral code of what you can't do. However the purpose is to game the metrics. For all the discussion that follows I'm going to assume we are within these limits.
If the boss wants profit margin as a metric, then you need to figure out how to do things cheaper, and how to get more sales, or higher value sales or some such, and sometimes get something off the books. Note that this last is why smart investors always ask about the bottom line - because the rules of what you can hide from the bottom line are strict enough that the metrics cannot be gamed to your disadvantage. That said off the books is sometimes a useful thing to have - sometimes you know you need to do something hard and so you need to leave an approved way to hide specific things in plain sight.
The problem is most developer metrics are things where gaming the metric isn't good for the company.
- mmcnl 5y ago"When a measure becomes a target, it seizes to become a good measure." - Some guy
- mavelikara 5y agoCeases*
- cratermoon 5y agoMarilyn Strathern
- theshrike79 5y ago> The problem is most developer metrics are things where gaming the metric isn't good for the company. This is a lesson more managers need to learn. You don't give engineers a metric to game, they'll run circles around your silly numbers. My favourite anecdote about this: I was a consultant for a multinational corp. The Natives had their bonus targets tied to "amount of open bugs at $date". What did they do? At $date-1 the natives assigned all their open issues to me, a poor lonely consultant - who was outside of the bonus structure. ...and at $date+1 they grabbed their issues back, bonus objectives met :D