The organizational learning disability is DeMarco and Lister's characterization of the tendency of software organizations to repeat the same failures across projects without improving — because the people who enforce counterproductive practices are rarely held accountable for the long-term consequences, and because the organizational structure provides no mechanism for post-failure analysis to change future behavior.
The Core Pattern
The learning disability operates through a structural disconnect between action and consequence. A manager enforces a practice — say, an open-plan office layout, a mandatory overtime policy, or a compressed schedule — that damages team productivity and project outcomes. The damage unfolds over months or years, is attributable to many factors, and is largely invisible to the manager who made the decision. By the time the consequences are clear, that manager may have moved to a different role, the project team has been disbanded and redistributed, and no organizational mechanism has connected the decision to its outcome.
DeMarco and Lister observe that this is not a failure of individual intelligence or good faith; it is a structural feature of how most software organizations process information about outcomes. Post-mortems, when conducted at all, are typically blame-avoidance exercises rather than genuine causal analyses. Their findings are recorded in documents that no one reads before the next project begins. The people who would need to change their behavior based on post-mortem findings — managers, not developers — are often not present for the analysis and are not accountable for implementing its conclusions.
Why Post-Mortems Fail
DeMarco draws on this pattern in both peopleware and slack to explain why organizations with access to good management advice — including the Peopleware thesis itself — continue to repeat the same mistakes. Post-mortems fail as learning instruments for several reasons:
The Accountability Gap
DeMarco and Lister note that the people most responsible for the conditions that cause project failure — the managers who enforce high interruption environments, who impose unrealistic schedules, who break up jelled teams for short-term resource allocation — typically do not experience the career consequences that would create incentives to change. A developer who writes buggy code faces direct, visible accountability. A manager whose open-plan office policy suppresses developer flow for an entire organization faces almost none.
This accountability gap is part of why the spanish-theory-of-management persists: extraction-based management decisions are made by people who will not bear the long-term productivity cost of those decisions, and the organizations cannot connect the decision to its cost clearly enough to create accountability.
Connection to Slack and Risk
The organizational learning disability is deeply intertwined with the slack-concept. Organizations at full capacity have no time for genuine reflection; every available hour is committed to current delivery. Learning requires time to step back, analyze, and experiment — all of which require slack. Organizations that have eliminated slack have simultaneously eliminated the conditions for learning from experience.
DeMarco develops the connection to risk-management-as-risk-embracement in waltzing-with-bears: organizations that suppress risk information are also organizations that cannot learn from the risks that materialize, because the suppression makes it impossible to connect outcomes to their probabilistic causes. The learning disability and risk suppression are two aspects of the same organizational failure mode.
Contrast with Functional Learning Organizations
DeMarco does not develop a full theory of organizational learning (that territory belongs to Peter Senge and others), but the learning disability concept implicitly defines what a learning organization would require: feedback loops that connect managerial decisions to their consequences, accountability structures that give managers skin in the outcome of their decisions, post-mortem processes with genuine implementation authority, and slack time that allows reflection and experimentation between projects. The absence of these features is the disability; their presence is the cure.