Dental laboratory · 14 technicians
Rework that everyone could see and nobody would raise
A lab kept absorbing remakes it did not cause. The pulse showed a speak-up problem between the bench and the client-facing side, not a technical one.
Illustrative composite scenario. Built from the DentalDNA™ instrument design and common deployment patterns to show how a wave runs in a working practice and how an owner reads the output. It is not a report of a named client engagement and the figures are modeled examples rather than measured customer results.
- Setting
- Independent dental laboratory serving 40 practices
- Respondents
- 12 of 14 technicians and coordinators
- Instruments
- Dental Team Health Pulse™, plus Leader Readiness for the lab manager
- Cycle
- Baseline, 90 days, re-pulse
The situation
- Remake rates were climbing and the owner assumed a skill gap on the bench.
- Technicians privately knew which incoming cases were under-prepped but flagged nothing.
- The client-facing coordinators did not want to challenge a practice and risk the account.
How the wave ran
One anonymous wave
Bench and coordinators together, since splitting fourteen people would identify them.
Protect the threshold
The wave stayed open until it cleared five responses comfortably; no team was redefined to force a report.
Look for the gap
The manager's readiness report and the team pulse disagreed on how disagreement was handled, that became the debrief.
One process change
The lowest dimension the team could feel within thirty days.
What the data showed
| Dimension | Reading | What it meant |
|---|---|---|
| Speak-up safety | Lowest dimension | Raising a bad impression felt like accusing a client, so nobody did it. |
| Role clarity | Developing | Nobody owned the decision to reject an incoming case. |
| Workload and pace | Strained but not critical | Rework, not volume, was eating the hours. |
| Recognition | Strong | The manager was well regarded, which is why the fix stuck. |
What the practice changed
- Named one person per shift with the explicit authority to reject an incoming case.
- Created a two-line case flag that went to the practice, sent by the lab, not by the technician.
- Manager worked their readiness priority: handling disagreement without smoothing it over.
- Reported remake causes back to the bench monthly, by category, never by name.
The ninety days
- 1.Days 1-30: rejection authority named and announced; flag template in use.
- 2.Days 31-60: monthly remake causes shared with the bench.
- 3.Days 61-90: re-pulse and compare speak-up safety and role clarity.
Owner takeaway
The bench was never the problem. The lab was paying for a conversation nobody felt safe having with a client.