The Difference Between Simple and Easy

A while ago, my boss made an interesting distinction.  Someone made the comment that lean was “easy”.  He said, “No, lean is simple, but it isn’t easy”.  I thought it would be fun to dig into this a little.  Sometimes the most profound things are “simple”.  I think that this statement that Nick made is one of those things.

Several years ago, we were holding a post job review on a project in Santa Cruz.  This project had several different elements.  Some punched windows, some curtain wall, some vent windows, louvers and some corrugated siding.  We track our labor by each system so part of the review is to talk about what went well and where we can improve and look at that by system.  Our field lead man made the point that the most difficult part of the project was the siding.  He felt we should avoid that material and scope of work in the future because of the amount of work it required.  The PM looked at the numbers and said “that was the most profitable part of the project!”.  So, the fact that it was “hard” was not the issue since they actually performed the work in less hours than we estimated.  The other “easier” systems had run over on hours.  Of all the systems on this job, the corrugated siding was the “simplest”.  You got the material in sheet form.  There was only one width and one length available.  You just cut it in on the site to fit.  It did require more manual labor on the site, but it was simple.  Now, think of the curtain wall system.  It wasn’t hard.  Unitized wall is fairly easy to set in the field.  You hook it up with a crane and set it in place.  But it isn’t simple.  Tons of engineering, shop drawings, fabrication tickets, automatic machinery, different vendors, glass sizes, and other elements go into creating this system that ends up being easy to set.  But no one would call it “simple”.

In lean, we are really searching for simplicity.  We don’t want complicated systems that take tons of “non value added” steps to create.  We are looking to eliminate the “waste” and only have value flow to our customer.  So we look to simplify the system.  We look to simplify the shop drawings and the tickets.  We look to simplify the fabrication required.  And with each simpler step, we remove waste.  Does that make it easy?  No.  Easy would be to just do what you did yesterday.  Easy would be to not challenge yourself each day to find a better way.  Easy is the “if it ain’t broke, don’t fix it” philosophy.  Making things simpler is the hard work.  There is nothing easy about it.

As another example, look at De La Salle football.  They built a simple system that created a 151 game winning streak that ran from 1992 – 2004.  Was it easy?  No.  They had to work hard every day, every game, every year to beat their rivals.  But even though the players they started with were just average and the players change every year, they managed to win every game for 12 years in a row.  Simplicity.  Speed off the ball was a key simple strategy and they made it work.  Tons of hard work went into getting that simple idea to flow.

So, don’t spend too much time in your lean journey looking for easy.  Spend your time trying to simplify your processes, simplify your systems, and remove steps.  Paul Akers had 4 things to identify to see if you should proceed with any improvement idea.  1.  Is it safer?  If it has the potential to make it less safe, do not proceed.  2.  Will this change improve quality?  If it has the potential to make quality worse, do not proceed.  Is it simpler?  If it has the potential to make things more complicated, do not proceed.  Finally, will it make it faster?  If not, it is not an improvement.  These checks are in order of importance, so if you can’t pass the safety test, don’t move on.  If you get past safety and can’t pass the quality step, don’t move on.  But his third step is simpler.  Even if it will make it easier (save time) you should forego any improvement that makes things less complicated even if it will save you time.

So think a little on this idea and let me know how you will apply it in your work.

Heading to Japan

Heading to Japan

During the first week in March, I will be visiting Japan.  I was invited on a tour being conducted by Norman Bodek.  Norman has been to Japan over 80 times and is responsible for bringing many of the books on lean published in Japan back to the United States.  Nick (my boss) had been invited on the trip by Paul Akers.  This is a fairly large group so I will get to meet a bunch of new people!

We are starting off in Tokyo.  We will be there for a couple of days and then move on to Nagoya.  In Nagoya we will visit Toyota and Mitsubishi.  We then move down to Kobe where we will visit the Mazda plant.  Our final stop is in Kyoto.

During this tour, we will be learning the Harada method from Norman.  Mr. Takashi Harada created a method of self development that speaks to the human side of lean.  It is a way to instill self reliance in each person by helping them achieve their goals.  I am in the middle of reading The Harada Method book and establishing my goal for the trip.

I will go into detail on my blog about my experience in Japan.  Since many people will not have this opportunity to go to Japan or spend a week with this amazing group of people, I hope to document my trip here on my blog and share the things I learn and see.

A Culture of Kaizen

