> ## Content Index > Fetch the complete content index at: https://why-organizations-misbehave.ghost.io/llms.txt > Use this file to discover other available public pages before exploring further. # Trapped by the systems we design - URL: https://why-organizations-misbehave.ghost.io/trapped-by-the-systems-we-design/ - Published: 2026-08-05T18:30:55.000Z - Updated: 2026-08-10T01:26:52.000Z - Description: In this edition, I consider the seven principles that are the analytical foundation of this newsletter. If you want to understand the conceptual framework underlying most of my articles, you should definitely read this one. - Author: Alexander Spradling, PhD - Tags: organizational design, organizational systems, human activity systems, emergent properties ## Organizations are human activity systems Unlike technical systems—which perform according to their design and are easily tweaked —organizations are shaped by the intentions, beliefs, values, and behaviors of the people within them. This makes them inherently complex, unpredictable, and resistant to outside control. This is also what makes organizational systems so easy to misdiagnose. When the gap between what a system claims to pursue and what it actually produces becomes visible, the instinct is to look for a cause at the same level as the symptom. A performance problem triggers a performance intervention. A communication breakdown triggers a communication training. A culture problem triggers a culture initiative. But the cause is rarely where the symptom appears. It lives in the structural conditions that make the symptom the logical and predictable response. ### An example you may recognize Consider something most people at work have experienced: a meeting culture that everyone agrees is broken. Too many meetings, too long, too unfocused, with too many people in the room who don't need to be there. Leaders acknowledge it. Employees complain about it. Occasionally someone launches an initiative to fix it — a new meeting protocol, a no-meeting day, a set of guidelines about who should be invited and why. And yet six months later the calendar looks exactly the same. Why this happens is not a mystery. It is an organizational system behaving exactly as its structure dictates and rewards. To understand what that means, consider the following. In most organizations meetings serve more than one purpose. At their best, they are genuine coordination mechanisms — the right people, at the right time, making decisions that require collective input. But they are also signals of relevance, proximity to power, and organizational standing. Being in the room means something beyond the content of the meeting itself. And it is that second function — not the first — that explains why meeting cultures are so resistant to change. When an initiative tries to reduce meetings by asking people to question whether they need to attend, it is asking them to voluntarily opt out of a system that signals their importance and conditions what they can and cannot control. The stated goal is efficiency. The structural incentive is visibility and impact. Until that misalignment is addressed, the meeting culture will self-regulate back to what the structure dictates and rewards. ## Seven principles of organizational systems The meeting culture example illustrates a set of principles that apply to all organizational systems, and that shape how every article in this newsletter approaches organizational behavior. ### Organizational systems are rarely designed — at least not fully. They emerge, and what emerges is complex Nobody sat down and purposefully designed the meeting culture described above. It accumulated over time through the interaction of decisions, habits, incentives, and interpretations that no one engineered as a whole. What emerged is of such complexity that it resists straightforward understanding. The whole behaves in ways that cannot be predicted from examining the parts in isolation. This is why organizational dysfunction is so often misdiagnosed — the visible symptom and its structural cause may be separated by several layers of interaction that are difficult to trace. And this is also why it will keep showing up under different names until the structural conditions change. ### Humans are not passive actors In a technical system, components behave according to their design. In an organizational system, the actors interpret the system they are part of, form beliefs about how it works, and adjust their behavior accordingly. In the meeting culture, people have learned that attendance signals relevance and commitment. That belief is now part of what the system produces. Changing the behavior requires changing the belief, which requires changing the structural conditions that make the belief reasonable in the first place. ### Outputs are more revealing than intentions The meeting culture says it values focused, efficient use of time. Yet, what it consistently produces is calendar overload and performative presence. The output is the more accurate statement of what the system is actually optimized for. Intentions describe what people want. Outputs describe what the structure enables and rewards. ### Consequences are how the system conditions the behavior of its actors If outputs reveal what the system is optimized for, consequences are the mechanism by which the system enforces that optimization. In the meeting culture example, the consequence of not attending a meeting is a loss of visibility and perceived impact. People don't need a policy to understand that. They need only one experience. The system communicates its actual values through what happens or doesn't happen when people act. Those signals shape behavior more reliably than any stated norm or cultural value. ### Well-intentioned interventions often make things worse As the saying goes, the road to hell is paved with good intentions. Every actor in the meeting culture can see the part they interact with directly. Few can see the whole. This is why well-intentioned interventions, such as meeting protocols, no-meeting days, and invitation guidelines often fail. They address a part of the system that looks like the problem without modifying the structural conditions that are producing it. The intention was to improve. The effect was to add complexity without changing what the structure enables. ### Some gaps are tolerated because they serve hidden interests Not all divergence between stated values and structural outputs is unintentional. In some cases the system is producing exactly what its architects actually desire, rather than what they publicly claim to desire. The gap is not between intention and outcome. It is between stated intention and real intention. This is the hardest version of the problem because addressing it requires naming what the system is actually optimized for, and this is a political act, not just a diagnostic one. And it is usually far more risky, because it exposes the interests of the people whose influence depends on the current system remaining exactly as it is. ### The diagnostic question precedes the design question Before asking how to change a system, the more useful question is where the system's behavior can actually be influenced. Not every part of an organizational system is equally responsive to intervention. Identifying the leverage points — the places where a targeted change produces disproportionate effects on the system's outputs — is a diagnostic problem. Redesigning the system is what follows. ## What to do with this Kurt Lewin once observed that there is nothing more practical than a good theory. The principles in this article are offered in that spirit. They are not abstract ideas but diagnostic tools that operate at a higher level than the symptoms that typically trigger organizational interventions. A performance problem, a communication breakdown, a culture that resists change: these are not the level where the solution lives. They are signals pointing to structural conditions that exist below what is immediately visible. The practical implication is this: when something in your organization persistently produces outcomes inconsistent with what you intend, resist the temptation to intervene at the level of the symptom. The symptom is information. It is telling you that somewhere in the structure, a condition exists that makes the current behavior the logical and predictable response. Your goal is to find that condition. *I go deeper on the structure/system distinction itself — and why dismantling a structure doesn't dismantle the system it's embedded in* [*"What structure really is, and why it matters"*](https://why-organizations-misbehave.ghost.io/what-structure-really-is-and-why-it-matters/)*.* --- Alexander Spradling, PhD, is an organizational consultant and executive coach based in Austin, Texas. He writes Why Organizations Misbehave.