Watch the recording of the panel discussion:
View or download the slides:
Listen to it as a podcast:
Frontline leader standard work is one of the most misunderstood disciplines in continuous improvement. Most organizations approach it as a checklist -- a list of behaviors a supervisor or manager is expected to perform daily, weekly, monthly. The list gets created. It gets distributed. Leaders work through it. And the program produces compliance without producing improvement.
The reason most checklist approaches fail isn't the format. It's the framing. Frontline leader standard work isn't fundamentally a list of leader behaviors. It's a system designed to make frontline employees successful one hundred percent of the time -- both at executing their standard work and at improving it. The leader's standard work exists in service of that purpose. When the purpose is clear, the specific behaviors follow naturally and adjust to the work at hand. When the purpose is missing, the behaviors become rituals without function.
This session walks through what frontline leader standard work actually is, why it matters, and how it operates day to day in a real primary care setting. Didier Rabino presents the underlying framework. Jen Ashley illustrates each piece with the specific tools, boards, and routines she uses in her care centers at Sutter Health. The two perspectives -- concept and application -- give the session unusual practical depth.
Didier Rabino is a Client Advisor at Value Capture, where he guides healthcare organizations in their Lean work. His background spans 13 years at Steelcase, where he helped develop the Steelcase Production System, 8 years at Andersen Windows leading development of the Andersen Management System, and 8 years as Lean Sensei for HealthEast and Fairview before joining Value Capture. He represents a particular kind of cross-industry Lean practitioner -- someone who has built management systems in manufacturing and then carried that discipline into healthcare.
Jen Ashley is Care Center Site Supervisor for Practice Design at Sutter Valley Medical Foundation. She joined Sutter in 2008 as a Patient Service Representative, moved into a Patient Service Coordinator role, and now leads a team on innovation for Practice Design and In-Person Patient Flow. Her perspective is particularly valuable because she's not a Lean specialist -- she's a frontline leader who has built the practices the session describes into her actual daily work, with real staff, real patients, and real constraints.
The session draws on a year of work Didier and Jen did together in primary care in Auburn, California. A white paper documenting the broader work -- which extends beyond frontline leader standard work to the pursuit of zero safety incidents, zero quality issues, and zero wait time -- is available on the Value Capture website.
The session is hosted by Mark Graban, Senior Advisor at KaiNexus and the author of Lean Hospitals, Healthcare Kaizen, Measures of Success, and The Mistakes That Make Us.
The framing Didier opens with is worth pausing on. Most discussions of frontline leader standard work start with the question of what the leader should do. This is the wrong starting point. The right starting point is the purpose -- what does the leader's standard work exist to accomplish?
The answer Didier gives: make frontline employees successful one hundred percent of the time at both executing their standard work and improving it. Everything the leader does is in service of that purpose.
This reframe has direct operational consequences. It means the leader's role isn't to police compliance with standards. It's to create the conditions that make following the standards possible, surface the problems that prevent following them, and engage the team in improving the standards over time. The work is fundamentally supportive, not supervisory in the older sense of the word.
It also clarifies an important division of responsibility. The frontline employee is responsible for the quality of the work -- following the standard, producing the expected outcome. The frontline leader is responsible for the flow of the work -- making sure the conditions are in place for the employee to do quality work, and making sure problems that disrupt flow get surfaced and addressed. In most organizations, Didier notes, these responsibilities are reversed. Leaders inspect quality after the fact while employees absorb the friction of poor flow. The reframe puts each responsibility where it belongs.
The framework Didier presents has three movements. The leader's standard work consists of activities in each.
Establish the standard work. The leader works with frontline employees to identify the key processes, define the expected outcomes, and design the standard work using a participative approach. The standard work then gets taught using a structured teaching method -- Training Within Industry's Job Instruction, in Jen's case. Once trained, employees can execute the work consistently.
Enable the standard work. The leader makes sure everything needed to follow the standard is available when work begins -- the information, the tools, the equipment, the materials. Without this preparation, the standard can't be followed even by employees who know it perfectly. The standard becomes aspirational rather than operational.
Support the standard work. The leader confirms in real time that the standard is being followed, provides feedback during the work, and operates a help chain that surfaces problems and removes obstacles as they occur. This is the most active part of the leader's day and the part most organizations underinvest in.
The three movements aren't sequential phases. They happen simultaneously across the day, the week, the month. But each one calls for different practices and different artifacts.
Jen's care centers use Training Within Industry's Job Instruction methodology to teach standard work. TWI is a teaching method developed by the U.S. War Manpower Commission before World War II to scale skilled industrial work quickly. The methodology is unusually well-tested and still effective in healthcare.
The structure of a JI breakdown has three columns. The important steps -- what the operator does, at a high level. The key points -- the specific elements that make each step successful. And the reasons -- why each step matters, including safety, quality, and the patient or customer impact. The breakdown structure is what separates teaching standard work from showing standard work.
The Job Instruction method itself has four steps:
Prepare the learner. Put them at ease. Find out what they already know. Get them interested in learning the job.
Present the operation. Tell, show, and explain each step. Stress key points. Instruct clearly, completely, and patiently.
Try out performance. Have the learner do the job while explaining each step and key point. Correct errors immediately. Continue until you know they know.
Follow up. Put the learner on their own. Designate the help chain. Check progress frequently. Taper off help.
The core principle Didier emphasizes: if the learner hasn't learned, the teacher hasn't taught. The framing puts responsibility on the teacher to verify the learning has occurred, not on the learner to absorb the instruction. A trainee who can't teach the work back hasn't fully learned it. The trainer's job is to keep working with the trainee until the teach-back is clean.
Two tools Jen uses to support the establishment work:
A time table. A simple schedule showing who is being trained, the date training began, and the planned follow-ups -- next day, next week, next month. This creates the cadence that prevents follow-up from being forgotten.
A training matrix. A grid showing every employee's training status across every job. This serves two purposes. It identifies gaps in capability the leader needs to address. And it identifies which employees can cover which roles when there's a call-out or a surge in demand. When someone is absent, the matrix tells the leader who can step in.
The enabling work begins each morning before patient demand arrives. Jen runs a daily stand-up with her team -- medical assistants, front desk staff, leads, and clinicians. The team reviews the day's expected demand, the equipment needed to meet it, and any foreseeable barriers. If something is broken, what's the workaround? If demand is high, can resources be pulled from another care center? Can equipment be pulled early to maintain flow?
The framing Jen uses: how are we going to win the day? The question isn't rhetorical. The team is actively planning for success rather than passively waiting for the day to unfold. The standard work can only be followed if the conditions for it have been established before the work starts. The enabling phase is where those conditions get checked.
Didier extends the framing. The standard work is a hypothesis. Every time the team executes the standard, they're testing whether the hypothesis holds. The enabling work is what makes the test possible -- without the right tools, information, and materials, the hypothesis can't even be evaluated, much less validated.
The phrase Jen uses, drawn from Lean practice broadly: inspect what you expect, and people will respect what you expect. The point isn't surveillance. It's signal. If leadership doesn't observe whether the standard work is being followed, the frontline rationally concludes that the standard work doesn't matter. If leadership does observe, the frontline rationally concludes that it does.
Jen's supporting work is structured through several tools.
A confirmation table. A monthly grid listing the key performance indicators and the specific days the leader or a designated team member will confirm each one. The cadence is visible -- everyone knows which standards get inspected when. The confirmations can be done by the leader, a lead, or a high performer in the care center.
A process observation calendar with Kamishibai cards. Jen uses physical pockets on a board, one per day, holding cards that identify which standard work she'll be observing that day, in which care center. After the observation, the card gets marked red or green based on whether the standard was being followed. Over a month, the pattern of red and green reveals which standards are holding and which need attention.
A higher-level management standard work tool. For the actual observation, Jen uses a simplified version of the operator standard work -- the high-level steps with a small map showing where in the exam room the employee should be during each step. The full operator standard work is too detailed to observe efficiently. The high-level version lets the leader watch the work flow without micromanaging.
Real-time feedback. After each observation, Jen gives the employee immediate feedback. What worked. What barriers showed up. What questions they have. The feedback isn't an evaluation. It's a coaching moment in the moment.
A process observation record. Jen records the outcome of each observation on a board -- red or green, with the date and any actions assigned. The board is visible to the team. The pattern over time tells the story of which standards are stable and which need attention.
The diagnostic value of red-marked observations isn't to identify employees who aren't following the standard. It's almost always the reverse. Through the pandemic, Jen notes, many of her red observations were the result of new guidelines that hadn't been incorporated into the standard work yet. The red observation surfaces the gap. The leader updates the standard. The employee gets the tools they need to do the work successfully. The standard becomes more accurate.
The division of responsibility Didier emphasizes is worth repeating because it inverts the assumption most organizations operate from.
The frontline employee is responsible for the quality of their work. They execute the standard. They produce the expected outcome. When they encounter a problem, they raise it through the help chain rather than working around it.
The frontline leader is responsible for the flow of the work. They make sure the conditions are in place for quality work to happen. They surface and address problems that disrupt flow. They maintain the help chain that supports employees in real time.
The implication for daily management: the leader's attention should be on flow indicators, not on quality outcomes. Quality outcomes are downstream of flow. If flow is broken -- if the standard work can't be followed because something is missing, or if a problem disrupts the work and doesn't get addressed -- quality will be poor as a consequence. Fixing the quality outcomes after the fact treats the symptom. Maintaining flow addresses the cause.
The phrase Didier uses repeatedly: problems are precious. The framing is deliberate. Most organizations treat problems as failures -- something to be minimized, hidden, or blamed on someone. Lean organizations treat problems as opportunities to learn. Every problem is information about how the system actually works versus how it was designed to work. Without problems, there's nothing to improve.
The discipline of treating problems as precious has operational consequences. Problems need to be captured at the point of cause, in real time, with enough detail to be useful. Jen uses a flip chart posted on the care center wall. When something disrupts the work -- a tool that doesn't function, a process that breaks down, a handoff that fails -- whoever sees it writes it on the flip chart with the cause as they understand it in the moment. Staff, providers, leadership -- anyone can capture a problem. No solution required. Just the disruption and the cause.
The simplicity is the point. If the capture mechanism requires logging into a system, completing a form, or interrupting the work, problems won't get captured. They'll get worked around and forgotten. The flip chart on the wall removes the friction. The act of writing the problem down is also a small assertion of dignity -- this matters enough to record, the person noticing it matters enough to be heard.
Didier draws a distinction that matters here, between point of cause and root cause. Point of cause is where the problem was created. Root cause is the underlying reason it was created. Most problem-solving jumps directly to the 5 whys analysis without first identifying point of cause. This produces speculation rather than analysis. The point of cause has to be established first -- where or when did the problem actually originate, what was happening at that moment -- before the 5 whys can produce real insight. The information about point of cause is perishable. The longer you wait to capture it, the less reliable it becomes.
One of Jen's tools surfaces a problem most primary care practices don't address well: the in-basket. Patient messages flow into virtual queues through the call center and the patient portal. The volume is significant, but unlike face-to-face patient demand, it's invisible unless someone makes it visible.
Jen's care center maintains a visual board, updated frequently, showing the current in-basket counts broken down by provider, MA basket, and individual folder. Anyone walking through the care center can see whether the team is winning or losing on virtual demand. The board sits next to a baseline established by customer demand and staffing -- with or without leadership intervention, the team can see whether the numbers are in the green or the red, and what needs to shift.
Didier shares an instructive moment from when they were first building this. They asked the people working the in-basket whether they were on track. Some staff with ten messages said they were on track. Others with two hundred messages also said they were on track. There was no shared understanding of what "on track" meant. People hesitated to ask for help. The board solved both problems. It made the standard for "on track" visible, and it made help arrive without requiring the employee to ask. When the numbers crossed the threshold, the help chain activated automatically.
The technical objection -- that the information already exists in the system, so the manual board is waste -- misses the point. The board isn't there to track the data. It's there to make the help chain operational. The information in the system requires someone to look. The information on the board operates on whoever happens to walk past.
If the morning stand-up plans the day, the end-of-day stand-down checks and adjusts. The team meets briefly, reviews what worked and what didn't, and engages with the problems captured during the day.
Jen's stand-down structure:
Establish psychological safety. Every time. The conversation is about processes, not people. Everyone has a voice. The work depends on team members being willing to speak honestly about problems, which depends on the conversation being safe to enter.
Review the standard work confirmation from the day. Jen shares the confirmation she did with an individual employee earlier and brings the learning to the whole team.
Reflect on the day. What worked? What barriers came up? Are there quick fixes the team can implement immediately?
Review the flip chart. Walk through the problems captured during the day. For each, decide whether it's a quick fix or whether it needs deeper analysis. Assign ownership for the ones that need follow-up.
The discipline of the stand-down is partly about timing. Five to ten minutes, maximum. Jen uses a timer. The stand-down isn't a problem-solving session -- it's a reflection and triage session. Problem-solving happens offline with specific owners. The stand-down's job is to surface, prioritize, and assign.
Daily cadence matters more than perfect execution. The team needs the rhythm of reflecting together at the end of each day for the practice to develop. Skipping the stand-down because the day was busy teaches the team that the stand-down is optional. The information captured during the day stays fresh because the reflection happens daily. Wait until the weekly meeting and the details have already begun to fade.
Problems take the team back to the existing standard. Opportunities take the team beyond it -- to a better standard than the current one. Both are valuable. The distinction matters because they call for different work.
Jen's care center uses a simplified A3 format for opportunity work. The A3 lives on the wall, visible to anyone passing through the care center. It has four quadrants: define the concern, analyze the cause, develop countermeasures, and identify the actions and owners needed to test the countermeasures.
The wall has three sections. New A3s start in the first section. As work progresses, they move to the second. When they're complete, they move to a folder and the learning gets entered into a shared system. The visible movement across the wall tells the team -- and anyone visiting -- what improvement work is happening in the care center.
The shared system is deliberately simple: an Excel spreadsheet accessible to everyone in the organization. As A3s close, their results get entered into the spreadsheet so other care centers can find and apply the learning. Leadership reviews the spreadsheet regularly to see what's been learned recently and what might apply elsewhere. The mechanism isn't elegant. It's functional. The learning spreads because the friction has been removed.
The book of knowledge sits alongside the system. Completed A3s go into a physical binder that becomes the care center's institutional memory. New staff coming through can see how the team has grown over time. Visitors can see the culture in operation. The binder is ceremonial in the best sense -- completing an A3 and adding it to the book is a real accomplishment that gets visibly recognized.
The session is primarily about the human practices and leader behaviors that make standard work succeed. The technology connection is real but specific to particular aspects of the work.
The platform's daily management features support the cadence Jen describes -- the morning stand-up, the end-of-day stand-down, the confirmation observations, the in-basket monitoring. Boards that need to live on physical walls in a care center work well as physical boards. Boards that need to be visible across multiple care centers, or that need to roll up to leadership dashboards, work better in a shared digital system.
The platform's problem capture and improvement tracking features support the flow of problems from initial observation through A3 analysis to completed improvement. The flip chart on the wall captures problems where they occur. The platform tracks them through whatever resolution path they need -- quick fix, A3 analysis, or escalation to other teams. The visibility into status that Jen describes through the three-section wall translates naturally into the platform's workflow visualization.
The platform's spread-of-learning features support the work that's currently happening through the simple Excel spreadsheet. When an A3 closes and the learning is captured, the platform makes that learning searchable and discoverable by other teams working on similar problems. The spread doesn't depend on someone remembering to look at a spreadsheet -- it can happen through search, through notifications, through cross-organizational visibility into improvement work.
The platform's training and confirmation features support the establishment work. The training matrix Jen describes -- showing capability across every employee and every role -- lives well in a system that can also track standard work updates, confirmation observations, and competency over time.
None of this substitutes for the human practices Didier and Jen describe. The leader's standard work is fundamentally relational. Standing up the team in the morning, walking the gemba during the day, sitting down with the team at the end of the day, coaching individual employees through their development -- these are practices the platform supports but cannot perform. The platform's value lies in making the practices easier to sustain at scale, freeing the leader's attention for the human work that determines whether the system actually produces excellence.
Didier Rabino serves as Client Advisor for Value Capture, guiding healthcare organizations in their Lean work. His prior responsibilities include 8 years as Lean Sensei for HealthEast and Fairview, 8 years at Andersen Windows where he led development of the Andersen Management System and served as plant manager, and 13 years at Steelcase where he started his career in operations leadership and supported the development of the Steelcase Production System.
Jen Ashley is Care Center Site Supervisor for Practice Design at Sutter Valley Medical Foundation. She holds a Bachelor's Degree and joined Sutter in 2008. Her Sutter career path started as a Patient Service Representative, then moved into a Patient Service Coordinator role, and now leads a team on innovation for Practice Design and In-Person Patient Flow.
What is the difference between point of cause and root cause?
Point of cause is where or when the problem was actually created in the process. Root cause is the underlying reason it was created. Most problem-solving jumps to 5 Whys analysis without first identifying point of cause, which produces speculation rather than analysis. The point of cause needs to be established first -- where or when did the problem originate, what was happening at that moment -- before 5 Whys can produce real insight. The information about point of cause is perishable. Capture it in real time, while the details are still fresh, or the analysis later will be unreliable.
Why is standard work a hypothesis?
Because the standard represents the team's current best understanding of how the work should be done, not a permanent truth. Every time the work is executed, the team is testing whether the hypothesis still holds. Conditions change -- new patient populations, new regulations, new equipment, new technology. A standard that worked six months ago may not work today. Treating the standard as a hypothesis rather than a rule keeps the team attentive to whether it's still producing the expected outcomes, and creates the expectation that the standard will be updated when it isn't.
What is the right cadence for stand-up and stand-down meetings?
Daily. The frequency matters more than the perfect execution. The team needs the rhythm of meeting briefly each morning and reflecting briefly each evening for the practice to develop. Jen's care centers run both daily, with a timer set for five to ten minutes maximum. The morning stand-up plans the day and surfaces foreseeable barriers. The evening stand-down reflects on what worked, what didn't, and what to do about it. Both are quick. The stand-down isn't a problem-solving session -- it's a reflection and triage session. Problem-solving happens offline with specific owners after the stand-down.
Why is psychological safety mentioned at the start of every stand-down?
Because the conversation depends on team members being willing to speak honestly about what didn't work, and that willingness depends on the conversation being safe to enter. Jen establishes psychological safety explicitly at the start of every stand-down by stating that the conversation is about processes, not people, and that everyone has a voice. The repetition matters. Psychological safety isn't established once and remembered. It has to be reestablished frequently because the alternative -- self-protection -- is the default that team members fall back on under pressure. Naming the safety condition out loud at the start of each session protects the conversation.
How do you get physicians to participate in stand-up and stand-down meetings?
This was Jen's biggest change management challenge. She didn't block schedules to require attendance. She made the meetings consistent, kept them brief, and rounded five minutes before each one to remind physicians they were happening and invite them to join. When physicians came, she made sure the conversation was useful to them -- not just operational discussion they could have skipped. Over time, physicians began joining on their own because they saw the value. Some started commenting that the once-monthly department meeting in a conference room felt redundant given the daily real-time conversations at the board. The shift was incremental and took months. Consistency and recognition of physician participation were the key levers.
What's the difference between a problem and an opportunity in this framework?
A problem takes the team back to the existing standard work -- something prevented the standard from being followed, and the work is to restore the conditions that make following the standard possible. An opportunity takes the team beyond the existing standard -- something could be done better than the current standard requires, and the work is to develop a new standard that produces better outcomes. Both are valuable. The distinction matters because they call for different responses. Problems are resolved by re-establishing the standard's preconditions. Opportunities are pursued through experimentation and standard work revision.
How long does it take to build this system in a care center?
Months. Jen is direct that the change management is significant -- staff and clinicians initially didn't understand why the practices mattered, and consistency over weeks and months was what eventually made the practices stick. The boards weren't perfect on day one. The training matrix had gaps. The stand-downs felt awkward. The practices became normal only through repetition. The leadership commitment to maintaining the cadence even when the day was busy was what carried the team through the early phase when the value wasn't yet visible. Once the value became visible -- when team members started seeing problems get solved that previously would have lingered -- the buy-in followed naturally.
Should the boards be electronic or handwritten?
The session's answer is handwritten, at least for the boards that operate at the care center level. Handwritten boards have a quality of being "always a draft" that electronic boards struggle to convey. Anyone with a pen can update them. They invite engagement rather than just transmission. Electronic systems are better for spreading information across multiple sites or rolling up to leadership dashboards. The two layers can coexist -- physical boards for the daily work at the point of care, digital systems for the cross-organizational visibility and learning. The mistake is using digital systems where physical ones would work better, or using physical ones where the work needs to travel.
.svg)
Copyright © 2026
Privacy Policy