General GENERAL

The seven deadly sins of the gemba

FEATURE – What are the immediate signs that tell us our workplace is not conducive to kaizen? The author reflects on his experience as a coach in the gemba to highlight them. Watch out for them in your company!

During a recent gemba walk, I was asked: “what are the deadly sins of the gemba?”. The question stopped me in my tracks. When I asked for clarification, the person explained that they wanted to know what symptoms of a wrong approach to lean implementation can be spotted just by looking. “What,” they asked, “is evident on the gemba, without having to look at the details, that indicates there may be a misinterpretation of lean principles?”.

I am not sure it is healthy to comment in moral terms on a method that is based on experiments without applying the rules, but let us think about it.

I think a “deadly sin” of lean thinking would be creating a work environment where there can be no kaizen or, to be more specific, where kaizen ideas cannot be expressed. And, yes, some signs you can see right away, as soon as you arrive on the shop floor.

If I had to list them off the top of my head, I would say:

1. No red bins.

2. Isolated workstations.

3. Parts moved in batches.

4. PowerPoint charts on the boards.

5. No daily planning and comments.

6. No 5S efforts.

7. No way to ask for help.

Now let us look at these examples one by one.

NO RED BINS

Red bins need to be literally red (red means a quality problem), but they do not need to be literally bins (they can be an area – like the red refrigerator here). Every process should have a clearly identified place to set defective – or potentially defective – components apart from the work. Without this dedicated place, it is obvious that the focus on quality is not on the shop floor with the employees, but somewhere in the management office. This completely kills the spirit of kaizen, because it tells people that we do not need them to do quality work, since whatever they do wrong will be fixed somewhere else.

There are two other horrible variants of the “no red bins” sin that you still see on the gemba:

Reject boxes painted red – nothing more than containers where defective parts are thrown without analysis. Painting them red does not make them red bins. A proper red bin should set the defective parts apart and trigger a quick analysis: what is wrong with this part? What happened in the process?

Jails – in some places, there are “locked jail cells” holding bad parts waiting to be analyzed by the quality department. In other words, when a part is potentially defective, it is locked up, and the quality department comes whenever it sees fit to see what the problem is. This is batching quality analysis. Obviously, it is very wrong to do this, since the message sent to everyone on the shop floor is to just keep working, wipe their noses, and not ask questions – if any problem comes up, put it in jail, and the quality people will deal with it eventually.

ISOLATED WORKSTATIONS

In recent years, many assembly lines have moved to lower-cost countries in the East, and the processes that remained in the West have become more technical and machine-bound. As a result, we see shop floors with machines scattered around and operators isolated behind each machine. This is the end of kaizen, because, even if an operator has the best idea for reducing work content and improving standard work, he cannot translate it into more productivity, because he is too isolated. This situation must be avoided at all costs, because it stifles teamwork and the spirit of kaizen.

Isolated workstations scattered across the workplace – or clusters in process islands – mean there is no flow; no flow means not looking at products one at a time, so there is no opportunity to see the variation between how we make two products; no variation means we do not see problems and do not carry out kaizen. In the old days, the first thing we would do to start lean was to create flow, sometimes clumsily, in order to create the conditions for kaizen. With isolated workstations, working together in a “relay race” is impossible, and not only will there be few kaizen ideas, but they will also be hard to implement because of the difficulty of showing their practical benefit.

PARTS MOVED IN BATCHES

You can tell right away when parts are moved in batches. There are usually stacks of containers on pallets waiting to be moved by forklifts. Forklifts, as opposed to trains, are usually another good clue. If parts are moved in batches at the workstation, they are probably being taken to a work-in-process or finished-goods inventory, and the real manager of the workplace is the MRP. Since MRP is good at rescheduling to keep people busy and is not very interested in improvement, the chances of kaizen are very low. As with isolated workstations, any place that is run by a computer means death to kaizen, because good ideas cannot be translated into better performance. IT scheduling systems are not flexible enough to incorporate good ideas.

Some clever people have found more flexible ways to move parts, using devices that look like trains, but these are still batches (instead of one large container, you are still moving three smaller containers at once). You need to move every part every hour, not create a fake pull flow. The question remains the same: if I have an idea that can reduce changeover time and, as a result, reduce the batch size (usually calculated as ten times the changeover time), can I benefit from it by moving parts faster? Without proper pull flow, I cannot, since pickup will still only happen once the batch is complete.

POWERPOINT CHARTS ON THE BOARDS

