Quality Software Management, Vol. 3: Congruent Actionwriting

qualitysoftware-managementsatircongruencemanagement-behavior
1994-01-01 · 3 min read · Edit on Pyrite

Published by dorset-house-publishing in 1994, _Quality Software Management, Vol. 3: Congruent Action_ addresses the layer of quality-software-management-framework that Weinberg considered most underestimated: the quality of managers' own behavior as communicators and decision-makers. Vol. 1 established that software management is a systems problem. Vol. 2 established that effective management requires accurate feedback. Vol. 3 establishes that both of the preceding conditions are undermined by incongruent behavior — and that incongruent management behavior is the norm rather than the exception in software organizations under pressure.

The volume draws extensively on virginia-satir's model of communication stances, which Satir developed in the context of family therapy and which Weinberg had been applying to organizational contexts for years through his work with her and through weinberg-and-weinberg. congruent-behavior in Satir's terms means attending simultaneously and honestly to self, other, and context — saying what you mean, hearing what others are saying, and taking the actual situation into account. The four incongruent stances — blaming (discounting others), placating (discounting self), superreasonable (discounting both self and others in favor of abstractions), and irrelevant (discounting everything) — are not character defects but stress responses. People in software organizations adopt them under pressure because they reduce immediate anxiety, at the cost of distorting communication and undermining the feedback loops on which effective management depends.

Weinberg's application of this framework to software management is specific and detailed. The blaming manager who attributes project failure to developer incompetence or customer unreasonableness cannot examine the process or structural factors that contributed to the failure; the blame narrative forecloses systemic analysis. The placating manager who agrees to everything — accepts every feature request, promises every deadline, tells every stakeholder what they want to hear — produces a project plan that is impossible before work begins, but the impossibility is invisible until the crisis arrives. The superreasonable manager who communicates exclusively through metrics, Gantt charts, and process documentation never engages with the human reality of the project; their subordinates learn to game the documentation while the actual situation deteriorates. The irrelevant manager who defuses every tense meeting with humor or topic changes ensures that genuine problems are never surfaced. In each case, the incongruent behavior produces exactly the kind of distorted or absent feedback that qsm-vol2-first-order-measurement-1993 identified as the central obstacle to effective management.

The argument that congruent behavior is a prerequisite for higher-pattern organizations connects back to the cultural-patterns-of-software-organizations model. A Pattern 3 organization — one capable of genuine steering — requires managers who can hear bad news, communicate honestly about constraints, and act on what the feedback actually shows rather than what they wish it showed. An organization where status meetings reliably suppress bad news is structurally incapable of Pattern 3 behavior, regardless of what measurement systems it has in place. The measurement systems Weinberg described in Vol. 2 are only as good as the congruence of the people who design, report, and interpret them.

The title of the volume — "Congruent Action" — emphasizes that congruence is not merely a communication style but a behavioral stance that shapes what an organization can and cannot do. Managers who cannot act congruently cannot take the difficult actions that quality improvement requires: declining features that would break the schedule, surfacing the real status of a troubled project, telling a powerful stakeholder that their requirements are contradictory. This behavioral dimension of the QSM framework sets it apart from process-centered approaches to software quality improvement. Process frameworks tell organizations what to do; Weinberg's framework asks whether the people responsible for doing it have the capacity to do it honestly. The practical implications for organizational change practitioners — including the community around aye-conference that took the framework most seriously — were substantial: before attempting to install new feedback mechanisms, diagnose whether the managers who will use them are capable of congruent action.