Dream Big, Act Small

by Jamie Flinchbaugh on March 10, 2010 · 1 comment

Yesterday I was working with a team who was working on a very long-term kind of change. They were really stuck, spending a lot of time trying to figure out how to achieve the end state. That is a mistake. Abraham Lincoln said:

“The best thing about the future is that it comes only one day at a time.”

Don’t try to create the entire future in one step. Know where you’re headed. Dream big. But act in one step at a time toward your dream. Take your first step. You don’t even have to know what the next step will be. But don’t let that stand in the way of taking your first step.

Dream Big. Act Small.

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

{ 1 comment }

Creating Employee Engagement, Part 4

by Jamie Flinchbaugh on March 8, 2010 · 1 comment

IMG00003-20090817-1020.jpg

This is the final part of a 4 part series on Creating Employee Engagement. You can first read Parts 1, 2, and 3.

Skills Required for Engagement

Skill gaps to create engagement exist both in employees and managers, although most transformation efforts tend to focus on only one or the other group.

Employees need to be able to able to identify problems. Have you ever walked into a team and asked “what problems do you have?” and received the answer “no problems.” Well, gee, I’ve been here 5 minutes and spotted 3, how do you have no problems? Not only do them need to be able to spot problems and opportunities, but do so consistently with other teammates.

Team members must be able to engage in brainstorming, experimentation, and communication to be able to develop, share, and decide on solutions to problems. The ability to work with your teammates in a productive way to determine solutions is more than just having the opportunity to contribute. Skills make this succeed or fail.

To be able to support others in idea development and execution, you must be willing and able to:

  • Listen
  • Give feedback
  • Share a common language of processes and ideas

To be able to contribute your own ideas, an individual must be able to:

  • Identify waste and opportunity in their work
  • Be able to study and find causes of problems and gaps
  • Able to develop solutions that are creative and affordable
  • Communicate ideas to others

Engagement is one of the major differentiators for companies in the years to come. Organizations shouldn’t be working on it to win some “best places to work” awards. They should work on developing engagement because the ideas of many can outrun the ideas of a few, and your organization can use every advantage it can find.

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

{ 1 comment }

Creating Employee Engagement, Part 3

by Jamie Flinchbaugh on March 5, 2010 · 3 comments

IMG00009-20090826-1118.jpg

This is part 3 on employee engagement. Read Part 1 and Part 2.

The Development of Systems to Support Engagement

When conducting an assessment, one of the most revealing questions that I seem to ask is “if you have found waste or an opportunity to improve, what do you do with it?” I usually get answers ranging from “I don’t know” to “I wait for the next kaizen event.” Organizations will often want people engaged and even teach them some skills to get them engaged, but fall short of creating a mechanism that actually enables this. Instead, we become dependent on the sheer willpower of the individual to decide to overcome momentum and make a change. This is a big chance to take.

Systems and processes must be build that support engagement. This includes problem solving to new idea engagement. There is certainly no one best mechanism.

When developing systems, consider two important criteria in the design. First, consider the natural flow of work. You want people to be able to leverage whatever systems you design while they are doing the work. If they have to disengage with the work to engage in some other system, it is not going to be very supportive of their needs. Second, consider how you can enable decision making at the point of activity within the systems. This might be decision guides, criteria, standard work, or simple empowerment. Anything that requires permission or interruption in order to complete a task is disempowering and disengages the employees.

Systems can include problem solving or help chain systems, suggestion or idea systems, or even processes such as scoreboards and team huddles. I wrote about help chain systems in a Leading Lean column Forging Your Help Chain, and shared the mistakes of many suggestion systems in another Leading Lean column Make Suggestions Productive. The second column demonstrates a common mistake when designing any such system: don’t build a new disconnected system from the work. It must be embedded in the work. It must be physically where the work is done, available when the work is done, work within the flow of daily work, and leverage the infrastructure that already exists.

What systems do you have that help build engagement? What has worked for you?

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

{ 3 comments }

Creating Employee Engagement, Part 2

by Jamie Flinchbaugh on March 3, 2010 · 1 comment

This is Part 2, you can read Part 1 on Creating Employee Engagement.

The Role of Culture in Engagement

Culture is the set of shared assumptions, beliefs, and principles that a group or organization holds. It is best measured or observed by the shared behaviors or habits that are exhibited.

A certain set of beliefs and behaviors need to be developed to support engagement. The most important people to exhibit these behaviors are front-line managers. They are in the best position to create the culture, and the easiest to destroy it, simply based on the frequency and consistency of engagement. Front-line managers are often ignored or at least under-invested in during a lean transformation.

