By Jon Miller | Post Date: November 2, 2009 4:54 PM | Comments: 12
When we say something is "not rocket science" we mean that it is not hard to figure out or to do. If managing people were as easy as rocket science I am sure a rocket scientist would have figured it out by now. Groups of people tend to behave in non-linear and unpredictable ways. We could say "management isn't non-linear dynamics" instead but in fact management is probably even harder. Involve customers, regulators and the unforseen historical or macrodynamic event and making money today tomorrow and day n+1+1... starts to look quite a bit harder than rocket science.
Fortunately we have learned a lot since the early days of Peter Drucker establishing management as a modern theory and practice. The Japanese were especially avid students of Drucker and created many unique management systems by building on ideas of others such as Drucker and Deming. Not least of these management systems is what we call gemba kanri or gemba management. More broadly it is basic Toyota-style shop floor management. Developing this gemba-focused, team based, high performance learning organization may be the areas that people struggle with the most in the pursuit of lean. Gemba management in layman's terms is when everyone works together and learns together by solving problems made visible on the front lines. It sounds easy but there are various barriers that we don't see until we run firmly into them.
Management is an art and a science. The art is in the 20% creativity, experience and panache that we each bring to it and the 80% is in the standard ways in which we operate within the management system, whether we call it best practices or the Acme Business System. These standards enable creativity within a lean enterprise. Even stronger than standards, there are certain universal laws that affect the success or failure of a lean transformation and sustainability of gemba management. Please excuse the inelegant notation in the formulas that follow due to limitations with my text editor. Here are five laws of gemba management:
Law #1: Go See Inverse Square Law
The speed of response to problems on the gemba is proportional to the inverse square of the distance of the support staff from the gemba.
The variables are
V = speed of response
D = distance between gemba and the respondent
V = 1 / (D*D)
This is highly intuitive. If an engineer or manager is 500 meters away from the andon light the the response speed will be slower than if they are located 5 meters from the location where the problems are identified. Gemba management, rapid problem solving through root cause analysis and team based performance management require that we rethink the distance we place between one set of brains and another.
Law #2: Wall Law
The frequency of leadership going to the gemba is inversely proportional to the number of walls separating them from the gemba.
If W equals the number of walls, doors and other physical impediments and f represents the daily frequency of visible support from leadership and staff on the gemba:
f = 1 / (1 + W)
This law tells of the folly of walling in our most senior leaders from the realities that affect the organization they lead. Most of us are not even conscious of the number of transactions we must go through in order to go to gemba, such as opening doors, navigating around desks, hallways, coffee machines and other temptations. This law states the obvious; remove barriers to getting to the truth and you will get to the truth more often. In addition this law has the distinction of being spelled with only three letters of the alphabet.
Law #3: The Non-invisibility Law
If need to ask > 0, then visual management = 0.
This is simply and if-then statement to the effect that formalizes the gemba kanri truism "If you have to ask, you don't have visual management of your operations". Visual management must leave no doubt. Nothing that is important should be invisible if true management by fact is to be practiced on the gemba.
Law #4: The Y-O Power Law
The effectiveness of root cause problem solving increases by a power of ten for each "why? question asked and decreases by a power of 10 for each "who?" question asked.
If E equals the effectiveness of root cause problem solving and O equals the number of "who" questions asked, while Y equals the number of "why?" questions asked,
E = 1+ (Y*10) / 1 + (O*10)
This does not mean that we never hold people accountable. Sometimes the root cause is simply a person who refuses to follow the standard, and there are standards for how to deal with these people. If there are no standards for how to deal with these people, that is the one of the points of cause. The root cause is still not the person but the fact that policies to enforce standards do not exist. In cases where there are no standards to begin with, people cannot be blamed. Accountability is not a two-way street, it is the three-way intersection of setting, observing and improving standards.
Law #5: Law of Sustainability
The sustainability of gemba management is a function of full engagement in continuous improvement activity over time.
Where S is the sustainability of a continuous improvement culture, a gemba management system or a lean transformation, this law is expressed as:
S = P*i*K*y
P = (people engaged in kaizen / total people)*100
i = interval in working days between kaizen ideas implemented by one person
K = number of kaizen ideas implemented per person per interval
y = years of continuity of total engagement in kaizen
If we take benchmark statistics from Toyota for example, we can calculate their chances of sustaining their continuous improvement culture. We will assume that 99% of 250,000 worldwide Toyota employees are engaged in kaizen. We will further assume that at a minimum they are implementing one idea per person per month or every twenty working days, which is in fact a suggestion system benchmark Toyota hits or exceeds at most sites. Toyota has had their suggestion system since 1950. Therefore:
P = (247,500 people engaged / 250,000 total people)*100 = 99%
i = 1 idea / 20 days = .05
K = 1 idea per person per interval
y = 59 years of continuity in full engagement kaizen
This yields the number 292%. In other words Toyota has close to 300% chance of sustaining their continuous improvement culture in the future, not considering adverse conditions that erode these chances. Factors such as leadership changes, a global economic crisis, the dilution of talent through management turnover, overly rapid global expansion or the complete change in business focus are all factors that today threaten the sustainability of the kaizen culture at Toyota. However, thanks to their 59 years of continuity, near full engagement, and high frequency of kaizen idea generation they are well equipped to weather this storm.
In theory, if you sustain full engagement for 20 years with 1 kaizen idea per person per month you will have a sustainable kaizen culture. This intuitively makes sense as 20 years is roughly a generational shift. For most of us is that a near term target to reach 100% sustainability requires the following conditions to be met:
P = 100% engagement
i = weekly or daily kaizens
K = 1 per person per interval
We have very little influence over the y variable on a day to day basis other than to not give up. We can't speed up time so we can only speed up the interval of kaizen to more frequent than one month, increase the number of small ideas generated, and expand the breadth of engagement to reach everyone.
By quadrupling the combined number and interval frequency you may be able to achieve sustainability in as little as 5 years of full engagement (e.g. S = 100%*0.2*5). However based on my experience length of time and breadth of involvement are the best indicators of success and sustainability. Most organizations focus a small number of people laser beams on improvement activity while treating the rest as dim light bulbs. Just as the sun comes out each day and shines its light on everyone we should all shine our lights on improvement every day.Comments are moderated to filter spam and inappropriate content. There may be a delay before your comment is published.