Change Management

Implementing Change Using Kanban- Part VIII

20170327_192100

Our new board! Actually its a wall!!

The board has moved. While it took longer than I thought it would, it still wasn’t too bad. A lot of people in the company were curious as to how I was going to do it. Some were openly skeptical.

This is what I did.

First I had to make sure the board would fit. I measured the length of the current board against how much wall space I would have at the new location. The old boards are actually longer (cumulatively), but the new wall has more height, so I was able to condense. Also, some of the old columns could be condensed. One was even removed. This gave me enough space.

20170322_104637

I measured the columns or rows with post it notes. (example, one column is 5 post its tall and 8  wide). I adjusted the sizes based upon what I thought would be needed for the new wall. I wrote these on the board to help me remember.

20170322_134149

I clipped the post its together with paperclips or binder clips depending on how many post its were in a column and put them in a bag with the name of the column and a number for the sequence of appearance working right to left. In hindsight, I didn’t need so many plastic bags. I could have made due with just a few gallon bags. A post it note on top of the individual piles indicated where they went.

I also took a few pictures of the old boards to help me remember where things were. This helped putting the board back up.

Total time for takedown- 45 minutes.

Starting right to left, I started drawing out the board. I used the post its to determine column width and row height.

I put up the post its. It was important to have poster putty handy. A lot of the post its have lost their sticky, particularly the older ones. This is actually the part that took the longest when putting them up—adding the poster putty.

Total time for putting up- 2 hours.

20170327_192100

All Done. With the height provided by the wall, I could divide the board up into sections (at the top–“TTU”, “Disconnect”, etc.). Charts showing progress are to the right. A quote from one of our satisfied sites is in the top right corner.

Comments once it was up:

“Its like a giant rainbow! . . . but its SO much!”

“I like how you are organized.”

“Dan, people are noticing all the post its on the left side of the board are disappearing.”

“Did Kris (our director) REALLY say you could have the whole wall?” Yes, he did.

One of the remote team members saw a picture of the new space. “What are all those notes doing on the far wall?”

“We’re putting you on another project, but you don’t get any more wall space.” (said in jest, but at the same time I think they were serious also).

20170324_110418

This is the view of the IT production department right outside the director’s office.

Observations once it was up

The board got a lot of stares. I used to be tucked away in a corner, but now the whole IT department is on one floor now and in a big open space. Some had never seen it before, others had seen it, but now it was in their face in a big way (see above). I was glad the board was getting the attention it needs, but at the same time, it also became a target. A couple of people thought I was taking up too much room and taking up white board space (the whole wall is a white board). One manager asked me if I could shrink it so her people would have room to write. I asked her team if they wanted more room, but they said no and thought the board was fine.

I saw people clustering together and looking at the board. I knew they were talking about it. Negative? Positive? I don’t know. I admit for a day or two I was a little paranoid that someone was going to make me remove it or condense it.

The team using the board is now in the same area. Its easier to get to and they can clearly see what needs to be done. There is more interaction with the board.

Challenges

I felt bad that it was taking up so much space. I felt like I was being selfish. What would people think? Why should I get a whole wall just for me?

Leadership still does not come to the board. I wish they would. We always have good conversations when they do.

Links to the rest of this series:
Part I
Part II
Part III
Part IV
Part V
Part VI
Part VII
Part VIII

Implementing Change Using Kanban- Part VII

20170301_144514.jpg

The latest version of our board. Tip-use dry erase markers. Our board changes regularly as we evolve our processes or try to accommodate management demand.

Here is the latest observations, challenges, lessons learned, triumphs, etc. of the Kanban board experiment in my current project.

Recent Comments

“I love the post-it notes.” ~A visitor for one of the other teams.

“It’s so pretty!” An interviewee for another team.

“Hey, whatever works.” ~ Our newest project manager (this is a common comment and bothers me for some reason).

“Its actually pretty ingenious.” ~ Our IT director to our visiting global PMO (who were visibly skeptical of the board). This is the first positive comment to come from him about the boards. I love it!

“And here we are investing in tools.” Global PMO member.

“Are we trying to save money?” Global PMO member.

“I have to tell our leadership that the greatest risk to the project is wind.” ~ Our IT director referring to the post-it notes.

