" /> Gemba Panta Rei: December 2006 Archives

« November 2006 | Main | January 2007 »

December 29, 2006

Top Five Non-Lean Things Gemba Did In 2006

Inspired by the "tag" idea from Mark Graban over at the Lean Blog, from our hansei list here are the top five non-Lean things Gemba did in 2006:

1. Trying to do too many things. How hard is it to walk the talk? Take Hoshin Kanri. Really hard. Wow. Letting new and interesting things distract me / my organization from the "critical few" was really easy. We did not take on projects "one piece flow" style. In 2007 we will focus on three breakthrough areas only. You heard it here first. Ask me "how are you doing with those three areas?" in 2007.

2. Building up inventory. We had a minor hiring spree in the beginning of 2006 to ramp up for some large projects in our "forecast". Well, forecasts are always wrong (and a signed contract is not money in the bank) so this caused some problems. New strategy in 2007: heijunka for consulting / training work, flexible and cross-trained consultants, and customer service policies supporting heijunka.

3. Off-shoring some of our IT work. We did this for cost reasons, or more because there is a lot we wanted to do (see 1 above) and a limited budget (see 2 above). Quality has not suffered, as many off-shoring operations do, but lead-times certainly did get longer. We are doing more with less (this is Lean) and I'm happy with the decision overall, but paying a higher price for faster service in some cases may have been more Lean.

4. Choosing to "batch" print. We will set up and print 3,000 copies first run rather than go the "on demand" route for printing Taiichi Ohno's book Workplace Management. We fought that fight, but some economies of scale are alive and well, driving us to make non-Lean short term decisions.

5. Traveling to the ends of the earth. Japan office consultants leading Lean projects in Canada, U.S. office consultants leading Lean projects in China, China consultants all over China (big place)... etc. "How does that work?" You might ask. Not as poorly as you might think, since most of the jet lag hits you when you get back from the trip rather then while on site. It's not Lean at all but someone's got to keep the airlines in business.

We do quite a few of the small things very Lean at Gemba, but the big things are still a challenge. The full and complete list of hansei for Gemba in 2006 is long and scary, but we can be grateful that we know what to do when we find a problem.

A Happy New Year to everyone.

December 28, 2006

Selecting a Management and Improvement System

Lean manufacturing is a system for managing and improving production operations. More broadly, Lean manufacturing principles can be applied to manage and improve any type of operation from healthcare to service and distribution, as we are increasingly seeing. But how does a decision maker select the appropriate management and improvement system when faced with many choices such as Lean manufacturing, Six Sigma, TOC, QRM, DFT or any hybrid?

A system is not only a set of tools but the ways in which you use them (what we call habits). If we think of management and improvement systems like Lean manufacturing as being analogous to software systems or to technologies, we can use similar selection and evaluation criteria.

Assuming that the promised costs and benefits from a faithful implementation of Lean manufacturing and other systems are more or less equal, the decision maker may find these questions useful when considering an investment in a management and improvement system:

1. Ease of use. How well is the user interface designed around the human? Does it enhance safety, creativity, job satisfaction as well as productivity? Does it put people first or the system first?

2. Learning curve. How much time and effort does it take to become competent in the new system? How quickly can everyone be trained in the basic workings of the system?

3. Portability. How easy is it for me to take this system I learned to another department? To another factory? To another job?

4. Compatibility. How well does it work with other functioning tools or systems that are in place? What incompatibilities need to be addressed in the short and mid-term?

5. Fullness of features. How complete is this system? How broadly can I apply it? How soon will I need an "upgrade" or plug-ins to fill in the missing features?

While Lean manufacturing is not a technology as such, these are the types of questions often asked during the technology selection process. It's a bit ironic that Lean manufacturing scores so highly on the five point evaluation above, yet has a strong bias towards the low-tech solution such as visual management systems instead of software dashboards. What does that say about technology?

December 27, 2006

Being an Improvement Agnostic

A while ago my colleague and I were doing our best imitations of slick salesmen in front of a group of leaders from a small, local manufacturing firm. We were fired up after a tour of their factory, confident that space could be cut to a third and productivity doubled with some quick application of Lean manufacturing principles. At the end of our presentation their President raised some typical objections.

"If what you say is really true, would you be willing to work for a percentage of the savings you help us achieve?"

To his surprise, we nodded our heads and said we would be happy to put it in writing. One of the Directors who had more experience in Lean manufacturing and what it could achieve realized that the President was about to overpay for Lean consulting and training services, and quickly change the topic.

We soon had all of the heads in the room nodding up and down in assent with what we were proposing, except the President. He was skeptical of the results we said Lean manufacturing could help them accomplish at their company. He had heard similar claims from other vendors hawking ERP, CRM, and Six Sigma.

"It's not like you are agnostic." He said to us.

The statement floored me. Clearly we had failed to communicate the essence of what we do, for this person believed that ERP, CRM, Six Sigma and Lean manufacturing were all more or less the same type of investment in his business.

What would you like for lunch: sliced pineapple, a raisin, chicken cordon bleu or a tuna sandwich? Where does a salesman go from a non sequitur like that? We wrapped things up as smoothly as we could and headed for greener pastures.