The beliefs that support engagement can be stated many ways, but are centered around two fundamental principles. One is that everyone can make a contribution, and is an expert at something. Two is that given the opportunity, most people want to make a positive contribution. These are foregone conclusions that all people share these beliefs. There are others that can also be enablers to success. What do you consider them to be?

But the important thing is not that front-line managers, and managers of managers, espouse those beliefs. What’s important is that they practice them through the right behaviors. Behaviors is what people experience and it’s what influences their own behaviors. Secondly, regardless of your role, the only way you can really measure whether your front-line managers believe these fundamental principles is by observing their behaviors.

So what behaviors best demonstrate these beliefs?

  1. How a person reacts when someone makes a mistake is a great indicator. If the first reaction to a mistake is condemnation and chastising, then this is not consistent with a belief that people are intending to do good. If instead a mistake is met with empathy and support to correct the mistake, that is a very different experience to the individual.
  2. An overall approach of inquiry first. Asking questions to draw out people’s knowledge, to learn from them, and even to challenge them demonstrates that you believe that they have the knowledge, they just need to put it to better use.
  3. A leader that believes that people can make a contribution will seek out opportunities to capture that, whether that is participation on kaizen events or the development of best practices. Exhibiting the opposite belief is that any time away from direct labor is inherent waste.

What other behaviors would you like to see?

If you are coaching others, keep in mind that just because someone isn’t exhibiting the right behaviors doesn’t mean that they DON’T carry those beliefs. They may lack the skills to exhibit them, or they may require feedback because they think they are exhibiting them when they are not. Sometimes there is a gap in our own true beliefs and our own behaviors. But in the end, it is the behaviors that make the difference.

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

{ 1 comment }

Creating Employee Engagement, Part 1

by Jamie Flinchbaugh on March 1, 2010 · 0 comments

IMG00008-20090825-0757.jpg

Learning happens in the classroom. Coaching happens through a formal mentor often away from our work. At least that’s what we’ve been lead to believe.  

But that view has many limitations.

As it applies to learning, learning is never internalized in the classroom. There is a difference between information, which is in the head, and knowledge, which is the ability to apply that information. What we ultimately care about is the latter. Except in a few extreme cases such as military simulations and teaching hospitals, application of knowledge is either skipped altogether or is quite contrived and limited.

As it applies to coaching, coaching requires knowledge of the current state, feedback, and active experimentation. None of these can happen effectively or efficiently away from the work. A sports coach requires observing the athlete in action and providing feedback in ways that help expose the gap between what is intended and what is realized.

So the assumptions are flawed. We must discard these ideas that most mechanisms of engagement can be mechanistic, contrived, and event-based. Instead, engagement must be fluid, at the point of activity, and continual. So how do you created that? I propose looking at it from a combination of building the right culture that enables and even values engagement, building the right systems or management infrastructure, and building skills in both employees and managers to make it all work.

In the following posts, I will explore each of these areas.

If you’d like to continue to get this content, sign up for free on the right-hand side of the page with just your email.

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

{ 0 comments }

Take Customer Feedback Seriously

by Jamie Flinchbaugh on February 26, 2010 · 4 comments

Plenty of companies say the focus on the customer. Many of them say they want customer feedback.  customin.tiff

But few post unfiltered, real-time customer feedback on the front-page of their website where everyone can see it, whether good or bad. CustomInk.com can say that. Here’s just the latest feedback as an example. Of course, you see it’s good feedback. But that’s earned, not just selective. If it’s going to end up on your website for all your customers to see, you don’t ignore what’s written. You take it seriously. And you do everything possible to fulfill those customer needs.

I spend a lot of time talking with people how the culture they’re trying to build. But when I ask what you’re doing to create that culture, to demonstrate that culture, to enable that culture, there is little tangible evidence.

Cultures don’t just happen, at least not the ones you want. Andy Carlino and I talked about this in Accidental versus Planned Cultures.

Words are cheap. Demonstrate the values you espouse.

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

{ 4 comments }

You must lack common sense!

by Jamie Flinchbaugh on February 24, 2010 · 16 comments

Kiyoshi Suzaki, a lean thinker who deserves to be at the top of any lean guru list, wrote:

Lean tools are common sense – after the fact.

I think that makes sense based on my observations. People see it, and they want to call lean “common sense”. Some organizations and I believe even books have called it “Common Sense Manufacturing.” Besides the fact, as Suzaki points out, that it’s not really common sense, there is a bigger problem.

By telling everyone that it is common sense, you are sending them the message that:

1. They lack common sense

2. They shouldn’t challenge it, because how can you challenge common sense.

