Tag Archives: success

Sustaining Improvement

Sustainment is arguably one of the most challenging parts of a Kaizen, or more, the most challenging part of Post-Kaizen. It can sometimes be very easy to drop a new process when there is stress, even though the old process was stressful as well. However, the old process brought along stress that you became conditioned to, it produced a level of stress you were used to, versus a new stress. This tends to negate all the hard work you put into the Kaizen itself. Processes can be broken down, the improvement measured through its results, but what happens when you revert to old ways as soon as there is resistance? How does one keep themselves from back-sliding after making new improvements?

sustain

Involvement: One vital part of maintaining improvement is engagement of your entire team, the entire workforce involved with the process. Sustaining improvements isn’t the job of one, but it’s accomplished through the work and perseverance of many. When everyone is involved with a process and the completion of that process, then you have many people invested in its sustainment. When there is only one or two out of the whole who are invested in improvement, it becomes easier to revert, as everyone is not on the same page.

involvement

Metrics/Data: Evaluating your improvements and its progression is also important Post-Kaizen. The data and metrics collected through the Kaizen show the improvement itself, and go on to show the improvements growth afterwards. Data and metrics can help with sustainment in that they will show you where improvement is falling-off, or where adjustments need to be made. Part of the services our office provides was implementing a 2,4,6 month check-in for Kaizens, which go over the improvements that had originally been made and the data and metrics collected along the way. This allows everyone to visually see how the metrics flux, and whether the metrics values have gone up or down due to lack of adherence to the sustainment plan, or because the new process needs some PDCA.

mmetrics

Evaluation: Sometimes,  having many action items to complete Post-Kaizen contributes to a lack of sustainment. If one person becomes bogged down with many different tasks to complete, or if many tasks are put into place and later found in need of adjustments, the wheels for back-sliding may have already begun to turn. Having action items completed before the end of the Kaizen gives you time to collect metrics and data for the changes made, and therefore gives you time to evaluate the effects of those changes. If  a large amount of the changes don’t get made, or the changes didn’t have the desired effect, it becomes very tempting to want to go back to the familiar “old-way”. Lean is all about testing the changes made In Real Time, so it’s important to give yourself time to evaluate the changes that are being made, their effects, as well as seeing that implementation doesn’t spread one person too thin. If it appears that one person is overburdened with action items, its okay to take it one item at a time, or to disperse the items in a different manner.

evaluation

Incorporation: Along with involving everyone in a process who has a say, you should also have a plan for incorporating this new improvement and knowledge into everyday culture. When approaching improvement and sustaining it, it’s helpful to have a mindset that revolves around continuous improvement. This allows for new ideas to be given, received, and applied in reaction to results. To help keep the thoughts from, “well, this isn’t working, lets just go back to the old way,” it’s more positive to think “if this doesn’t work, we can find something to try next.” When improvement is blended into one’s daily routine, it becomes easier to train someone who’s new to the process, as well as to hand-off the information down the road. This makes sure that improvements are not only sustained by those who were first involved, but those after as well.

incorporate

Continuous Improvement: Last but not least, improvement rarely is spot-on the first try, meaning Post-Kaizen improvements may not always go smoothly. There may be stress on the new process, unforeseen road bumps, or even resistance to something new. Remember that just because you spent time creating a new process, it does not mean that the new process is set in stone, and it will more-than-likely need improvements of its own. Never be afraid to make tweaks or ask, “how can we make this process even better?” Incremental improvement is just as effective as all other improvement efforts, don’t feel like it all has to be done at once, take the time to make improvements at a sustainable pace.

continuous-improvement

Sustaining improvement is a tricky thing, but it’s a challenge well worth the fight! After all, you’re trying to become more effective in the service and value you provide. I have a lot more to say on the subject, however I will save that for another time. Please feel free to comment with any thoughts or experiences that you have with sustaining improvement!

 

 

 


The Gembas Role in Data Collection

Data collection can be a tricky thing, especially in a Higher Education setting. We tend to have to get creative in identifying what data would be helpful in representing improvement, as well as how we can collect the data using the resources we already have. This need for creative thinking skills tends to make brainstorming a collection plan seem ambiguous and maybe even insignificant at times.

