In 1987, demarco and lister published peopleware through Dorset House, presenting data from the Coding War Games — a multi-year productivity study involving hundreds of professional programmers — that showed environmental quality, specifically freedom from interruption, as the dominant predictor of individual coding performance.
The Coding War Games Finding
The Coding War Games collected performance data from programmers working in their own offices, under their own conditions. The variance in individual performance was enormous — ratios of 10:1 between top and bottom performers were documented. The key finding: this variance did not correlate with years of experience, salary level, or programming language. It correlated with workspace quality — and the most powerful workspace variable was uninterrupted time.
demarco and lister did not use the word "flow." But the mechanism they documented is precisely flow-state: the state takes 15-25 minutes to achieve, and any interruption — a phone call, a colleague stopping by, an open-plan office ambient noise — destroys it in seconds. Programmers in low-interruption environments weren't working harder; they were entering and sustaining flow-state at higher rates.
The "Furniture Police" Critique
peopleware coined the memorable phrase "furniture police" for management that prioritizes open-plan visibility over cognitive privacy. The book argued that the open-plan office — then ascendant as a productivity and collaboration innovation — was empirically destroying the very productivity it claimed to enable. This critique anticipated by decades the research that would eventually confirm it.
Lineage Significance
peopleware-publication-1987 sits at the intersection of foundational-research-1975-1990 (which was producing flow research in parallel, without software engineering contact) and the software-bridge-1987-2001 era it helped inaugurate. It brought flow's functional logic — uninterrupted concentration as precondition for optimal output — into software practice language, even without the theoretical vocabulary. The book's data became the empirical anchor for subsequent arguments about developer productivity, and its argument structure prefigures the flow-as-mechanism-behind-lean-agile synthesis.