Airplane Oxygen Masks and Lean Leadership Responsibility

We’ve all heard the flight attendant’s compulsory safety announcement regarding oxygen masks. Personally, I’ve grown pretty numb to the whole safety monologue.

Not a good thing.

During a relatively recent trip on a Southwest flight there was a refreshing twist to the typically sober announcement.

It went something like this, “In the event of a sudden loss in cabin pressure, oxygen masks will descend from the ceiling. Stop screaming, grab the mask, and pull it over your face. If you have a small child traveling with you, secure your mask before assisting with theirs. If you are traveling with two small children, decide now which one you love more.”

Pretty funny.

But, the truth is there’s a reason that the parent (or guardian) should don the mask first and THEN attend to his or her charge(s). The parent needs to maintain his mental and physical faculties so that he can effectively take care of others. This is not self-serving.

So, this leads (surprise, surprise!) to a lean metaphor.

Lean leaders need to put on the oxygen mask first.

The “oxygen” here is lean competency.

Jeffrey Liker and Gary Convis in their book, The Toyota Way to Lean Leadership: Achieving and Sustaining Excellence through Leadership Development, which I highly recommend, captures this notion well.

Their Toyota Way Leadership Model reflects the following. Please note the ORDER.

  1. Commit to Self-Development. Learn to live True North values through repeated learning cycles,
  2. Coach and Develop Others. See and challenge true potential in others through self-development learning cycles,
  3. Support Daily Kaizen. Build local capability throughout for daily management, and
  4. Create Vision and Align Goals. Create True North vision and align goals vertically and horizontally.

Leaders can’t teach what they do not have. So, they must first put on the oxygen mask of understanding (or at least genuinely commit to and begin to walk the road to understanding) before they can effectively and credibly BEGIN to coach and develop others.

With that, good luck deciding which colleague you first assist with that oxygen mask thing.

Related posts: Book Review: Leading the Lean Enterprise Transformation, Why Do You Ask?, 12 Narrow Lean Gates

Share

Tags:

Visual Controls, Spider-Man, and Do Hotel Chains Really Care About Saving the Planet?

In many ways, visual controls are a 24/7 mirror of leadership’s competency and credibility.

That’s pretty scary if you think about it.

It’s like voluntarily living in a fishbowl. Not that everyone truly understands the gravity of that.

It reminds me of the Spider-Man quote (allegedly borrowed from Voltaire or someone before him), “With great power comes great responsibility.”

So, with the application of visual controls comes great responsibility.

Effective visuals are a universal, self-explaining, unapologetic proclamation to anyone within eyesight and possession of some basic (lean) thinking, that this here, taken together as a system, is our current process health and level of process adherence and sufficiency. This is the established standard, providing insight into one or more of the what, why, where, when (timing, sequence, conditions), how much, how long, who, with whom, targets, and trends. It necessarily highlights the abnormal condition(s)…and prompts correction.

Of course, a lack of competency is belied by visual controls that are tool-driven. We’ve all seen the hodge-podge of stuff  - disconnected visuals that are not part of a system and not applied within the context of a lean management system.

Silly “eye candy.”

Or the visual that is not, as it’s supposed to be, worker-managed…and thus is not maintained, or not maintained consistently, or not maintained properly…and leadership doesn’t seem to care.

So, no one cares.

It may be because the visual control is not sufficient. Or it’s an adherence issue. Or both.  Or perhaps, when problems are identified, no one knows what to do next.

Problem-solving, anyone?

Either way, it turns out to be a leadership competency AND credibility thing.

Naked, for the world to see.

And, the world judges.

The world, whether it’s customers, community, associates, managers, or executives eventually come to a conclusion that lean doesn’t work, the company doesn’t care, leadership doesn’t know what they heck they’re doing, the folks don’t have any discipline, etc.

This leads me to the hotel towel thing.

I’m sure most folks who have stayed in a hotel have seen the rather ubiquitous sign or placard that says something about saving the planet. The verbiage, however clunky, seeks to appeal to our sense of social (and environmental) justice.

Yes, washing towels needlessly is MUDA!

So, I always hang them up after each use.

And, about 80% of the time, housekeeping takes the towel away (and presumably washes it)!

So, I judge the hotel and its leadership. They don’t care about saving the planet!

