by Marc Onetto<\/p>\n
The spirit of lean management<\/strong>\u00a0was already at Amazon when I arrived in 2007. Since the day he created Amazon, Jeff Bezos has been totally customer-centric. He knew that customers would not pay for waste\u2014and that focus on waste prevention is a fundamental concept of lean. The company\u2019s information technology was always very good at understanding what the customer wanted and passing the right signal down. For example, the selection of the transportation method for a given package is driven, first, by the promised delivery date to the customer. Lower-cost options enter the equation only if they provide an equal probability of on-time delivery. That\u2019s basically a lean principle.<\/p>\n As a technology company, Amazon initially had the belief that most issues could be resolved with technology, so it was not systematically engaging frontline workers in a process of continuous improvement. Part of lean is the strong engagement of the front line\u2014with the\u00a0gemba<\/em>\u00a0workers\u2014on continuous improvement. Amazon has more people working in the fulfillment centers and customer-service centers than it does computer-science engineers. We needed the engagement of all these people to succeed, since they are the ones who are actually receiving, stowing, picking, packing, and sending packages or responding to customers by phone, chat, or e-mail.<\/p>\n Earlier in Amazon\u2019s development, the company had been trying to automate almost everything in a fulfillment center. The automation was designed for books but did not work for new types of goods, such as shoes, as Amazon expanded its selection. When the shoebox reached the flip mechanism in the automated machine that was supposed to collect the shoes and bring them to the packing line, they went flying out of the box. As a consequence, we were limited to certain types of goods in the automated warehouses.<\/p>\n Given the business evolution of Amazon from a bookstore to the store for everything, we had to reinvent automation, following the lean principle of \u201cautonomation\u201d: keep the humans for high-value, complex work and use machines to support those tasks. Humans are extremely creative and flexible. The challenge of course is that sometimes they are tired or angry, and they make mistakes. From a Six Sigma perspective, all humans are considered to be at about a Three Sigma level, meaning that they perform a task with about 93 percent accuracy and 7 percent defects. Autonomation helps human beings perform tasks in a defect-free and safe way by only automating the basic, repetitive, low-value steps in a process. The result is the best of both worlds: a very flexible human being assisted by a machine that brings the process up from Three Sigma to Six Sigma.<\/p>\n Another major dimension of the deployment of lean was the enforcement of \u201cstandard work.\u201d The problem at many companies, including Amazon, is that workers\u2019 assigned tasks are very vague; it\u2019s up to the worker to figure things out. So when we started to consider improving our workers\u2019 performance,\u00a0<\/sup>we had to take a detailed look at their assigned tasks. We quickly realized that what was happening in reality was quite different from what was written down\u2014and it was riddled with abnormalities. So we set a very well-defined standard process, tracked all abnormalities, and assigned\u00a0kaizen<\/em>\u00a0teams to eliminate them.<\/p>\n I saw this directly when I worked on the stow line in one of the fulfillment centers. Each worker on that line has a trolley full of products and a scanner. The job is to stow the products on the shelves and, at the same time, to scan each item and the corresponding shelf number so the computer knows where the product is located. The standard work-productivity target was 20 minutes per trolley. But when I started to scan products, I realized that I had to scan some things four times before the scanner recognized them. So instead of 20 minutes per trolley, it took me 45. I looked incompetent; I couldn\u2019t meet the target. But in fact I was affected by an abnormality: the bad performance of the scanner, which I learned later was due to a low level of charge in its battery.<\/p>\n At the end of the day we analyzed all the abnormalities reported by the workers. And in my case we looked for the root cause of the scanner issue. How many scans could be completed during the life of the scanner battery? Did we have a process to check and reload the scanner batteries? Frontline managers didn\u2019t have any of that information, so there were several hours of low productivity at the end of every scanner\u2019s battery charge. That root-cause analysis helped us put a whole process in place to load and monitor our scanners. Now workers will never miss productivity targets because their scanner batteries are low.<\/p>\n Kaizen<\/em>\u00a0and the whole process of continuous improvement was, and continues to be, a powerful tool at Amazon. That\u2019s partly because for a long time Jeff Bezos has had all of senior management work in customer service at least one day a year. This allowed executives to see events on the front line, to understand the problems that came up, and to help find solutions.<\/p>\n Each\u00a0kaizen<\/em>\u00a0is a very simple thing, but the accumulation of\u00a0kaizens<\/em>\u00a0makes an enormous difference. On one of Bezos\u2019s days on the front line with me, he was staffed in Receiving, which is where all of the defects that come from the ordering process and the delivering process arrive, and you have to deal with all sorts of problems. At the time, Amazon had just started its Fulfillment by Amazon business.\u00a0Some of the merchants were not very disciplined, so they were sending products that were not labeled or packed properly.<\/p>\n Bezos opened a box of shampoo and all of the bottles were broken. They spilled all over him and he nearly cut himself. No customer is going to buy shampoo if the bottle is broken, and we can\u2019t risk the health of the worker opening the package. So we agreed that we had to implement a \u201cthree strikes\u201d packing process for merchants using our fulfillment services: the first time there is a problem we explain the packing rules, the second time we give the merchants a warning, and the third time we end their relationship as merchants with Amazon. That was one of the most memorable\u00a0kaizens<\/em>\u00a0for me.<\/p>\n We also used\u00a0kaizen<\/em>\u00a0at the workstation level to reach new productivity objectives for stowing products. Our goal has always been to stow products within a certain time period and with a certain number of frontline staff, because stowing accounts for about 20 percent of the costs in our fulfillment centers.<\/p>\n The challenge was that the productivity of our carts was very unpredictable: stowing a small book does not take the same time as stowing a computer screen. We spent time on the front line recording the time to stow different products, and we decided there were three types of carts. We defined products for each type and the time to stow those products. We then tested that idea and revised the process. We used\u00a0kaizen<\/em>\u00a0to improve the standard work by reducing stowing times, so we solved things bottom-up on the front line to achieve the top-down goals for productivity.<\/p>\n Our ideal\u00a0kaizen<\/em>\u00a0teams are a combination of frontline workers, engineers, and a few executives who are going to ask questions and have no preconceived ideas. You put these people together and you say, \u201cHere\u2019s a problem; we\u2019re going to improve it.\u201d Then you raise the bar on improvement. The\u00a0kaizen\u00a0<\/em>team should be judged on results that will be meaningful for the company in the long term. You have to ask people to use their brains and their imaginations to solve problems.<\/p>\n Soon after I started at Amazon, I discussed implementing the\u00a0andon-<\/em>cord\u00a0principle in customer service. Bezos was enthusiastic about it right away and we implemented it in about six months. The process begins when a service agent gets a phone call from a customer explaining that there is a problem with the product he or she has just received from us. If it\u2019s a repetitive defect, we empower the customer-service agent to \u201cstop the line,\u201d which means taking the product off the website until we fix the defect. The objective is to start the line again with the defect resolved. We created an entire background process to identify, track, and resolve these defects.<\/p>\n The\u00a0andon\u00a0<\/em>cord has had an amazing impact; it eliminates tens of thousands of defects per year. The other wonderful thing is that the\u00a0andon<\/em>\u00a0cord has empowered frontline workers. The authority to stop the line is an enormous proof of trust for customer-service agents, who usually have no real authority to help irate customers over the telephone. With the cord, the agents have been able to tell customers that the product has been placed in the lab for quality problems until the defect can be resolved. At the same time, they offer customers a new product or reimburse them. Customers can see products pulled for quality issues on the website in real time. This has created incredible energy and motivated our frontline people to do great work for our customers. Our frontline people\u2019s assessments are almost always correct: 98 percent of the time, the\u00a0andon\u00a0<\/em>cord is pulled for a real defect\u2014proof, if it were needed, that when you set up a good process, you can trust people on the front line to use it well.<\/p>\n Perhaps the biggest challenge I see is the application of lean-management principles to software creation, which is highly complex, with numerous opportunities for defects. Software engineers have not yet been able to stop the line and detect defects in real time during development. The only real testing happens once the software is completed, with the customer as a beta tester. To me, this is unacceptable; we would never do that with a washing machine. We would not ask customers to tell us when the washer leaks or what\u2019s wrong with it once it has arrived at their homes. I\u2019ve tried to address the problem, and some of Amazon\u2019s computer-science engineers have looked at it, but it is still one of the biggest challenges for lean.<\/p>\n On the other hand, I\u2019m extremely excited about 3-D printing. I don\u2019t completely know what it means on a larger scale. Right now, Amazon is selling 3-D printers, but to my knowledge it has not yet expanded to actual products on demand. Perhaps some manufacturers are beginning to distribute 3-D printed products. It\u2019s not science fiction anymore, but it is still experimental.<\/p>\n It\u2019s fascinating because it\u2019s the concept of print on demand extended to absolutely any product. Today, in some fulfillment centers, there is printing equipment that allows Amazon to print and ship a book within four hours of a customer order for it. 3-D printing is just an extension of this concept to all sorts of goods other than books. The idea of making a product for the customer at the time the customer actually orders it is fascinating because that\u2019s what the creators of lean always dreamed about. It\u2019s the ultimate just in time.<\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[71],"tags":[],"blocksy_meta":"","yoast_head":"\nKaizen<\/em>\u00a0in the fulfillment center<\/h3>\n
Pulling the\u00a0andon<\/em>\u00a0cord<\/h3>\n
Next frontiers<\/h3>\n