Another clear sign that the company does not understand kaizen is large areas with lots of boards full of PowerPoint charts, most of them hiding the shop floor. This is where frontline managers gather for so-called “visual management” or “leader standard work,” but it makes no sense. It is nothing more than another way of showing operators the difference between the people who do the work and those who run the show.

True visual management creates a workplace where the differences between normal and abnormal can be identified immediately, without having to look at a board. The charts are handwritten, because they are filled in as the work progresses (as opposed to being printed from a computer), and they are conducive to kaizen – not the other way around.

On the boards, we look in particular for:

  • Photos of defective parts: explaining over and over what can happen at the customer if certain criteria are not observed in production. Daily analysis and discussion of customer problems are essential to keeping the spirit of kaizen alive.
  • Operator tracking, to ensure that operators take responsibility for their results and always think about better ways to do the work. Be careful, however, that the tracking is not linked, or does not seem to be linked, to a performance appraisal. In lean thinking, these tracking charts are about the “check” part of PDCA, as a way to support the spirit of kaizen by having an instant measure of results.

Management loves to talk to itself and fill boards with information it believes operators should follow. This is the opposite of lean management (talking to operators to address their concerns) and a sure sign that the workplace is not designed for kaizen.

NO DAILY PLANNING AT THE WORKSTATIONS

Production Analysis Boards, which show hourly targets, actuals, and comments, are not for control, but for developing autonomy. Teams are taught to 1) plan the day's output (like planning your route to visit someone on the weekend), 2) check how the day is going, hour by hour, and 3) write down any obstacles encountered in keeping the promise for the day. In a lean environment, it is the comments that matter most – the team's engagement in observing and explaining what is not working as it should.

Comments on the plan, whether on an hourly board or an actual plan, are essential to starting kaizen – they are the first step toward taking responsibility for our problems and seeking to solve them. Of course, this only works if management is interested and regularly comes to check the boards to have that conversation. Otherwise, people will quickly abandon the demanding practice of saying what, in their opinion, is wrong with the process.