Make me cynical.

Not a very lean feeling.

Related posts: Effective Visual Controls Are Self-Explaining, Visual of the Visual?, Ineffective Visual Controls – 9 Root Causes

Share

Tags: ,

Lean and Free Will

To borrow a phrase that was borrowed by Pope Benedict XVI for his (in)famous 2006 Regensburg lecture, “There is no compulsion in lean.”

OK, the pontiff didn’t really use the word “lean” (rather it was “religion”), but the underlying sentiment is much the same.

How so?

Well, you can’t FORCE someone to embrace lean with both heart and mind.

In the end, it must be an intrinsic thing. Organizations achieve and sustain transformative levels when folks “get it,” and “live it.” Meaning, when BOTH their intellect and will are engaged.

The foundational principles of lean are humility and respect for the individual. As such, we must respect each and every person’s free will while doing our level best to teach them.

Free will is pretty much a blind faculty. It’s got to be directed by the brain.

Of course, you can force someone to DO lean things – follow standard work, participate in kaizen activities, respond to abnormal conditions, etc.

However, this is purely extrinsic in nature and therefore is not transformative…at least initially. (I guess the spouses in a number of arranged marriages end up falling in love.)

Compelling people to do things that they otherwise might not want to do is often required in life (hey, son/daughter feed the dog, take out the trash…), including business.

Especially in business.

When a company seriously undertakes a lean transformation, there are certain expectations around adherence and behavior. If employees do not meet the expectations, they must be coached by technically competent believers. Sometimes, eventually, they must leave the organization, voluntarily or involuntarily.

In a derivative of Pascal’s wager…you can act yourself into a new way of being. Through acting lean, meaning engaging in lean actions, folks can start to get it.

The risk obviously, is that these “practitioners” end up just practicing the tools and maybe the systems. That can often be superficial, without real, lasting buy-in.

Understanding and embracing lean principles (the “why”) takes reflection, and deep, consistent coaching.

Presuming that folks have some insight into the technical side (the “how”), and have the ecosystem for improvement (like a robust lean management system and good lean leadership behaviors), the litmus test for whether an organization is bridging the lean compulsion realm to the lean transformation realm is DAILY kaizen.

Yes, management driven kaizen typically manifests itself in kaizen events as pulled by value stream improvement plans and the like. This is system driven kaizen. Not a bad place at all.

But, it’s nearly impossible to fake daily kaizen.

How can you fake voluntary kaizen in the form of (implemented) employee suggestions, kaizen circle activities, and the buzz of countermeasure discussions during daily reflection meetings?!?

My answer is, you can’t.

This extract of the Shingo Prize Model Guidelines, specifically the Examples of Ideal Behaviors for Continuous Process Improvement, drives it home:

  • “Every associate in every part of the organization is engaged every day in
    using the appropriate tools of continuous improvement to eliminate waste and
    maximize value creation.
  • Associates everywhere seek to understand the principles (the why) behind the
    tools (the how); they learn and use that knowledge to continuously improve the
    application of the tools.
  • All associates demonstrate the courage and integrity to tell the truth,
    stop production, and be accountable for defects they observe or create
    themselves.
  • Associates share their expertise in developing best practice standard work and
    demonstrate the discipline to follow it until a better way has been developed.”

So, in the end, there is no true compulsion in lean.

Which is another reason why lean transformations are so darned hard to pull off and why it’s so special when they do happen.

Related posts: The Intrinsic Discipline of the Lean Leader, 12 Narrow Lean Gates, Guest Post: “Magical Thinking”

Share

Tags:

Kaizen: From System to Principle-Driven [Lean Thinker Webinar Series]

Last month, I teamed up with Gemba Academy’s Ron Pereira and presented a two-part webinar on the subject of kaizen. Both sessions were recorded and are right here for your viewing.

The description of the webinar went something like this:

Many folks share an anti-kaizen event sentiment. Daily kaizen is the only way to go, right?

The truth is most successful lean organizations jump-started their transformation through the effective application of kaizen events…and then they transitioned to a sustainable kaizen culture by balancing daily kaizen and events.

Join Mark Hamel, author of the Shingo Award-winning book, Kaizen Event Fieldbook, and Gemba Tales blogger, for some insight on how to do both well.

