"Yes, productivity is measurable — but only as a basket of four metrics (Speed, Effectiveness, Quality, Impact) designed to hold each other in tension so no single number can be gamed"
Evidence from the Archive
DX
At a 150-engineer org, a 3-point DXI improvement translated to ~100 hours/week recovered — equivalent to two full-time developers gained
Laura Tacho's Core 4 framework holds Speed, Effectiveness, Quality, and Impact in explicit tension so no single number can be gamed
Tacho and her co-author Abi Noda created Core 4 specifically to solve the implementation gap that DORA, SPACE, and DevEx left behind. Her diagnosis is that the frameworks are individually insufficient: DORA is too narrow, SPACE is too abstract, DevEx is too disconnected from business outcomes. The common failure mode is companies measuring either activity or nothing, then arguing.
Core 4 resolves this: four dimensions — Speed (PR throughput, deploy frequency), Effectiveness (developer experience index), Quality (change failure rate), Impact (percent of time on new capabilities vs. maintenance) — used as a system, never in isolation. The design principle is mutual tension: you can't raise Speed without tanking Quality, can't raise Impact without eventually hurting Effectiveness. At a 150-engineer org, a 3-point DXI improvement translated to ~100 hours per week recovered — two full-time developers gained.
In Laura's own words: "The four dimensions of Core 4 are designed to hold each other in tension: we don't want to increase speed at the expense of developer experience, or spend more time on new features while quality takes a nosedive. These metrics are designed to be used together as a system to provide a balanced look at overall team performance." (Introducing Core 4's core design principle.)