Observations

  • Bottlenecks become more apparent when the time frame is shortened and the work load increases. Ex. I’m the main one updating the board. If others could do it when they complete their work, that would mean I wouldn’t have to do it all the time. At the same time, if I don’t do it, we lose insight into what is happening on the project.
  • The boards take up a lot of space (and is actually growing). What if every project used a board like this? Would we have any wall space left? Would we be fighting for wall space?
  • As numbers/WIP increased and the pressure to hurry up and finish increased, it became more apparent how much time it takes creating post-it notes. The short-term thinking side of me wanted to stop doing it and just get on with the work, but I reminded myself how the initial time spent creating them paid off in the long term. I was surprised at what feels like my ‘instinct’ telling me not to use the board.
  • A pretty big negative for the board is stats gathering. It takes me up to 2 hours gathering the info from the post-it notes and putting it in a spreadsheet for reporting.

Lessons Learned

  • My supervisor didn’t like our process for shipping and scheduling equipment. He wanted us to change it because he thought it was creating bottlenecks. Our team didn’t like the idea. We thought it complicated matters and created a risk. In the end, everyone decided to try an experiment based on what he wanted. The board was updated and after a few hiccups and adjustments, the new way worked just fine. Lesson Learned—Don’t be too resistant to an outsider’s suggestion for changing your process. They might be on to something and you can always try an experiment to see if it works. If not—just go back to the old way. We are fortunate my supervisor simply did not force us to change our process and allowed the experiment.

Triumphs

  • For a couple of weeks, it appeared I wasn’t going to be able to bring the board to the new location. I had a team member come up and talk about possibilities of where we could put it. And here I was thinking no one cared. That really meant a lot. In the end, it boiled down to the IT director, who is determined to make the project a success. I told him the board was critical to the project’s success. He agreed there would be a spot for it in the new building.

Experiments

Limit WIP.png

The boards’ first attempts at limiting WIP.

  • I’m attempting to limit WIP (without the team members realizing it). It seems to be working. I’m sure if management knew I was doing it, though, they would get mad.
  • I put up a brief synopsis of what Kanban is near the board. My supervisor read it and it sparked some good conversation. I’m hoping others will read it as well. Perhaps I can alter it so its more readable.
  • I think I need to stop giving logical explanations for using the board. I’m trying to ‘testify’ instead. The idea is to appeal to a person’s heart, not their head. I’m trying to remember to say things like:
    • “Its the best tool I’ve ever used.”
    • “It didn’t make much sense to me when I first saw one.”
    • “It saves my bacon on a daily basis.”
    • “It allows me to sleep at night.” (my favorite)

Challenges

white-post-its

Post-it notes on top of post-it notes–sign of too much WIP!

  • Because there is so much WIP, we have tons of issues identified on the board (highlighted with blue post-its). There are so many, its now become noise and I need ANOTHER post-it (white) to identify higher priority items we need to discuss as a team. Having no WIP limits suck!
  • Limiting WIP is such a foreign/difficult concept here (though the seeds may have at least been planted). I tried to explain why limiting one of my team mate’s WIP would help her but I was told, “No—just send them all to me.”
  • Global PMO visited our office and saw my board. I was happy to see our IT director talk it up (see his comment above). I gave a brief explanation of how the board worked. There seemed to be some skepticism (their comments are above). Its kind of odd to me that a PMO group doesn’t recognize a Kanban board.

Opportunities

  • Another project manager asked me about the board. He said he’s struggling with the organization of his project and needs something. I let him borrow my Kanban book and Stop Starting, Start Finishing. He quickly discovered Kanban was being used elsewhere (one of his team members said they used one at Hyundai). I’ve seen him walking around with the Kanban book and he said he wants to sit down and talk with me about it. One of his teammates has been wanting to try Kanban for some time. He even took my class. This gives us a champion on the inside.

Wishes

  • I really wished our partner could see and use the board. I think it would help them tremendously (which would help us). They seem to be so overwhelmed. I know they are in spreadsheet hell. I’ve been thinking about looking into Lean Kit (though I am skeptical of electronic Kanban boards over physical ones).  It may be too late to use it for this project, but perhaps we could use it on the next one???

Links to the rest of this series:
Part I
Part II
Part III
Part IV
Part V
Part VI
Part VII

BOOK REVIEW: Deming’s Profound Changes

profound-changesDAN’S SCORE: stars-4-5
Deming’s Profound Changes: When Will the Sleeping Giant Awaken?
by Ken Delavigne and Dan Robertson


I first learned about this book while listening to one of the Deming podcasts interviewing Daniel Robertson.

Though it took me a little while to get into it,  this is one of the best books I have read in some time.