3. Anyone not doing this probably doesn’t deserve to live, let alone going on working here.

Is that respecting people? Even if that doesn’t matter to you, will that be the best message to send if you want their buy in? At best what you will get is quiet compliance.

Taiichi Ohno said something a bit differently:

Common sense is always wrong.

This I believe is a more sensible approach to common sense. We must challenge what we think we know. If everyone is absolutely certain (think world is flat, 9 planets in the solar system examples), then no one is challenging it. And it’s probably wrong.

Don’t let your choice of words get in the way of your choice of purpose and vision.

What is your reaction when you hear “common sense” as a descriptor? What is your reaction?

For books by Suzaki and Ohno, check out these options:


  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

The Impact of Repetition

by Jamie Flinchbaugh on February 22, 2010

We tackle the value of repetition on culture in the latest installment of the Cultural Transformation video series. The example given of a repeated pattern was SQDCM, or Safety Quality Delivery Cost Morale. This pattern was repeated in the organization at every level every day. Now, 15 years later, it has remained an embedded part of the culture. Repetition leads to habits, and habits forms the basis of any culture. Check out the video:

If you have trouble viewing the video, you can view it or download it directly at this link.

How have you used repetition to help drive cultural transformation in your organization?

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

The new Lean Learning Center Video Blog

by Jamie Flinchbaugh on February 21, 2010

LLC_logo.jpgAndy Carlino and I will be publishing occasional video blogs. We’ve done a couple of topics already, which we only posted as links directly to the video. We’ve recently added this video blog page to the Lean Learning Center website.  

If you want to stay tuned to when note posts are released, you can subscribe for free by signing up for Membership here. You also will be notified and able to download the latest issues of Lean Progress , our quarterly newsletter.

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark

Organizational Design and the Role of HR in Lean

by Jamie Flinchbaugh on February 19, 2010 · 9 comments

This originally appeared on the Lean Career Compass blog.

Lean is a human system. And human resources deals with humans, right? So HR should have a pretty active role in lean. In most cases, I see them sitting on the sidelines. This is sad. It’s not that they don’t want to get involved, they don’t know how. There are many levers that HR can pull that can help a lean transformation move forward. Organizational design is one of them.

fy2007afr_lg_state_org_chart.gif

Most of the organizational design that we observe is trying to solve a poorly designed problem statement. For example, these two teams aren’t working well together, so let’s put them together under one roof. That makes sense on the surface, but because it was done based on symptoms instead of understanding a problem, it solves one symptom while creating a new problem.

If a connection is broken, by putting two groups or two people together you can improve the connection (or more accurately overcome it as this is a workaround). But at the same time you pulled one group further away from another connection, often exposing it’s weakness. So now you have a new problem. This is what I call a waste shell game. Watch the shell…it’s moving, it’s moving…where it stops, nobody knows. This is a bad, ad hoc, and reactive way to use organizational design to improve performance.

Point 1: Define the problem statement or operational objective before beginning to design the organization

Instead, you must first understand how you want the process to work. You must have an ideal or effective process by understanding the activities, connections, and flows. Activities, connections, flows – these are the building blocks of your processes. You then build your organizational design around the most efficient ways to make those connections and flows work.

Point 2: Design your organization around the process that you want

For example, at a hotel, one of the most important operating factors is cleaning rooms according to their schedule and on time. On time allows you to plan room availability around checkins, particularly if you have several different room types. Most leaders wanting to improve the flow of room cleaning would just want to consume more resources by adding more to the cleaning crew.

But after prioritizing the flow around stable and predictable outcomes, and understanding the supporting activities and connections within the work such as stocking carts, the design actually took someone out of the cleaning crew. They were made a team leader, although not with any pay difference. They handled many of the connections, such as supplies to carts, but also provided an important connecting in managing a part of the flow, which is an exception. An exception in the process is a room that will take longer to clean than normally required. Instead of just falling behind schedule, when a team member enters the room they ask themselves if they can clean it in the allowed time. If not, they first contact the team leader who comes and helps them clean the room. This room takes two people instead of one, but this was a better response to the exception than pushing the entire process behind schedule.

Point 3: Often the most effective designs are responsive to changes, defects, and problems

This is an example of designing the organizational structure, and the roles and responsibilities, around an understanding of the process, including the exceptions and problems within the process. This is a fundamental and highly value-added role that HR can play in this stage of the process.

What have been your lessons on organizational design in lean? And how can HR help?

  • Twitter
  • LinkedIn
  • Delicious
  • StumbleUpon
  • Google Bookmarks
  • Share/Bookmark