Somewhere in your health system right now, a team is doing something remarkable. They spent a week last month rethinking how patients move through pre-op. They ran experiments, hit some dead ends, and landed on something that cut prep time by 20 minutes. The department knows. The staff who work directly with that unit know. The data is in a folder or on a wall somewhere.
Everyone else? They have no idea.
This is one of the quieter problems in healthcare improvement work. A continuous improvement event or value stream is an investment of time, energy, and trust. When the work stays inside the unit where it happened, that investment pays only a fraction of what it could. The pharmacy team running their own improvement event next quarter doesn't know what pre-op learned. The night shift supervisor who has the same friction in a different department never hears the story. Leadership can't connect the dots across the organization because the dots were never shared.
Internal communication is the mechanism that turns departmental events and wins into organizational learning.
Stories about improvement move through many channels. They show up on visual management boards where teams gather for daily huddles. Leaders bring them into conversations during rounding. Managers share them during shift updates so that staff working evenings or nights hear the same message as those who worked earlier in the day. Internal newsletters, digital platforms (including video recorded on a phone), and staff meetings all become part of the system that helps the learning spread.
The effort a team puts into an improvement event becomes part of a larger story about how the organization is learning and evolving.
As for that story, don’t report just the metrics; include the human thread. What was happening before? Who was frustrated, and why? What did the team try that didn't work? What changed, and what does it mean for the people on that unit and the patients they care for? Is there a patient testimonial or quote that shows the direct patient impact? Staff can connect with the story, repeat it, and see themselves in it. It also signals to every other team that their work is worth telling.
The words you use are also important. Improvement work has its own vocabulary, and some of it is negative and awful.
- It’s not “Unit 4 completed an event.” It’s “The team on Unit 4 found a way to give nurses back 20 minutes per shift.”
- It’s not “supply retrieval time increased by 23%.” It’s “Our nurses were walking nearly 4 miles a shift just searching for supplies.”
- It’s not about “eliminating waste.” It’s about removing steps that don’t add value for
patients or staff.
- It’s not about “fixing inefficiency.” It’s about reducing friction in a caregiver’s day.
When organizations get this right, when they build a real rhythm of sharing improvement work across shifts, departments, and roles, something starts to shift. People stop seeing change as something that happens to certain units and start seeing it as something the whole organization is doing together. They bring ideas forward. They ask, "Has anyone else tried this?" They start feeling like they're part of something rather than just adjacent to it.
Submit a comment