The book’s premise is about how our current traditional style of management came to be (i.e. Frederick Taylor’s management theories), why it is damaging business and how accepting Deming’s new management philosophy will help us improve. The authors emphasize Japan is doing so well because they have abandoned Taylorism and adopted Deming’s principles. The authors believe Japan is wondering when America will also make the switch—thus the tag line “When will the sleeping giant awaken?”

I think this quote taken from the book summarizes the intent:

We will win, and you will lose. You cannot do anything about it because your failure is an internal disease. Your companies are based on Taylor’s principles. Worse, your heads are Taylorized, too.” ~Konosuke Matsuhita, Founder, Matsuhita Electronics (Panasonic), 1988.

My favorite take aways (this was tough to sort out—I tried to shorten this list the best I can, but there is simply a ton of stuff in here):

  • Self-managed teams sound Deming-like, but unless they are managed as a system, they will suboptimize and will have a tendency to listen only to the voice of the customer (ex. focusing on specifications) instead of listening to the voice of the process. This sounds very much what scrum teams are trying to do with their focus on customer value. This has certainly made me think.
  • Many people don’t understand continuous improvement. Continuous improvement must be in a specific direction guided by purpose or an aim. In order to do this, people need to continuously gain new knowledge and we are not used to doing that.
  • There was a study done on what it was the Japanese were doing differently. It was found what they were doing was reducing complexity. I.e they were understanding and then simplifying the system. It was hard to pinpoint what exactly they were simplifying, but whenever they did this, it created positive ripple effects throughout the organization. (Terrifying. It seems every place I work with wants to achieve some objective and if making something complex achieves that aim, so be it. I’m not sure how we break out of this mindset). This whole chapter was fascinating to me.
  • The authors list out six dimensions of complexity: number (number of employees, departments, work batches, etc.), volume, density (ex. being geographically spread out), process time (lead or cycle time), variation, and context level (i.e. a manager will understand and see things at a different level than an employee and vice versa).
  • Western management focuses on ROI in the beginning, but the Japanese understand that reducing complexity eventually pays returns. (Wow. How do you convince a CFO of that strategy??).
  • Management is constantly under scrutiny and pressure from stock holders, creditors, and often the press. All of these folks want RESULTS. This creates a culture obsessed with outcomes and self interest (i.e. they don’t want to lose their power or career) and creates a short-term mindset. The authors note its no wonder managers are constantly making demands on their organizations that exceed their capacity. They force the system to shoulder increased complexity and thus make the system less capable.
  • The effects of increased complexity are often subtle and hard to detect in an organization and difficult to trace back to where the issue originated.
  • He gave a list of excuses commonly held for the decline in U.S. competitiveness and debunks each one. These include labor issues (such as with Unions), foreign competition and not buying American, lack of automation, trade barriers, government interference, lack of employee motivation, and employee education. The authors state the underlying message with all these issues is that we are managing wrong and we must change.
  • The authors suggest that those who are attempting to promote change need to understand the various elements of it. This will help them bring about change and improvement more swiftly. Change will take a great deal of time and effort and there will be many forces, directly and indirectly, opposing it. Fortitude, faith, and courage are essential.
  • The authors also discuss why people want to be managers and discuss how we need to be promoting the right people into these positions by looking for certain characteristics. They also discuss how to develop these types of managers.
  • They give a strategy on implementing change. They said to break issues into Cosmic (i.e. deep complex issues), low-hanging fruit, and no brainers. They said to go after the low-hanging fruit. I was surprised by this strategy as the Toyota Way goes after the root problem. They said when you solve enough low-hanging fruit and no brainer issues, the Cosmic issues have a tendency to go away.
  • They suggest a good way to figure out what to start working on first is to ask the question, “What bugging you?” I started asking this question when I solicit feedback from our customers.
  • They suggest we do the following: Be an exemplar, Keep Growing in Knowledge, and Widen Your Personal Orbit of Influence (this last one is what I struggle with).

 

1952533952-frederick-taylor

Frederick Winslow Taylor. The authors premise is the West is stuck in a modern-day form of Tayloristic thinking, a style of management invented over a hundred years ago. Good for its time, but its way past time to evolve.

Though the book explains Taylor’s philosophies, I’m still not sure I understand them despite a whole chapter on it. Of course, I can be dense. I reckon I need to review.

 

I thought it interesting the authors emphasize Taylor as being the biggest impact on modern management, but they don’t mention the 1841 head-on train collision and the subsequent adoption of military-style organization. This event is cited in two books I’ve read (The Leaders Handbook and The Leaders Guide To Radical Management) and given as the main reason for modern style management.