This week, we had another 2 Kaizen events in our company.  As many of you know, we have been working on adopting lean into our company for the last couple of years.  As this process has evolved, I thought it might be interesting to document my thinking so far.  This has been the most interesting part of lean for me.  Unlike most of the other subjects I have studied (music, programming, project management, etc…) this is not a linear progression.  It is also not a simple subject.  It is a combination of intellectual learning and hands-on experiments that continually evolves for me.  If you asked me what my definition of lean was 6 months ago, it would be very different than what I would tell you today.  No doubt, if I blog about this in the future, my thoughts will have morphed again.  Here are some of my thoughts to date:

  1. Lean is top down.  We started our lean journey in the management group.  COO, CFO, Vice Presidents, Controller, Owner, Directors.  We all began this journey together before we announced anything to the company.  What would this look like?  What does it mean to continually improve together?  What do we need to know in order to teach this to our teams?  We read books on the subject together, sharing our key points each week in our management meeting.  We made improvement videos every week to learn the discipline of Kaizen.  We took tours and met other lean leaders to get their input. We toured companies that we admired and that we wanted to emulate.  We toured companies where the way they saw lean was very different from what we wanted to do.  We toured companies that had started then failed.  We learned from all of them.  We sent two of our best employees off to get certified in lean.  Was that a good path for us?  Lots of exploration and study to really understand if this was something we could commit to 1000 percent.
  2. Lean is bottom up.  We put everyone in a lean class.  As we began our roll-out, we wanted to be sure our staff understood what we were trying to do.  We taught the classes.  We were the teachers and coaches for the whole company.   We still are.  I have 3 one hour classes that I teach every week.  These classes were cross-functional.  We were exposed to people from other departments (front desk, accounting, auto shop, project management, purchasing, engineering, shop, field).  We were teaching people we don’t manage and meeting a ton of people we hardly ever work with.
  3. Lean is a team sport.  Working together to fix things.  Working together to solve problems and make things better.  We have been doing two Kaizen events each month.  Pick a problem, select a team, sequester them for one week, bring in a coach and work on that problem and see if you can create a better way.  Again, very cross functional so you are working with a bunch of people you might only have a passing exposure to.
  4. Lean is visual.  Get out of your computer.  Put up a white board.  Write down the plan for the day, write down how you are doing, write down your problems.  Get the team around the board and talk it out.  Make things better each day.  Work as a team.  Have the managers walk the floor and see the problems.  Have the managers help solve them.

The bottom line, lean is about people.  This road we are going down has started to really open up the communication between all parts of the company.  It is starting to break down department walls and boundaries.  I’m working along side people from all over the company, not just the people that work for me.  We are creating solutions that will really impact and help our customers.  It is exposing so many problems it is hard to get your head around it all.  I feel like we are a great company but man, do we have a ton of things to work on.  But we are acknowledging these and putting things in place to get closer to the company we want to be.  All of our problems are coming down to the system we have put in place.  It is never a “people” problem, it is always coming down to the crazy system we gave them to follow.

It was a great week this week.  The report-outs yesterday confirm that people really appreciate having a voice and having their ideas heard and implemented.  We reduced change-over on one machine this week from one hour to about 10 minutes based on an employee suggestion.  We are creating strategies to solve other problems that have existed for years.  Lean is hard, but when your whole team gets committed, it can be amazing.

 

Continuous Improvement

Continuous Improvement

“Enhance our reputation through continuous improvement”

This is one of Walters & Wolf’s core values. I’m assuming that many companies have something similar. Before we began our lean journey, this value wasn’t always in evidence. As a company, we were always making changes. When new technology became available or someone found a better way to do something, we would change. I think it is human nature to want to make things easier and better. So, like most companies, we were moving forward and generally “improving”.

The big change with lean is that there is a context for things. We have a “North Star” if you will. One piece flow. To get to a point where things flow simply and easily through the system. Where the process is visible and you can see where you are at all times. But we are a long way from this goal.

So, each day, we ask ourselves: How should this process operate? How is it operating now? What needs to change to get there?

Invariably, when you start asking these questions, you get this answer: “We can’t do that because….” or “We’ve tried that before but it doesn’t work because…” Most people think that these are good reasons not to try things. But it is quite the opposite. Let me explain.

Lean isn’t about making things easier. Lean is a system that helps expose problems. Every time you want to change a process and move toward flow, you will have problems. There will be things that won’t work. There will be other parts of the process that thwart that effort. But what is really happening is that by stressing the system and making changes, you are exposing the problems you need to work on.

Most lean books use the analogy of the water and the rocks. Imagine that you are looking at a river. In this river you can see the tops of a few large boulders in the water. If you begin to lower the water level, more and more rocks will become exposed. It is the same in lean. At first, there are just a few rocks to navigate through. But the closer you come to flow, the more rocks will be exposed and the more work it will take to solve these problems to move forward.