For many the term "agnostic" is a step away from "atheist" and a dirty word if you are religious.
An agnostic is a person who questions religious or spiritual beliefs on the basis that God is unknown and unknowable, and the agnostic does not lay claim to a particular system of belief for this reason.

While a believer will say "there is a God" and an atheist will say "there is no God" the agnostic will say "I don't know if there is or not". The common perception of the religious agnostic is that because it is impossible to know, the agnostic chooses not to believe. In fact, agnosticism is a system of belief of a kind. Much like the scientific method, the agnostic mind holds that Truth is unknown and unknowable, except what has been demonstrated through experience.

Professor Thomas Huxley is credited with coining this term. In his words:

"In matters of the intellect, follow your reason as far as it will take you, without regard to any other consideration. And negatively: In matters of the intellect, do not pretend that conclusions are certain which are not demonstrated or demonstrable"

I have no certain conclusions Lean manufacturing is "the way", except through direct experience. It would be foolish of me to claim that Lean manufacturing should come before any of the other "beliefs" such as ERP, CRM or Six Sigma without first seeing what an organization needs most and understanding the available solutions. So perhaps the President had a point in questioning my improvement agnosticism.

Being an improvement agnostic means not holding to a particular system of belief too strongly if it has not been demonstrated or if they are not demonstrable. Test the null hypothesis, in other words. Follow reason to its natural conclusion, regardless of what we want to believe as fans of kaizen and the Toyota Production System.

I don't know that there is a perfect process, or that we can ever know the perfect process. I have a strong hunch that it does not exist today (except perhaps in nature) and that I may never see it. I don't have an unshakable faith that Lean manufacturing works, only belief from demonstrated experience.

Another improvement approach may work better or be more appropriate, as we've experienced that certain organizations are not ready for Lean transformation without some basic organizational development. If it improves safety, quality, delivery and cost it's all kaizen as far as I am concerned. That's as close as I will come today to being an improvement agnostic.

December 26, 2006

Holiday Shopping is Wasteful

It's time for my second annual Boxing Day railing against the waste caused by holiday spending at the year end. This year we find a December 23, 2006 Wall Street Journal article titled How Christmas Brings Out the Grinch in Economists lending support to my theory that we would all be better off if we spread our holiday shopping across 12 months rather than the 12 days of Christmas:

Economists aren't suggesting Christmas be abolished. Still, in the latest Wall Street Journal forecasting survey, more than two of three economists opined that if Christmas ceased to exist as a holiday, consumers would either spend more on themselves or spread their gift purchases more evenly across other events such as birthdays.

This is attributed mainly to the fact that people buy "ill-considered presents" in the form of unwanted goods that do not please the people who receive them. George Mason University Professor Tyler Cowen says "The economy is better off" if fewer gifts are given since the gifts are not enjoyed much anyway. The gifts are wasted, in other words. From the WSJ article:

In the cold, hard analysis of the dismal science, Christmas is a highly inefficient way of connecting consumers with goods.

Putting the goods in the hands of people who want them improve what economists call "social welfare" which is the overall well-being of a society (and not to be confused with government financial assistance). The Wall Street Journal article introduces what economists call this "deadweight loss" and is defined as follows in a Wikipedia entry:

In economics, a deadweight loss is a permanent loss of well being to society that can occur when equilibrium for a good or service is not Pareto optimal, (that at least one individual could be made better off without others being made worse off). Deadweight loss can be thought of destroying a given quantity of a good or service in question, and in many cases natural waste in a system (like leakage from water pipes) is equivalent to, and is also called, deadweight loss.

This type of seasonal demand spike causes problems from a Lean manufacturing perspective since it becomes necessary to either build up inventories ahead of time for the holiday season, creating waste in the form of storage, overproduction, obsolescence, handling, etc. Equipment and other fixed assets that are not as flexible as labor must also be kept on hand during the slow season, creating a waste as assets do not generate as much cash and profit in these times.

The Lean answer is to do heijunka (averaging volume and mix to smooth production) through a combination of increased flexibility and speed in the manufacturing supply chain, customer service and sales policies to support a leveled demand, and modified consumer behavior. From the article:

In theory, smoother sales throughout the year would be better for retailers, enabling them to avoid the extra costs of planning and stocking up for the holidays.

According to the article, some economists think we would be better off without holiday spending, to the tune of about $457 billion this holiday season or about $4,000 per U.S. household, according to National Retail Federation numbers.

So what would it take to get rid of this year-end spike and level out the demand for consumer goods so that we can convert those warehouses into value-adding space, the cash tied up in inventory and idle machines, and be Leaner and less wasteful as a society? According to the WSJ article:

Overall, sales tend to spike about 15% in the last two months of the year, accounting for a quarter of retailers' annual revenue.

If we leveled out our spending that would be an extra 1.25% per month for 12 months. I think we could all handle that.

And no, I did not get what I wanted for Christmas.

December 23, 2006

Note to Toyota: Top Five Things to Do in 2007 as World's #1 Automobile Manufacturer

According to a Wall Street Journal article today Toyota Is Poised to Surpass GM As the Top Car Maker Next Year. That would be 9.04 million vehicles, just ahead of General Motors. Congratulations are premature, but it's not too early to start thinking about New Year's resolutions for the worlds biggest car company. Here are five things I would like to see Toyota do in 2007:

