Observer Effect

A small high-value fix can appear inactive or low-output on an activity dashboard. Large amounts of poor-quality code can appear productive when monitored signals are visible and frequent. Surveillance changes the behavior it attempts to measure. Monitoring changes developer behavior by pushing work patterns toward dashboard rewards. Activity measurement causes behavior to optimize for activity instead of engineering outcomes. When employees know activity signals are tracked, their measured behavior becomes performative. Employees optimize for visible activity when surveillance systems appear to value it. The observer effect describes how monitored people change their behavior when measured on visible signals. Developers under surveillance may optimize for what monitoring systems can see instead of what the codebase needs. Monitoring-driven behavior change produces performative work, distorted incentives, and worse engineering outcomes.