This week in our company, we are working on reducing the amount of work in process between our fabrication and our assembly glaze operations. We’ve made a lot of changes here over the last couple of years. Back in the day, we used to fabricate all of the metal before we started assembly glaze. We then started working by floors, then by weeks, then by days. Each time the amount of inventory was reduced, the amount of “looking for stuff” was reduced, and our throughput increased. If we were at flow, the time between cutting a piece of metal and setting that unit on the building would be measured in hours. But right now, it is measured in weeks. But every time we try to change this process and move toward flow, we find new problems. “We can’t do that because we would need to pull metal every day for the fabrication team”. “We can’t do that because the yields on the stock length metal will be awful”. “We can’t do that because we’d have to change the clamps on the saw 15 times a day to do those small batches”. “We can’t do that because we’d have to print the same fabrication drawing over and over for every part”. And so on.

And all those things are true. But they are not reasons not to do it, they are the problems we need to solve to make the change. We are identifying what we need to improve. By continually moving to smaller and smaller batch sizes, we are continually having to solve more and more problems that impede our ability to make that next step. And each problem we solve makes us a little better at what we do.

So continuous improvement in lean is about establishing a goal or “North Star”, making small steps each day to strive towards it, to find the “we can’t do that because” statements, then find a way to solve those problems and improve each day.

Standard Work

Standard Work

A popular concept in Lean is standard work.  Taiichi Ohno once said “Where there is no standard, there can be no Kaizen”.  We tend to think of this as looking for the best way to do something, documenting that standard, creating some type of visual control (posting the process maybe) and then enforcing that standard.

I’ve been re-reading the Toyota Kata book this week and found an interesting quote on the subject:

A popular concept is that we can utilize standards to maintain a process condition (Figure 1-3). However, it is generally not possible simply to maintain a level of process performance. A process will tend to erode no matter what, even if a standard is defined, explained to everyone, and posted. This is not because of poor discipline by workers (as many of us may believe), but due to interaction effects and entropy, which says than any organized process naturally tends to decline to a chaotic state if we leave it alone.   The point is that a process is either slipping back or being improved, and the best and perhaps only way to prevent slipping back is to keep trying to move forward, even if only in small steps. 

This is a fresh look at the idea of “standard work”.  In order to create a standard, we need to be working toward improving the process.  This way our process is constantly evolving and therefore people will more likely follow the standard.  If we try to nail down a standard then just tell people to follow it, it will eventually erode and when you revisit that process later, you will find the standard has faded and people are not following the standard any longer.

Kaizen at Walters & Wolf

Kaizen at Walters & Wolf

We had our first Kaizen events at Walters & Wolf last week.  Kaizen is the word for Continuous Improvement in Japanese.  It literally means, Change for the Good.  We sometimes use Kaizen to refer to the small incremental changes we are making each day.  But we sometimes use it as an adjective to describe a more focused improvement event.

I had attended a Kaizen event at another company a while ago (see my previous post about the slot machine company) and was very impressed with how much you could get done in a week with a focused group of people.  We have been searching for someone to help us with doing this at our company and I’m happy to say we have found a good guide.

If you’ve read Paul Akers book,  you will remember the story about how two young kids, Brad and John, came to Fastcap and helped Paul understand how to improve his setup times so that he would not have to build in batches and could produce his laser jamb product using pull and flow methods.  Brad came to our facility a few weeks ago and agreed to help us with learning more about lean and how it applies to our company.

We had two events this last week.  One in the shop and one in the office.  Both were tremendously successful and really helped establish how powerful it can be if you get a group of people together with a focused purpose to change or study a process.

I think the most interesting thing was looking at how the lean principles of flow and pull can be applied to any process.  Obviously our shop is a very physical process.  If you work in batches it produces inventory that can be seen.  You can typically identify your bottlenecks by the amount of material that stacks up before them.  You can watch people leave their stations to go and look for materials or information.  It is much easier to “see” what is happening.  In our office Kaizen, we were having very similar issues.  But here, you can’t walk up and see it.  In a virtual process, you have to create a map of what is really happening in order to start to see where you are creating batches and creating bottlenecks.

I learned a ton this past week.  I learned how to address an “unbalanced” line.  In our circumstances (office and shop) we don’t do the same thing every day or even every 15 minutes.  You can’t just do a simple operator load chart and balance our lines.  You have to address the fact that the line will be unbalanced at all times and find a way to address that to get the best possible throughput.  As in most things, the planning and communication are critical to the process.   I also learned how to analyze a physical process and also how to analyze a virtual process.   We learned how to see the Muri and Mura in our virtual processes and how to use Just In Time concepts to address them.

These coming weeks will be very interesting as we implement some of the ideas we came up with.  I will keep you posted on our progress.