1. Remain humble. You've got plenty of practice at this, but we all know it's not easy.

2. As the single largest supplier of carbon-emitting vehicles in the world, take a leading role in promoting lifestyles and technologies to reverse global warming.

3. Keep telling the world how you did it. Not only is it good for our business when the world learns more about the Toyota Production System, I believe it's also good for people.

4. Don't just apologize, tell us what's really up with those millions of recalls.

5. Start talking to Tesla Motors about licensing their technology for mass market versions of their cars. Sure the hybrids are nice, but...

If all you do is make more cars than anybody else, and do it better than anybody else, I will be disappointed. Toyota, you know you are capable of much more than that.

December 22, 2006

Ford CEO Mullaly's First Impressions

In the December 22, 2006 Wall Street Journal article titled Mulally's 'First Impressions' published the letter from the former Lean leader of Boeing and now CEO of the Ford Motor to the employees of the company.

He starts out by acknowledging that there will be tough decisions ahead, and that Ford will continue to lose talent in the short term. He emphasizes the latent "greatness" of Ford the company, the dealer network, product development and that "Ford people are winners by nature".

Mulally's job is to motivate and focus these great resources, and to bring together the "pockets of success" into an integrated whole. The following openness and humility in when talking about his weekly Business Plan Review is encouraging:

We talk to each other with candor and respect. We are all determined to get to one plan for our company. We will all participate, and we will all support each other's efforts to succeed. I don't yet know everything I need to know about Ford, but I do know that this is the only way I can work.

This plan, Mulally says, will be built around three priorities:

• PEOPLE: A skilled and motivated work force.
• PRODUCTS: Detailed customer knowledge and focus.
• PRODUCTIVITY: A lean global enterprise.

Boeing's Lean effort is far from perfect. But of any American CEO today, Mulally has the track record and credibility when speaking about "a lean global enterprise" to actually deliver on this.

In plain language he explains what fundamental questions the people at Ford need to answer together:

What are the critical elements needed for a compelling business plan? How accurate are our assumptions? How do we get losses behind us and once again create profitable growth for all?

If Mulally and the Ford team do nothing more than what is outlined in his letter, they will have a terrific chance at success. He closes the article by acknowledging that people of Ford have been through tough times and by offering hope:

Everyone loves a comeback story. Let's work together to write the best one ever.

I'm looking forward to reading that comeback story in a few years.

December 21, 2006

Gemba Keiei by Taiichi Ohno, Chapter 37: The Standard Time Should be the Shortest Time

"Speaking of standards, time study is another thing everyone gets wrong." The typical time study is based on taking 10 times and setting an average time as the standard. Ohno says this is very bad because if you are watching someone do something 10 times and they are doing it differently each time you should stop to correct them right away. This is the kaizen "stop and fix" mentality, extended to time study.

Ohno asks what's the point of just taking times that are not good times to begin with, when you can take the shortest time as the best time. "Some say that is harsh, but what's harsh about it?" asks Ohno. "The shortest time is the easiest method."

The purpose of process observation and time study is not to get an average time and build in the waste and variation to the standard time but to ask why there is variation between different people or between the same person over 10 repetitions of the same process. Ohno is looking at time study not from the standpoint of establishing Industrial Engineering standards but from a kaizen standpoint.

Ohno recommends not including allowances for breaks to go to the toilet. These times are unreliable anyway, he says, so let people go to the toilet when they need so long as they stop the line. The team lead or the supervisor should step in to keep the line going. He says that allowing times to go to the toilet as part of the standard time, whether people need to go or not, just creates slack.

This again is an example of the jidoka (stop the line) principle built into his thinking, influencing how time study should be done. The principles (stop and fix) dictate how the improvement tool (time study) should be used. This is an important lesson.

Ohno ends the chapter by saying that if you have to take several measurements in order to set a standard, use the shortest time. Then find the reasons why this time can not be met and teach them how to make it possible to do it in the shortest time.

Just as the theme from Chapter 6 was "Costs do not exist to be calculated. Costs exist to be reduced" the theme from this chapter could be stated as "Times do not exist to be studied. Times exist to be reduced."

December 19, 2006

When is Point Kaizen OK?

Point kaizen refers to small, isolated improvements that are easy to implement quickly. The impact of point kaizens are typically small but they can have a large impact. Point kaizen are in contrast to line kaizen, plane kaizen, cube kaizen, etc.
lean%20geometry.png

There is no limit to how small a point kaizen can be. That is why it is "zero dimensions". This is good in that most point kaizen are immediate and remove safety hazards, make the workplace cleaner, etc. However one of the criticisms of point kaizens as the only type of continuous improvement effort is that it is hard to see the bottom line impact, or that the positive effects of point kaizen in one area can wipe out the benefits of a point kaizen in anotter area.

An example of a point kaizen would be organizing (5S) a tool cabinet in a machine shop.

A line kaizen would be layout change to create better flow, which may make the tool cabinet totally unnecessary, as the tools could be attached directly to the machine at point of use.

