Westrum Typology & CALMS

Two frameworks that operationalize "culture eats strategy for breakfast." Westrum predicts performance; CALMS prescribes practices.

Overview

Westrum and CALMS

Two frameworks every senior DevOps engineer should be able to discuss precisely. Westrum tells you WHERE you are; CALMS tells you WHAT TO DO to move toward Generative.

Westrum organizational typology — Ron Westrum, 2004 paper "A Typology of Organisational Cultures" — Cultural assessment
CALMS — Jez Humble and John Willis, ~2010, extended from CAMS by adding Lean — Operational pillars

Westrum organizational typology

Westrum studied aviation safety and healthcare. He found three types of organizations, distinguished by how they handle information.

Pathological — Information hoarded for personal advantage; messengers punished; failure scapegoated; novelty suppressed; bridging across silos discouraged — A manager who knows about a coming disaster and doesn't tell their boss because telling would reflect badly on them
Bureaucratic — Information follows official channels; departments defend turf; rules trump mission; novelty meets "not invented here" — A process everyone knows is broken but nobody can change because "that's the procedure"
Generative — Information flows freely to where it's needed; teams bridge silos; failure investigated for systemic learning; mission over position; novelty encouraged — An engineer who finds a bug in another team's code DMs that team and fixes it together, regardless of hierarchy

The evidence

The Accelerate research (Forsgren, Humble, Kim, 2018) ran statistical analysis on multi-year DORA survey data. Generative cultures STRONGLY PREDICT software delivery performance: the four DORA metrics all correlate with Westrum scores.

> [!IMPORTANT] Culture is not a "soft" concern. It is the LIMITING FACTOR for software performance. You can't out-engineer a Pathological culture.

CALMS: the prescription

CALMS is the prescription side: five operational pillars.

Culture — Shared accountability between dev and ops; no "throwing over the wall"; on-call, goals and metrics shared
Automation — Eliminate manual repetition: CI/CD, IaC, configuration management, testing, deployment, monitoring, runbooks. The 50% rule (SRE-style) caps manual toil
Lean — Continuous improvement; eliminate waste; reduce batch sizes; surface and remove queues. Adapted from the Toyota Production System and Lean manufacturing
Measurement — Measure outcomes (DORA metrics, customer satisfaction, error budgets), not vanity metrics (lines of code, hours worked)
Sharing — Knowledge transfer across teams: communities of practice, internal blogs, documentation, postmortems published broadly, public conference talks

The predecessor CAMS (Damon Edwards, John Willis, 2010 Velocity Conference) had four pillars. Humble added Lean explicitly because the Lean influence was under-recognized.

The interview test

Place an organization on the Westrum typology with specific evidence
Map a specific dysfunction to a CALMS pillar
Explain why culture (Westrum) is upstream of practice (CALMS)
Cite Accelerate as the empirical foundation

Key concepts

Pathological organization: Power-oriented. Information hoarded; messengers punished; failure scapegoated; novelty suppressed. Predicts low DORA performance. Engineers leave; recruitment is hard.
Bureaucratic organization: Rule-oriented. Silos defend turf; rules > mission; novelty leads to "not invented here." Mid-range DORA performance. Stable but slow.
Generative organization: Performance-oriented. Information flows to where it's needed; bridging across silos; failure investigated for learning; mission > position. Predicts high DORA performance. Engineers stay; recruitment is easy.
CALMS: Culture, Automation, Lean, Measurement, Sharing. Jez Humble extension of John Willis' CAMS. The five operational pillars of DevOps practice.
Culture is upstream of practice: You can mandate practices (CI/CD, automation, postmortems) but they only stick in the right cultural soil. Pathological cultures perform CALMS practices as compliance theater. Generative cultures perform them as natural extensions of values.
Accelerate (the empirical foundation): Forsgren, Humble, Kim (2018) ran rigorous statistical analysis on 23,000+ survey respondents and found Westrum + technical practices PREDICT DORA performance. The first software-engineering management research with statistical rigor.

When to use it

Diagnosing a stalled DevOps transformation — Westrum typology often reveals "culture limits practice"
Onboarding into a new team or company — quickly assess Westrum type via 1:1 conversations
Designing organizational change — CALMS as the operational checklist of practices to shift
Justifying engineering investment to leadership — Accelerate's correlation between Generative culture and business performance

Interview questions

How do you assess whether an organization is Pathological, Bureaucratic, or Generative?
Walk me through CALMS and how each pillar shows up.
How do CALMS, Westrum, and DORA relate?