Unfortunately, many Production Analysis Boards I have seen are devoid of analysis – management does not care enough about the current working conditions to discuss with its teams how to improve them on an hourly basis. As a result, the “comments” column is always empty – or sometimes does not even exist –, which makes the board just another tool for showing that output is below plan (yes, well, there's a surprise). Without visible interest in why the output was not achieved (defective parts? Slow machines? Lack of qualified staff? Problems with components? Target hard to reach with the current work method?), there is no way to start kaizen.

NO 5S EFFORTS

I do not mean that the workspace is messy or dirty – I mean that there is no 5S plan. The purpose of 5S is people's learning through the regular practice of 5S to create the kind of work environment where standardized work is easy to follow.

Five S is actually 3S, followed by a fourth and a fifth S:

1. Sort and eliminate: look around and throw away anything that will not be useful in the near future (or archive it).

2. Set in order: every item in regular use should have a dedicated place, in a way that makes it easy to access when needed, according to the frequency or urgency of use. Setting in order is not just “a place for everything, and everything in its place”; it is about thinking where things should be according to how they are used.

3. Shine: make sure everything is clean and working after use – so that the next cycle happens without surprises. Clean up after use, change the batteries, put fuel in the car after driving. Shining means taking responsibility for the workplace and making sure the next user can do their job with confidence.

4. Standardize: what is the 5S plan so that 5S takes place regularly? This is where the team takes responsibility for itself and decides on a standard way to carry out 5S (after each job? Five minutes before the end of the day? A weekly cleanup?). This is when 5S really starts to happen, when teams begin doing kaizen on their environment based on what they find during their regular 3S exercises.

5. Sustain: how can management support the fourth-S plan? By auditing and helping to improve the work environment. The fifth S is about engaging teams in their own workplace and recognizing their work by helping them with problems that are beyond their control (such as IT problems, replacing poor equipment, etc.).

Without 5S, kaizen is unlikely to happen, because people will not try to take responsibility for their workplace and improve it. Improving the 3S is the smallest kaizen anyone can do, and it is a great start. By introducing 5S carefully (which does not mean: “clean your room!”), management can support and sustain kaizen and then move on to real work methods.

NO WAY TO ASK FOR HELP

Last but not least - perhaps this should even be at the top of the list - is knowing how, at any workstation, people can deal with a difficulty. In many cases, managers explain that when something seems wrong, employees simply have to stop their work and go find their manager, who, by the way, has an open-door policy and will certainly help them. Sure, let us imagine the person stopping their work (and therefore affecting output) and promptly interrupting their manager. No doubt the manager will immediately stop his own work and help, right? What is the likelihood of that happening?

The purpose of an andon system is to create a built-in learning system. Whenever in doubt, an employee can signal a problem and receive support within a minute from their team leader, who will then check the standards and lend a hand to correct the situation. This is like having an on-site tutor whose job is to help you learn and maintain standards while you work. The relationship that this close contact builds is essential to kaizen, which emerges spontaneously when people point out the same difficulty several times and begin to wonder whether it is possible to change how things are done to eliminate a problem.

Creating a pull system with andon is not the end point of lean, but it is the starting point of kaizen. As Jim Womack and Dan Jones saw years ago, the entry fee for lean is to focus on value, distinguish value streams, improve flow, and pull in order to then relentlessly pursue perfection through kaizen. Kaizenmeans building a better process with the people who do the work and taking their workplace to a higher state of performance, not by having all the answers and implementing them, but by exploring problems with people and accelerating the flow of ideas up the management line and across departments.

Beyond these obvious "sins" that show up when you take your first step on the gemba, there is a deep problem that requires a second look to solve: are people working as teams, and do the teams have a leader? Teams are the locus of kaizenkaizen will really be possible – and, in fact, this worldview explains how the gemba is configured around the previous “7 sins.”

One of the first questions my father, Freddy Ballé, asks on the shop floor (after asking about quality performance) is: how are people organized? Management often presents organization charts to show how authority flows from the CEO down to each department head and employee. "No, no," he explains, pointing to a value-adding employee, "how is this person organized? What team is she part of? Who is the team leader?" One of Toyota's most important - and revolutionary - ideas is to redefine the job as JOB = WORK + KAIZEN, and not just work. Kaizen happens in a team when the team 1) masters its own work procedures and improves by discovering new and better ways, and 2) individuals come up with new ideas and suggestions. This will not happen on its own unless a team leader leads this process with the support of his own frontline manager. The lack of teams or team leaders is probably the biggest sign on the shop floor that the company, regardless of all the lean bureaucracy it has put in place, is not seriously committed to developing the kaizen spirit in every person.

TO CONCLUDE

I am not sure that “deadly sins” is the right term. The definition of “sin” is a transgression in the eyes of God – which seems a bit excessive in the context of lean thinking –, while another, more casual meaning is simply “missing the mark.” In this simpler sense, it is really easy to miss the mark in a lean implementation. The purpose of lean tools and processes is kaizen – improving customer satisfaction by engaging all employees in small changes, one after the other. Too often, managers will “implement” lean to fix the process and simply replace, for example, an ERP system with kanban cards, still without kaizen.

Kanban, for example, should be a tool for kaizen (cards constantly reduced), and not the other way around – doing kaizen to install kanban. The goal is 1) to receive improvement suggestions from every person all the time, 2) to prevent problems and eradicate their causes on a daily basis, and 3) for teams to take responsibility for their own work methods and improve them regularly, one topic after another.

Certain workplace conditions, such as flow and pull, will support kaizen; others will inhibit it. In this sense, yes, you can see at a glance how certain features in a shop floor layout can make it hard for kaizen to happen and thrive. Learning to see them immediately and understanding the various ways in which they will hinder your ability to improve is a fundamental part of learning to think the lean way.

This article was originally published in: Planet Lean

Read also: continue your learning journey

The new bounded rationality: why more AI does not mean better management

Lean It Up

The new bounded rationality: why more AI does not mean better management

Read article
Pets and management: Modern Pets' lean journey to ‘scale’ veterinary service

Healthcare

Pets and management: Modern Pets' lean journey to ‘scale’ veterinary service

Read article

From theory to practice: next steps

Team in a consulting meeting

Lean operations consulting

Diagnosis, planning and implementation with experts working directly in your organization's gemba.

Learn more →
Professional organizing sticky notes on a board

Lean training

In-person and online training for leaders who want to implement continuous improvement in their organizations.

See upcoming dates →
Launch of the book Gente Lean — Management is not about tools, it's about people

Turn knowledge into results.

At LeanShop you'll find the leading books, e-books and collections on Lean, Lean Thinking, continuous improvement, leadership and operational excellence to take your management to the next level. Explore content that helps professionals and companies create more value with less waste.

Visit LeanShop now →