A plane kaizen would be to deploy these layout improvements horizontally (yokoten) to other lines, and this may change the design of the original flow line now that the entire shop is being moved and door-to-door flow can being considered.

A cube kaizen would be to make improvements "up and down" from the plane, or upstream and downstream by including the suppliers and customers (such as configuration engineering, heat treat, assembly, shipping, etc.). This might change how the parts are designed or how orders are released, further changing the layout of the factory (plane).

The idea is that as you go from point to line to plane to cube you are expanding your kaizen efforts enterprise-wide. This expands your thinking from one small area to the entire value stream. Just as in geometry, each type of kaizen adds another dimension (line = 1 dimension, plane = 2 dimensions, cube = 3 dimensions). Moving to each higher dimension brings you closer to the customer, and also to systemic root causes.

Some call cube kaizen "3D kaizen" but this is confusing with 3D as in "dirty, dangerous, difficult" rather than 3D as in "3 dimensions".

There is a common misunderstanding of the definition of kaizen being a series of small, incremental, common sense improvements rather than more broadly any type of improvement that follows certain principles. If you only make small, incremental improvements this is only point kaizen, and that is not ok.

So when is it OK to do point kaizen?

1. When the alternative is no kaizen

2. When the point improvement does not worsen safety, quality, delivery or cost for upstream or downstream processes (i.e. when you avoid local optimization)

3. When it is part of a series of connected point improvements (a weaker version of line kaizen)

4. When the point improvement promotes a behavior change such as a "go see" style of management

5. When the points of improvement are along continuous process (as opposed to discrete processes) and therefore by definition can have an impact similar to a line kaizen

I would rather have people do point kaizen than not do kaizen at all. However it is too easy for people to learn a Lean tool and focus too much on implementing the tool for its sake rather than trying to understand the geometry of kaizen and how to use the tool to go from point to line to plane to cube.

December 17, 2006

The Starfish, the Spider and the Span of Five

I just finished reading The Starfish and the Spider: The Unstoppable Power of Leaderless Organizations by Ori Brafman nd Rod A. Beckstrom. It is a quick read with some interesting ideas. I have a number of issues with the book, and by examining these issues we can learn something about the Toyota Production System and the role of supervisors in Lean manufacturing, among other things.

The authors tell compelling stories of successful examples of starfish organizations including the Apache tribe, Wikipedia, Craigslist, al Qaeda, blogs, eBay, file sharing and others. Toyota is included in Chapter 8 as a hybrid between the centralized and decentralized organization, but more on that later.

If you are a failing spider organization (one that dies when it's head is cut off), the idea of becoming a starfish organization that is more adaptable and able to survive being cut apart, only to regrow from its parts may be attractive. However, you need the same endurance to build and maintain either type of organization. Neither path is the easy answer and neither is inherently superior. According to the authors the starfish organization has five "Legs". These are 1) Circles, 2) The Catalyst, 3) Ideology, 4) The Preexisting Network and 5) The Champion. There are some immediately obvious links with Lean.

Lean can not function without circles, whether you call them cross-functional teams for various innovation, improvement and management activities, or whether they are quality circles (QC Circles) and other front-line teams.

Lean is an ideology.

The notion of the catalyst as a type of leader who is more of a teacher than an order-giver fits well within the Lean value of "manager as teacher" instead of the traditional "manager as boss". There is a difference in that these catalysis can typically shun all responsibility for the organization and simply act as sparks or instigators, while managers have profit and loss responsibilities they can not shirk.

Inasmuch as Lean is about changing how work is done within a preexisting network (an organization, typically centralized) this point is covered.

And anyone who has been appointed Lean Champion and wondered what it mean can take some inspiration between pages 98 and 105.

The three things that are not discussed but seem to be essential if you are interested in building a starfish organization are 1) direct customer involvement in the design and deliver of your product or service, 2) small teams making local decisions on how a product or service is delivered or improved, under the tutelage of a team leader and 3) the removal of the economies of scale to enable these things. These three things are all inter-related, and they should be familiar to any student of the Toyota Production System.

While most of the starfish organization examples in the book have benefited significantly from information technology, the authors vastly underplay the impact of disruptive technologies in the demise of the "spider" organizations and the rise of the "starfish". They give too most of the credit to the organizational characteristics, which they call the Five Legs.

The internet, or information technology, has a very low cost of entry and is highly scalable at a low cost. These are disruptive technologies, in the hands of the customers and they are also destroying economies of scale. Want to go to buy something at an auction? No need to have an auction house, parking lot and auctioneer. There is almost no set up cost on eBay.

If a disruptive technology creates an economy of scale or depends on it, this will not enable a starfish organization. If the disruptive technology of the last decade had been something like the steam engine, the would be a completely different story and spider organizations would be all the rage, since it takes a certain amount of capital to own a and maintain a steam engine.

It's not that starfish organizations are better or worse than spider organizations, they are simply able to compete in select niches because of the availability of the resource called information technology. To put it another way, without the internet this book could not have happened. That's not to say starfish organizations aren't a real phenomenon, only that the readers should take caution in applying the starfish model to their organization if they do not have a way of using the internet as a significant technology accelerator and remover of economies of scale.

