Organizational Autonomy and Change Resistance

Definition

Leopold and Kaltenecker, drawing on systems theory, argue that organizations are not machines that can be controlled by pressing a button but "autopoietic" systems—self-organizing, self-referential, self-regulating. They have their own laws and logic that external actors can barely identify, let alone influence. An organization decides how to react to its environment autonomously and builds on prior experience even when facing existential threats. This autonomy is not a character flaw but a feature: it's what lets organizations survive. However, it also means that imposed change—solutions from outside that don't respect the organization's actual logic—either fails or provokes resistance that appears irrational from the outsider's perspective.

In the Book

The book contrasts two change failures. A software testing firm faced real market pressure: products were no longer cutting-edge, services too expensive. The marketing director raised the alarm. Instead of the usual leap-to-action, the executive board took time for genuine diagnosis. They interviewed loyal customers and internal staff, discovered the deeper pattern (lead times, flexibility, reliability were the real issues, not features), and developed solutions that respected the organization's existing relationships and expertise while addressing the system-level problems. The change worked.

In contrast, an electronics firm faced similar market crisis. The director resisted change, holding to old practices until crisis forced his resignation. The new director hired an external crisis manager who brought best practices from other industries and imposed structural changes top-down, bypassing existing knowledge and relationships. The organization experienced it as disrespect: experienced employees were made redundant, others fled, customers lost their trusted contacts. Autonomy was violated. The imposed structure didn't align with the organization's actual logic, so the system collapsed from within.

The distinction is profound: one change respected the organization's autonomy (existing relationships, expertise, culture) while addressing the real problem. The other treated the organization as a machine to be reprogrammed, ignoring its autopoietic nature.

Why It Matters

This concept explains why many well-intentioned, technically sound change initiatives fail: they treat the organization as an object to be redesigned rather than a living system to be understood. It reorients change strategy from "here's the best practice" to "what is this system's actual logic, and how do we evolve it?" For leaders implementing change, it means investing heavily in understanding how the organization currently works, what assumptions drive it, who the real power brokers are (not the org chart), and what informal logic keeps it functioning. Then changes are designed to respect that logic while redirecting it toward new goals. Imposed solutions, no matter how perfect on paper, trigger the system's immune response. This concept provides the theoretical foundation for Leopold and Kaltenecker's insistence on extensive interviews, stakeholder engagement, and cultural analysis before design workshops.