Teams perform the way the system treats them.

Two practices hire from the same schools, pay similar rates, and serve the same community. In one, a new medical assistant notices a medication discrepancy and says so out loud, and the chart gets corrected. In the other, the same person notices the same discrepancy and stays quiet. The difference is not the person. It is what each system taught its people about speaking.

A quiet team is not always a calm team. Sometimes it is an early warning system that has been switched off.

The psychology is well mapped

Amy Edmondson’s research established psychological safety, the shared belief that a team is safe for questions, concerns, and admissions of error, as what allows teams to learn and improve.¹ Her earlier hospital research produced the finding worth holding onto: the better-led units reported more errors, because reporting was safe enough to do.² Google’s internal study of its own teams reached a similar conclusion, ranking psychological safety first among the dynamics that separated effective teams.³

Project Aristotle 2016 · Edmondson 1996, 1999 · ISMP survey cited in Joint Commission Sentinel Event Alert 40

The Joint Commission has named intimidating and disruptive behaviors as a threat to a culture of safety, linked to errors and preventable adverse events, and its leadership standards call on leaders to build and maintain that culture.⁴ California has written reporting into regulation: workplace violence prevention rules for health care settings, and for most other employers, require a written plan, training, an incident log, and protection for staff who report.⁵

Mechanisms, not posters

1. A daily huddle A standing agenda where every role speaks.
2. An escalation protocol Concerns route by procedure rather than by courage.
3. Debriefs after hard events The process is examined before the person.
4. Reporting that changes something Staff report as often as reporting proves useful.
5. Recognition of the right behavior Thanks for the flag, not only for the heroics.
6. More than one reporting path Written into the plan and known before anyone needs it.

What gets reinforced gets repeated. If raising a concern earns a sigh, concerns fade. If flagging a scheduling error earns a thank you and a workflow change, flags continue. Every practice is already running a behavioral system. The opportunity is to design it.

For small practices and behavioral health programs, where teams are close and every relationship carries weight, this is the multiplier on everything else. The clinical talent is real. The environment the system builds around it decides how much of that talent reaches the patient.

Starting points

Five mechanisms any practice can start this month.

1. Start a ten minute huddle. Same time, same three questions: what happened, what is coming, what is in the way.
2. Thank the first flag. Publicly recognize the next person who raises a concern, and share what changed.
3. Measure your culture. Run AHRQ’s free Medical Office Survey on Patient Safety Culture.
4. Add a second reporting path. Make sure at least one route sits outside the direct chain of command.
5. Debrief one hard event. Ask what allowed it, and document the system change.

Resources