Starfish do not move very fast or go very far. By comparison, a spider is a quick little critter and will crawl up your arm and bite you on the head lickety-split. This book is the story of high-tech starfish moving faster than spiders.

The local interest story is that my house has had no electricity since Thursday evening (this blog entry published via Starbucks WiFi connection). When we have windstorms like we did in the Puget Sound this week and 700,000 people lose power, these starfish organizations will depend on big spiders like the Puget Sound Energy people to come in and fix things and get their electricity back so they can power their computers and internet connections.

Could starfish organizations get out and fix downed power lines? Possibly. Could they run a regional power grid? Not with the current power generation infrastructure and economies of scale. Give us a new technology called co-generation or micro-generation of power and we may see starfish organizations for electric power generation. The point is that starfish require a new technology to destroy an economy of scale, or they will not be able to move fast enough to survive when the tide goes out.

The authors seem to like the idea of "no one is in charge" with the caveat that anyone / everyone can contribute to shape these starfish organizations. In Lean manufacturing terms we could say they are customer-driven to the extreme, and this can be a good thing, particularly since these organizations are not encumbered by economies of scale and can let customers (members of starfish organizations) do what they want to shape the product / service / community.

This is an important point. What allows these organizations to succeed by being extremely customer driven is that there are no local economies (costs) such as fixed assets that need to absorb earned hours, etc. that get in the way. Customers are having an impact on the design of a service that has very little fixed overhead and requires no costly molds or tooling to prototype the new design.

This is a key concern of Lean accounting in terms of how product launch and marketing decision are made by organizations who are pushed to sell based on numbers that are not driven by cost assumptions which have nothing to do with customer needs and everything to do with the prevailing technology for designing and delivering the product or service.

By the authors' definition the starfish organizations directly include the people that are consuming the services (Alcoholics Anonymous, eBay, Wikipedia) while this is almost never true of spider organizations (automobile manufacturing). This fact alone has been written about in many books, and could have been highlighted more in this book.

None of the examples given of starfish organizations make anything. They either sell a product or provide a service. They do not require significant fixed assets or a supply chain of any complexity in order to exist. Many of the examples are not for profit business at all, so the applicability of the starfish principle in making money is in itself questionable.

In Chapter 8 the authors introduce the notion of the "sweet spot" of some between the spider and the starfish is greater than either. Drucker, GM and Toyota make appearances. When the subtitle of the book is "The Unstoppable Power of Leaderless Organizations", needing a "sweet spot" between a starfish and spider (decentralized and centralized) seems like a cop out designed to explain the non-starfish aberration that is a Toyota full of strong leaders.

A story from NUMMI (New United Motor Manufacturing Inc.), the joint venture between Toyota and GM is used to illustrate the fact that the circles of workers in the factory became self-managing. When a plant manager from another GM site joined the workforce as a factory worker in a one-man sabotage experiment, the members of his team stepped in to set him on the right path, rather than the managers doing so. The sabotage seemed fairly harmless, and it would be interesting to learn how long the sabotage would have been allowed before the team leader stepped in, rather than the peers on the team.

The authors say that Toyota has found a "sweet spot" between centralized and decentralized organizations where their "circles" have enough autonomy and freedom to be creative but not to much so that thy introduce variance into the process.

The authors miss the critical importance of strong supervision for long-term kaizen (continuous improvement) at Toyota. Certainly there are quality circles and other team based improvement activities but these rely on the so-called "span of five" style groupings of team leaders and supervisors to teach, support, and troubleshoot for five other team members. They are not equals. It is not a "circle" in the sense that an Alcoholics Anonymous group is a circle or in the sense that people working on a Wikipedia page are a circle.

The authors also marvel at the 100% acceptance of employee suggestions at (Toyota cites 99%) as proof that these circles act like starfish organizations. They claim that team members are free to make changes, and that if other team members don't like those changes they can change it back. While it is true that changes at Toyota are performed as experiments, and that if an experiment fails (it is not an improvement) things are reversed or further improvements are conducted, it is not correct to say that workers can make suggestions that are 100% accepted.

While making changes to Wikipedia, or allowing team member/customers to direct how Alcoholics Anonymous sessions or Earth Liberation Front actions are taken may be alright, allowing workers (no matter how talented they may be) to make real-time changes to assembly lines moving at one vehicle per 60 seconds has intolerable real-world consequences. This is not how it happens at Toyota.

Again the span of five concept and strong supervision is involved in making the ideas of workers real life improvements. Workers have ideas, and these often require significant coaching and nurturing before they turn into feasible experiments whose impact can be measured using the PDCA (Plan Do ChecK Act) process. There is not sweet spot between spiders and starfish at Toyota. There is centralization pushed down and implemented to through each level in the organization all the way to the front lines. The highly structured nature of the organization allows for flexibility, since people are well trained to follow certain principles when responding to changes or problems.

Can the starfish concept really even apply to manufacturing companies so tied to economies of scale (whether illusory or real), or to an organization that has a complex supply chain? Can we have mass production without the management of fixed assets such as equipment, land and buildings? Perhaps the ultimate in Lean is to move beyond mass production to many small micro producers with virtually no fixed assets, and direct local customer involvement. Then again, I think we tried this several hundred years ago before something called the Industrial Revolution came along.

