CASE STUDY
When Local Improvement Wasn't Enough
How St. Clair Hospital scaled a Lean culture across 2,400 employees with a two-person improvement team
At a glance
- 328-bed independent community hospital
- 2,400+ employees across hospital, outpatient centers, and physician network
- Member of the Mayo Clinic Care Network
- 1,600+ employees trained in Toyota principles
- 1.4 FTE dedicated to Lean coaching
The organization
St. Clair Hospital is a 328-bed independent community hospital in the southern suburbs of Pittsburgh, Pennsylvania. Independent is unusual in a region dominated by two large healthcare systems -- one of the hospital's leaders has described St. Clair as "the Switzerland of the area." The organization serves more than 2,400 employees across the main hospital, several outpatient centers, and a growing integrated physician network. St. Clair is a member of the Mayo Clinic Care Network.
The Lean journey began in 2008 when a new CEO arrived with prior exposure to the Toyota Production System through Paul O'Neill and the Pittsburgh Regional Health Initiative. Tania Lyon, PhD, was recruited as the first Director of Organizational Performance Improvement -- a role that didn't exist before she filled it. Over the following years, the program trained more than 1,600 St. Clair employees in Toyota principles and methods.
By any standard, the program worked. Patient satisfaction percentile rankings climbed steadily. Quality, safety, and financial indicators all moved in the right direction. But midway through the journey, Tania's team hit a structural ceiling that had nothing to do with the quality of their Lean work and everything to do with the infrastructure supporting it.
The system before
The hospital had introduced paper-based idea boards in every department two years into the journey. More than one hundred laminated boards across the facility. Pre-printed Post-it notes for capturing ideas. A defined workflow: green light moves an idea forward, red light returns it with an explanation, escalation to a spreadsheet for items beyond local authority.
The boards worked for five years.
They produced ideas. They made improvement visible at the local level. They gave leadership a focal point for safety rounds -- a rotating group of leaders would visit two departments every Wednesday at 10 a.m., huddle with available staff, look at the board, and capture observations. Tania often carried a pack of Post-it notes herself, writing down ideas as staff shared them verbally and sticking them on the board to demonstrate that what was raised was heard.
What worked locally didn't scale. What was on one department's wall was invisible to every other department. A team on one floor was solving a problem another team would have wanted to know about, and there was no way to surface the connection. Some boards hummed with activity. Others gathered cobwebs. That unevenness was a coaching opportunity -- but with only two part-time Lean coaches supporting 2,400 employees, Tania couldn't be everywhere.
The deeper problem was measurement. As Tania put it:
"I had no way to measure whether our improvement culture itself was improving."
The metric she most needed to manage was the one her system couldn't produce. Every time she considered asking managers to translate their paper records into spreadsheets and reports, she backed off -- managers were overworked as it was, and the waste of generating that data manually would have exceeded its value.
The turning point
By the fifth year of running paper boards, two things had changed. The culture had matured to the point where surfacing ideas was just an expectation -- the visibility-on-the-wall function of physical boards was no longer as essential. And Tania had reached the limits of what she could see, measure, and coach with the existing system.
After evaluating several vendors, St. Clair selected KaiNexus. The decision was partly about feature fit and partly about culture fit -- the platform itself emerged from Lean thinking, which meant conversations with the vendor team used the same vocabulary Tania's team used internally.
Hear the story in Tania's own words:
How they rolled it out
Four deliberate choices defined the rollout.
They went slowly. Department by department over two years, on a planned schedule. Each onboarding was treated as a culture conversation, not a software training. One-on-one with each manager: what are we trying to do as an organization, what's your role in supporting it, how does this tool help.
They piloted first. The pharmacy went first -- data-driven, scientifically minded, strong management support. The pilot exposed integration questions and gave the team a working template before expansion. A pharmacy manager who initially resisted the switch eventually became one of the platform's strongest advocates, finding uses Tania's team hadn't anticipated.
They engaged the chain of command. Most of the rollout effort focused on directors and managers rather than frontline staff. With limited central coaching resources, the local management chain had to be the help chain. Directors hold managers accountable. Managers serve as platform champions for their teams. The Lean coaches focus their hours where the highest leverage lives.
They standardized the rollout itself. After the pharmacy pilot, the team developed a repeatable checklist for each department onboarding -- the order of steps, the communication plan, the meetings, the training touchpoints. Lean discipline applied to the rollout of a Lean platform.
The unplanned accelerator
The biggest surprise came from a regulatory requirement.
CMS requires every department to develop an annual performance improvement plan. For years at St. Clair, this had been a check-the-box exercise -- managers filled out a template, turned it in, the form went into a binder, no one revisited it. The hospital had been gradually making PI plans more meaningful by moving them onto A3 templates, but the artifact still felt like a form.
The team realized they could put all PI plans into KaiNexus immediately, well before the department-by-department rollout would have reached every manager. They did. The entire leadership team learned the platform faster than planned. Instead of dreading another system, leaders started pulling for it because the platform made their PI plans visible, collaborative, and useful in a way the paper version never had been.
The rollout accelerated from there.
A further refinement followed a year later. PI plans had initially been A3 forms uploaded as files -- functional, but static. Managers filled out the A3 at the end of the project as a report rather than using it during the project as a thinking guide. When the A3 template was integrated directly into the platform, the document became living -- editable, accessible, and usable as a worksheet. That shift required additional coaching with managers about what A3 thinking actually is, but the platform now supported the discipline rather than fighting it.
Building accountability into the system
One of the more sophisticated configurations was how St. Clair pushed accountability into the existing chain of command rather than centralizing it in the Lean team.
The standard expectation: no idea should sit unassigned longer than seven days. The platform allowed something the paper system couldn't -- automatic surfacing of bottlenecks at higher levels. Directors' default boards show only ideas that have been unassigned for more than 14 days, stuck in overdue status for more than 14 days, or waiting for approval that long. The board becomes a tool for the conversation a director needs to have with a manager who's falling behind.
The same logic extended upward to vice presidents, who received customized bottleneck boards covering all their areas of responsibility. The Lean coaches no longer had to function as enforcers. The system surfaces the issues to the people whose job it is to address them.
The results
Two metrics tell the clearest story of what changed.
In year one of platform adoption, 45 percent of submitted ideas resulted in change. The most common idea category was staff satisfaction -- often environmental and convenience-oriented suggestions, the predictable pattern that emerges when staff first realize they have a real channel for input.
In year two, the completion rate rose to 66 percent. The most common idea category had shifted from staff satisfaction to quality improvement.
That shift didn't happen on its own. Tania's team did focused training with managers on how to respond to staff ideas -- specifically, how to walk past a proposed solution back to the underlying problem and coach the staff member to articulate it better. Her standing example: a staff member proposes free pizza parties every Friday because morale is poor. The manager's reflex is to reject the solution. The Lean-coaching response is to dismiss the solution but pursue the observation.
"I'm interested in your observation that morale is poor. What evidence do you have?"
The visible improvement in metrics is a function of the invisible work of coaching managers to coach their staff. The platform made that invisible work surface-able. Tania could now see how managers were responding to staff ideas and intervene where intervention was helpful. The data drove the coaching. The coaching changed the pattern. The next cycle's data reflected the change.
Year one to year two
- Idea completion rate: 45% → 66%
- Most common idea category: staff satisfaction → quality improvement
Tania's framing
Asked late in a webinar to describe what the platform had become for her team, Tania reached for a clinical analogy that lands hard with healthcare audiences.
"What KaiNexus has been for our Lean team is that status board that gives us a window into the improvement work -- and maybe even more importantly, the improvement culture of the organization."
The reference is to the electronic patient status board in St. Clair's emergency department -- a living view of every patient's stage, every order's status, every waiting moment that needs attention. Not historical data. Living information that drives action in the moment.
KaiNexus, in Tania's framing, became the same kind of operational dashboard for the work of getting better.
What it took
The St. Clair story is not a story about software replacing leadership work. The platform amplified what the coaching produced. Without the coaching -- the standard work, the A3 discipline, the conversations about how to respond to staff ideas, the choice to go slowly and engage managers as champions -- the platform would have produced tracked-but-shallow improvement.
With it, a two-coach team built something that reaches across 2,400 employees, surfaces bottlenecks to the people who can address them, demonstrates measurable culture change with real data, and gives the cumulative impact of small Kaizen improvements the visibility they need to be defensible to leadership.
St. Clair continues to use KaiNexus as part of its ongoing Lean program.
The lessons travel. The infrastructure problem St. Clair hit at five years into their paper-board journey is the same infrastructure problem most CI programs hit at some point. The choices Tania's team made about how to solve it -- slow rollout, manager-first engagement, accountability pushed into the existing chain of command, coaching the coaches -- are reproducible in any organization willing to do the work.
About the work described in this case study
Tania Lyon, PhD served as the first Director of Organizational Performance Improvement at St. Clair Hospital, where she led the Lean transformation effort and the team's transition from paper-based idea boards to KaiNexus. She had previously spent five years with the Pittsburgh Regional Health Initiative (PRHI), where she helped develop the nonprofit's nationally acclaimed healthcare professional curriculum and coached Lean improvement efforts across multiple healthcare settings. Tania holds a PhD in Sociology from Princeton University and a BA in Peace and Conflict Studies from UC Berkeley.
.svg)
Add a Comment