Hospital core laboratory · 3 sections
A quiet lab is not always a safe lab
A core lab with almost no reported incidents used the Laboratory Operations & Quality Culture Assessment™ to test whether the silence meant safety or fear.
Illustrative composite scenario. Built from the HealthDNA™ instrument design and common deployment patterns to show how a wave runs and how leaders read the output. It is not a report of a named client engagement and the figures are modeled examples rather than measured customer results.
- Setting
- Hospital core lab: chemistry, hematology, microbiology
- Respondents
- 34 MLS, MLT and phlebotomy staff
- Instruments
- Lab Operations & Quality Culture, Just Culture & Psychological Safety
- Cycle
- Baseline, section-level readout, re-pulse at 90 days
The situation
- n/aIncident reporting was near zero and leadership read that as a strong quality program.
- n/aMeanwhile turnaround-time complaints from the ED were rising and two experienced techs had just resigned.
- n/aSection supervisors disagreed about whether workload or competency was the problem.
How the wave was run
Report by section
Chemistry, hematology and micro were reported separately, each held to the five-respondent minimum.
Pair the two instruments
Quality culture explains the process; psychological safety explains whether anyone will say the process broke.
Give sections their own data
Each supervisor got only their section plus the lab-wide comparison, which kept the conversation local.
What the data showed
| Dimension | Reading | What it meant |
|---|---|---|
| Speak-up and reporting behavior | Lowest in the lab | The low incident count reflected reporting reluctance, not the absence of events. |
| Workload and staffing load | At risk in one section only | The strain was concentrated, not lab-wide, so a lab-wide fix would have missed it. |
| Competency and training | Solid | The retraining plan leadership had drafted would have solved the wrong problem. |
What leadership changed
- ✓Reframed near-miss reporting as a quality metric to increase, with a monthly count target.
- ✓Published what changed after each reported event, by section.
- ✓Rebalanced staffing in the one section carrying the load instead of across the whole lab.
- ✓Held section-level readouts rather than one all-staff meeting.
The 90-day cadence
- 1Days 1-30: section readouts and the near-miss reframe.
- 2Days 31-60: staffing change in the strained section; monthly "what changed" note.
- 3Days 61-90: re-pulse and compare speak-up scores section by section.
Low event counts are an ambiguous signal. Pairing quality culture with psychological safety told leadership which kind of quiet they had.
Instruments used
Ready to run your own wave?
Run this scenario in your organization
Tell us the setting and we will show the instrument, a sample unit report and what a first pulse would look like.
No PHI is ever collected. We only use this to schedule a walkthrough.