December 15, 2006

Gemba Keiei by Taiichi Ohno, Chapter 36: Only the Gemba Can Do Cost Reduction

Taiichi Ohno begins the chapter by demonstrating the Toyota philosophy of "aim for 10X improvement, not 10% improvement". He instructed Human Resources to give the shop floor 10 people even though they had asked for 100 people. Let them struggle and they will figure out how to get it done with 90 less people than they thought they needed. That's how Human Resources can make a 90% improvement, he says.

Ohno says that in a similar way Finance can do kaizen by using the cash freed up through inventory reduction on the gemba to make more money. The point is that when Finance allocates costs or requires cost savings from design or production this is not really kaizen. Finance must create value, but they depend on the gemba for this.

"The gemba must become fanatical about cost reduction with 'Only the gemba can do cost reduction' as a belief." Says Ohno.

Taiichi Ohno makes a very interesting and important distinction between cost knowledge and cost awareness.

"People are overly concerned with knowledge of cost, but this displaces cost awareness. I say you don't need cost knowledge. I'm not even interested in learning the terminology."

He goes on to make the point that cost calculation and cost reduction plans based on monthly targets are unreliable. When times are good and volumes are high, results may come quickly while at other times it may take a lot longer to see results. Implementing robots or computers can yield quick results, or they can take a lot longer than planned. Ohno emphasizes the importance for patience and perseverance when doing kaizen, particularly when volumes are reduced.

The word for 'perseverance' in Japanese that Ohno uses is 辛抱 (shin-bo). When people say "We must do 辛抱" in Japanese this means "We must endure hard times" and implies personal sacrifice. It is different from persevering as in simply working hard and not giving up. Understanding this and considering GM's struggles today, Ohno's following comment becomes poignant:

"If General Motors' UAW had the perseverance to accept a reduction in wage they would become a formidable competitor (to Toyota). In Japan we are not there yet, and suggesting a reduction in wages would cause an outcry..."

Ohno switches themes mid-chapter. I would have taken the second half of this chapter and made it a separate chapter named "Follow the Rules You Make". He talks a lot about rules, setting of rules, how people perceive and sometimes resist rules that are set, how kanban and Standard Work both rely on setting and following rules, as well as how Standard Work should be frequently improved updated on the gemba.

Certainly these things are related to cost reduction on the gemba, but Ohno does not make an explicit connection. I think he was telling his stories and might have drifted a bit. Nonetheless it makes for a chapter rich in the wisdom of Taiichi Ohno.

December 12, 2006

Making a Business Out of Organizing (Making You Feel on Top of Things)

I came across Productivity Cafe, the blog of Susan Sabo of Organizers, Inc. today. She is an author, speaker and consultant who "helps people feel on top of things by training, coaching, and persuading them to be more organized and productive" according to her bio on the blog.

There are many practical and useful ideas on this blog. She doesn't call it kaizen but Susan is promoting the kind of everyone everyday improvements that we love to find.

Of immediate interest to the Lean practitioner, there are some great photographs from a garage before & after 5S or in Susan's terms "organizing". The before & after photographs from the office are also good examples and can be used for office 5S training.

There are many kaizen ideas in the Productivity Cafe archives that we can put to use here in our office right away. Keep up the good work Organizers!

December 10, 2006

Gemba Keiei by Taiichi Ohno, Chapter 35: The Monaka System

How many Japanese words do we have in the Lean lexicon? Do we really need another? It's a rhetorical question, but would you rather have "sweet azuki bean jam wafer system"? I thought not. "Replaceable core system" also works, if you must. However, Taiichi Ohno gives us the monaka system.

"Dies are not general purpose items. So here is something we did." Taiichi Ohno goes on to explain the challenge of making dies that are reusable as general purpose tools rather than specialized tools. While the press machine is general purpose (can be use to make many different types of products by changing the die) the die itself is typically for only one type of part.

The monaka is a Japanese sweet that is made from a sweet bread-like crust and a sweet bean filling in the middle. The same crust can be used and filled with different "monaka" center to make different varieties of this Japanese sweet. So Ohno is making an analogy of the outer part of the die being similar to the outside crust of this food and the core of the die being the monaka or sweet bean part of this food.

Here is a picture of gourd-shaped monaka snack from a store in Tokyo. The black in the middle is the sweet azuki bean. Click on the links in blue letters between the two red squares on the bottom of this page to see other examples of tasty monaka.

Ohno says that while the sweet bean spoils if cooked ahead (overproduction) you can make the crust ahead an then cook the sweet bean filling to demand when you get the order. He also says it is a waste not to make the crusts in advance, and wait until you have an order and then struggle to make them all at once. It sounds very much like he is saying "build ahead" for the crusts, even when you don't have orders, in anticipation of orders. It is a very odd thing that he is making an exception here and actually promoting overproduction of crusts.

The idea with the die is to have the middle section hollow so that a core can be replaced and the "crust" of the die reused. Ohno admits there are challenges to this, but that this idea is being attempted in some areas. He says it will take five or ten years to go completely in this direction. As he said this back in 1989, I would be interesting in hearing from someone at Toyota just how far they did go with the monaka system.

