This episode steps into a more provocative space—one that many practitioners have felt but rarely name directly: when surveillance crosses the line into something else. Amber Young and Barbara Phillips are joined by Wayne Abba, a longtime leader in earned value whose perspective is grounded in decades of experience shaping the discipline at its highest levels. From the start, the conversation frames a tension that runs through the entire episode—what earned value was designed to be, and what it can become when misapplied. At its core, this discussion challenges a fundamental shift: the movement of EVM from a management-enabling process to something treated more like a compliance-driven “business system.” That change, while subtle on paper, has had real consequences in practice—altering how organizations interact, how reviews are conducted, and how data is used. Instead of enabling insight and collaboration, surveillance can begin to feel like fault-finding, where metrics are no longer signals for decision-making but triggers for scrutiny. The episode brings this to life through stories—moments where rigid application of rules led to counterproductive behavior, where teams were incentivized to hide variance rather than surface it, and where the presence of oversight changed the way people reported reality. In one striking example, direction was given not to report variances at all during the early phase of a project—an outcome that reveals how easily systems can be distorted when the focus shifts from understanding performance to avoiding consequences. But this isn’t a critique without contrast. There is a clear vision of what works: collaboration, shared accountability, and early, integrated understanding of the baseline. The origin story of the Integrated Baseline Review (IBR) becomes a turning point in the conversation—an example of how government and industry can come together not to police each other, but to align on scope, risk, and execution from the beginning. A recurring theme is intent. Surveillance, in itself, isn’t the problem. In the right context, it can provide credibility, structure, and support—especially for teams trying to implement EVM effectively. But when used as a “club,” it drives behavior in the wrong direction. When used as an enabler, it strengthens the system. This episode is ultimately about balance—and about remembering what EVM is meant to do. Not to punish, but to inform. Not to isolate, but to integrate. And not to create fear, but to support better decisions through reliable, objective data.