While I have a face for radio and a voice for silent movies, I think there’s some value-added stuff in these webinars. Of course, the fact that the recordings, accessible now only to Gemba Academy subscribers of their Complete Lean Package, are free to you should lessen the pain.

Speaking of Gemba Academy, I cannot say enough about their lean training offerings – including the scope, content, value, and state of the art HD video delivery method! Please check them out.

I hope you enjoy the webinars.

Related post: How to Avoid Kaizen Event Malpractice [Webinar]

Share

Tags: ,

Why Do You Ask?

This question is typically posed in response to a question that is deemed a bit nosey. It’s actually more of a statement. Along the lines of, “Mind you own business!”

But, for the purpose of this post, it really is a question – one of, and for, the lean leader’s self-reflection.

What truly is the purpose of the questions that we ask? Granted that we must always consider the particular situation, the intent of our questions says a lot about our own lean leadership effectiveness.

click to enlarge

Do we ask questions targeted primarily to extract information from others so that WE can solve the problem for them (maybe despite them)?

Or, do we ask questions to develop the critical thinking of others so that they can develop their own problem-solving muscle and so that they can learn how to mentor others in a similar way?

In short, the role of the lean leader is to teach and learn. NOT to fix.

I know, I know, this is crazy talk.

…Especially when we have historically and routinely been rewarded for being someone who quickly fixes problems single-handedly. All hail the superhero!

What the heck is it with Toyota and that notion of building people before cars?!? Looks like we’ll need a double-dose of patience, humility, and help in questioning strategies and techniques.

So, when is the “extraction method” OK? I’m guessing there are a couple acceptable scenarios where leader as fixer is appropriate (see below). However, the rest of the time, it should be leader as teacher.

  • Life or death situations, and/or when time is really short. The mentor asking the mentee, “What do you think we should do to disarm this soon to detonate explosive device?” probably isn’t going to work out too well.
  • Subject matter expert dealing with a non-expert in an area where deep mentorship is not pragmatic or important. For example, it’s OK for the doctor to ask closed or leading questions after the initial open-ended question of “How do you feel?” The doctor is trying to quickly discern the situation and help the patient heal. The doctor/patient relationship is usually not about the physician teaching the patient to self-diagnose and treat.

In order to develop problem-solvers, we need to help our mentees identify and acknowledge the problem and ultimately, solve the problem. This requires the mentee to think, to engage, and to take ownership.  The extract and tell method that is often employed by leaders doesn’t do any of that well.

click to enlarge

What kind of questions help folks to identify and acknowledge problems?

  • What did you observe?
  • What is/was supposed to happen?
  • What is actually happening/happened?
  • How do you feel about that?

In order to provide good coaching, the lean leader needs to understand how the mentee is thinking, why they’re thinking it, and what they know/think they know and don’t know. Some simple, open-ended questions:

  • What are you thinking?
  • Why do you think that?
  • What makes you say that?
  • How do you know?

Finally, the mentor must help the learner through the PDCA process without doing the telling and without taking ownership themselves. This includes prompting the mentee to identify and articulate the problem to be solved, discover the root causes, formulate potential countermeasures, converge on and experiment with the countermeasure(s), reflect (a.k.a. check) and adjust. Here are some example questions (in addition to the relevant ones listed above):

  • When/where is the problem happening?
  • When/where is the problem not happening?
  • What do you think is causing the problem?
  • How do you know those are the causes?
  • How can you address those causes?
  • Did the countermeasures work as planned?
  • How do you know the countermeasures were effective?
  • What’s your plan?

One thing that I’m sure you have noted is that the example questions are all open-ended in nature. That’s because closed questions (typically limiting a person to a yes or no answer) and leading questions (i.e., “When are going to get the police report?” versus “What further information do you need to close this claim?”) do little to foster critical thinking and ownership.

Open-ended questions also demonstrate the leader’s respect for the mentee’s ability to think. That’s important.

So, ask away with good intent…and listen.

Related posts: Lean Listening, 12 Narrow Lean Gates, 6 Leadership Habits for Effective Tiered Meetings

Share

Tags:

Point of Use Storage and Looking Upstream

During my recent travels, I came upon a somewhat bizarre sight. There was a paper towel dispenser mounted on a stairwell wall!?!