Ohno says that this type of versatility and the ability to reuse general purpose dies and equipment is characteristic of the Toyota method.

He goes on to say that there are three elements to running a business: man (people), materials (or more broadly "things") and money. Companies must generate a profit in order to be able to continue to exist and contribute to society. Ohno says you can make money in three ways. First by being good at selling things, second by being good at managing money, and third by reducing cost.

When making sales is easy, the gemba gets lazy about reducing cost. As long as times are good you may not notice but as it becomes more challenging to make sales and as it gets harder to make money through financial instruments, engineering work and work on the gemba become most important, says Ohno.

Ohno points out the difference between having 500,000,000 yen in cash or 500,000,000 yen in the warehouse as inventory. On the one hand you can use the cash to to make money through investments in financial instruments while the inventory will cost you 10% interest to the bank. You can pay dividends on profits to shareholders on one hand, interest to the bank on the other.

"When people hear cost reduction they tend to think of it as an accounting function. But accounting can't do cost reduction." Taiichi Ohno says it's all up to what you do on the gemba to make a profit, pay your taxes and contribute to your country.

December 8, 2006

And Now We Have "Kakushin" (sigh...)

In the December 9, 2006 Wall Street Journal article titled As Rivals Catch Up, Toyota CEO Spurs Big Efficiency Drive the Toyota Motor Corporation President Watanabe adds another Japanese word to the Lean lexicon: kakushin. Debates could rage for years among Lean geeks: is it kaizen, kaikaku or kakushin?

Let's get this out of the way so we can get back to work:

Kaizen = 改善 = change+good = improvement / continuous improvement
Kaikaku = 改革 = change+revolutionary = transformation / reform / big improvement
Kakushin = 革新 = new+revolutionary = innovation / reform / renewal

The WSJ article explains kakushin as "revolutionary change" but this is wrong. Kakushin literally means "innovation" or reform as in the reformists in a political party. It is different than innovation as in the current business buzzword, meaning coming up with new things to sell. "Renewal" or "radical renewal" would be best for kakushin. Kakushin is more akin to kaikaku than kaizen.

So why is Watanabe using kakushin rather than kaikaku? For one, kaikaku is becoming a rather tired word in Japan. Perhaps a new word is needed to get everyone's attention. The former prime minister of Japan was beating that drum throughout his tenure, and kaikaku in Japan has caught on to mean something similar to "Lean transformation" to manufacturers and other business, though it is a bit broader and vaguer.

Clearly Watanabe is putting his own stamp on the change he wants to see at Toyota using this word. What does he want from kakushin? Start with cutting the number of parts in a car in half, make the factories faster more flexible to manufacture the simplified cars, and cut out $8.68 billion in cost, according to the WSJ article.

One quote from the WSJ article is classic Toyota thinking:

"We know our resources are stretched thin; there's no doubt about that," Mr. Watanabe says. "But at least we are beginning to know where our problems lie now. Our biggest fear is: What if those issues get stuffed in a desk drawer?"

That would be a big, scary desk drawer.

The rest of the article is a combination standard PR-piece profiling Watanabe and contrasting Toyota's success to Detroit's woes, but it also discusses efforts at Toyota to slim down machinery, equipment and even paint lines in an effort to be more flexible and cut cost, which gives a better idea of what Watanabe means by kakushin.

What I want to know is, what are they going to do when they run out of "kai" and "kaku" words to rally the troops around?

December 6, 2006

When the Customer Defines Value, But They Define It Poorly What Do You Do?

If a customer says "Here's how I want to do Lean." and the consultant says "That's not the right way." and the customer says "Who's the customer here?" and the consultant says "You are." and the customer says "Then I say what I'm willing to pay for." and the consultant says "Yes, but you are asking us to do something in a less effective way than we could." and so on until the customer fires the consultant, you have a situation where Lean thinking is put to the test.

In Lean thinking the customer is supposed to define value, but if the supplier is a Lean thinker (consultant) and recognizes that the service the customer is asking for is full of waste then integrity requires that the supplier (consultant) not deliver what the customer is asking for. When the customer defines value but they define it poorly what do you do?

Part of the reason consultants are so reviled is that they do not listen to the customer. They don't attempt to understand the current condition thoroughly enough. They try to sell what is easy or what they have tried and what worked before. They are not humble. How does the consultant know, other than through experience, anecdotal evidence or perhaps gut feel that what the customer is asking for is wrong?

We find that many of our customers are becoming more educated and sophisticated about Lean. They form an image in their minds of what they want from a Lean transformation or a relationship with Lean instructors. This makes them better buyers of Lean training services and better shepherds of a Lean transformation in their companies. This is good. Yet we are recently seeing cases where the customer is not always right.

If you are selling a widget it may be alright to chant the mantra "the customer is always right" and give them whatever they ask for even if it is not what they really need, if the customer is stubborn. But when the product you are dealing is redesigning the work of thousands of real people (Lean transformation) in a way that influences the culture of an organization for years to come and without a doubt the future financial viability of the company, the seller bears a certain moral responsibility.

