After finding out my flight had been delayed, I took advantage of the opportunity to stop at one my favorite eating establishments. It was too late for lunch but too early for dinner. Nevertheless, the establishment was unusually crowded. Patrons queued at the hostess station, servers queued at the portal between the kitchen and dining area, advocating for their orders, while recently seated patrons waited to have their orders taken. The scene was nothing less than chaotic. Patrons began losing their tempers and this only added to the chaos as the harried staff responded to the frustrated requests. Eventually, what occurred could only be described as a total service breakdown and the manager was summoned from a back office.
It was amazing to me how quickly the manager was able to restore order. With a very methodical approach, she began directing the team to alleviate the bottle-necks in the process from the back of the line to the entry point. I began to observe her correct subtle deviations from standard process that had been abandoned in the chaos. Her actions were focused, directed, and confident. It was clear, that she had been here before and knew exactly what was required. This seemed to have a calming effect on both the staff and the patrons. It was a magnificent example of service recovery.
Naturally, as both a lean healthcare coach and as a life-long and avid student of human behavior the opportunity to observe this left me with a lot to ponder. Within nearly all healthcare institutions there are completely analogous breakdowns and recoveries that occur on a regular basis. This is especially true in services that encounter significant variability in demand. The two questions I was left pondering were: 1.) Why did it take a service breakdown to pull the manager from the back-office? 2.) Why was the manager able to restore order so quickly but the team could not? They are a lot of contributing factors that could be considered. I would propose that the primary concept for consideration in this case is the Andon.
So what’s an Andon? In the Toyota Production System (TPS) an andon is an indicator of status. This indicator is usually visual, at times audible, and is used to prevent a breakdown in process. These are often associated with highly automated processes but most definitely have their place in a lean healthcare setting. In fact, the essential concepts associated with andons are not new to healthcare and, collectively, are often referred to as a system of thresholds, triggers, and responses. So let’s apply the andon concept to the service breakdown described above and use the example to translate the concept to healthcare.
The first concept associated with the andon is that of a threshold. This is some visual indicator that helps the team to understand that a potential problem exists. In our case study above, the andon was a complaint reaching the manager’s office. Not the best possible andon, but an andon. In healthcare, one example of a threshold associated with an andon may be the number of patients within a waiting or service area; where an exceeded threshold serves as an indicator of abnormally high volume. The idea is to make this visual to the team to drive a change in behavior. This leads to the second concept associated with andons, the trigger.
Who has the authority to pull the trigger? For the andon to be fully functional, authority to pull the trigger must reside in the individual(s) best positioned to observe that the threshold has been exceeded. In many healthcare institutions, as in the case study above, the ability to pull the trigger lies exclusively with the manager. In our case above, only the manager had the authority to pull the trigger; to initiate a change in directed action. The down-side to this was that the team floundered until she was roused from her office by the complaint(s). Managing under these circumstances becomes habitual fire-fighting. Implementing a well designed system of andons removes the manager from the fire-fighting role into a coach and resource allocator role. This leads us to the final concept associated with andons, the response.
Once the trigger has been pulled, proactively and in advance of service failure, a systematic and well defined set of actions are executed in response to the trigger to prevent service failure. In our case study, the manager’s approach to service recovery was focused, directed, and confident. It was clear, that she had been here before and knew exactly what was required. However, the team did not have a common understanding of her method and, basically, just followed her lead. Sound familiar? After-all wasn’t it her experience that landed her in the manager role? The success of her actions in restoring service, however, is not unique. They are, in fact, possible to duplicate, document, and coach. It is, often, the fundamental failure to duplicate (test), document, and coach that inhibits the team from being able to proactively anticipate and course correct.
Returning to the original questions my experience left me to ponder: 1.) Why did it take a service breakdown to pull the manager from the back-office? 2.) Why was the manager able to restore order so quickly but the team could not? Consider the following:
- Andons are informal and undocumented versus andons are well defined, documented, trained, coached and evaluated on an ongoing basis.
- Thresholds are intangible and not easily identified versus thresholds are defined and easily observed.
- Triggers are informal, not clearly visible and only invoked by management versus triggers are defined and visible with authority delegated to resources best positioned in the service process to observe and invoke.
- Thresholds and triggers predict and prevent service failure versus thresholds and triggers are in response to service failure.
- Responses are informal, undocumented, understood by few versus responses are well defined, documented, trained, coached and evaluated (tested) on an ongoing basis.
The above list is not intended to be exhaustive, but rather, thought provoking. If the experience described in the case study above is frequently analogous to experiences within your department, a well designed and implemented system of andons may serve to empower the team to course correct independently while simultaneously transitioning managers out of the fire-fighter role and into a coach / resource allocator role.
This week’s blog was written by Bradley Schultz, a director and consultant for HPP. Before joining HPP, Bradley was serving as Vice President of Operations & Quality for Infinity Resources Inc. where he pioneered the application of Lean, Six-Sigma, Work-Out™, and CAP (Change Acceleration Process) in the retail market sector. Bradley’s educational background includes: a Bachelor of Science degree in Business Administration from Cardinal Stritch University in Milwaukee, Post Graduate Certification in Quality Engineering from Milwaukee School of Engineering, a Master of Arts degree in Business Administration from Marquette University in Milwaukee, Six-Sigma Master Black Belt Certification from General Electric, and Front-Line Leadership Development Certification from Achieve Global.





