It is tempting to describe disappointing organizational results as a failure of design, as though the system in place was meant to produce something better and simply fell short through poor execution, insufficient effort, or bad luck. A more precise and considerably more useful framing inverts this assumption entirely: the system is not failing to produce its intended design. It is succeeding, perfectly, at producing exactly what it was actually built to produce, whether or not that output matches what anyone intended when the system was first assembled.
This reframing is uncomfortable because it removes the comfortable explanation of results falling short of a design's intent, replacing it with a more demanding claim: the current results are not a deviation from the system's design. They are the system's design, expressed accurately, regardless of what anyone believes that design was supposed to produce.
The Gap Between Intended and Actual Design
Every system has two designs that frequently diverge considerably: the design as stated, documented, or intended by the people who believe they understand how it operates, and the design as actually constituted, reflected accurately only in the outcomes the system consistently produces. When these two designs align, stated intent and actual outcome match closely, and the system can be reasonably described as working as designed. When they diverge, which happens considerably more often than most organizations acknowledge, the actual design, revealed by outcomes, is the more accurate description of what the system genuinely is, regardless of what any policy document or organizational chart claims.
This divergence typically develops gradually, through the same accumulation of individually reasonable decisions discussed elsewhere in relation to how systems form over time. A process modified to handle an exception, an incentive adjusted to address a specific concern, a reporting relationship altered informally without ever being reflected in the official structure: each of these changes contributes to an actual design that increasingly departs from the stated one, until the gap between what the organization believes its system does and what that system actually produces becomes substantial.
Why This Reframing Changes the Diagnostic Question
Accepting that current results reflect the system's actual design, rather than a failure to achieve its intended one, changes the fundamental diagnostic question asked when results disappoint. The question shifts from why did we fail to achieve what we designed this system to do, an inquiry that tends to search for execution failures, insufficient effort, or unfortunate circumstance, to what is this system actually designed to produce, given that it is currently producing exactly this, an inquiry that searches instead for the structural features responsible for the outcome being observed.
This second question is considerably more productive because it takes the system's actual behavior as reliable evidence of its actual design, rather than treating that behavior as a mysterious deviation from an assumed design that may never have matched reality in the first place. A system consistently producing slow decision cycles, for instance, is not failing to achieve fast decision-making. It is succeeding at producing slow decisions, which means the diagnostic task is to identify what structural features, whatever their original intent, are actually generating this consistent outcome.
What Accountability Looks Like Under This Framing
This reframing has significant implications for how accountability gets assigned when results disappoint. Under the assumption that a system failed to achieve its intended design, accountability naturally attaches to whoever was responsible for executing within that system, since the design itself is assumed to have been sound and the shortfall attributed to imperfect implementation. Under the assumption that the system is producing exactly what it was actually built to produce, accountability shifts toward whoever is responsible for the system's actual design, including the accumulated history of decisions that shaped it, which frequently implicates structural choices made well before the specific outcome being examined.
This shift in accountability is often resisted precisely because it is more uncomfortable than attributing shortfalls to individual execution. It requires examining decisions made by people who may still hold significant authority, decisions that may have seemed entirely reasonable at the time they were made, and structural features that have often been in place long enough to seem like permanent fixtures rather than the modifiable design choices they actually are. This discomfort does not diminish the accuracy of the reframing. It simply explains why organizations frequently resist adopting it even when the evidence for its accuracy is substantial.
Using the Principle Diagnostically
Applied deliberately, this principle becomes a useful diagnostic tool: whenever a system consistently produces an undesirable outcome, the productive response is to ask what specific structural features would need to be present for this particular outcome to occur reliably, and then search for those features within the actual system rather than the intended one. This search frequently reveals structural causes that were never part of any deliberate design, having accumulated instead through the ordinary drift discussed elsewhere, but that are nonetheless genuinely responsible for the outcome being observed.
This diagnostic approach requires setting aside, at least temporarily, assumptions about what the system was supposed to do, since these assumptions can actively interfere with accurately identifying what the system is actually doing. A system assumed to prioritize quality, for instance, but consistently producing quality shortfalls, is more accurately understood, at least provisionally, as a system actually structured to prioritize something else, whether speed, cost, or some other factor whose actual priority within the system's design exceeds whatever priority quality nominally holds in its stated intent.
Redesign as the Logical Response
If current results reflect the system's actual design rather than a failure to achieve its intended one, then changing those results requires changing the actual design, not simply reasserting the intended one more forcefully. Restating a commitment to quality, for instance, accomplishes little if the system's actual structure, its incentives, its information flows, its accumulated exceptions, continues to prioritize something else in practice. Genuine improvement requires identifying and altering the specific structural features responsible for the current outcome, which is a considerably more demanding task than simply articulating what the outcome was supposed to be.
This is, in the end, the practical value of accepting that every organization is perfectly designed for its current results. It replaces the comfortable but unproductive search for execution failures with the more demanding but considerably more useful search for the actual structural causes generating the outcomes an organization observes, a search that offers a genuine path toward different results, provided the organization is willing to locate and alter what its system is actually doing rather than what it was assumed to be doing.
