Nobody ever gets credit for fixing problems that never happened (2001) [pdf]

The concept of "nobody gets credit for fixing problems that never happened" speaks to the inherent difficulties in evaluating the effectiveness of preventative measures. In the realm of technology, this is particularly pertinent when it comes to issues like security vulnerabilities or system failures, where the absence of incidents can be just as telling as their presence. This dynamic creates a Catch-22, where the very act of preventing problems can make it seem like nothing is being done.

The implications of this phenomenon are far-reaching, affecting how we design, deploy, and evaluate technology systems. As we move forward, it's crucial that we develop more nuanced metrics for measuring success, ones that account for the unseen aspects of system maintenance and improvement. The increasing reliance on AI and automation only exacerbates this issue, as the line between human and machine involvement becomes increasingly blurred.