Quality Culture Audit Worksheet
The team said "on track, no blockers" at every standup for a month. The bug tracker disagreed, and nobody had compared the two.
A new engineering lead spent her first fortnight in one-to-ones, where everyone called the team careful and collaborative. When she finally read the tracker, one timeout bug had been closed as stale twice and most incident notes named the same engineer. The flaky test suite had appeared in five consecutive retros with no owner.
(Composite example, assembled from patterns common in teams that describe themselves more confidently than their records do. The figures are illustrative.)
Working records beat self-description. Schein calls them artifacts, the visible layer above espoused values and assumptions. This worksheet starts from that end: a timed read of five sources, four vital signs, a diagnosis using Westrum's culture types, and rules for acting. Your window of outsider clarity is limited; many leaders use the first 90 days as the rule of thumb. As a further rule of thumb, thirty minutes of reading gives a first, evidence-based picture, often sharper than the team's own account.
One of the most honest records a team keeps is its bug tracker, because nobody polishes it for an audience. (ShiftQuality's view.)
Read in the open. Tell the team what you are reading and why; covert reading costs trust you will need.
Step 1: the thirty-minute read
Read the content, not the summary numbers.
Ten random bug tickets from last month (5 min)
☐ Written with care, or copied and pasted?
☐ Who responds, and in what tone?
☐ Do the same bugs recur under different IDs?
☐ Closed because fixed, or because stale?
Noticed: ______
Three pull request threads, full history (10 min)
☐ Do reviewers engage, or rubber-stamp?
☐ Do the same few names review most changes?
☐ Are disagreements settled technically or socially?
☐ Do nitpicks outnumber substantive comments?
Noticed: ______
The last retro notes (5 min)
☐ Are action items assigned to people, or only listed?
☐ Do earlier items return as completed, or as repeated complaints?
☐ Which complaint never resolves, because the team has stopped fighting it?
Recurring complaint: ______
Last week of the main engineering channel (5 min)
☐ Are questions answered with trusted doc links, or one-off replies?
☐ What does the team joke about? Teams often joke about what they cannot fix.
Noticed: ______
On-call schedule and the last three incident write-ups (5 min)
☐ Does expertise rotate, or do a few people carry it?
☐ Is there a plan to change that load?
Noticed: ______
Step 2: score the four vital signs
Vital sign | How to read it | Your reading |
Standup-versus-tracker gap | Compare standup claims with what reaches the tracker over the next two weeks. One of the most useful signals you have | ☐ Small ☐ Large |
Hero ratio | Share of incidents resolved by the top three engineers | ☐ Distributed ☐ Concentrated |
"We know" count | Specific problems met with "we know about that" | Count: ______ |
Documentation reflex | The usual first reply to a question | ☐ "Here's the doc" ☐ "Let me explain" ☐ "Ask a named person" |
The gap. A large gap is often a leadership problem in disguise: engineers often perform certainty when they believe leadership cannot handle uncertainty, which fits Edmondson's work on psychological safety.
The hero ratio. Concentration is a risk signal: the people carrying it are a single point of failure and a burnout risk. Treat "a leading indicator of attrition" as a rule of thumb, not a finding.
The count and the reflex. As a rule of thumb, a dozen "we know"s means the team has surrendered to problems that now shape its decisions. "Let me explain" means knowledge lives in heads; "ask a named person" means it is trapped in one.
Step 3: name the kind of team you have
Westrum sorts cultures by how information flows and how messengers are treated: pathological (power-oriented), bureaucratic (rule-oriented) and generative (performance-oriented). DORA uses the same typology in its software delivery research.
☐ Pathological ☐ Bureaucratic ☐ Generative
This team, under pressure, tends to ______.
The compensating habits holding it together are ______.
The one change that would help the most people is ______.
Step 4: act on what you find
☐ Resist fixing everything. The urge peaks straight after the audit.
☐ Keep compensating habits until replacements exist. Heroes and workarounds do real work.
☐ Change the thing that helps the most people first. Usually a small process change: a clearer on-call rotation, a real incident review, review pairing.
☐ Move at the pace of cultural change, measured in quarters, not weeks. A practitioner rule of thumb puts it at six to eighteen months. Move faster and the team performs the new culture, then reverts.
How to use it
Who: the leader who has just inherited the team, within the first weeks. Thirty minutes to read, a little longer to score and write up.
Output: five sets of notes, four vital signs, a Westrum placement and three completed sentences.
Done when: you can state the culture and its compensating habits in one paragraph, backed by artifacts, and you have chosen one first change.
Where this changes
A team of four or five can read in twenty minutes, and its hero ratio may just reflect headcount. A large or regulated organisation needs a week-long version: sit in on standups, reviews, a retro and an incident review, meet each engineer, and read six months of delivery and incident trends.
The reasoning behind this audit, with a worked first-week example, is in the quality culture audit. On owning the result rather than delegating it, read why leaders own quality. To track whether your first change works, pair this with quality metrics that actually matter.
Final takeaway
A team's records show its culture better than its own account. Read them early, openly, place the team on Westrum's scale, and change one thing at the pace culture actually moves.
Sources
Ron Westrum, "A typology of organisational cultures," Quality & Safety in Health Care 13(Suppl 2), ii22–ii27 (2004). https://doi.org/10.1136/qshc.2003.009522
DORA, Capabilities: Generative organizational culture (Westrum's types applied to software delivery). https://dora.dev/capabilities/generative-organizational-culture/
Edgar H. Schein, Organizational Culture and Leadership, 5th ed., Wiley (2017): levels of culture, from artifacts to basic assumptions.
Amy Edmondson, "Psychological Safety and Learning Behavior in Work Teams," Administrative Science Quarterly 44(2), 350–383 (1999).
Michael D. Watkins, The First 90 Days, Harvard Business Review Press (2003; updated edition 2013): the 90-day transition frame.
