Quality Culture & Empowerment
The observable behaviors — reporting, stop-work authority, Just Culture — that decide whether the quality system tells the truth.
Culture is what determines whether every other domain is telling the truth: audit trails stay honest, deviations surface early, and investigations reach real causes only when it is safe to be honest. SPEQ scores this domain through observable behaviors — how problems actually surface and what authority frontline staff actually hold — because psychological safety cannot be honestly self-rated by a single respondent. It maps directly onto the FDA QMM Employee Empowerment and Engagement practice area, the one teams most often under-invest in.
The observable evidence a practitioner — or an inspector — would expect at each maturity level. Drawn from the assessment questions themselves.
How do errors, deviations, and near-misses actually surface in your organisation?
Problems surface late — found by QA review or audit rather than reported by the people involved
Reporting channels exist, but self-reporting a mistake is rare and feels risky
Deviations and near-misses are routinely self-reported; investigations ask how the system allowed it before who did it
Speak-up and near-miss rates are trended as leading indicators and reviewed at management review
High-trust reporting culture: near-miss analytics drive preventive action, and reporting health is benchmarked across the network
What authority do frontline staff have when they see a quality problem?
No defined authority — work continues until a supervisor or QA steps in
Escalation is informal; whether someone speaks up depends on the individual and the supervisor
A documented, trained right to stop the line, reject material, or escalate — with a defined response
Stop-work authority is used in practice and visibly backed by leadership; responses to error follow a written Just Culture standard
Closed-loop empowerment: stop-work signals and frontline improvement ideas are tracked to action, with culture-health metrics reported to leadership
- ›Investigations stop at "human error" and retraining because deeper system causes are never safe to name — a failure to thoroughly investigate discrepancies.
- ›Records completed in advance, backdated, or pre-softened under production pressure — data-integrity findings whose root cause is cultural, not technical.
- ›Operators aware of recurring defects or procedural workarounds with no expectation or protected channel to report them — surfaced in inspection interviews.
- ›Repeat deviations with identical root causes because near-misses go unlogged — the system cannot learn from what people are afraid to report.