I thought some of the examples were a little dated, for example the computer industry examples, though pertinent and correct, were stated as something new, but are now near 20 years old. During the podcast interview, Robertson stated he doesn’t think the book needs to be updated because the advice is still the same.

The book can be bought here.

Implementing Change Using Kanban- Part VI

20170118_191033

Our board. Note the graphs to the left indicating trends. I’ll post about those soon.

Here are some recent goings-ons with the Kanban board.

I’ve told this to others in my organization and I’ll continue to say it, this board is central to the project’s organization and understanding. It saves my bacon daily–simply because I know what the heck is going on. I highly recommend one.

Just to remind my readers—my organization does not embrace Kanban, Agile, or any type of improvement methodology or philosophy. This series documents the challenges, failures, and triumphs of trying something different.

  • There are many who still just don’t get it. I still get teased:
    • “Watch out! Don’t knock off any post-it notes!” as a group of people walk by.
    • “What if someone just comes along and . . .”  Person moves post-it note to elsewhere on the board (actually, I can figure out where its supposed to go just by looking at it).
    • “What if there is a fire?” often said with a smirk. (“Everyone grab a post-it note!”
    • Of these comments, I know some of its just good ribbing and some its genuine disbelief. Regardless, this is something I’ve learned just comes with the territory. For the most part, I feel people have come to respect what I do even if they don’t quite get it.
  • The series was featured on the Deming Institute! One of my team members, who had lived in Japan, immediately understood the significance of this. “Everyone has GOT to know about this!” he said. This is about as far as the excitement went, though. I told my supervisor, and he seemed to think it was cool, but didn’t say much about it. When I told our PMO lead, he asked, “Whose Deming?” After I explained, another colleague laughed and said, “It sounds like a cult.” This sucked some of the wind out of my sails.
  • Team members are starting to interact with the board after some encouragement. I’ll be at my desk and here the pop and soft rattle of a post-it note moving on the board from behind me. Its a good sound—the board removes me as a bottle neck. The board is showing the team what needs to be worked on without me telling them!
  • One of our team members, a former navy man, compared the board to boards they use in the navy to monitor ships that are all over the world. He said he likes the board.
  • I’ve said this before and will say it again—it would be better if all those who use the board were right next to it. Those who are at my location work in another room. They have to get up, walk out of their room, down a hall, and in to my area to see what is going on. Up to a hundred feet. I can understand why they might think the board is a pain. I also think this causes the board not to always get updated like it should.
  • Related– it would be better if all our remote partners could see it. I believe one of our partners suffer from cumbersome internal processes and systems and I think our board could give them some clarity. There are things I regularly see that I have to keep bringing to their attention, but if they could see it themselves, they wouldn’t need me to point it out. Ideally, the board would be electronic so all remote team members can see it, but also retain its current size so those in its presence can read it and discuss it.
  • We’ve had new people come on board to help me with the project. I asked them to use the board. There was some resistance to it, including from their manager, at first. This company is used to working in spreadsheets (which I’m seeing more and more of the problems of). One member openly said, “I’m not going to use this.” I think she was intimidated by it, but once I told her why it was important to the project and I showed how it worked and told her not to worry about all the nuances, she chilled.
  • One of the new team members seems to really like the idea. I think he may become a champion of convincing others of the board’s merits. I think a board like this would help them with their own work. I’m wondering if he is starting to see this.
  • The new people have been taking the post-it notes back to their desks. I allowed this because they needed the information on the notes to complete their work. The negative– sometimes I’m looking for a site and can’t find it. I’ve started wondering if this was a good idea. I’m worried the post its will get lost. This again drives home the point that it would be better if we were all in the same location.
  • While everyone knows I’m very aware of what is going on with the project, they are not happy with the results they are seeing (the project has been behind schedule since the first week). This make me concerned that people will conclude that a board like this does not help get a better result. My argument—what type of predicament would we be in without it?
  • Its official. We are moving to a new location and there seems to be some disagreement on if there is room for the board. My supervisor and teammate think so, but others have told me there won’t be any room. I wonder sometimes if I am going to be made to conform. I wonder if anyone has any idea how important this board is to understanding a very complex project and how its central to the project’s organization. Of course, if it can be accommodated–all who currently use the board will be in the same location and that would be very, very good. We’ll see what happens!
  • Someone told me that one of the manager’s admired the fact that I did what I believed to be right despite strong pressure not to. He said we needed more people to do that. I believe they were referring to the board.
  • As I study Lean, I’ve come to the conclusion that the board actually duplicates effort which is wasteful. I have to write information from an e-mail or spreadsheet onto the post-it note. This is the downside. The upside, it puts the information in a form where I am able to synthesize it. I am unable to do this when its in its original form. I wonder if there is a way to get both worlds?
20170112_193705

See the column on the far right? That’s how many we have actually completed! Conclusion- we have plenty of starting and not enough finishing. See those blue notes? Those are things we have to revisit. That’s a lot of rework and only adds to the WIP. I’m not certain how to convince others that this is an issue.

  • This company does not believe in (or understand the importance of) limiting work limits and finishing before you start something else. As a result, the board is getting cluttered with tons of post-its and its getting harder to find specific posts its. There has also been times where I have duplicated a note.
  • During my last post on this series, I wished our partner would start sending over smaller batches at more frequent intervals so we could create flow. I was able to convince them to do that. However, we are still not getting the results we want from them. Because I don’t have a clear insight into our partner’s processes, I’m unable to understand where the bottlenecks are and where to help fix them. Management is getting frustrated. We asked the partner to double their batch size, but because still don’t see good results, leadership has insisted they do them all at once. So much for the concept of flow. . .
  • Because management has asked for everything to be released at once, I predict our board is going to get very crowded and our WIP is going to explode. I wonder sometimes if the board will be any of any use at that point. I might be spending all my time just updating it and that’s not going to help us get any work done. That could just be the fear talking, though. Who knows?

What I wish for

  • I wish management would visit our area more often to understand what is going on and help us solve our issues. The board (and all the charts I display) is just as much for them as it is for our people. They don’t come by, though, and we usually only talk during reporting meetings (which often results in their frustration). Without management being able to ‘see’ what is happening they have to revert to my interpretations. They aren’t getting the results, though, and as discussed, they are very much getting more and more frustrated.
  • I wish there was some way (technologically) for everyone involved in the project to see this board without us losing its size and “physicallness” it currently has. Even if I were to create this board in OneNote (which would be a large undertaking) so everyone could see it, I’m not certain everyone would use it and I would lose the benefits its currently giving the project. This is a risk I’m not willing to take.
  • I wished people at my company would read my blog. Maybe I’ll get ballsy and send my blog to our IT director. Hmmm . . .

Links to the rest of this series:
Part I
Part II
Part III
Part IV
Part V
Part VI

Implementing Change Using Kanban- Part V

The previous post in this series is here.

Here’s some of the latest events with our experiment with the Kanban board. I think what amazes me the most is how it continues to evolve–in how it looks, how we use it, and how we are starting to view our work.

  • I added another board to the left of the original. I call this board “Provisioning.” This represents all the sites that are in progress with our partner. There are no process columns. Its because I don’t have a clear understanding of their process. However, I know what sites they have, and I started writing a post-it note for each. It became time consuming to write each and once its on the board, I have a hard time finding it again because there are so many. I decided I would just make the post-it when the partner sent the site. If something needed to be addressed before it was sent over, I would create the post-it and label it with the block or action item. I must say, though, having so many post-its on the board gives us a better visual of how many sites are coming over and the enormity of the work involved.

    img_10931

    This is a new board–it represents the work we are waiting for from our partner. In hindsight, I’m not so sure we really needed it. We just need to know how many the partner has and if there are any areas that need our attention (i.e. items that are blocked or needs some sort of action).

  • I also added another wall for our clean up. I didn’t create a white wall for this one. I just use pins and the post its and move them over column by column (there are only three). This represents disconnecting the old circuits portion of the project. Once these are completed, the site is considered done. What disturbs me, and I have been pointing this out to our team, is that there are only about 6 sites absolutely done. Why aren’t we finishing? I believe the problem is because of the emphasis on getting the sites to the TTU portion of the project. Once that is done, the interest in the site begins to wane. Management wants us to put our effort into completing more TTUs. As a result, the sites are stacking and not finishing the whole process. I believe the board is highlighting this problem and management is beginning to see the issue. They are giving us another resource to help us finish these up.
  • I believe the importance of working upstream vs. downstream has dawned on us. (is this pull vs. push?) When we work, we read the boards from right to left. I believe this is helping us understand the concept of finishing what we have started. I believe this is a big jump for us. I have spoken to my manager about this concept and he agrees that it is the smartest way to work. That is a relief.
  • Bottlenecks are much more apparent. I really hate seeing them. For one, I quickly run out of space in my columns. See below.

    img_10981

    See the two long columns of green and yellow? This is a result of working in large batches. The greens will sit there for several days before work begins on them. If I get any more that need to go into this column, the post its are going to get piled on top of each other (which has actually already started). These areas are called “queues.” These items are waiting for us to have time to work on them

  • Bottlenecks are exacerbated because we are working in large batches. Our partner is working in batches of 25. We get nothing then all of the sudden we get a whole lot. One of my team mates is following a similar pattern. He started setting one time a day in the week to work on all the sites that have been sent to him. I understand why he is doing it. He has conflicting priorities, and if he can schedule a couple of hours where he isn’t disturbed he can get it done. The problem is the sites are sitting there anywhere from a day up to a week and it increases lag time. We’ve been talking about batches lately and the trouble of working with large ones. I even showed my manager the concept of single-piece flow. At first he was skeptical, but I think he began to see its merits.

    img_10971

    Notice how items are piling up in columns–the result of working in large batches. These items come in all at once and then wait. There is also an emphasis on a certain point on the board to be completed. As a result the items to the right of that point are not getting completed. See how all the post-its are clogging on the right hand side of the board? We have a lot of starting and not enough finishing.

  • We are starting to talk about the concept of flow vs. large chunks come through and how it would be better if items were coming over more frequently but in smaller batches. We aren’t sure exactly how to make it happen. My feeling is we will have to change how our partner does their work.
  • Some of the best conversations I’ve had with my supervisor and the head of the IT department is when we are at the board. I can explain and show things to them. It also helps that I keep charts and statistical data nearby so they can se the data. I think they appreciate the transparency.
  • I did a training on Kanban boards. One manager experimented with it some, but so far no one has started using one. I’m told I’m still an inspiration to them though and they love coming into my area. I wish I could help more. I think I just need to work with them more often. Its tough because all our time is limited.
  • I’ve gotten more concrete with our additional post-its. Blue is for action items. Pink is for blocks. Blocks mean the item can not move forward. Blue means the item can move, but there is something we need to do with it. Also, I put the date in the bottom right, the company owner in the bottom center, and the site the problem is associated with in the bottom left. Admittedly, it can get tiring doing this, but it really helps us keep track of so many things we need to work on and the visual lets us see any patterns where these items are becoming a problem. For instance, we see a lot of blue after our TTU. This is because that many issues are encountered during TTU that we have to address. Its made us think more about putting the quality in the first time around and trying to be more proactive instead of fixing it afterward.
  • I use the post-its to hold data (usually in the form of dates) which I then transfer to excel and create graphs. The charts that seem to matter the most to management is the burndown and the run chart showing rate of circuit completions per week (which needs to be at 15 a week in order to meet our target deadline). I keep up-to-date charts near the board so everyone can see it. I believe the charts reinforces the idea that my project management philosophy doesn’t end at colorful post-it notes on a white board—I have a lot of hard data.
  • I’m still getting mixed reactions from different people on the boards themselves. Folks who have never seen them before will often snap their heads with a double take when they enter the room. Sometimes I find people just staring at them.  I did have someone say I had made a mess creating them. Others have told me they think they are really cool. An agile coach told me to talk them up. I’ve been doing that.
  • There is still talk of moving to another location. I’d be fine packing the boards up. It would be pretty easy actually. My concern is having wall space near my future work area. I hope I will be accommodated.

Things I wish we could change to make it better:

  • Have our partner work in smaller and more frequent batches. I think this would even out our overall workload and create flow.
  • Have my supervisor and our IT head see the boards more often. We usually have some good conversations when they come over. I can tell they “get it” and they are getting used to looking at the boards to help them understand what is going on (even if they still don’t understand the nuances).
  • I wish all those who work with the Kanban board were near it. I think it would make it easier for them to identify what needs to be worked on.

Links to the rest of this series:
Part I
Part II
Part III
Part IV
Part V

Implementing Change Using Kanban- Part IV

Here’s some latest happenings on my wall charts. The last post is here.

  • The head of our IT department came by my cubicle the other week. My boards attract his attention whenever he’s in the area. We started discussing what was going on with the project. He could see from the board that sites were starting to move through the process which made him glad. He could plainly see the blocks. He was able to help me get rid of six. He seemed a little perturbed we hadn’t figured out how to get rid of them ourselves, though. He then looked at the burn down chart next to the board, pointed at the WIP which was still way above the sloping diagonal line and said he wanted the WIP on the line the next time I gave my report. That was unnerving. All I could say was I wanted it on the line too. Maybe he isn’t pleased how things are progressing, but I hope he appreciates the transparency I am trying to show. Its something he once said he wanted from the project managers. I actually wished he would come by more often so we could have more discussions. At the same time, if he did, I can’t help wonder if he will only blame me for not getting more work done.
  • My other team member gave input on how the board could be better changed– showing the sites that have been queued the longest from top to bottom. He also has becoming by more frequently to look what needs to be done. I wish he sat closer to me so he could have more easy access to it. I think it would help. The problem is, my project is just one of three or four others he has to work on and my supervisor who sits in the next room over, prefers my team member to be closer to him, also, I don’t sit with the rest of my department (which is sort of good, because there is no wall space there).

 

img_1076

My teammate’s contribution to improving the board. He wanted to identify how long our sites had been in provisioning.  Note the burn down to the left.

 

  • One day, this same team member came by to look at the board. I heard one of the other employees chiding him about getting into the whole post-it note thing. My team member replied that the board actually had its merits.
  • I had someone ask me how to make a Kanban board so they could use it for their own purposes.  I had to cram what I could in a 30 minute session because his time was limited. He’s used similar boards in the past but hadn’t thought of putting in ‘Done’ columns. I also explained to him the importance of limiting WIP but I’m not certain he understood. Since I went over with him how to make the board (a few weeks now), I’ve seen his board still lying on the ground next to his cubicle. He said he’s been busy. Whenever he comes by he still marvels at my board. Wish I could do more to help him.
  • This same person I helped said that one of these board would help one of the other teams. I had the same thought because what they do is similar to what I do. I know their manager has seen my boards, but she is one of the folks who doesn’t understand why I just don’t use a spreadsheet. Her team would have to want a board like this, and they haven’t shown much interest, and I’m not certain how supportive she would be.
  • There’s some talk of moving the department and there is a concern there won’t be any wall space for my board. I’m not sure what I’ll do in that situation. I could go electronic, but the board will lose a lot if its power if I do that. Its size and location is much of its strength. It will be more difficult to have conversations about it if its tucked away on my computer. It will also make it more difficult to read. Of course, since I’ve been here, there has been talk of moving and it hasn’t happened.
  • I had another project manager come by to view my boards. She really liked them and I could see the wheels turning on how she could create her own. It reinforces the idea that I need to make time to teach how these work. This same project manager said my ideas would find more acceptance and traction in her department than in mine. Maybe.
  • The board is getting more and more crowded with work. Its starting to look like a parking lot. My company does not understand or appreciate the concept of limiting WIP or flow. I’m thinking of ways to rearrange the board that will highlight where items are queuing. My concern is this will only cause people to get upset that we aren’t doing our work. We’ll see. Perhaps it will start more conversations about how having too much WIP is slowing us down.

The next post in this series is here.

Links to the rest of this series:
Part I
Part II
Part III
Part IV
Part V

The Story of NUMMI: The Difficulty of Changing Paradigms

nummi-plant-toyotaMost people would probably tell you they don’t have a problem with change. The unspoken add-on should be, “as long as it doesn’t contradict my core beliefs.” Whether we realize it or not, we are prisoners of our own culture, ideas, and experience—i.e., our paradigms, and we must change them to find success.

I first heard the story of NUMMI when I attended my CSM class. Its a popular story in the Lean circles. NUMMI was a joint venture between Toyota and GM during the 1980s. Toyota wanted to start making cars in the U.S. GM wanted to know what Toyota’s methods were. At the time, foreign cars, particularly Toyota, was cutting more and more into GM’s market share and GM didn’t know how to make small inexpensive fuel-efficient cars.

GM brought to the table its former plant in Freemont, a facility notorious for its poor quality, productivity, and hostility between workers and employers. Toyota brought its now fabled Toyota Production System. The transformation was incredible. Folks predicted this would be the turning point in GM’s misfortunes.

They were wrong.

Despite NUMMI’s success, the lessons learned couldn’t spread to other plants because GM simply couldn’t change its paradigms. This culminated in its 2009 bankruptcy and the multi-billion dollar government bailout and the subsequent closure of NUMMI.

The NUMMI story can be found at This American Life podcast or transcript.

nummi-time-of-death-921-am-pacific-daylight-time-18822_2

Last Corolla off the NUMMI plant floor when it closed in 2010. A bad combination of economic downturn and folks unable to change their paradigms. The plant is now Tesla Motors.

A retrospective of NUMMI from Steve Bera, one of the 16 GM employees selected to use the lessons from NUMMI to change GM, the dubbed “NUMMI commandos,” can be found at a pair of podcasts on leanblog.org here and here.

 

After listening to these programs, I found myself a little depressed. One of the podcasts stated NUMMI succeeded because the plant had to start from scratch. The workers had to change because they couldn’t find jobs. The other GM plants were still in business and despite NUMMI’s success, people’s paradigms (i.e. “that won’t work here”) killed the change movement. Without a crisis, the GM plants weren’t willing to change its ways.

young-deming

“It would be a mistake to export American management to a friendly country.” BEST DEMING QUOTE EVER.

This is a direct parallel with what Deming taught. He pointed out that after WWII, Japan had to change because its infrastructure and culture lay in ashes and ruins. He said America’s crisis was invisible–we had been successful because we had no competitors after the war. We could manage however we wanted to and still be successful (and we were). Because we were successful, we thought our management methods were sound. How could we know otherwise? But those days are over. The other countries have recovered and now our chickens are coming home to roost. Our ways of management, i.e. our paradigms, have to change or we will become extinct.

 

It made me wonder– if an organization hasn’t been brought to its knees, is it possible to change its ways? Do we have to destroy the old system first? And if true, are we change agents wasting our time?

Handling Change: The Warrior or the Sage?

MACARTHUR LUZON

General Douglas MacArthur. It was the pipe that terrified them. Obviously.

I’ve come to realize Agile is missing an important ingredient in its philosophy: how do you get people stuck in their ways to change their minds?

I believe one of the key skills for being a good scrum master is knowing how to be a good change agent. An agile mentality is not intuitive and runs counter to much of what we’ve grown up with. What do you do when you meet resistance? My go-to strategy is to be empathetic, compassionate, and try to understand underlying reasons for non-compliance.

I had an interesting conversation with one of my friends and fellow scrum master, Carl Allen, who has a very different approach. Here’s some of our exchange:

Carl E. Allen 11:48 AM:
the fact of the matter is there are “the wrong people in the wrong seats of the bus” who feel they don’t have to do what everyone else has to do.
there has to be some consequence for willful disregard of rules and process.
M. Dan Bracewell 11:49 AM:
how do you know they are a willful disregard? why are they being disregarded? Isn’t that the real question?
Carl E. Allen 11:49 AM:
we’re not talking about ignorance, or not knowing any better, we’re talking about acute blatant insubordination here.
M. Dan Bracewell 11:49 AM:
I don’t buy it.
Carl E. Allen 11:51 AM:
the system is at fault, but unfortunately, you have to resort to brutality to correct a very narrow margin right now.
M. Dan Bracewell 11:53 AM:
I don’t agree. that’s managing by fear and intimidation.
Carl E. Allen 11:54 AM:
sometimes.. SOMETIMES you need that. Because if you have just politics and kumbya then the people get to a point where they KNOW there’s nothing that’s going to happen to them.
M. Dan Bracewell 11:55 AM:
this isn’t war.
Carl E. Allen 11:55 AM:
Everything is war.
Sun Tzu =)
M. Dan Bracewell 11:55 AM:
I don’t agree with Sun Tzu.
we’ve got to change our mindsets or we will continue to have these problems.
Carl E. Allen 11:56 AM:
well we have a problem that politics and peace won’t solve.

 