We can easily generate a process map for the current state and future state and then count how many steps were eliminated, but what if five steps were removed, and one was created? It would appear (numerically) as if four steps were removed. Which is true, but how can we account for the process change in the new step? How can we measure that the new process adds more value than the old process? How do we represent the waste of five steps versus one new step? This is where our creative thinking ends and we decide that removing four steps is “good enough.”

In a video I recently watched, Mike Wroblewski, a senior consultant from the Kaizen Institute, shared a little bit about all the things we should consider before we create a data collection plan. The part that really stuck with me was his emphasis on going to the Gemba, the place where work is done, and asking questions. Wroblewski’s video showed me, that you can’t fully grasp the current state until you immerse yourself in the environment of the user, even if it is only observation. Once you’ve gone to the Gemba, it becomes more clear what the steps in the process are. From here you can identify metrics that represent the frequency of an event, such as the number of corrections to file, or that represent importance. For example, how critical is it that this step be in the process at all.

gemba

By now you’re probably thinking, “this is all great, but why do we even care about metrics?” Results. When you think of a research project, you want to know the results. When you missed the ending of a baseball game, you want to know the results. When you hear of someone applying for a new job, you want to hear the results. We as humans are hard wired around, “what happened next?” Lean and Continuous Improvement is no exception to this. When an improvement event is initiated, we soon begin talking about data collection before and after a kaizen so that we have results to showcase the work that was done. Metrics can be the difference between a department hypothetically getting $500 towards improvement efforts or $50,000. Metrics and results drive more people to put in the energy to improve their work from good to great.

This outlook and approach towards data collection is one that our lean practitioners here on campus have been trying to implement more and more, as well creating a more systematic approach towards getting numbers easily, accurately, and that will also provide meaningful data.

 


Wedding Bells Are No Exception

So often we get caught up in our projects: we start them, prioritize them, and then devote all of our attention to them one by one until they’re completed. We very rarely have a single project that is on-going for a long period of time; why is this?

I think it’s because we don’t want lingering work, we thrive off of completion. From that we gain satisfaction and pride in our work.

There is, however, a trade-off for this pride. That is, when we continuously move from one project to the next, seeing each to completion before starting the next, most of us quickly become burned out. When we get burned out we lose our energy and our enthusiasm, as well as become negative, frustrated, and unproductive. That satisfaction we were chasing before no longer sustains us.

Back in February, one of my co-worker’s blogged on incremental improvement, and recently she blogged about Preemptive Improvement. In these blogs, she’s shared how our office has been using small improvements to achieve a high future state and strive for perfection, even when a correction isn’t necessary. These methods are some that I’ve been applying in my own personal life heavily in the last year or so.

Last July I got engaged, we set a date 11 months out and so commenced the wedding planning. For all those who’ve been married, you probably know the magnitude of this task. I’ve always been a “planner,” per say, and I tend to enjoy getting to use my creativity, so from the beginning I’ve been pretty excited about the planning process. However, I know a lot of people who’ve gotten married and I’ve learned that the entire process isn’t always fun, or creative. I also know myself and I tend to go and go and go, and focus on one thing until it’s complete before I’ll start the next; meaning, I tend to burn myself out.

Knowing the planning wouldn’t always play on my interests, and knowing that I sometimes overburden myself were good things to be aware of back in July. Because of this, I was able to plan ahead and use my lean thinking skills to combat potential burnouts or becoming a bridezilla (my worst nightmare). I did this by utilizing the skills I’ve learned here in the Office of Continuous Improvement. I can honestly, say with 10 days left until the wedding, that I’ve only had two “burnouts,” one as a result of over-processing, and the other was out of my control to change.

After talking to multiple soon-to-be wives, I’ve learned that I am the one who’s been the least bit stressed about the planning process as a whole and I believe this is from all of the lean I’ve implemented… From organizing my thoughts via a gigantic affinity diagram, laying out the roles and responsibilities of our family members in a swim lane, using a decision matrix to decide on venues and vendors, ICE prioritization of tasks, plentiful checklists, recognizing when I was over processing, and also taking it one step at a time and remembering that the entire wedding doesn’t need to be planned over-night.