Actually, there were at least two in the stairwell.

Being a (hopefully) typically curious lean thinker, I had to ask one of the managers within the office complex about the origin and purpose of the dispensers.

It seems that some time ago, a manager, who is no longer with the company, had them installed. The said manager would regularly ascend and descend the stairs while holding a cup of coffee.

Actually, the stairwell is next to the complex’ basement level cafeteria, so I’m guessing we’re talking mostly about ascending… with a full cup.

In any event, occasionally, the manager would spill his coffee in the stairwell. Not a safe or clean situation.

A spill in the stairwell requires a means to clean up the stairwell. It’s easier to take care of a spill with a paper towel. So, obviously, we need some point of use paper towels. Right?

I don’t know about you, but I’m thinking a coffee cup lid might have been a more effective countermeasure.

Why not keep the coffee from spilling in the first place?

One lesson. Lean thinkers should, by habit, look upstream of the value stream (in this case the procuring, transporting, and drinking coffee value stream) when assessing improvement opportunities. It’s generally more effective to address problems/potential problems before they happen than after. Or at least when the problems are smaller, easier, and cheaper to deal with.

As for the point of use paper towel dispensers, curiously, there were no point of use trash cans. Nothing like carrying your hot, wet paper towels with you and your partially filled coffee cup up the stairwell…

But, I’m guessing the dispensers get very little use, anyway. Most folks use lids.

Related posts: Lean Space – Some Thoughts and 10 Questions, Point of Use Storage – Sometimes It’s REALLY Important!

Share

Tags: ,

All I Really Need to Know about Lean I Learned at Waffle House [guest post]

Ok, so the title is a little overreaching, but so was, “All I really need to know about life I learned in kindergarten,” and that didn’t stop that email from being forwarded a few million times.

My learning experience began at about 4 a.m., while sitting at a Waffle House counter with my buddy. He was dozing in his seat.

No, we weren’t up early because we couldn’t wait to start the day’s kaizen. It was the weekend and we were at the end of our evening…but, I digress.

Sitting at the counter, I was unusually alert for the hour. My intensity came from a focus on getting some food into me.

The Waffle House had its usual pre-dawn crowd and the staff was seating tables as fast as they could clear the debris from the previous customers.

No sooner than I had given my order to the waitress, I heard her call it out to a cook who seemed to continuously throw food on the grill. He was in constant motion, never slowing down to ask for an order to be repeated.

I further noticed that the wait staff never gave the cook any written record of the order. Diners all have tickets on spinning wheels, right?! At least that’s the way they’re portrayed on TV.

And the cook never wrote anything down. Heck, he didn’t have any available time for writing.

“Oh great,” I thought, “I’m going to get something other than my precise culinary selection.”

Well, to my surprise, my plate showed up exactly as requested!

So, as I inhaled my meal, I watched the cook prepare 25-30 plates without once stopping to ask about an order. It was at this point that I began to seriously question whether or not I possessed the mental capacity necessary to be a successful Waffle House cook.

This sobering and burning question bothered me throughout the day. Now, no offense to Waffle House cooks, they’ve been very good to me over the years, but their pay grade doesn’t seem to square with super memory and perception powers…

Fast forward to the next week.  Still doubting that I would ever have the right stuff to be a Waffle House cook, I returned to the Waffle House to do what my sensei had taught me first – direct observation.