w-edwards-deming-1950s_650

W. Edwards Deming. Nerdy-looking, but pure business god.

Carl contends that some people are beyond fixing. Whether they did it to themselves or a corrupt environment did it to them is besides the point. They simply need to go.

 

It made me think of the Post-War Japanese Economic Miracle. Two people are cited for this event: General McArthur and Dr. W. Edwards Deming. After the Japanese were brought to their knees by crisis, McArthur came in and ripped out what was left of the old empirical Japanese system. Deming then came along and taught the Japanese how to do business.

When Deming came back to America, he found himself the proverbial prophet in his own land. Business managers would have little or nothing to do with him. After all, they were all successful. Why did they need to make any changes? (never mind WWII had destroyed all their major competitors and they had a free hand in the market). Even when the Japanese began to finally catch up and surpass the Americans in quality and productivity, few could comprehend Deming’s philosophy. He still met resistance from those stuck in their ways.

The descendants of Deming’s ideas, like we agilists, face the same problem he did. How do we get people to change for the better who are resistant? Carl would suggest we be like McArthur: rip out the old environment so folks who can make productive change like Deming can do their jobs.

I’m not convinced Carl is right, but he certainly got me thinking. What do you think? Is this a viable strategy to create change? Do we need the warriors to first come in with their swords and warhammers before the sages come in with their books and control charts?