I’ve also gathered that on average, the last three weeks before the wedding tend to be the busiest with wrapping up small details. However, because of the prioritization that we conducted early on, and the small deadlines we set, we were able to spend two of those weeks towards something not related to wedding, and only spend the last week wrapping up details.

34643065_10204681238907051_8619962606741880832_n (1)
This is the original affinity diagram that kicked off the planning (kind of) last August. Things would get added and removed as we moved, but at one point it took up this entire 10 ft wall.

The purpose of today’s blog post is to show you that as long as you learn how to slow down your thinking, anyone can implement and benefit from small improvements striving for perfection.

 

 

 

 


4 things you (probably) didn’t know about a Kaizen event

In the last 10 years we’ve gained a lot of momentum in sharing Lean with the people of this campus; the largest connection has been made through hosting Kaizens, improvement events. However, when hosting a kaizen there’s not always team members that have ever heard of Lean and Continuous Improvement, let alone fully grasp its concepts. This isn’t their fault, how could they possibly understand something they haven’t been exposed to?

That being said, there’s eight things you probably didn’t know about a kaizen event that can help you to understand them a little more, the first four will be covered here:

  1. We’re not here to fix it for you – So often when our office assists with a kaizen, others believe that we are the ones that are going to come up with the solutions. This isn’t the case, the facilitators and coordinators are there to coach the team through a new way of problem solving, so that the team can develop the solutions.
  2. No silent objectors – A whisper can be more damaging than a shout. Meaning, if a team member has an idea, in agreeance  to the conversation or not, and it’s whispered or only kept as a thought, then that may be lost potential. We highly encourage all members of the team to share all of their thoughts and opinions so we can gain all perspectives. I mean, each team member was invited to the kaizen for a reason, right? And just to clarify we don’t encourage shouting, there’s really no need for it in a positive and mutual-respect environment, but shouting your idea is better than not expressing it at all.
  3. Blame the process, not the person – People are out of scope when identifying problems in a process. The process is the way it is, because it was able to be that way. Typically people don’t try to do a bad job, or deliberately cause waste. It’s easy to blame people, but really that person was just a victim to the faults of a process.
  4. It’s okay to disagree, but it’s not okay to be disagreeable – This kind of ties to #2, we encourage ALL opinions to be shared. Including opposing opinions. BUT, there is a difference between a difference of opinion and simply being irritable or challenging to work with.

So there’s four things you probably didn’t know about kaizen events, particularly the culture of a kaizen event. Stay tuned for the next four.

If you’d like to learn more about kaizen events, and how we run things here on campus, consider subscribing to our blog. We aim to get a post up once a week.

Mortgage-Industry-to-Change-URLA-1003-in-2018-1080x675


The Purpose of Lean

The Office of Continuous Improvement had the pleasure of welcoming guest Karyn Ross on Monday afternoon (and on her birthday, no less!). Having her here at Michigan Tech was a wonderful opportunity, as we get to learn more about Lean from another perspective.

While talking with Karyn and students from Leaders in Continuous Improvement, Karyn was asked how to better cultivate a Lean culture, was there certain tools that they should be using. Karyn’s response was not what I expected, but I was also pleasantly intrigued, as she addressed our usage of tools and Lean culture in a way that allowed be to look at Lean in a way I hadn’t previously.

In terms of tools, there are many that we have in order to help us make an improvement, and there tends to be heavy dependency on these tools. However, improvement is more than implementation of just a tool or tools: it’s the combination of principles, practice AND tools that allow us to accomplish an overall purpose. It is the establishment of the purpose that seems to have been forgotten, which means that an important key to improvement has been forgotten as well.

When beginning an improvement event, the first step is to identify and evaluate the current state, when really we should be asking and establishing what our purpose for the improvement is. “What is it we want to accomplish? What do we need to do, in order to make that accomplishment? How can it be done in a way that fulfills our purpose?” Establishing your purpose allows you to be able to define your target of the improvement. Only after the purpose and  your target are established can you truly look at your current state and start to find how to bridge the gaps. Only then can tools be used without creating waste.

In terms of culture, Karyn asked, “What is the purpose of Lean?”  To which the immediate response was the one I had only ever known; “To make all processes more efficient and effective.”