It's a tough challenge. If we walk away, some other consultant will happily sell them the "wrong thing". If we stay on and do the easy thing of accepting the assignment in hoping we can influence them towards the right thing, we risk wasting everyone's time. It's not buyer beware, it's seller beware. If only more consultants thought this way perhaps we wouldn't get such a bad name.

December 5, 2006

How to Put Kaizen into Your Culture

These are the two steps for how to put kaizen into your culture.

First, communicate with your people until you have a common agreement and 100% alignment on these principles:

The reason we can make our living is because we serve our customers.

Customers pay for value, as defined by them.

Most of the work we do in order to deliver value to our customers is actually waste.

The target condition is zero waste.

Nobody has achieved this target condition, therefore we strive to be the first and never give up.

All improvement ideas should eliminate one or more types of wastes.

A safe, clean and organized workplace promotes quality and productivity.

Improvement is everyone's job.

Each one of us has the power to make things better.

The current condition is unacceptable, no matter how good we are.

Second, teach those who demonstrate behavior that contradicts the above principles, but do not tolerate such behavior from anyone.

If you have respect for people, putting kaizen into your culture is simple. I really don't have much more to say about that.

December 4, 2006

One-Hour Low Tech Lean Introduction

Today was a lesson for me in just-in-time delivery of Lean training (or Lean Lean training) and also in the value of being prepared. We arrived half a day late to a distribution center where we were asked to give Lean overview training to the warehouse managers. We had prepared fifty plus PowerPoint slides complete with Lean fundamentals, a simulation, three case studies, and a road map to implementation, everything had asked for. We had a plan.

But no plan goes according to plan. Arriving late, we were asked to give one-hour low tech lean introduction rather than the slick presentation we had prepared for to the group of managers, since time was limited. Twelve of us crowded into an office.

Think fast: if you have only 60 minutes, no visual aids and you have to communicate what is most important about Lean, what would you say?

Looking back, there were 10 main points. We spent the most time on topics 3, 4, 5, 6. Here is the recipe:

1. Where does Lean come from?
2. Why has Toyota been so successful?
3. "Kaizen and respect for people"
4. What are the 7 types of waste?
5. What is 5S and how does it make waste visible?
6. What is flow and how does it make problems visible?
7. What is takt time and how do we use it?
8. What should we do when you find a problem?
9. What is the role of standards in Lean?
10. What is the role of the manager in a Lean company?

To these ingredients add your own experiences, ask for examples from the audience, and stir. Sprinkle impressive kaizen statistics as appropriate. At the end of one hour your audience will have a better understanding of Lean and how it applies to them.

As in Lean, less is more when doing presentations. This off-the-cuff (or just-in-time) training resulted in good discussion among the managers. "Let's take a walk and see if we can have a discussion about the wastes in our facility" said the director and we all took a ninety minute gemba walk across half a million square feet of warehouse.

December 1, 2006

Gemba Keiei by Taiichi Ohno, Chapter 34: The Pitfall of Cost Calculation

In this chapter Taiichi Ohno talks about the pitfalls of using cost calculation to justify new equipment purchases and also decisions to scrap or replace equipment based on depreciation.

"Whenever we need to make a decision, we end up doing something like cost calculation. Cost calculation is not wrong, but I think top management sometimes makes the wrong judgment because of it."

Taiichi Ohno explains how equipment purchases are made based on forecasts of production volume over a period of years. When these assumptions are wrong, these can become expensive purchases. He points out how it is easy to make cost calculations say what you want them to, when you have already decided that you want to buy the machine.

Ohno moves on to the discussion of equipment depreciation as part of cost calculation. Equipment depreciation contributes to retained profit. Ohno criticizes production engineers in large, profitable companies who say "That machine is fully depreciated. It is old and wearing out. We can improve productivity by buying a new machine." Ohno says believing that the money from the retained profit was used to buy the new machine is a misconception.

Ohno wants to see a company continue to use the fully depreciated equipment. The machine is already paid for and can make more profit more quickly than investing in new equipment. Yet accountants want to take advantage of depreciation against taxes.

Ohno is a fan of general purpose machines rather than equipment specialized or optimized for a particular product. Simple, fully depreciated general purpose machines can be easily modified and dedicated for a new part, and this is a key aspect of flexibility for Lean manufacturing.

Ohno says he first began telling people to build what he calls "general purpose dedicated machines" after the first oil shock in 1973. By the late 1980s this had become more common practice and the majority of equipment cost was in the tool and die. At Toyota 60% of the cost of the equipment is the tooling (metal dies), says Ohno.

Putting Ohno's comments from this chapter in historical context, the Japanese economy grew steadily between 1950 and 1990 and between these years. Ohno likely saw many investment decisions that were based on the assumption of ever higher production volumes, and by definition not all forecasts can be correct. The result being either overproduction to justify the equipment cost (the greatest of the seven types of waste) or an embarrassingly idle new machine.

I'm sure Ohno saw many old but useful machines scrapped and replaced by the new generation of engineers who had never experienced the post-war days of scarcity and had fallen into the pitfall of cost calculation. Today when we walk through the Toyota's Kamigo engine plant in Japan you will see plenty of "general purpose dedicated machines" and old equipment, thoroughly depreciated but still making money for Toyota.