My direct observation was both fruitful and easy. Seems that the Waffle House employs quite a bit of standard work. It turned out, like with all good magic tricks, I had been fooled by watching all the motion (the cook) instead of what the assistant was doing. I found that the shukimi goes something like this:

  1. There are 3 operators working together – waitress, prep station operator, and cook.
  2. Upon taking an order, the waitress walks to a prescribed spot (there’s an X on the floor for good visual control) and calls the order out in a specific manner. This keeps multiple orders from being called at the same time and in fact is the single point for scheduling.
  3. Orders are called out one seat at a time regardless of the number of people at the table – single piece flow with 100% MTO as their finished goods strategy.
  4. As the waitress calls the orders, the cook grabs his tools (which are stored point of use with some good 5S) and pulls materials from his kanban (which has been stored with minimal packaging).
  5. While the cook is focused on getting the cooking started, it’s the prep station that is in fact capturing the details of the order. Here are some examples:
    1. One plate representing each order is queued up in order of receipt – FIFO
    2. “Kit” items are placed on the plate to indicate the specific details of the order. A jelly packet right side up means one type of toast while upside down means another.
    3. A single butter pack indicates one waffle, while two means two waffles.
    4. A single hash brown is laid on the plate in an orientation that indicates well done, smothered with onions, or some variety of ingredients.
    5. A slice of cheese on one side of the plate means hash browns scattered and covered. If the cheese has a different plate position, it calls for scrambled eggs with cheese.
    6. Plates are lined up on the buckboard until full. A full buckboard tells the waitress to stop calling orders for a few minutes and also tells the manager they may need a 2nd cook – a brilliantly simple application of visual management.
    7. The cook matches up the food on the grill with the order as defined by the visual on the plate. This drives standard presentation to the customer. Once completed, the cook signals for a pick-up. The waitress doesn’t need to ask which plates are complete as she can identify at a quick glance.

The Waffle House system is impressive in its simplicity and effectiveness. As for the writing-free environment, the cook can scan the plate line from a distance and understand requirements much more quickly that reading a written ticket. Bottom line, the Waffle House’s system eliminates a great deal of waste while expertly delivering on service level expectations.

While I am not likely to switch careers (though I am relieved that, if needed, I might be able to cut it as a cook), I do believe that there is an opportunity for Waffle House-like visual scheduling in many industries.

Just imagine if your operation’s make-to-order demand requirements could be flawlessly communicated throughout the value stream using only those items that are contained within the finished goods…like a home fry.

John Domagala authored this guest post. He has spent the last 25 working in manufacturing, most recently in the electronics industry. Trained as a Master Black Belt by GE and exposed to the Toyota Production System 8 years ago by Mr. Nakao, much of John’s focus is facilitating lean transformations.

Another related breakfast food post: Beyond Toast Kaizen – Lean Breakfast Concepts, Circa 1937 [guest post],

Share

Tags:

Tiered Meeting = Team Stand-up A3

For some time, I have searched for a metaphor to convey the meaning and delivery of a tiered meeting (a.k.a. huddle, reflection meeting, sunrise meeting, etc.).

I think that I’ve settled upon a decent (sort of) metaphor – “team stand-up A3.”

The simple explanation is that tiered meetings, a critical element of an effective lean management system, are: 1) team-based, 2) conducted in the standing position (to discourage long-winded discourse), and 3) is largely about practicing PDCA (A3 thinking).

The team stand-up A3’s agenda approximates the following. The underlined words represent traditional A3 section titles.

  • Team leader shares the meeting theme (what the team is about to talk about) and provides some background (why they’re talking about it)
  • Team leader facilitates team exploration of the current conditions and target conditions (as represented by the performance metrics on the team’s board, leader standard work insight, etc.) and identification and acknowledgement of the problem(s) (the gap between current and target)
  • Team leader facilitates team problem analysis to identify root causes
  • Team converges on countermeasures (who, what, when) or a plan to do/continue problem-solving at another time after the meeting
  • Team leader facilitates follow-up on prior action items
  • Team leader facilitates “round robin” to seek out any open issues, suggestion, and/or questions
  • Team leader verifies take-aways and closes the meeting

Related posts: How to Audit a Lean Management System, Animated Cartoon: “What’s the Problem?”, 6 Leadership Habits for Effective Tiered Meetings

Share

Tags: ,

Simplistic Ain’t Lean

Leonardo da Vinci’s quote, “Simplicity is the ultimate sophistication,” could easily serve as a lean tagline.

Surely, lean tools, like standard work, visual controls, and mistake proofing devices, are only truly effective if they are easily explained, understood, deployed, maintained, and adjusted. Heck, lean principles are simple too, just hard to implement.

This whole simplicity stuff is consistent with the Shigeo Shingo-identified first objective of continuous improvement – easier (followed immediately by better, faster, and cheaper).

But, some folks in their rush to keep things simple, careen into “simplism.”

Simplism, defined by thefreedictionary.com, is, “[t]he tendency to oversimplify an issue or a problem by ignoring complexities or complications.”

I think a lot of simplism is driven by a type of unthinking lean just-do-it machismo, detachment from the gemba, and/or ignorance of lean principles, systems, and tools.