I was taken aback by Karyn, smiling, saying, “Can we flip flop those two?”

What did she mean, to flip the two? In most everything I had read about Lean, all that I had learned through training, the saying was always “efficient” and then “effective”. How could you be effective without being efficient first? Karyn went on to talk about that when a group works towards their purpose, and produces an end result that adds value to their customer, then they are being effective. The more value you produce for the customer, the more effective you are being, and the more you are fulfilling your purpose. Therefore, being more effective allows you to become more efficient, as you fulfill your purpose in the best, Lean way possible.

In all, I think that there is a lot that we can all learn about our purpose within Lean and about our own culture, Karyn more than helped me learn about my own. Towards the end of our visit, Karyn herself was asked what is the purpose of Lean, to which she replied:

“The purpose of Lean, is to help people improve the world.”

Karyn was overall, engaging and knowledgeable, and I wish I had had more time to talk to her. I hope that now, with my new found knowledge about my own purpose within Lean, that I can help other people improve the world, and do so more effectively.

 

 


Taking the Plunge into 5S

For some people accomplishment comes from the words, “our work here is done,” however, I believe that accomplishment can also come from, “we’ve only just begun.”

As we’ve shared in the past, each year 15-18 Michigan Tech faculty and staff come together in hopes of becoming the newest additions to our facilitator co-hort here on campus. To achieve the title of a “Level 1 Facilitator,” each candidate must attend seven days of training, complete various homework assignments, and participate as either a team leader or a facilitator on a new kaizen with three to four other candidates.

The group I’ve been assigned to has decided that their kaizen was going to be to 5S the Foundry Lab located in the Material Science and Engineering building. A couple of weeks ago, four future graduates, and an already seasoned facilitator, went to the gemba, where work is done. Our tour of the Foundry Lab consisted of Team Leader, Matthew Otte (Material Science and Engineering) walking us through the various workstations and processes for every corner of the lab. Our walk took a little over an hour and a half, and we really only scraped the surface for potential areas of improvement.

Before
This is the top view of the Foundry lab before any changes have been made.

Following this Gemba walk I found myself a little overwhelmed by the magnitude of potential within the lab. I was struggling with imagining where, how and when to start.

One of my favorite things about lean is that it has taught me to become an independent problem solver. When this overwhelming feeling creeped in I remembered that the most important thing with any change is to just start. There’s no rule that says you must jump from current state to ideal state in one step. Continuous Improvement is about incremental changes. It doesn’t matter how big the stride, what matters is the direction.

Considering this, the team and I regrouped, and we decided to start with one single workbench and slowly pick away at other areas within the Foundry.

Before finishing station
This is a before picture of the finishing station workbench our team decided to start with.

Now, these emotions I experienced weren’t necessarily circumstantial, however they’ve been encountered many times by many people and seem to be associated with any sort of change. Commonly, this sense of being overwhelmed is coupled with 5S. I’ve found that in most cases, when 5S is initiated, there’s usually a lot that needs to be done.  These emotions can be used as a trigger to take a deep breath, and pick one incremental change at a time.


A foot in the door: Commencement Kaizens

For the last six months a team has been pulled together to address various areas of the commencement process here at Michigan Tech, from ticketing to safety, and from configuration of space to guest speakers. This team has covered the commencement process inside and out, and with all of the stakeholders involved too! That’s HUGE!! The team has met 13 times already, for a total of 20 hours, and they are just getting started on most of it.

Before I introduce the teams let me tell a little bit more about how the Office of Continuous Improvement and the commencement committee have paired up and identified the kaizens that they’d like to move forward on. The meetings mentioned used swim lanes, a process mapping tool to map out the commencement process. The details to go on the swim lanes were acquired by the team leader, Kelly Vizanko, who emailed all of the stake holders and asked for their timelines. For the ones that were not received via email, they attended half-hour segments to help the team map out their part of the process. These meetings then identified areas of waste using kaizen bursts. From there the kaizen bursts were grouped based on the sub-process that they fell into and then later placed into a ICE Table, used for prioritization. This is how the kaizens were identified, by the most important/greatest impact, the level of control the team had, and by the ease to implement change/improvement. The kaizens identified were: Ticketing, Preparation, Volunteers, and Space + Configuration.

