Tag: Contingency Training

Contingency Plans – Crisis Management in Lean Organizations

Contingency Planning For Lean Organizations – Part IV – Crisis Management

In a previous post we eluded that lean organizations are likely to be more susceptible to disruptions or adverse conditions and may even have a greater impact on the business.  To some degree this may be true, however, in reality, Lean has positioned these organizations to be more agile and extremely responsive to crisis situations to mitigate losses.

True lean organizations have learned to manage change as normal course of operation.  A crisis only presents a disruption of larger scale.  Chapter 10 of Steven J. Spear’s book, “Chasing the Rabbit”, exemplifies how high velocity, or lean, organizations have managed to overcome significant crisis situations that would typically cripple most organizations.

Problem solving is intrinsic at all levels of a lean organization and, in the case of Toyota, problem solving skills extend beyond the walls of the organization itself.  It is clear that an infrastructure of people having well developed problem solving skills is a key component to managing the unexpected.    The events presented in this chapter demonstrate the agility that is present in a lean organization, namely Toyota in this case and it’s supplier base.

Training is a Contingency

Toyota has clearly been the leader in Lean manufacturing and even more so in developing problem solving skills at all levels of the organization company-wide.  The primary reason for this is the investment that Toyota puts into the development of people and their problem solving skills at the onset of their employment with the company.  The ability to see problems, correct them in real time, and share the results (company-wide) is a testament to the system and it’s effectiveness has been proven on many occassions.

Prevention, preparation, and training (which is also a form of prevention) are as much an integral part of  contingency planning as are the actual steps that must be executed when a crisis situation occurs.  Toyota has developed a rapid response reflex that is inherent in the organization’s infrastructure to rapidly regain it’s capabilities when a crisis strikes.

Crisis Culture

We highly recommend reading Steven J. Spear’s “Chasing the Rabbit” to learn and appreciate the four capabilities that distinguish “High Velocity” organizations.  The key to lean is creating a cultural climate that is driven by the relentless pursuit of improvement and elimination of waste.  Learning to recognize waste and correcting the condition as it occurs requires keen observation and sharp problem solving skills.

Creating a culture of this nature is an evolutionary process – not revolutionary.  In many ways the simplicity of the four capabilities is it’s greatest ally.  Instilling these principles and capabilities into the organization demands time and effort, but the results are well worth it.  Lean was not intended to be complex and the principles demonstrated and exemplified in Chasing the Rabbit confirm this to be true.  This is not to be construed as saying that the challenges are easy … but with the right team they are certainly easier.

Until Next Time – STAY Lean!

"Click"
Advertisements

Lean Contingency Planning For Lean Operations – IT and the BSOD

Coincidentally, we are having a first hand experience with the Blue Screen of Death or BSOD with one of our laptops today.  The completely unexpected critical system error that renders Windows completely helpless.  If this isn’t on your list of IT concerns, it should be.

In our case the error appears to be video related – driver or card.  Most IT specialists know how to deal with these types of errors but for the average user, the message that appears is enough to make you sweat.  If the system can’t fix the error, you may very well end up staring at a Black Screen – just as we are.

How is it that we were still able to produce this POST?  Well, we are currently executing our contingency plan and using another system that is operated independently.  Most companies back up their data to prevent or minimize loss.  Another concern that is often overlooked is accessibility to that back up data in the event the system goes down.

What have we learned?

We are not the first to experience this problem.  We did a Google search using some brief terms such as “Computer Black Screen”, “Laptop Black Screen”, and we even Googled parts of the error message that appeared on the screen.  The result?  Thousands of people have experienced this same error.

The point of this post is to demonstrate that you do not have to re-invent the wheel to determine potential solutions or to discover problems that may occur.  Quite likely, they may already have happened and solutions are already developed and available.

There are two probable solutions to our video issue:

  1. Update the video device driver (Free)
  2. Replace the video card (Cost $)

Hopefully, the first solution is the answer to our problem.  Video cards are not sitting on our shelf and the downtime may be extended if we can’t find something locally.

It is noteworthy that we have not yet identified the root cause of this failure.  We haven’t loaded any new software or experienced problems in recent history.  This may be the topic for a future problem solving post.

Regardless of the outcome of our present dilemma, we have learned that it is a good idea to keep device drivers up to date.  As a planned activity, this may prevent some of you from having to experience the BSOD as we have today.

The loss incurred for this event is more than just the cost to repair.  This computer may be down for a few days.  How much is the down time worth?  Unless we play out the scenarios that may threaten or pose a risk to our business, we may never have the opportunity to prepare for the event until it actually happens.

Keep an open mind and use the resources available to you to help solve the problem.  In some cases a simple Google search could confirm your concern in a matter of seconds.

Until Next Time – STAY Lean!