Simplism begets simplistic directives. Like, within the next quarter, team leaders need to facilitate problem-solving like their counterparts at Toyota.

Except, there just might be some “complications” that need to be addressed first, such as the fact that Toyota team leader span of controls is in the 5-8 associate range, and our team leaders have 15 to 20 associates… not to mention the profound training and mentorship that is required to develop effective team leaders.

Simplism begets simplistic countermeasures.

Countermeasures must address root causes – real root causes. And, the countermeasures must work in the real world.

For example, when a given process is irreducibly complex (for now), the standard work might have to be more than 1 page.

The simplistic practitioner (and I have encountered such folks) might maintain that standard work can’t be more than a page. “It’s too hard for my (well-educated) folks to absorb…”

Simplism shouldn’t be allowed to trump lean principles.

If the one page standard work is insufficient, then the steps, sequence, cycle times, standard WIP, etc. may not be appropriately defined. What then? Is it OK for the operators to improvise?

Ignoring complexity and complications. It’s just magical, non-lean thinking.

Lean leaders can’t be simplistic.

Related posts: Guest Post: “Magical Thinking”, Working Smarter, or Just Harder? Thoughts on Standard Work., Kaizen Principle: Bias for Action

Share

Tags:

Tattoos, Lean, and Regrets

A friend and colleague provided me with this tattoo parlor photo. He was passing by and just couldn’t resist the irony of it all.

The lack of permanence around the sign construction makes the whole thing even more entertaining.

My friend and I share the same passion for lean as well as an often bizarre brand of humor. He thought the photo was blog worthy, although he wasn’t quite sure of the exact subject.

Well, I’m not one to waste a good picture.

______________________________________

Lean, by it’s very nature, is not permanent. Certainly, if a transformation is not progressing, then it’s not transforming.

If it’s stagnant, it is decaying.

But, I digress.

I’m no expert on tattoos. In fact, I don’t have any.  Although, there were several “near misses” in my younger days.

Other than the stick on variety or henna types, there is very little PDCA around them. Sure there is “plan”, which sometimes doesn’t get the proper rigor before it quickly turns into “do.” Note that tattoo plan and do is best done without the assistance of alcohol and peer pressure.

The “check” part, other than the review of the stencil before the needle, seems to happen largely after the artwork is complete. By then, “act” or “adjust” options are pretty limited.

Lean is a lot more forgiving. Real PDCA, especially within the proper culture, is freeing. Renewable in may ways.

But, as I think through my modest career thus far, I have to ask myself whether I have any lean regrets.

Unlike in the song My Way, my regrets are not too few to mention. So, here are some of my own, along with regrets that I think others should have (based upon my observations over the years).

  • Bending or compromising on one or more lean principles
  • Being too rigid on a lean tool and missing the point (a.k.a. the principle)
  • Not using open-ended questions enough
  • Making technical changes without corresponding management system changes (i.e., leader standard work)…and seeing improvement gains evaporate over time
  • Getting into useless arguments about whether folks need to adhere to standard work. Sure we need to understand the why, but following standard work is a condition of employment. End of story. Improve it if the standard work is not sufficient.
  • Assuming (a.k.a. not validating) that folks understand key lean concepts
  • Not aligning leadership at the very beginning of the lean transformation
  • Not acting quickly enough to remove the saboteurs (after a genuine effort to convert them)
  • Forgetting that people development is as important as business results
  • Giving someone a fish because it’s more expedient than teaching them how to fish
  • Basing leadership assignments more on technical skills than core competencies/behavioral skills
  • Not fixing (or at least containing) problems immediately
  • Prematurely moving from pilot to full scale deployment
  • Ruminating about stuff while sitting in a conference room rather than going to the gemba and personally conducting direct observations
  • Short-cutting problem-solving

The list could go on and on and on.

Of course, unlike in a tattoo scenario, we can reflect and adjust. We can turn our regrets, assuming that we can grasp the root cause(s) and apply effective countermeasures, into strengths.

And, in a form of yokoten, we can share our hard-earned learnings, so that others may better avoid some of our mistakes.

What “lean regrets” do you have?

Related posts: Want a Kaizen Culture? Take Your Vitamin C!, Lean Listening, 12 Narrow Lean Gates

Share

Tags: ,