Ticketing consisted of eight people:

  • Kelly Vizanko (Registrar’s Office) – Team Leader
  • Ashley DeVoge (Ticketing Office) – Team Leader
  • Megan Goke (Office of Continuous Improvement) – Facilitator
  • Rylie Store (Office of Continuous Improvement) – Process Improvement Coordinator
  • Alisha Kocjan (Registrar’s Office) – Team Member
  • Shanda Miller (Bookstore) – Team Member
  • Nancy Byers-Sprague (Graduate School) – Team Member
  • Mary Stevens (Graduate School) – Team Member

This kaizen is wrapping up soon with a report out to the commencement committee. Several changes are expected such as scanning tickets to track the number of bodies in the room, communication to students (undergraduate and graduate) streamlined, established a limit for how many tickets will be issued, etc…

Day 1
This is a photo of Day one of the very first kaizen. This is half of the start of the swimlane that ended up being created.

The Commencement Volunteers and Preparation kaizens are just about to take off, all we are waiting on is the dates to come (for the volunteer kaizen) and our team to be solidified for the preparation kaizen.

The team for volunteers is:

  • Kelly Vizanko – Team Leader
  • Gina LeMay (Research Office) – Facilitator
  • Megan Goke – Facilitator
  • Rylie Store – PIC
  • Alisha Kocjan – Team Member
  • Joel Isaacson (Athletics) – Team Member
  • Jennifer Biekkola (Alumni House) – Team Member
  • Brian Cadwell (Public Safety & Police Services (PSPS))- Team Member
  • Daniel Bennett (University Safety & Security – PSPS) – Team Member

And to kick off the Preparation Kaizen we have:

  • Kelly Vizanko – Team Leader
  • Alisha Kocjan – Team Leader
  • Laura Harry (Memorial Union) – Facilitator
  • Rylie Store – PIC
ICE Table
Here is the team leaders and the facilitators working on prioritizing the kaizens.

All in all, we have a ways to go on these kaizens but the goal is to have at least something changed in each of these areas by April 2018, and to reassess after this year’s commencement ceremony. A foot in the door for lean, just as the students are about to leave.


What is a PIC

Very recently, I was given the opportunity to write a blog post for the Michigan Lean Consortium’s newsletter. In that blog post I wrote about how Michigan Tech is bringing lean to students, but more specifically on the Process Improvement Coordinators, commonly know as the PICs. While writing, it dawned on me that we have never really talked in depth about what our PICs do for the Office of Continuous Improvement.

Lately, we have been introducing a few new members to our PIC  team: Blake, Dominique, and not too long before them we had Matt. Even further back in time than Matt, we introduced Ari in April and Anita in March. In this time frame, Anita and Matt went their separate ways to prioritize other things in their lives. For me, Rylie, I was introduced way back in March of 2016.

Overall you’ve gotten to know a little about each of us, and hear from us during our journey with the office. However, what is it that we actually do for the office? What is our contribution? Where does our value lie?

Well the answer is sort of simple, we are process improvement coordinators for kaizen events. This means that we are responsible to make sure that all of the right people are in the right place, at the right time, and with the all of materials they need to be successful. We work closely with all levels of faculty and staff through the use of lean methods and thinking. We are well respected by these employees and are treated as equivalents whenever we’re seated at the table. On average, once each PIC is well out of their training they can be assigned eight different kaizens that they are coordinating. Deviating away from this part of our role, the PICs can also be responsible for aiding in facilitation of a kaizen,  data collection, and creating presentations for reporting out.

Kaizens are what we all know how to do, but there’s a lot more projects that us PICs are involved in; this is variable depending on which PIC you are talking about. For example, Blake and Dominique just completed training and are starting to get into kaizens. Ari and Dominique are currently working on a question bank for our facilitators to study for the Lean Bronze Certification test, a nationally recognized certification. Ari is also working on coordinating a information session on lean for students taught by the PICs. My big on-going project is training in the new PICs. This is done through a course that I designed along side a former PIC, Aspen, to accommodate all learning styles while enabling coaching opportunities for our more seasoned PICS.

