What is a “Socio-Technical System?”

Lately the term “socio-technical system has been starting to show up more and I thought this would be an opportunity to weigh in on what I think it means.

Though the concept has been around since at least 1951 (see below), I think I have tended to “bleep over” the term as jargon without giving it a lot of thought. I don’t think I am alone in that.

People who try to describe the meaning tend to describe a system “that integrates the social and technical aspects” or words like that.

I would posit that it goes much deeper, and we “bleep over” the concept at our peril if we want our organizations to function well.

The Origin of Social-Technical Theory

*Up through the 1940s, coal mining in the UK was largely pick and shovel work aided by drills and, sometimes, explosives. A work crew typically consisted of three to half a dozen men (and they were all men) who were task organized to strip the coal off the seam face, shovel it into mining carts, and move those carts to the transport system.

These teams were distributed through the mine, and because the distance and working conditions really precluded a lot of supervision, the teams largely oversaw their own work.

Since each team worked independently, the system as a whole could easily accommodate the simple fact that in some spots the coal is harder to dig out than in others.

(If you want to get more of a feel for the work and working conditions, check out the photos in this Daily Mirror article: https://www.mirror.co.uk/news/real-life-stories/britains-last-deep-coal-pit-7000879)

The work also met every definition of “difficult, dirty and dangerous.” That work environment, though, created a social bond among the team members as they worked together to accomplish the task of “mining coal.”

The system was not without its problems, however. The social structure was built around loyalty to the small work team. When “trams” (coal carts) were in short supply, for example, the “trammers” would horde carts to optimize their team’s performance at the expense of other teams being limited by the number of carts available.

This all changed shortly after WWII.

The Long Wall Method

In the late 1940s the industrial engineers turned this craft production system into a factory system with the tasks divided between three shifts.

Long Wall Mining Shift Schedule

The process would begin on the evening shift. They would drill blast holes along the top of the coal seam, then dig an undercut about six inches high at the base to allow the blast to drop the coal. This would be done along a long (up to a couple of hundred meters) face of the coal seam. (Hence the name “long wall mining.”)

Meanwhile another team would break down the conveyor system that ran parallel to the coal face in preparation for moving it forward to position it for removing the loose coal.

Then night shift had two teams. One would extend the “gateway tunnels” at either end of the coal face. This was a crew of 8 men. Simultaneously another team would rebuild the conveyer in the new position.

Once all of this work was done, the shots would be fired, dropping the coal into a pile along the coal seam face.

Day shift would take the loose coal and transfer it to the conveyor system to be taken out of the mine.

Yes, this is an oversimplification, but it suffices for this discussion.

On paper, this process was far more efficient.

In practice, though, things did not go smoothly.

“Isolated Dependence”

A “filler” loads loose coal onto the conveyor.

Looking at this work breakdown, the first two shifts are prep work. Only the day shift, the “fillers,” actually get the coal out of the mine. But their success was entirely dependent on how well the first two shifts did their jobs. If everything was not “by the book” then the fillers would be significantly hampered. Since they were paid by the ton of coal extracted, there was more at stake than just a sense of accomplishment.

If the previous shifts ran into problems – such as a “shot” that failed to separate all of the coal from the roof of the seam, or harder material, etc. these inconsistencies slowed down the “fillers” and made them less successful. If the conveyor was not completely or correctly assembled, they could not begin work until this was corrected.

Because management pressure was on the key performance indicator – the rate of coal extraction, and because the “fillers” were paid by the ton of coal extracted, this created resentment between the “fillers” and crews on the other two shifts, as well as conflicts with management which the working crews began to regard (with ample evidence) as disconnected from the realities of their work.

Then, if the “fillers” were too far behind at the end of their shift, that would delay the start of the next cycle and things spiraled downward from there.

Productivity plummeted. The study I am citing here was commissioned to determine why. Their conclusion, in short, was that the new work organization was built around the paradigm of a factory assembly line without regard for the variation of geology. Success of the three shift cycle depended on each shift meeting a rigid schedule, but that schedule did not account for the simple fact that coal seams are not uniform.

In addition, the work organization destroyed the social structure of the mining crews. Their success was dependent on people they no longer saw or interacted with. The oncoming filler shift, in particular, would be confronted with all of the obstacles left by the previous two shifts. As their resentment for being unsupported built, their willingness to put in any extra effort dropped to zero.

Again – this is an oversimplification. If you want to read the full paper there is a link at the end of this post.

Oversimplification or not, however, the effect was stark. The social structure of the organization was driven to fundamentally change by alternations in the technical structure of the work. Quoting from my source material* :

The effect of the introduction of mechanized methods of face preparation and conveying, along with the retention of manual filling, has been not only to isolate the filler from those with whom he formerly shared the coal-getting task as a whole, but to make him one of a large aggregate serviced by the same small group of preparation workers.

The work design was based on a mechanistic view that ignored the how the social structure impacted the performance of the team.

The Mechanistic View

Installed in the year 1410, the Prague Astronomical Clock is the third-oldest in the world, and the oldest still in operation. (Prague is an awesome city, by the way.) Photo © Steve Collins, used under Creative Commons license via Flickr and Wikimedia

By the turn of the last century we thought we had the ways of the universe pretty well understood. Hundreds of years (thousands of years in some early societies) earlier we had the ability to predict the motion of the stars and planets – to the point that we could build machines that were analogues of their movements.

The prevailing model in psychology was classical conditioning which, in essence, said that behavior is an almost algorithmic learned response based on previous positive and negative reinforcements.

This mechanistic model leads to a belief that we can carefully design the machine and people’s work within the machine can be carefully designed and shaped through rewards and consequences.

And as long as everything, and every one, works as they are supposed to, it’s all good. If a machine malfunctions, we fix it. If people don’t follow procedures, we “motivate them” with incentives.

This model prevails even today and even colors our teaching of continuous improvement. One of the places we need tend to inherently adopt a mechanistic view is when we use the word “system.”

The Mechanistic View of “System”

In today’s world, when people talk about “the system” they are often referring to an information system of some type. Common examples are an Enterprise Resource Planning (ERP) system, or an Electronic Health Records (EHR) system. And these information processing systems do tend to shape how the organization functions, for better or for worse.

So when people talk about a “system” I think the reflex is to think of the system as a machine that is carefully designed, built, and tuned to perform a particular function or behave in a particular way.

And people tend to assume that once it is working, it will continue to work so long as it is maintained to be kept in the same condition.

This thinking often extends to the people as well. They are often viewed as servicing “the system” – providing it with information, and following the instructions it gives. (this is particularly true in ERP / MRP environments.) Everything is part of a machine, and as long as everyone does their jobs, and the equipment functions as intended, then it all works.

In practice, though, these systems tend to isolate people from one another, or into small single task groups in much the same way as happened in the coal mine.

The Mechanistic Paradigm at Work

The reason I explained all of this is so we can look at our own workplaces through this lens. The crucial question is: Do the work structures and systems support or hamper the social structure of effective teamwork?

Let’s take another look at those ERP or EHR systems. Without the interaction with and the interaction between the people who use them, those “systems” are inert. They do nothing. The mechanistic paradigm, though, tends to look at people as performing a task to serve or enable the system. Instead, we should look at the information system as a tool that should enable people do to a job they otherwise could not.

On the Shop Floor

The sign says “Hearing Protection Required.” The reality is that it is impossible for more than 3 or 4 people to have a conversation on the shop floor, as they are shouting to be heard. The final operation is highly automated, each machine has two people working in isolation, even from one another for the most part. In addition, the machine crews are isolated from one another, both by distance and by the noise level.

The machine operator is measured on his hourly rate of production vs. a standard expectation.

Meanwhile at the opposite end of the building, the production scheduling team works to carefully orchestrate the availability of packaging materials, purchased components, as well as scheduling each phase of production so work is available for the next step.

They do all of this with their ERP system and every day they create orders to issue components, production orders to the various areas in the shop, and purchase orders to their suppliers. They adjust priorities at least daily, based not only on lead times and changing customer requirements, but also on the reality of what has actually been produced, or not, up to this point. Items are early, they are late, production runs ahead, though mostly behind, the scheduled intent.

Everyone is frustrated. The planner / schedulers because production never seems to make what they planned. And production because scheduling never seems to schedule things that can be made with the available materials, etc. Shortages are discovered, an ad-hoc plan is created to keep things moving – but that may well consume components that were earmarked for something later in the week, and the cycle continues.

To make things even more interesting, the planner / schedulers are using production capacity numbers that they know are higher than reality. They are under pressure to put in unrealistic numbers because the real numbers would make the site’s cost estimates too high and attract scrutiny from corporate.

This means “the system” produces schedules that cannot be met by actual production even if everything else works, which, in turn, means continuously over-promising, under-delivering, and adjusting priorities.

Though the work is very different, we have a social structure not unlike the British coal mine.

This is what “isolated dependence” looks like in today’s work environments. If you are seeing blame casting and conflict between groups who are dependent on one another you likely have a similar situation in your organization.

Counter-Productive Response

Unfortunately the typical management response is to increase monitoring, control, incentives, “accountability” on individual parts of the process rather than looking at the entire system.

These things tend to increase the sense of isolation and frustration as they can create a sense of victimhood between the separate groups. For example, in the above situation everyone there told me that they used to have pull system on the factory floor, and it had worked really well, operated predictably, and gave them a lot more insight into what was actually happening. But some time ago a new management team wanted to track everything in the computer “for control” so the current system was installed.

Ironically, that management team had turned over, but for whatever reason people were very reluctant to return to what they knew had worked in the past. But I digress.

The Implications

Human beings are innately social. In any organization, or casual group trying to get something done, people develop webs of social networks. The more they can interact, the more everyone stays on the same page.

There are a few things we can do to reinforce this.

Bring People Together

And I mean bring them together literally, physically. Rather than just confronting one another in the morning meeting, have them literally work side-by-side with the common goal of a smooth process.

Have a Shared, Objective, Truth

Eliminate the need to ask or query “status.” Eliminate the one person who knows the big picture. Get the truth out there in the open– literally, physically. (See a trend here?)

In a well managed operation I nearly always find rich “information radiators” that are an inherent part of the process itself (rather than being a display of information that was input just so it can be displayed). This information is not simply a passive display. It is actively used by the people doing the work to they know where they stand, what comes next, and when they need to raise a concern.

A classic example of this is a heijunka or load-leveling box. The cards, or work orders, or pick tickets, are placed in slots that are based on the time that work is expected to start if everything is working normally. Thus it is insanely easy to spot if something is getting behind, long before it would show up in the daily production report. Menlo Innovations’ Work Authorization Board does the same thing.

The goal is for conversations to be about “How to respond” rather than discussions about “what is happening.”

This is really the purpose of nearly every “lean tool” — to ask, and answer, two key questions:

  • What should be happening?
  • What is actually happening?

and then invite a conversation about any difference between the two.

The fact that “we have made 234 widgets” is meaningless without a point of comparison of “how many widgets should we have made up to this point?” The goal is to invite curiosity and foster actual conversations, and eliminate debates about what should be and what actually is.

But more often, this is what I most find lacking. People well tell me they can easily query status, look up individual orders, but even then there is rarely a timely comparison between “nominal” and “actual” in that information. Even if status can be queried, there is often a lack a “compared to what?” Or worse, the status is abstracted from reality, for example, measured in “earned hours” or some other financial metric. Often “ahead or behind” is not known until the end of the day… or the week, or sometimes even the month. The greater the lag, the bigger is the scramble to make up production with overtime.

So here is question #1 for you: If I were to ask you, right now, “Is this operation ahead or behind?” could you tell me? Can the people who are actually doing the work tell me? And by “tell me” I mean immediately, without having to go research or launch some kind of query.

Another version of this question is, “How far behind do you allow yourself to get before you actually know there is a problem?”

Social-Technical

So what we have is a technical aspect of a process that is deliberately designed to support meaningful social interactions between the people responsible for carrying out the work and accomplishing the overall task… as a team. We bring people together rather than isolating them from one another.

This is hard – Yup.

And these principles run against management “best practices” that have been taught since the 1920s.

Where to start? If any of this seems impossible, work on trust. Think about this – Why would people be reluctant to display an objective truth without the ability to first qualify it?

Why would people be reluctant to create a true dependent relationship with another department?

All of these things come down to a culture of self-defense because people feel a need to protect themselves from something or someone. Even if that force is long gone, the effects of leadership-by-fear linger, sometimes for many years, unless you take proactive and direct steps to eliminate that fear.

So… if this seems hard, work on that first.


* The original study of the interplay between social structure and work organization and technology looks to be the 1951 paper “Some Social and Psychological Consequences of the Longwall Method of Coal-Getting: An Examination of the Psychological Situation and Technological Content of the Work System” by E.L. Trist and K.W. Bamforth

Respect, Standards and Jidoka

Many years ago I wrote an article for SME called The Essence of Jidoka. In that article I described a four step process designed to improve productivity and drive continuous improvement. Since then these four steps have been picked up and incorporated into the training materials of many consultants, used to write the Wikipedia article on jidoka (which I most assuredly did not author), and even found their way into some academic papers. Sometimes with attribution back to my article, may times without.

In that article, “jidoka” was described as a four step process:

  1. Detect a problem.
  2. Stop.
  3. Fix or correct the problem.
  4. Find the root cause and implement a permanent countermeasure.

But I would like to take a hard look at the first step: Detect the problem. This is where, I believe, most organizations actually fall down. And in doing so, they also fall down on respect for people.

The key question is: “What do you consider a problem?”

Most organizations do not see a problem until the symptoms are bad enough that they are compelled to do something about it. This means people have been struggling with issues for some time already. The machine isn’t reliably producing good parts. Or someone is having to rework material. Or the supplies cabinet is always short, and the nurses have to launch a safari to find what they need.

Contrast this with a company like Toyota. Every Toyota-trained leader I have ever dealt with is very consistent. A problem is any deviation from the standard. More importantly, a deviation from the standard (1) forces people to improvise and (2) is an opportunity to learn.

This definition, of course, leads to a question: “What is a standard?”

Probably the best explanation to date is in the research done by Steven Spear at Harvard. His work was summarized in the landmark article Decoding the DNA of the Toyota Production System.

Spear’s research concluded there were four tacit rules for how activities, information connections, flow paths, and improvements were designed and executed in Toyota operations. Each of those rules describes:

Any deviation from the standard triggers some kind of alert that gets someone’s attention. And whose attention is explicitly defined – That is a standard as well.

As I look at a work area, I often see a lot of 5S type of activity. Things and their intended locations are marked and labeled. These are standards. They establish what should be where. But the question to ask is “What happens if something is out of place?”

That is a deviation from the standard. It is a problem.

Stop

Fix or Correct (put it back – restore the standard condition)

Investigate the root cause

“What’s going on with the air wrench today?”

“Actually it is an extra one.”

“Really? Where did it come from?”

“I borrowed it from the Team Member in work zone 3.”

“Ah, OK. Why did you need his?”

“The regular one isn’t working.”

“Hey – thanks for letting me know. I’ll get it to maintenance.”

“Thanks”

“Did you tell anyone about the problem before now?”

“No, I just borrowed the wrench. I just needed to get this job done, then forgot. It’s no big deal, it’s easier to just borrow Scott’s wrench.”

And in that exchange, what have you discovered about your daily management system by simply being curious about a trivial deviation from a 5S standard?

Is this the Team Member’s fault?

Probably not. What is your standard? What is he supposed to do if the wrench stops working? Is there an escalation process and a response for this kind of small stoppage? Or are your Team Members just expected to find a way to work through the issue? Which of those responses is more respectful of the Team Member who spends her time trying to create value for you?

Often times there is no standard.

But without a standard you have no way to tell if there is a problem (other than a feeling that something isn’t right). And if you are sure there is a problem, without a standard you can’t really define what “fixed” is.

So start with defining the standard. First, go back to Decoding the DNA of the Toyota Production System. You can get an idea of the kinds of things you should standardize.

As you think of standards, consider a standard for your standard:

  • Express it from the viewpoint of the process customer.
  • Define it in a way that can be verified as “met” or “not met.” No gray zones. You can quantify the magnitude of a problem, but not whether you have one.
  • There is a visual or other control tells the appropriate person, right away, if there is a deviation from your standard?
  • Is there a standard that triggers a response to clear the problem?

5S is nothing more than the first step of setting standards. Many people say to start there, but don’t say why. The point is to practice setting standards and holding them. Taiichi Ohno is quoted as saying:

“If there is no standard, there can be no kaizen.”

Any deviation from the standard is a problem.

Your choice, as a leader, is how to handle that problem.

Daily Management for Improvement

I’m digging through old archives again, and came across this graphic I put together around 2006 or so. It depicts more detailed version of “Organize, Standardize, Stabilize, Optimize” showing the continuous comparison between “what should be happening” and “what is actually happening.” It is the gap between these two that drives improvement forward.

Like the pocket card in the last post, this is built on a foundation established by the work of Steven Spear, especially his PhD dissertation that is summarized in Decoding the DNA of the Toyota Production System. By the way, if you are in the business of continuous improvement, reading (and understanding) this breakthrough work is critical for you.

Other than generally sharing this, my other reason for putting this up is that in the Toyota Kata community there has been discussion for about a decade about whether or not the right hand loop – pushing for stability – is an appropriate use of the Improvement Kata.

I think that is an unfortunate result of some very early conversations about the difference between “troubleshooting” and “improving” a process. We get into semantic arguments about “problem solving” as somehow different from “root cause analysis” and how the Improvement Kata is somehow distinct, again, from those activities.

This makes no sense to me for a couple of reasons.

Scientific Thinking is the Foundation

Toyota Kata is not a problem solving tool. It is a teaching method for teaching scientific thinking, and it is a teaching method for learning to teach scientific thinking. In the books and most literature, it uses organizational processes as working examples for the “starter kata,” but exactly the same thinking structure works for such diverse things as working through quality issues, developing entirely new products and processes, working through leadership and people issues. The underlying sub-structures may change, but the basic steps are the same.

When I encounter an organization that already has a “standard problem solving approach” I do not attempt to tell them they are wrong or confuse them by introducing a different structure. Rather, I adapt the Improvement and Coaching Kata to align with their existing jargon and language, and help them learn to go deeper and more thoroughly into their existing process.

Stability is a Target Condition

I see a lot of pushback about working to “return a process to standard.” In reality, that is the bulk of the activity in day-to-day improvement. The whole point of having a standard in the first place is to be able to see when the actual process or result is somehow different.

Think about it: If there isn’t an active means of comparing “actual” vs. “standard” what is the point of having a standard in the first place?

Think of the standard as a target condtion.

What obstacles are preventing you from [operating to that standard]? You can guess, but the best way is to diligently try to operate to the target condition and see what gets in your way. That might not happen immediately. Maybe some time will go by, then BAM! You get a surprise.

This is good. You have learned. Something you didn’t expect has interfered with getting things done the way you wanted to. Time to dig in and learn what happened.

Maybe there was some condition that you could have detected earlier and gotten out in front of. Who knows?

This is all part of the continuum of Troubleshooting by Defining Standards.

You Cannot Meet a Challenge Without Working on Stability

As you are working to reach new level of performance – working toward a new challenge – there will be a point when the process works sometimes, so you know it is possible. But it doesn’t work every time because there are still intermittent obstacles that get in the way.

Nevertheless, you have to work diligently to see problems as they occur, respond to them, dig into causes (root cause analysis anyone?) and systematically protect your process from those issues.

The only real difference between covering this territory for the first time vs. trying to recover a previously stable process is that in the later case you can ask “What has changed?”

But, in the end, in both cases – stabilizing a new process vs. re-stabilizing an old one – you are dealing with conditions that are changing from one run to the next. That is why it works sometimes and not others. You don’t know what is changing. You are trying to figure it out by experimenting and learning.

What About Root Cause Analysis?

My challenge is still a stable process.

My current condition is my level of understanding of how the process works today, and the exact mechanism that results in a defect. Even defects are produced by a process – just not the process we want.

That understanding will be incomplete by definition – because if we truly understood what was going on we wouldn’t have the problem. So… what do I know (and can prove with evidence) and what do I not know.

What do I suspect? What evidence do I need to gather to rule out this possible cause, or keep it in play? Next experiment. What do I expect to learn?

I’ll write a more detailed post about this at some point. I think it is a topic worth digging into. Suffice it to say that I have absolutely used the Improvement Kata structure to coach people through finding the root cause of wicked quality problems.

It really helped that they were able to see the same underlying pattern that I had already been teaching them. It made things simpler.

Don’t Complicate a Simple Concept

It’s all “solving problems” (the term “problem solving” apparently has some specific form it needs to take for some people).

The underlying structure for all of it is scientific thinking. Some say it’s PDCA / PDSA. Same thing.

Splitting semantic hairs and saying “this is different” makes simple things complicated. Yes, there are advanced tools that you use when things get tough. But… addition and subtraction; basic algebra; advanced polynomials; basic differential calculus; advanced multivariate calculus – IT IS ALL MATH. You apply the math you must to model and solve the problem at hand.

DON’T apply more math than you need just because you can. That serves no purpose except, perhaps, to prove how smart you are… to nobody in particular.

Solving problems is the same. There are some cases where I need to develop a designed experiment to better understand the current condition – the interactions between variables. There are cases where other statistical tools are needed. Use them when you must, but not just because you can.

Use the simplest method that works.

It will feel worse because it’s getting better.

image

The line is starting to flow, or at least there is more time flowing than not flowing. The places where it isn’t flowing well are now much more evident.

Things are speeding up. That is placing more stress on the engineering and materials supply processes where, before, they were shielded by a rough start-up that was always behind schedule.

They are catching up on the backlog, closing in on “on schedule shipment.”

“John” forgot to send a batch of parts to an outside processor. Before that would have been no big deal, it would be a day or so before those things were actually needed. But this time it briefly stopped the line and forced a work-around.

When everything was a work-around, nobody noticed. This time it got on the radar. It feels worse because the system is sensitive to smaller problems now, and there are plenty of those.

It isn’t “John’s” fault. He is flooded with a constant flow of things he needs to react to. There isn’t a structure for him to work within. That is the next opportunity.

Thus, it is critically important to remember a Toyota mantra:

‘No problem’ is a big problem.

If problems are not coming up, then your system is hiding them, plain and simple. You have stopped learning, stopped improving, stopped growing.

It is an easy groove to get into because we get all kinds of feel-good brain chemicals when things are going smoothly. We want more of those, less of the ones that call us to action.

But it is those “call to action” things that drive us to get better.

Team Member Saves

image

Now and then one of your team members makes a great save. They catch something that could have caused a defect, an accident, or done harm in some way.

Often we celebrate these saves, sometimes informally, sometimes formally. And that is well and appropriate.

But let’s make sure we are celebrating for the right reasons.

The save isn’t what should be celebrated.

Rather, the celebration should be a big THANK YOU for finding a gap in your process.

Somehow the process is capable of producing a defect, resulting in an accident, or doing harm. Your team member noticed that.

We usually just celebrate correcting the immediate problem.

But What is preventing exactly the same thing from happening tomorrow?*

image

That front-line customer-facing team member is your last line of defense.

They only get an opportunity to make a “save” when every other point in the process has failed to detect the  problem.

Given enough “shots” at this front line team-member, sooner or later, one is going to get through.

What happens then? Is the inverse logic applied? “You should have caught that.”

Perhaps, but where in the process was the problem actually created?

Somewhere, long before this diving catch, there is an instant when the process went from operating safely and defect free to creating an opportunity, an opening, for a problem to pass undetected.

Where and when was that moment?

Or is that how the process normally operates, and we are just lucky most of the time?

Dig in, think about it.

And thank that team member for saving you, but don’t count on it every time.

———-

*Thanks to Craig for this great way to sum up the question.

Toyota Kata, Kaizen Events and A3

I’ve been asked to explain the relationship between “Toyota Kata” and Kaizen Events, and I am guessing that the person asking the question isn’t the only one who has the question, so I thought I’d take a crack at it here.

To answer this question, I need to define what I mean when I say “kaizen event.”

Kaizen Events

In a typical western company, a kaizen event is geared toward implementing lean tools. There are exceptions, but I think they are different enough to warrant addressing them separately. (If you don’t read this, I changed my mind as I was writing it.)

At this point, I am going to borrow from an earlier post How Does Kaizen Differ From a Kaizen Event:

The kaizen event leader is usually a specialist whose job is to plan and lead these things, identifies an improvement opportunity. He might be tasked by shop floor management to tackle a chronic or painful problem, or might be executing the “lean plan” that calls for a series of implementation events.

It is his job to plan and execute the event and to bring the expertise of “how to make improvements” to the work force and their leaders.

Here’s the Problem

The full-time kaizen event leaders typically get really good at seeing improvement opportunities, organizing groups for improvement, and quickly getting things done. They get good at it because they do it all of the time.

The area supervisors might be involved in a kaizen event in their area a few times a year if that. Some companies target having each employee in one kaizen event a year.

That’s 40 hours of improvement. All at once. The question is: What do they do (and learn) the other 1900 hours that year?

What do they do when something unexpected happens that disrupts the flow of work? Usually kaizen events don’t deal with how to manage on a day-to-day basis other than leaving an expectation for “standard work” in their wake.

But “standard work” is how you want the work to go when there aren’t any problems. When (not if) there are problems, what’s supposed to happen?

This is why many shop floor leaders think “kaizen” is disconnected from reality. Reality is that parts are late, machines break, things don’t fit, Sally calls in sick, and the assembler has to tap out threads now and then. In the hospital, the meds are late, supply drawers have run out, and there is a safari mounted to find linens.

These things are in the way of running to the standard work. They are obstacles that weren’t discovered (or were glossed over as “resistance to change”) during the workshop.

The supervisor has to get the job done, has to get the stuff out the door, has to make sure the patients’ rooms are turned over, whatever the work is. And nobody is carving out time, or providing technical and organizational support (coaching) to build his skills at using these problems as opportunities for developing his improvement skills, and smoothing out the work.

OK – that is my paradigm for kaizen events. And even if they work really well, the only people who actually get good at breaking down problems, running PDCA cycles, etc. are the professional facilitators or workshop leaders. Many of these practitioners become the “go-to” people for just about everything, and improvement becomes something that management delegates.

What are they good for? Obviously it isn’t all negative, because we keep doing them.

A kaizen event is a good mechanism for bringing together a cross functional team to take on a difficult problem. When “improvement” is regarded as an exception rather than “part of the daily work,” sometimes we have to stake out a week simply to get calendars aligned and make the right people available at the same time.

BUT… consider if you would an organization that put in a formal daily structure to address these things, and talked about what was (or was not) getting done on a daily basis with the boss.

No, it wasn’t “Toyota Kata” like it is described in the book, but if that book had been available at the time, it would have been. But they had a mechanism that drove learning, and shifted their conversations into the language of learning and problem solving, and that is the objective of ALL of this.

Instead of forcing themselves to carve out a week or two a year, they instead focused on making improvement and problem-solving a daily habit. And because it is a daily habit, it is now (as of my last contact with them a couple of months ago), deeply embedded into “the way we do things” and I doubt they’re that conscious of it anymore.

This organization still ran “event” like activities, especially in new product introduction.

In another company, a dedicated team ran the layout and machinery concepts of a new product line through countless PDCA cycles by using mockups. These type of events have been kind of branded “3P” but because changes and experiments can be run very rapidly, the improvement kata just naturally flows with it.

Kaizen Events as Toyota Kata Kickstarts

If you take a deeper look into the structure of a kaizen event, they generally follow the improvement kata. The team gets a goal (the challenge), they spend a day or so grasping the current condition – process mapping, taking cycle times, etc; they develop some kind of target end state, often called a vision, sometimes called the target and mapped on a “target sheet.” Then they start applying “ideas” to get to the goal.

At the end of the week, they report-out on what they have accomplished, and what they have left to do.

If we were to take that fundamental structure, and be more rigorous about application of Toyota Kata, and engage the area’s leader as the “learner” who is ensuring all of the “ideas” are structured as experiments, and applied the coaching kata on top of it all… we would have a pretty decent way to kickstart Toyota Kata into an area of the organization.

Now, on Monday morning, it isn’t what is left to do. It is the next target condition or the next obstacle or the next PDCA cycle.

Toyota Kata

If we are applying Toyota Kata the correct way, we are building the improvement skills of line leadership, and hopefully they are making a shift and taking on improvement is a core part of their daily job, versus something they ensure others are doing.

One thing to keep in mind: The improvement kata is a practice routine for developing a pattern of thinking. It is not intended to be a new “improvement technique,” because it uses the same improvement techniques we have been using for decades.

The coaching kata is a practice routine to learn how to verify the line-of-reasoning of someone working on improvements, and keep them on a thinking pattern that works.

By practicing these things on a daily basis, these thought patterns can become habits and the idea of needing a special event with a professional facilitator becomes redundant. We need the special event and professional facilitator today because a lot of very competent people don’t know how to do it. When everybody does it habitually, you end up hearing regular meetings being conducted with this language.

We can be more clear about what skills we are trying to develop, and more easily assess whether we are following sound thinking to arrive at a solution. (Luck is another way that can look the same unless the line of reasoning is explained.)

What About A3?

When used as originally intended, the A3 is also a mechanism for coaching someone through the improvement pattern. There are likely variations from the formal improvement kata the way that Mike Rother defines it.

However, if you check out John Shook’s book Managing to Learn, you will see the coaching process as primary in how the A3 is used. Managing to Learn doesn’t describe a practice routine for beginners. Rather, it showcases a mature organization practicing what they use the Improvement Kata and the Coaching Kata to learn how to do.

The A3 itself is just a portable version of an improvement board. It facilitates a sit-down conversation across a table for a problem that is perhaps slightly more complex.

An added afterthought – the A3 is a sophisticated tool. It is powerful, flexible, but requires a skilled coach to bring out the best from it. It can function as a solo thing, but that misses the entire point.

For a coach that is just learning, who is coaching an improver who is just learning, all of the flexibility means the coach must spend extra time creating structure and imposing it. I’ve seen attempts at that – creating standard A3 “templates” and handing them out as if filling out the blocks will cause the process to execute.

The improvement kata is a routine for beginners to practice.

The coaching kata is a routine for beginners to practice.

Although you might want to end up flying one of these (notice this aircraft is a flight trainer by the way):

T-38

They usually start you off in something like this:

image of Cessna 172

The high-performance aircraft requires a much higher level of instructor skill to teach an experienced pilot to fly it.

And finally, though others may differ, I have not seen much good come from throwing them up on a big screen and using them as a briefing format. That is still “seeking approval” behavior vs. “being coaching on the thinking process.” As I said, your mileage may vary here. It really depends on the intent of the boss – is he there to develop people, or there to grant approval or pick apart proposals?

So How Do They All Relate?

The improvement kata is (or absolutely should be) the underlying structure of any improvement activity, be it daily improvement, a staff meeting discussing changes in policy, a conversation about desired outcomes for customers (or patients!).

The open “think out loud” conversation flushes out the thinking behind the proposal, the action item, the adjustment to the process. It slows people down a bit so they aren’t jumping to a solution before being able to articulate the problem.

Using the improvement kata on a daily basis, across the gamut of conversations about problems, changes, adjustments and improvements strengthens the analytical thinking skills of a much wider swath of the organization than participating in one or two kaizen events a year. There is also no possible way to successfully just “attend” an improvement activity if you are the learner being coached.

Active Control

Imagine you are driving an automobile with a high-performance suspension. You are on a perfectly straight stretch of road, with smooth pavement. Get yourself up to, say, 65 miles per hour (100 km/h). Got it pointed down the middle of the road?

OK, close your eyes, let go of the steering wheel and wait. (Actually closing your eyes is optional.)

Can you predict what will happen, more likely sooner than later?

It doesn’t matter how “stable” your car is.

There are small, random things that are eventually going to cause your car to drift away from the centerline and off the road, into the ditch on one side, or over the cliff on the other. (Didn’t I mention those?)

I often see people set up a well performing process and treat it the same way – as though it will continue to work the same way forever, without any intervention.

But your process is going to encounter random chatter, and when it does, what typically happens?

In most cases, the team members can find a way to work around the issue, and likely continue to get things done, though they will have added a bit of friction, requiring a bit more effort, to do so. They will add a redundant check to make sure no mistake got made. They will add some inventory under the work bench, in case something runs out. They will carry the product over to the other machine because the one they are supposed to use isn’t working as it should be.

They will clean up the spilled coolant, catch the leaking oil.

They will head up-line to borrow a team member’s grease bucket.

They’ll tap out paint clogged or unthreaded holes, cut wires that are delivered too long to length, even drill new holes to mount the part that doesn’t fit.

In the office, they get one more signature, send an email to back-up the “unreliable” ERP messages, and make screen prints so they can enter the data into another system.

“Waste is often disguised as useful work.”

All of this easily goes unnoticed, and eventually (maybe) the process becomes cumbersome enough that someone decides to address it with an improvement activity. And the cycle starts again.

How do we stop the cycle?

The point of intervention is in the last paragraph… “All of this goes unnoticed.”

It isn’t a matter of standing and watching for problems. Sakichi Toyoda figured that out almost 100 years ago. It is about designing your process to detect anomalies in either execution (how it is done, how long it takes) or results immediately, signal, and trigger some kind of response.

Here are some fundamental questions to ask yourself:

Before the process even begins, does the team member have everything he needs to succeed? How does he know? I’m talking about parts, information, tools, air pressure, assistance… whatever you know is needed to get the job done.

If the team member doesn’t have everything needed exactly what do you want him to do?

Is the team member carrying out the process in a way that gets the desired result? How does she know? Is there a sequence of steps that you know will give her the result you want? What alerts her if one of them is skipped?

If the team member, for whatever reason, isn’t able to carry out those steps in sequence, exactly what do you want her to do? Go find a grease bucket? Or let you know?

How long do you want to allow your team member to try to fix something or make it work before letting you know there is a problem? Related to this – how far behind can you allow him to get before he can’t catch up, even with help?

Once the team member has completed the process, how does he know the result is what was expected? If the team member doesn’t have a way to positively verify a good outcome, who does detect the problem, when, where and how? It might be your customer!

An Active Control System

Even if you have all of those checks in place, however, you still need to answer a few more questions starting with “Once the team member detects a problem, what do you what exactly do you want them to do?”

I alluded a little to this above, but let’s go a bit deeper.andon-pull

On a production line, a typical way for a team member to signal a problem is with some kind of andon. This might, for example, take the form of a rope along the line that the team member can pull in order to trigger a signal of some kind.

But that is the easy part. Lots of factories have copied the mechanics of Toyota’s andon only to see them fall into disuse following a period of cynicism.

The hard part is what is supposed to happen next?

Now we are back to the original questions because the andon is nothing more than a trigger for another process.

Who is the designated first responder? (Remember, if it is everybody’s problem, it is nobody’s problem.) Does that person know who he is?

What is the standard for the response? What is the first responder supposed to do, and how long does she have to do it?

When we had takt times on the order of dozens of minutes, our standard for the first response making face-to-face contact with the team member who signaled was 30 seconds.

How much intervention can the first responder make before being required to escalate the problem to the next level?

As a minimum

As a minimum, the first responder’s primary goal is to restore the normal pattern of work. This might be as simple as pitching in and helping because something minor tripped up the team member’s timing.

This is active control – a system or process that detects something going outside the established parameters, and applying an adjustment to get it back. Active control requires a process to detect abnormalities, a trigger, and a response that restores things. It is no different than maintaining thickness in a rolling operation – the machine measures the output, and adjusts the pressure accordingly – or an autopilot that keeps an airplane on course.

Without some kind of active control system, your process will erode over time as the team members do the only things they can do in an effort to keep things moving: They can overproduce and build inventory to compensate, they can add extra process steps, they can add just about any of the things we call “waste.”

The only question is what do you want them to do?

Clearing the Problem / Solving the Problem

As I work with clients to get a “problem solving culture” embedded, one common challenge is the distinction between the short term work-around to remove the obstacle, and the long-term countermeasure that actually improves the process.

I addressed this at a conceptual level in the “Morning Market” post a while ago.

Last week I was working with a client who has begun using the work-around as their key insight into the issue they have to solve.

When the work flow is disrupted, they are careful to capture what they had to do in order to clear the problem and get the item back into the normal production flow.

“We had to wait for parts.”

“We had to rework _____.”

“We had to get on someone else’s login for enough security to do the task.”

“We had to find the ____.”

“We had to replace ___”

This is really valuable information. By appending “Why did…” in front of the statement, they have a fairly well defined starting point for getting to the bottom of the actual issue.

By making the containment action the first “Why?” they get off the containment-as-solution mindset.

It might not work for everyone, but it is working very well for them.

“Please continue.”  Smile

Mike Rother: Time to Retire the Wedge

Note – this post was written pretty much simultaneously with a post on the lean.org forum.

Mike Rother has put up a compelling presentation that highlights a long-standing misunderstanding about the purpose of “standards.”

Some time ago, a (well-meaning) author or consultant constructed a graphic that shows the PDCA wheel rolling up the incline of improvement. There is a wedge labeled “Standards” shoved as a chock block under the wheel to keep it from rolling back. That graphic has been copied many times over the years, and shows up in nearly every presentation about PDCA or standard work.

The implication – at least as interpreted by most – is that a process is changed for the better, a new standard is created, and people are expected to follow the standard to “hold the gains” while they work on rolling the PDCA wheel up to the next level on the ramp.

Slide 6 (taken from the book Toyota Kata) shows the underlying assumptions that are implied by this approach, especially when it doesn’t work.

There are some interesting assumptions embedded in the “wedge thinking.”

The first one is that “the standard can be ‘held’ by the people doing the work.

That, in turn, means that if when things start to deteriorate, the workers and first line leaders are somehow responsible for the “slippage” or “not supporting the changes.”

With this attitude, we hear things like “Our workers aren’t disciplined enough” or “How do I make them follow the standard?” The logical countermeasures are those associated with compliance – audits focused on compliance, and sometimes even escalating punitive actions.

Back in my early days, I had a shop floor team member call us on it quite well: “How can you expect us to hold some kind of standard work if the parts don’t fit?” (or aren’t here, or the tools don’t work, or jigs are misaligned, or the machine isn’t running right, or someone is absent, or we are being told to hurry and just get stuff out the door?)

This is the approach of control. The standard is fixed until we decide to change it.

Taiichi Ohno didn’t teach it this way.

Neither did Deming or Juran. Neither did Goldratt. Nor does Six Sigma, TQM, TPM.

Indeed, if we want creativity to be focused on improvements, we have to look up the incline, not back.

We are putting “standards” on the wrong side of the wheel. Rother’s presentation gets it right – the “standards” are the target – what we are striving to achieve.

The purpose of standards is to compare what we actually do against what we wanted to do so we know when they are different and so we have some idea what stopped us from getting there.

Then we have to swarm the problem, and remove the barrier. Try it again, and learn what stops us the next time.

The old model shows “standards” as a countermeasure to prevent backsliding, when in reality, standards are a test to see if our true countermeasures are working.

I believe this model of “standards” as something for compliance is a cancer that is holding us back in our quest to establish a new level of understanding around what “continuous improvement” really means.

It is time to actively refute the model.

If you own your corporate training materials, find that slide (it is in there somewhere) and change it.

If you see this model in a presentation, challenge it. Ask what should happen if something gets in the way of meeting this “standard.”

“What, exactly do you expect the team member to do?”  That sparks an interesting conversation which reveals quite a bit.

5S in Three Bullets

I was in a conversation today and we ended up boiling 5S down to three key points:

  • You have everything you need.
  • You need everything you have.
  • You can see everything clearly belongs where it is.

Of course at the next level, these statements are the standards you are continuously checking against.

Presumably we have cleared out everything else, leaving only what we thought was needed, and established visual controls to verify we have those things, and only those things, in the work area.

Then, as the work is done, the moment someone discovers something else is needed, THAT is the time to deal with the issue.

– Ask “Is this something we should need in the normal course of the work?”

If so, then you learned something that you didn’t know or didn’t remember when you first organized the area. Add that item, find a place for it, and establish a visual control. Right now.

If not, then “Why did we need it this time?”

What broke the normal pattern of work?

This is where 5S breaks down – when we don’t discriminate between something that is needed in the normal course of work, and something that is needed as an exception.

If we just “get it” and add it to the work area, then we normalize deviance and incrementally erode the process. If we ignore the issue, we add “getting this when it is needed” to the work cycle.

If, on the other hand, we seek to understand what broke the normal pattern and deal with the core issue, we have a shot at real kaizen. (It is perfectly OK to get what you need and keep it around as a temporary countermeasure. Just put it someplace where you will KNOW when you used it.)

The worst thing you can do is allow these small problems to accumulate and try to correct them en-mass as some kind of “corrective action.”

Kanban

Likewise, kanban can be expressed the same way. It is more dynamic, but is really answering the same questions in the context of materials.

 

Standard Work

If you paraphrase these key points to just about any other “tool of lean” then the purpose of surfacing problems and driving solution becomes apparent.

  • You are doing everything that is required.
  • Everything being done is required.
  • Everything being done clearly is part of the sequence.

Take a look at the other classic “tools of lean.” How would they fit into the same pattern?