Keeping You Informed On Lean Manufacturing
Last week, I made the case for leaving the word “efficiency” out of your lexicon. Just in the past few days, I ran into another example of why manufacturers need to quit saying (or even thinking about) efficiency.
Continue reading “If You Can’t Say “Efficiency”….What DO You Say?”
I once worked for an organization that provided training and consulting to businesses and non-profits here in Northeast Ohio. Our primary “product” was labor-management cooperation initiatives, which took many forms: lean manufacturing, Total Quality Management, quality circles, even ISO 9000. Oddly, the president of the organization didn’t know much about any of these concepts. He had been a quality manager at a local manufacturing firm and the board figured he must know something about labor-management cooperation. (Yeah, I don’t get the connection either.)
He and I would have these discussions during which he’d tell me that I needed to quit using the word “culture” and use the term “efficiency” more often. “Managers don’t understand ‘culture’ but they understand ‘efficiency'”, he’d argue. I would agree that managers didn’t understand “culture”. I’d go on to say that they didn’t understand “efficiency” either. But, they’re employees had a clear idea as to what managers meant when they used the word. And they didn’t see it as good for them.
My point was (and remains today) that managers use the word “efficiency” as a euphemism to mean “We want more of the stuff we like without you asking for more of the stuff you like” when talking with employees. When managers talk about “improving efficiency”, employees never (NEVER) imagine that they’re going to hear anything that will be good for them. I’m sure many of you reading this have heard your own managers talk about “efficiency”. Did you, for a moment, imagine that what those managers had in mind was more investment in learning experiences and more autonomy for you? (If so, good for you…you had one of those rare, very enlightened bosses who really understood how to optimize the performance of a work team. )
“But don’t employees use that word, too?” They sure do…sometimes. But they use it as a synonym for “work together better” or something like that. You can bet that they don’t mean “we’ll work harder and faster for the same or even less consideration”…which, too often, is what their bosses have in mind even if they don’t want to say it out loud.
So, don’t say “efficiency”. It doesn’t send the message that you think it does. In future posts, I’ll tell you what you should say instead.
I stumbled across this article in my Google Alerts feed. (If you’re not familiar with Google Alerts, I recommend that you look into it. Essentially, you tell Google Alerts what topics you’re interested in, then Google scoops up articles on those topics and sends you a digest with links on a frequency that you choose. I get it weekly.) Take a few minutes to read it over.
I admit that I have a bit of regard for some Marxist arguments and points of view. Not so much the “workers revolt and take over the system and everyone will live happily every after” point. That one hasn’t worked out so well for the societies that tried it. But some of Marx’s other points of view and predictions have had merit. (Here’s an article that goes over some of those points more eloquently than I can.)
So when I saw this article critiquing lean production from the Marxist point of view, I was intrigued. Cutting to the chase, the author doesn’t like lean. But here’s the thing: Most of what he thinks he doesn’t like about lean just isn’t so. Here’s another thing: Most of what the author is wrong about, managers who think that they’re “in favor of lean” are also wrong about. So…Marxists don’t like lean and capitalists (most of them, anyway) purport to like lean but they’re all pointing to the same wrong reasons for their positions. Got it?
Let me pull some examples from the article to illustrate what I mean. Here’s the second sentence of the article: “It is a production system that bolsters the cost-reduction capacities of capitalist employers through an obsessive and competitive regime of intensifying work.”
That sentence is simply wrong. As in, not true. As in, completely and utterly in error. As in, altogether full of shit.
But…it’s a definition that most hard-right capitalists wouldn’t have much argument with. Lean messaging has always focused on cost reduction. When managers ask for evidence that lean works, first and foremost, they are interested in evidence of cost savings. When lean practitioners want to provide evidence of the value of lean, they point to cost savings.
So, Marxists complain that lean is all about cost reduction. Capitalists ask, “So what’s the problem with that?” Wise lean practitioners say: “You’re both wrong. The only goal of lean is to figure out how to provide more value to the customer. Period. Any organization who embarks on a lean effort holding cost reduction as the primary goal is very likely to fail.”
And that “work intensification” thing? Altogether wrong. I tell my clients that, when lean has been applied and is working the way it should, the workplace is much calmer and relaxed. “Work intensification” doesn’t sound like “calm and relaxed” at all, does it? But most hard-right capitalists, though they might choose different words (like, “work more efficiently”) probably don’t have a problem with a vision of their workers scurrying about the plant floor looking busy as all heck, right?
There is no work intensification in lean. There is no “scurrying” or “working more efficiently” in lean. There is only calm as the flow of work becomes more and more consistent and predictable.
Here’s another line from the article: “[Lean] encourages workers to compete against one another…” Utterly false. But capitalists, too, believe that “a bit of friendly competition” is good for the organization. How else to explain “Employee of the Month” awards given to just twelve employees each year? Lean seeks to remove competition and replace it with collaboration and coordination.
In the same sentence the author claims that lean “increases [workers’] dependence on employers”. Implemented correctly, lean increases the autonomy of workers. Again, though, most managers going into lean aren’t thinking about how to increase worker autonomy. They believe that doing so would reduce their own control and authority. They like the “tools” part of the “tools and results” lean message because it suggests that lean is all about getting workers to change their behaviors while leaders get to continue behaving the way they always have. For those managers, it’s not about “worker autonomy”, which would mean that workers are making decisions and solving problems that currently are the domain of managers. It’s about finally getting those darned workers to do what they should have been doing all along.
All to say, that too many capitalists and at least one Marxist don’t actually have much of a clue as to what lean really is.
I’ve all but given up on LinkedIn. A platform that was meant to be a place for managers to network and share ideas has become a warren of congratulatory notes and advertisements. Every so often I run into an interesting discussion like this one about Value Stream Mapping.
Here’s the question that kicks all the back-and-forth off: “Have the TPS Senseis ever done a VSM during a kaizen workshop?” (Talk about your string of lean jargon!
As you read the responses to the original post, you’ll see that bashing VSM’s appears to be a favorite pastime of some lean practitioners: “VSMs are imbecilic.”
A number of others are more charitable.
Like most lean tools, VSM’s are useful…and they can be overdone. Some of the commenters pointed to the many symbols and the rote manner in which VSM’s are developed. Others mention the number of dusty VSM’s adorning the walls of organizations they’ve known. (I’ve seen that myself. I pointed to one such example on the wall of a meeting room at a prospective client. When I said, “I see you’ve done a Value Stream Map,” to the general manager, he replied, “Is that what that is? A consultant we had a couple of years ago put that together. We kind of forgot it was there.”) But those aren’t deficits of the tool itself, they are deficits of the manner in which they’re developed and used (or not used).
First, I’ve never done a kaizen workshop. So I’ve never done a VSM (Value!” Stream Map) as part of one. But I have worked on any number of VSM’s with client teams. I like them. I find that most clients don’t actually know how material and information flow through their organizations, so the development of a map often turns on a lot of “eureka!” and idea bulbs. This is especially true of non-manufacturing processes.
I find that drawing a process map with simple boxes and arrows as a team is describing the flow of work, information, and materials serves as a good “note taking” method. Additionally, a process map is a picture, a map of information and material flow. People like using pictures and maps to understand complex things.
Best of all, getting people together to develop and discuss and Value Stream Map actually changes the culture of an organization. It’s a collaborative process. It’s a sharing process. It’s a creative process. It’s a process that creates empathy and understanding of others in the organization.
So, if you’re one of those folks who don’t seem to like VSM’s much…maybe you’re not developing or using them correctly.
Actually, it never was.I had an interesting experience recently that involved the manner in which lean has been defined, described, taught, and talked about for these past 30 years or so. I was asked to take part in something of a discussion group that would toss around ideas as to how lean and the way it’s presented to managers could be “re-imagined”. I was very much up for the project. During our first virtual get-together, we divided into four topic groups: Messaging, Deployment, Site Visits (I never quite understood that one) and…something else that escapes me at the moment. I chose the Messaging group; in fact, I volunteered to lead it, which meant taking responsibility for pulling my team members together virtually on a regular basis to discuss how messaging about lean principles and methods has or has not been effective. I was looking forward to getting the chance to exchange thoughts with other practitioners.
Let me take a step back to go over my own view of “lean messaging” as it’s been practiced for the past few decades: with a few exceptions, it sucks. The literature on lean (for the most part, IMHO) is boring, jejune, pedantic, and largely free of merit. (I’ve expressed my views in several of my Industry Week articles, which I’ll link to below.) There are, of course, no small number of speakers, teachers, and practitioners who are worth listening to. But too much of what we all hear and read speaks to lean tactics and tools with promises of “greater efficiency” and “reduced wastes (i.e. “costs”). As a result, managers hire people like to help “their people” implement a “set of tools” and expect “cost savings”. And they fail. Over and over again.
I used to work for a guy that got impatient with me whenever I spoke about the organization’s culture and how it supports or hinders lean.
“Managers don’t want to hear about ‘culture’,” he’d tell me.
“Correction,” I’d reply, “Managers who are dumb shits don’t want to hear about culture.”
He was right, of course. Too many managers want to know how much sin they can commit and still get to heaven. That is, they’ve heard things that lead them to believe that lean provides a straightforward path to productivity and all that’s needed is a “sensei” and a few “kaizen blitzes”.
All to say, I was eager to find out if my own cynical view of the “lean message” was mine alone or if others felt the same way.
It turned out that others felt the same way. I was, frankly, kind of shocked at the extent to which the few of us that met with some regularity seemed to be on the same page with respect to the inadequacy of lean messaging. We were all of a mind that:
So far, so good, right? We have a small group of practitioners who are on the same page with respect to the problem at hand. We can turn our focus to how to change the messaging! Well, I guess the folks who pulled us all together in the first place got wind of our anarchical discussions and showed up at our last meeting. It was soon clear that their interest wasn’t so much in the development of “different and effective messaging” as it was in the development of “attractive messaging”. My colleagues allowed as how “attractive messaging” was directly responsible for most lean failures. The next thing you know I’m practically shouting at the folks who had pulled us together, team members are leaving the meeting rapidly and suddenly, and the whole effort comes to a crashing halt.
I’m going to try to stay in touch with my fellow team members…we had gotten some good discussions going. I’m unhappy that things have ended this way. Oh, well. Maybe they, like my old boss, have a point…calling managers who don’t want to talk about their organization’s culture “dumb shits” might not be the best approach. I guess I just can’t help myself.
Some time ago, I was having a discussion with an operator about workplace organization. During our conversation, the operator pointed to a fixture that was stored on the floor under a piece of equipment. He told me that the fixture was heavy but there was no other place to store it. The circumstance was an ergonomic injury waiting to happen.
The solution was actually pretty easy: buy a small lift table to keep the fixture on.
Read any text about lean and you’ll get to the chapters about takt time, kanban, poke yoke, maybe even heijunka. You won’t often find the chapter that tells you to make certain that all tooling and fixtures are easy to get to, easy to maneuver, easy to put away. But until you listen to your operators and help them eliminate or, at least, reduce the frustrations they deal with every day, they aren’t going to be interested in anything else you say about lean.
Ron Jacques and I have made a pretty good writing team over the past year or so. Ron has a long and varied career in manufacturing. The guy has a million stories! (He’s also, if his stories are any evidence, a damn good manager of manufacturing operations.) Our workflow has been that he gives me the stories and I turn them into articles; we’re the Lennon and McCartney of lean writing!
Our recent article provides a twist on the rightfully honored idea of “going to the gemba”. The lesson is…use all of your senses!
We’re pretty sure you’ll enjoy this one.
We’re pretty sure that you’ll enjoy the others we’ve written over the past several months that I haven’t posted here on the blog. I’ll provide links to those articles, one at a time so that I don’t overwhelm you, over the next few months.
I think that I’ve mentioned that I teach in the B-school at nearby Kent State University. In the course catalogue, the course is referred to as “Individual and Group Behavior in Organizations”. I call it “Organizational Behavior” (and so does the rest of the world.) During the first class of each semester, I tell my students, “The world is full of dumbass managers…I don’t want you to be one of them.”
OK, so I posted that in a comment on LinkedIn recently…and got some pushback:
In 23 years of full-time teaching, I never described managers using an ad hominem attack. I simply ask my students to lead in ways that better than how they have been led.
So…am I wrong to make a generalization about “dumbass managers”?
In part…yes, of course, I’m wrong. As the old saying goes, “No generalization is worth a damn, including this one.”
My larger point is that too many managers are not up to the job. We can argue whether my language is appropriate or not, but to focus on that is to miss the point. Evidence supports the argument that the “Great Resignation” is caused primarily by toxic corporate cultures. Such cultures aren’t “accidents” or “acts of God”. They are created by managers who are ignorant, careless, negligent, and/or just don’t give a damn. As a former colleague of mine once said, “A fish stinks from the head”. If the place smells rotten, look to leadership for the source of the stink.
And here’s the thing…creating a strong, positive culture isn’t that difficult. It’s not brain surgery, at least. Don’t get me wrong….it takes patience, perseverance, and discipline. But there’s no “secret sauce” to it that some organizations have figured out. It may not be easy, but it IS straightforward.
Here’s the second thing…there is a wealth of data that confirms that a strong, positive culture provides superior performance just about any way you want to measure it. Stock price, revenues, margin, customer satisfaction…they’re all directly correlated to culture. When the culture gets better, so do those measures.
So…creating a strong, positive culture is straightforward and it provides measurable benefits. And yet weak, toxic cultures seem to be widespread, if not prevalent. There must be a lot of dumbass managers out there.
First, everything I’ve read about blogging says that bloggers aren’t to point out (apologize for) long periods between blog posts. “Just start posting again and forgo the mea culpas,” the experts tell me. But….two years between posts? Who does that?
I was recently reading some typically boring article on lean that, like so many others, harped on the importance of takt time. Now, I’m not one to deride the idea of takt time, especially given that many others seem to find it useful. (Or I guess they do….else why does it continue to show up in the literature so often?) It’s just that pretty much everything I’ve ever read provides the same tired definition without really explaining what it means.
Here’s an example of that tired definition (I picked this one pretty much at random…I just web searched on “takt time definition and went to the first one I saw):
“Takt time is the rate at which you need to complete a product to meet customer demand. For example, if you receive a new product order every 4 hours, your team needs to finish a product in 4 hours or less to meet demand.”
First, who gets a “new product order” every four hours? (Given that the first sentence refers to “customer demand”, I assume the author is speaking of new product orders from customers, not production work releases.) Second, in what world is a manufacturer in a position to start on an order that has just been received immediately after the previous one is finished? Mind you, I’m not saying the definition is totally bogus, I’m just saying that it’s confusing.
Here’s the definition in Wikipedia:
“Takt time is a manufacturing term to describe the required product assembly duration that is needed to match the demand. For example, if the customer demand is 10 units per week, then, given a 40-hour workweek and steady flow through the production line, the average duration between production starts should be 4 hours, ideally.”
Once again, we’re left to figure out what to do if we don’t get new product orders every four hours. Or what to do if customer orders come in willy-nilly in a wide variety of quantities and characteristics.
Some books and articles provide a formula for takt time as if customer demand were constant across time and not something that changed moment by moment.
Once again, I’m not saying that the definition is wrong, I’m just saying that it’s not very helpful. No client I’ve ever worked for has the steady, predictable flow of customer orders that takt time definitions always seem to refer to.
We’d be better off if practitioners were more forthcoming about the underlying purpose of takt time (assuming that they actually know it): smooth, predictable flow of material through the manufacturing process. It wouldn’t be difficult to get workers to brainstorm, for example, those things that prevent smooth flow: downtime, scrap, errors, problems with material, tooling, machinery, and so on. It would be easier (and better) to get operators talking about how to reduce or eliminate those things than it would be to try to teach takt time. So let’s do that.
I’m surprised at myself that I’ve never written about Little’s Law. It’s one of those things we lean geeks love to trot out to show that…we’re lean geeks.
This article gives a quick background of Little’s Law. As the article says, Little’s Law (and equation) has been translated to the manufacturing setting thus:
Work In Process (WIP) = Throughput X Cycle Time