Discussion about this post

User's avatar
Liz U Kato's avatar

I work for the Federal Government (health) and this resonates with what I see. Government staff are buried under dozens of process requirements (like Small business requirements) and leadership measures success as no one yelled at us, not “did we objectively improve things.”

Expand full comment
Matt Hagy's avatar

> And importantly, telling agencies to try to hit a half-dozen different goals … doesn’t ensure that all those things will be done simultaneously. What it ensures is that, with no principled way to evaluate projects or say no to things, costs explode.

The cynic in me wants to believe that agency leaders would like to avoid a simple and objective measure of performance. If they are solely evaluated by ridership/dollar-spent then they could fail to improve on that metric and be charged with bad decision making. In contrast, if they claim to be balancing numerous unquantifiable objectives, then it’s much harder to criticize their performance. For example, if we point out the low ridership volume then they can point to their progress in expanding access and creating good paying jobs.

And I think there is a general tendency for all leaders and workers to resist objective evaluation. For example, I've seen this criticism applied to the anti-testing movement in education where it is alleged that poor teachers simply want to evade detection.

I’ve also seen this aversion to performance evaluation within the tech industry, particularly within discussions on the tech forum Hacker News. While there are many poor approaches to measuring software developer performance (e.g., lines of code count), there still need to be some objective evaluation. Quality measures can include annual peer review using a rubric of dimensions.

Yet there is commonly fierce objection to any evaluation of software engineers within such discussions. Numerous excuses are given for any proposal, while no alternatives are offered. It seems software engineering is conceived as some impalpable art that cannot be evaluated, even by fellow artists. And this extends to strategies and criteria for interviewing prospective engineers. All commonly used methods, such as whiterboarding code exercises, are castigated as inadequate to measure the intangible brilliance and abilities of engineers.

I just think we all have some natural aversion to being evaluated for fear of failure. Therefore our institutions, both public and private, need to be designed to counteract that tendency.

Expand full comment
258 more comments...

No posts