Westrum Organizational Culture Typology Questionnaire

To assess how information flows in your organization, use this questionnaire. Part A is the six-item scale validated in software delivery research. Part B places the unit in one of the three types across all seven of Westrum's dimensions. Part C records behavioral evidence.

See westrum-organizational-culture-typology.

Evidence: Good. Unusually strong for a culture instrument. The typology was developed from safety-critical industry case studies, then operationalized as a six-item scale and validated in large-sample software delivery research, where generative culture statistically predicts both delivery performance and organizational performance. The evidence is correlational and self-report, and the typology flattens what is really a continuum — but the chain from this construct to outcomes is better established than almost anywhere else in this collection.

Before you run it

• Team level and above. Never individual.
• Minimum five responses.
• Short enough to run quarterly, which is how it is most useful — the trend matters more than any single administration.
• A genuinely pathological unit may report itself as generative out of fear. Read Part A alongside the behavioral evidence in Part C, always.

Part A: The six-item scale

Rate each 1 (strongly disagree) to 7 (strongly agree). Adapted from the published scale.

1. On my team, information is actively sought.

   • Rating (1–7): [ ]

2. Messengers are not punished when they deliver news of failures or other bad news.

   • Rating (1–7): [ ]

3. Responsibilities are shared.

   • Rating (1–7): [ ]

4. Cross-functional collaboration is encouraged and rewarded.

   • Rating (1–7): [ ]

5. Failure causes inquiry.

   • Rating (1–7): [ ]

6. New ideas are welcomed.

   • Rating (1–7): [ ]

Mean: [ ]

Part B: Type placement

For each dimension, mark which column describes your unit as it actually behaves — not as its policies say. Answer for the last six months, and for the worst week rather than the best.

Count: Pathological [ ] Bureaucratic [ ] Generative [ ]

Read the columns as a whole rather than averaging. The rows co-occur because they all follow from the orientation: an organization that shoots messengers also discourages bridging and crushes novelty.

Part C: Behavioral evidence

Perception scores can be optimistic. These are observable.

1. The last serious failure. What was the first question asked — who, which rule was broken, or what about our system made this the reasonable thing to do?

   • Answer:

2. The last bad-news bearer. Name the last person who raised a serious problem early. Where are they now, and what happened to them?

   • Answer:

3. Escalation latency. How long between a problem being known at the front line and being known by the person who can fix it?

   • Duration: [ ]

4. Distortion. When bad news reaches senior leadership, how much has it been softened on the way? Compare an incident as first reported locally with how it appeared in the board paper.

   • Answer:

5. Undelivered news. Ask your direct reports what they did not tell you last quarter. Record both the answer and your own reaction to it.

   • Answer:

6. New ideas. Of the last five suggestions from outside the leadership team, how many were implemented, how many died in process, and how many were dismissed?

   • Implemented [ ] Died in process [ ] Dismissed [ ]

Analysis

• Item 2 is the load-bearing item. "Messengers are not punished" predicts the rest. If it scores below 4, treat every other score as unreliable: in a unit where bad news is punished, a survey is also bad news.

• "Failure leads to inquiry" is the diagnostic row in Part B. Pathological cultures ask who, bureaucratic cultures ask which rule, generative cultures ask what about our system. Only the third produces learning; the other two produce hidden information, which is the precondition for the next and larger failure.

• Mixed Part B counts are normal and informative. Most units are bureaucratic with pathological edges under pressure. The dimensions that go pathological when the organization is stressed are the ones to work on, because that is when information matters most.

• Compare Part A and Part C. A high scale score with a Part C item 2 answer of "they left six months later" means the scale is measuring what people believe it is safe to say. Trust the behavior.

• Part C item 5 is the fastest executive diagnostic in this repository. Ask it, and then watch your own reaction. The reaction is the finding, and it is the mechanism by which the culture is produced.

• One senior leader reacting badly to bad news once can undo a year of improvement. That asymmetry is the whole problem, and it means the intervention is nearly always leader behavior rather than a programme.

• Expect reporting to rise as the score improves, and brief leadership before it does. Rising near-miss and incident reports are the signature of a unit becoming generative, and they will be read as deterioration by anyone not told in advance. See measurement-and-metrics.

• Pair with delivery or safety outcomes. This is one of very few culture constructs with a demonstrated link to performance, so measure both and look at them together. See dora-metrics for the software chain, high-reliability-organizations for the safety one, and psychological-safety-questionnaire for the team-level counterpart.