Paired instrument: Burke-Litwin Causal Model questionnaire

The Burke-Litwin Causal Model of Organizational Performance and Change is a system-based diagnostic framework created by W. Warner Burke and George H. Litwin in 1992. Unlike static checklists, it maps explicit cause-and-effect relationships among twelve specific organizational dimensions to explain how external forces cascade through an enterprise to influence individual motivation and final performance. [1, 2, 3]

Evidence: Mixed. More empirically ambitious than most diagnostics here, and only partly validated. The transformational versus transactional distinction is the best-supported element: it corresponds to a real and repeatedly observed failure pattern, in which structural or procedural fixes are applied to problems rooted in leadership, strategy, or culture. The full twelve-factor causal structure — including the specific direction and strength of each path — has not been confirmed, and some published tests find the hypothesized causal ordering only partially supported. Treat the tiers as sound and the individual arrows as hypotheses.

Use when: performance is declining and you need the root cause rather than the symptom; during deep cultural change; when previous fixes have not worked and nobody can say why.

Do not use when: you need a diagnosis this week. The model is data-heavy and requires significant stakeholder consultation across twelve interacting factors. For a rapid screen, use weisbord-six-box-model or mckinsey-7s-framework first, then come here when a specific breakdown is flagged.

The Input, Throughput, and Output Architecture

The model is structured hierarchically, showing that changes at the top or outer rings exert a dominant causal flow downward into internal operations and individual behaviors. [2]

  • Input (1 Factor):
  1. External Environment: Market conditions, competitors, regulations, technologies, and economic factors outside the organization that act as the ultimate trigger for adaptation. [1]
  • Throughput - Transformational Factors (3 Factors): These deep-seated levers alter the fundamental character and identity of the enterprise (transformational change).
  1. Mission and Strategy: What the organization aims to achieve and its fundamental approach to competing.
  2. Leadership: The executive behaviors and role-modeling that set the tone and direction for the system.
  3. Organizational Culture: The shared values, unwritten rules, norms, and core beliefs that define "the way we do things here". [1, 3, 4, 5]
  • Throughput - Transactional Factors (7 Factors): These everyday operational mechanisms respond to the transformational tier and drive incremental alignment (transactional change).
  1. Structure: The formal hierarchy, reporting lines, and allocation of decision rights.
  2. Management Practices: How managers execute strategy through prioritization, planning, and resource deployment.
  3. Systems (Policies & Procedures): The formal routines, IT tools, and standard operating processes.
  4. Work Unit Climate: The localized team atmosphere, trust levels, and psychological safety.
  5. Task Requirements & Individual Skills: The technical and interpersonal capabilities required versus the actual talent profile.
  6. Individual Needs & Values: What specific employees care about (autonomy, recognition, purpose) relative to rewards.
  7. Motivation: The psychological engine and energy level that converts workplace experience into effort. [3, 6]
  • Output (1 Factor):
  1. Individual and Organizational Performance: The final result (productivity, revenue, retention, customer satisfaction) that feeds back up to influence the external environment. [3, 7]

Core Mechanics and Change Logic

  • Transformational vs. Transactional: A key utility of the model is telling leaders when they face a transformational challenge (requiring shifts in strategy, leadership, or culture) versus a transactional challenge (tweaking structure, systems, or climate). Trying to fix a cultural or strategic misfit with a surface-level restructuring will stall out. [6]
  • Motivation as a Mediator: Employee motivation sits near the bottom as a central clearinghouse. How workers experience the upstream structure, climate, and management practices directly dictates their motivation, which dictates performance. [3]

Examples by audience

  • Health care: falling performance on a pathway, traced upstream, typically lands at management practices and work unit climate — not at individual skills, which is where a retraining programme would have been aimed. The model earns its cost here by preventing an expensive intervention at the wrong tier.

  • Software: a delivery slowdown traced upstream usually lands at structure and systems — coupling, approval gates, shared pipelines — not at motivation, which is where an engagement programme would have been aimed. See conways-law and dora-metrics.

  • Executive: the model's chief executive value is preventing you from authorizing a restructure to solve a leadership problem, including when the leadership problem is your own. That is also why executives find it uncomfortable, and why the contracting conversation in entry-and-contracting matters before you start.

Limitations

  • Data-heavy and slow: twelve interacting factors require real stakeholder consultation, not a workshop.
  • More than most groups will hold in mind at once; the tiers are easier to teach than the individual paths.
  • The causal arrows are the least validated part. Treat the transformational and transactional tiers as sound, and any specific path as a hypothesis.

Questionnaire

A paired, copy-and-use diagnostic instrument for this model: burke-litwin-causal-model-questionnaire.

Sources

[1] https://mutomorro.com [2] https://lemonlearning.com [3] https://umbrex.com [4] https://lemonlearning.com [5] https://mutomorro.com [6] https://thinkinsights.net [7] https://www.youtube.com

Organizational Development — a comprehensive practitioner's guide to OD for health care professionals, software engineers, and senior executives. Every framework says what the evidence is, and where it is weak.

Source and contributions: github.com/organizational-development. Built with the Lily Design System™.