Paper idea boards work. For about five years.
That's not a knock on paper. It's the actual pattern Tania Lyon observed leading St. Clair Hospital's Lean transformation. Paper boards mounted in every department captured frontline ideas, made improvement visible at the local level, and gave managers a clear structure for responding to staff suggestions. They were inexpensive, low-tech, and easy to participate in. The hospital ran them successfully for five years.
Then the boards started costing the organization more than they were producing.
The improvement work itself was thriving. What had broken down was the system's ability to see what the improvement work was producing. A department on the second floor was working on something the third-floor team would have wanted to know about, and nobody knew the work existed. A manager was running a sophisticated improvement program; the manager next door wasn't, and there was no way for leadership to tell the difference at a glance. Tania, as Director of Organizational Performance Improvement, had no way to measure whether the improvement culture itself was improving -- the metric she most needed to manage was the one her current system couldn't produce.
This webinar is her account of what changed when St. Clair moved from paper to KaiNexus -- what they expected, what surprised them, what they had to relearn about coaching and leadership development, and what the second year of digital adoption looked like compared to the first. It's a practical case study, not a methodology talk. The lessons travel.
Tania Lyon is the first Director of Organizational Performance Improvement at St. Clair Hospital, a 328-bed independent community hospital in the southern suburbs of Pittsburgh. She has trained over 1,600 St. Clair employees in Toyota principles and methods. Prior to St. Clair, she spent five years with the Pittsburgh Regional Health Initiative developing their healthcare Lean curriculum. She holds a PhD in Sociology from Princeton and a BA in Peace and Conflict Studies from UC Berkeley.
St. Clair began its Lean journey in 2008 when a new CEO with prior exposure to the Toyota Production System (through Paul O'Neill and the Pittsburgh Regional Health Initiative) brought the approach to the hospital. Tania was recruited to build the program from scratch -- a position that didn't exist before she filled it.
She organized her department around three pillars: training, operations, and engagement. Training meant classroom introduction to Toyota principles -- every frontline employee attends at least a half-day class to establish shared vocabulary. Operations meant directly coaching strategic improvement projects. Engagement was the cultural work: getting a critical mass of employees thinking differently about their own work.
The paper idea boards launched in 2010 as the operational tool for engagement. Roughly one hundred laminated boards in departments across the hospital, with pre-printed Post-it notes for capturing ideas. A defined workflow: green light moves an idea right across the board, red light returns it with an explanation, and ideas that exceed local authority get escalated through a spreadsheet that Tania's department reviewed.
What worked: visibility at the local level, low barrier to participation, and a focal point for leadership rounding. St. Clair built a Wednesday-morning safety round practice where a rotating group of leaders would visit two departments, huddle with whoever was available, look at the board, and ask about safety concerns and ideas. Often staff would share ideas verbally that had never made it to the board -- Tania would write them on a Post-it on the spot and stick them up, demonstrating that ideas surfaced this way got captured rather than disappearing.
What didn't work showed up gradually. Boards in some departments hummed with activity. Boards in others gathered cobwebs. That unevenness was expected, but it had no remediation path. The work happening in active departments was invisible to anyone outside those departments. And Tania had no way to measure progress, because asking already-overworked managers to translate paper records into spreadsheets and roll-up reports would have created more waste than the data was worth. She kept backing away from that conversation for years.
By 2015, two things had changed. The culture had matured to the point where surfacing ideas was just an expectation -- staff knew this was how things worked, so the visibility-on-the-wall function of paper boards was no longer as essential. And Tania was hitting the ceiling of what she could see, measure, and coach with the paper system.
After evaluating several vendors, St. Clair selected KaiNexus, partly because of feature fit and partly because of culture fit -- the company itself emerged from Lean thinking, which meant the conversations with the platform team used the same language Tania's team used internally.
The benefits she names aren't surprising in the abstract, but the specifics are worth attention.
Transparency. What used to be siloed on department walls became visible across the organization. As coaches, Tania and her colleague could now see where work was being done, where it wasn't, and where the quality of work suggested coaching attention was needed. Two part-time coaches supporting an organization of 2,400 employees can't do constant rounding. Visibility lets them target where to spend their limited hours.
Collaboration across departments. St. Clair's engagement surveys consistently showed the same pattern: people rated cooperation within their department highly and cooperation across departments very poorly. Lean thinking is fundamentally about flow and customer-supplier relationships across handoffs. A shared platform where multi-department teams could see the same information and contribute on the same opportunity gave the cross-departmental work an infrastructure it had been missing.
Data on improvement culture itself. This was the one Tania had been waiting for. How many people are participating? How many ideas are resulting in action? What is the cumulative impact? And specifically: can we now show that small Kaizen improvements -- the kind that don't impress anyone individually but add up substantially in aggregate -- actually produce returns worth the discipline of capturing them? The data made the Kaizen case in a way no rhetorical argument could.
Tania's team made four deliberate choices about the rollout that are worth examining in detail, because the temptation in any technology adoption is to do the opposite of each.
They went slowly. Department by department, on a deliberate schedule. The two-year rollout plan reflected limited coaching resources, but the underlying reason was deeper. Each department onboarding was treated as a culture-of-improvement conversation, not a software training. One-on-one with each manager: what are we trying to do as an organization, what's your role as a manager in supporting it, how does this tool help you do that. The technology was the vehicle for the culture conversation, not the point of it.
They piloted first. The pharmacy department was the first to migrate. They were data-driven, scientifically minded, had strong management support, and were already documenting improvement work well on their paper boards. Tania learned the system through the pilot with them -- including discovering uses for the platform that her team hadn't anticipated. A pharmacy manager who initially resisted the switch eventually embraced it and started using KaiNexus in ways the original rollout plan didn't include.
They engaged the chain of command. Most of the rollout effort focused on directors and managers -- the help chain in Lean terms. Tania's department couldn't be the single point of support for 2,400 employees with two part-time coaches. The directors hold managers accountable. The managers serve as the local champions and primary support for frontline staff. The Lean coaches touch the system lightly with frontline staff and intensively with the management team.
They built and followed a standard checklist. After the pharmacy pilot, Tania's team developed a repeatable checklist for each department onboarding -- the order of steps, the communication plan, the meetings, the training touchpoints. This is itself a Lean discipline applied to the rollout: don't rebuild the process every time, codify what works and follow it consistently.
The biggest unplanned win came from a CMS requirement.
CMS requires every department to develop an annual performance improvement plan. For years, this had been a check-the-box exercise -- managers filled out a template, turned it in, and the form went into a binder nobody opened again. Over time, the hospital had been working to make PI plans more meaningful, transitioning them onto A3 templates so documentation was consistent across departments.
The original rollout plan didn't include putting PI plans into KaiNexus right away. It became obvious that the right move was to do exactly that. The result was unexpected: the entire leadership team learned KaiNexus immediately, and instead of dreading another system, they started pulling for it. The rollout accelerated from there.
The follow-up insight came a year later. PI plans started as A3 forms uploaded as files -- which worked, but felt static. People filled out the A3 at the end of the project rather than as a thinking guide during it. When the A3 template was integrated directly into KaiNexus, the document became living -- editable, accessible, and usable as a worksheet rather than a report. That shift required additional coaching with managers about what A3 thinking actually is (a guide for thinking, not a record of completed work), but the platform now supported the discipline rather than fighting it.
One of the more sophisticated moves Tania describes is how they configured KaiNexus to push accountability into the existing chain of command rather than into her department.
The expectation under the paper system had been that no Post-it should sit in the first column longer than seven days. The same expectation transferred to KaiNexus. But the platform allowed something the paper system couldn't: automatic surfacing of bottlenecks at higher levels of the chain.
Directors' default boards show only ideas that have been unassigned for more than 14 days, or stuck in overdue status for more than 14 days, or waiting for approval that long. The board is a tool for the conversation a director needs to have with a manager who's falling behind. It gives directors a low-friction way to hold managers accountable without requiring Tania's department to function as the enforcer.
The same logic extends upward to vice presidents, who have customized bottleneck boards covering all their areas of responsibility. The system enables the accountability conversation; the humans have the conversation.
The numbers Tania shares illustrate something worth attention. The first year of KaiNexus adoption, 45 percent of submitted ideas resulted in change. The most common idea category was staff satisfaction -- often environmental or convenience-oriented ideas, the predictable "release-valve" pattern that happens when staff first realize they have a real channel for suggesting things.
By 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 not to reject ideas out of hand when the proposed solution doesn't work, and instead to walk the conversation back to the underlying problem. Her example: a staff member proposes free pizza parties every Friday to address poor morale. The manager's instinct is to reject the solution. The Lean-coaching response is to dismiss the solution but pursue the observation. "I'm not sure that's the right solution, but I'm interested in your observation that morale is poor. Can you tell me what evidence you have to support that?" That conversation teaches staff how to articulate problems rather than solutions, opens up the solution space, and produces better-formed ideas in subsequent cycles.
The visible improvement in metrics is a function of the invisible work of coaching the coaches. KaiNexus 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 drives the coaching, the coaching changes the patterns, and the next cycle's data reflects the change.
St. Clair has 2,400 employees and 1.4 FTE dedicated to Lean coaching. Tania's training model reflects that constraint and is worth examining for any organization with similar resource ratios.
Frontline staff get minimum touch time -- usually a 10-minute demo during a department staff meeting. The functional ask is small: know how to log in and how to submit an idea. Everything beyond that can be learned through use and through manager support.
Managers get the deepest attention. One-on-one walkthroughs, half-hour classroom training when new functionality launches, ongoing coaching support on demand. The managers are the location leaders in KaiNexus and the real owners of the platform's success at the local level.
Directors get lighter engagement. They're included in the department kickoff meetings, they get their default bottleneck boards configured, and they're equipped to hold managers accountable -- but they're not asked to track everything themselves.
This stratification isn't just practical. It reflects the Lean help-chain model. The closer you are to the work, the more touch you need. The further from the work, the more your role is to support and remove obstacles. Tania's department applies that model to itself.
Late in the session Tania makes a connection that's worth pulling forward.
She describes the electronic status board St. Clair built in their emergency department as one of the most impactful improvements early in her tenure. The status board gave clinical staff a real-time view of every patient's stage, every order's status, every waiting moment that needed attention. Not historical data. Living information that drove action in the moment.
KaiNexus, she realized, had become her status board for the improvement work itself. It's open on her desktop all day. She's in and out of it constantly. It tells her where work is happening, where it's stuck, where coaching attention would help most. The metaphor is exact: a living view of improvement culture in the same way the ED status board is a living view of patient flow.
That framing is useful for anyone trying to explain why this kind of platform matters. It isn't a suggestion box. It isn't a project tracker. It's the operational dashboard for the work of getting better.
The St. Clair story illustrates several patterns that map directly to how KaiNexus is designed to support sustained improvement.
The transparency that lets a two-coach team monitor a 2,400-person organization. The accountability infrastructure that pushes responsibility into the existing management chain rather than centralizing it. The data on improvement culture itself -- participation, completion, impact -- that makes the small Kaizen approach defensible to leadership. The bottleneck filtering that surfaces where coaching attention belongs. The A3 integration that turns the thinking framework into a living workspace rather than a post-hoc report.
None of these substitutes for the leadership behaviors and coaching discipline that Tania's team built over years. The platform amplifies what the coaching produces. Without the coaching, the platform produces tracked-but-shallow improvement. With it, the platform makes a small team's reach scale to an organization that would otherwise overwhelm them.
Tania Lyon, PhD is the first Director of Organizational Performance Improvement at St. Clair Hospital, a 328-bed independent community hospital in the southern suburbs of Pittsburgh, where she has led Lean transformation efforts for seven years. She has trained over 1,600 St. Clair employees in Toyota principles and methods. Her background in Lean healthcare began at the Pittsburgh Regional Health Initiative (PRHI), where she spent five years helping develop the nonprofit's nationally acclaimed healthcare professional curriculum and coaching Lean improvement efforts across multiple healthcare settings. Tania is also interested in Lean applications for low-resource healthcare settings, including hospitals in Malawi and Haiti. She earned her PhD in Sociology from Princeton University and her BA in Peace and Conflict Studies from UC Berkeley.
When does a paper improvement system stop working?
When the work it produces becomes too distributed and too complex for the system to make visible. Paper idea boards work well at the local level -- one department, one manager, one team's worth of ideas. They start to fail when leadership needs to see patterns across departments, when teams need to collaborate across silos, when measurement of improvement culture itself becomes important, or when the manual effort of pulling reports from physical artifacts exceeds the value of doing so. St. Clair ran paper boards successfully for five years before hitting these limits. The right time to switch isn't a calendar date -- it's when the system itself becomes the constraint on further progress.
What does a slow, deliberate rollout look like?
Tania's team rolled out KaiNexus over two years, department by department, on a deliberate schedule with a repeatable onboarding checklist. They piloted with one strong department (their pharmacy), learned the system through that pilot, and only then expanded. Each department onboarding was treated as a culture conversation, not a technology training. The reason for going slowly wasn't just resource limitation -- it was that each department deserved a real conversation about what this tool meant, what the manager's role was in supporting it, and how the platform connected to the broader goal of building an improvement culture. Going fast would have undermined that conversation.
How do you build accountability without making the Lean team the enforcer?
By configuring the platform so that accountability surfaces automatically at the right level of the management chain. At St. Clair, directors' default boards show only ideas that have been stuck for more than 14 days. That gives directors a low-friction way to hold managers accountable in their regular one-on-ones. Vice presidents have similar bottleneck boards covering their broader areas. The Lean coaches don't have to function as enforcers because the system surfaces the issues to the people who should be addressing them. The accountability conversation happens within the existing management structure.
How do you coach managers to respond well to staff ideas?
By focusing on the underlying problem rather than the proposed solution. Frontline staff frequently submit ideas as solutions ("we should have free pizza parties on Fridays") rather than as problem observations ("morale is poor"). The instinct of a busy manager is to reject the solution. The Lean-coaching response is to dismiss the solution while pursuing the observation: "I'm not sure that's the right solution, but I'm interested in your observation. What evidence do you have?" Over time, this teaches staff to articulate problems rather than solutions, which produces better-formed ideas. Tania's team coaches the managers to coach their staff this way -- the platform makes it visible whether the coaching is landing.
What changed between year one and year two of adoption?
The completion rate for submitted ideas rose from 45 percent to 66 percent. The most common idea category shifted from staff satisfaction (often environmental and convenience-oriented "release-valve" ideas common in early adoption) to quality improvement. That shift wasn't automatic -- it reflected focused coaching on managers about how to respond to staff ideas. The visible improvement in metrics was a function of invisible coaching work that the platform made surface-able.
How can a small Lean team support a large organization?
Stratify your engagement based on proximity to the work. Frontline staff need minimum touch time -- learn how to submit an idea, the rest can develop through use. Managers need the deepest attention because they're the local champions and the primary support for frontline staff. Directors need lighter engagement focused on accountability infrastructure rather than direct coaching. The Lean coaches focus their limited hours where the work happens, which is at the manager layer. The platform amplifies what the small team produces, but doesn't substitute for the coaching itself.
.svg)
Copyright © 2026
Privacy Policy