The last bit of what we do is our routine standard work: blog posts, newsletters, report-outs, presentations, keeping up with kaizens and our access database, the typical. The key with our work, however, is that we don’t only do our work, we are continuously improving it through the PDCA cycle. As a team we have decided to highly boost the lean culture of mutual respect, by asking lots of questions and eliminating blame from our work.

In summary, our PICs are always on the go, and our “typical” day in the office is really unpredictable. Each day is different, and that’s how we like it, as it allows for growth and things to get done, without the lag of a droning routine.


Using Lean for small practices

It’s about that time of year again when members of the Office of Continuous Improvement are getting prepared to attend the Michigan Lean Consortium conference. At the conference members of our office will have the opportunity to hear from other Lean practitioners and learn about their Lean journey. In addition, the Office of Continuous Improvement will also be displaying a poster board to showcase how we have implemented Lean here at Michigan Tech.

When we practice Lean we often think of an effect that will benefit a large group of people or an entire process. However, Lean can be used in the most simple of processes, like creating a poster board for the MLC conference.

When we made the poster for the MLC conference, we used the 5 whys tool to decide what information we should include. As a result, it allowed us to narrow down our topic to include information that we believe the customer (other Lean practitioners in this instance) would value most.

After we came to a common agreement on the topic we did an affinity diagram to figure out how we wanted to display the information. An affinity diagram is where everyone in the group writes down ideas on sticky notes and then the notes are filtered into categories for organization. This allowed everyone to have a voice in the discussion and organizing the thoughts into categories allows everyone to be on the same page.

As a result of using Lean tools, we were able to effectively collaborate to get the poster done in a timely matter.

 

Poster

 

We wanted to create a lasting impression for those that will be encountering our board so we came to the agreement to include some of Houghton’s Iconic structures. We did this to draw the audience’s attention while also including information that we thought they would find of value. As a result of using some of the Lean tools, this simple process of making a poster became an even simpler process with an even better end product.

 


Lean at Home

When I last visited home, something in the relationship dynamic I have with my dad shifted; not only did I occasionally treat for coffee, but we had conversations about work. This is not to say we never talked about work prior to this trip, but the conversation was significantly less one-sided and lasted easily ten times as long. Until recently our work never really overlapped, he did his job and I did mine in completely separate worlds, Lean is what bridged the gap.

Becoming immersed in Lean Culture has actually filled many gaps throughout my life. Starting to take part in Lean around campus reminded me of the “Chores Board” my parents used to assign my sister and I tasks well before I could even say the word “Kanban”, or my dad’s tool board in the garage with clear spots for all of his tools. Lean was all around me before I even knew what it was, and upon telling my father of this revelation I had he laughed briefly and said something to the effect of: “of course, because Lean just makes sense.” He was right, it makes sense to organize different tasks somewhere you can see them so that they actually get done, it makes sense to keep things near the location they will be used at, and it makes sense to organize your work space and reduce excess so that you can easily find the things you need and increase your productivity. It turns out that Lean had been ingrained in my home life in a way I never really noticed.

If you walk into the Office of Continuous Improvement here on campus, it is easy to initially feel a little overwhelmed by all of our visual management systems and you can pretty immediately tell there is something different about the culture here compared to most office environments. Our office has five full whiteboards that help keep us on track, and that’s what many people think of when they think of where they would see Lean Culture; they think of work.

My home growing up had elements of Lean Culture all around without most people noticing it, and it still does. My apartment seems pretty normal, maybe a little more tidy than necessarily expected of a college student, but otherwise normal. Underneath the appearance, are all of those Lean principles that have silently guided my life thus far. Everything in my apartment has a place, and if it does not yet, it will shortly. This goes to show that practicing Lean does not necessarily mean having bright post-it notes everywhere or giant kanban boards, it can be as simple as using 5S in your garage, or using visual management to help your kids keep track of their chores.

Having Lean principles implemented around me during my life has definitely helped me develop into a better organized, more productive person, and to me it makes sense; it can to everyone. Likely you have already practiced some element of Lean either in your personal or professional life, just maybe without realizing it, much like I did.