Published by dorset-house-publishing in 1997, _Quality Software Management, Vol. 4: Anticipating Change_ is the capstone of quality-software-management-framework, completing a project that Weinberg had sustained across five years and four volumes. Where the preceding volumes established the conceptual foundations (systems thinking), the informational prerequisites (measurement), and the behavioral conditions (congruence), Vol. 4 addresses the question that runs underneath all of them: how do organizations actually change? The answer draws most directly on virginia-satir's satir-change-model, which Weinberg had been applying in consulting work for years and which he here develops into its most systematic form.
The Satir Change Model describes five stages through which individuals, families, and — in Weinberg's application — software organizations move when significant change occurs: Late Status Quo, Foreign Element, Chaos, Transforming Idea, and New Status Quo. The model's most important insight, which Weinberg emphasizes throughout the volume, is that chaos is not a failure of change management but an inherent feature of real change. When a foreign element — a new technology, a new leader, a quality crisis, a competitive disruption — enters an organization, it destabilizes the existing equilibrium. Performance drops, anxiety rises, blame increases. Organizations and change practitioners who try to skip or suppress this chaos stage typically fail: they either reassert the old status quo (the change doesn't take) or impose a solution from outside before the organization has developed the capacity to integrate it (the solution collapses when the external pressure is removed). The volume teaches managers and consultants to recognize chaos as evidence that change is real, and to support organizations through it rather than trying to eliminate it.
The concept of the anticipating organization, from which the volume takes its title, is the fully developed form of Pattern 4 in the cultural-patterns-of-software-organizations model. An anticipating organization is not merely one that responds well to change after it arrives; it is one that has built organizational capability to recognize the early signals of coming change and begin preparing before crisis forces action. This requires precisely the combination of capabilities described in the three preceding volumes: systems thinking that can model organizational dynamics and extrapolate from early signals, measurement systems that surface honest early-warning information, and congruent behavior from leaders who can act on what that information shows even when it is unwelcome. Vol. 4 is in this sense a synthesis: the anticipating organization is the one that has successfully integrated all four layers of the QSM framework.
The practical guidance in the volume addresses how organizations can develop change capability — not through any single process intervention but through sustained attention to the conditions that make change possible. Weinberg draws on the consulting work of weinberg-and-weinberg and the broader community of practitioners associated with aye-conference to illustrate what pattern transitions actually look like in practice: the specific resistance patterns that emerge when foreign elements arrive, the organizational dynamics that make certain transforming ideas available or unavailable, and the kinds of practice and integration work that stabilize change at a new level. The moi-model of motivation, ideas, and organization appears in this context as a diagnostic for understanding what an organization needs at different stages of the change cycle.
The four-year gap between Vol. 3 (1994) and Vol. 4 (1997) reflects both the ambition of the capstone and the difficulty of synthesizing the full framework. The QSM series as a whole represents the most systematic working-out of the argument that animates Weinberg's entire career: that programming-as-human-activity is not a slogan but a serious proposition with specific implications for how software work should be managed, measured, and improved. Vol. 4's completion closed a project that had no real equivalent in the software quality literature of its time — theoretically grounded in systems thinking, practically grounded in decades of consulting experience, and stubbornly insistent that the human dimensions of software work are not soft complications to the real technical problems but the essential phenomena that determine organizational outcomes.