4 ms·
I think you also need to set up an "adversarial" organization. Have a team responsible for reporting metrics that is distinct from the team that is responsible
by bentcorner 3y ago
I think you also need to set up an "adversarial" organization. Have a team responsible for reporting metrics that is distinct from the team that is responsible for software that drive the metrics. Classic Dev/QA partnership.
- ethbr0 3y agoThe US military essentially landed on a similar solution. - Regularly rotate personnel - Reward review by a random board The rotations prevent cooperation of "adversarial" parties from corrupting the process. A review based on a blend of quantitative metrics (basics/table stakes) and qualitative metrics (everything else) prevents quantitative-metrics-gaming from dominating. The system has a ton of flaws, is inefficient, and produces suboptimal outcomes a fair amount of the time, but damned if it doesn't scale.