Archive

Archive for July, 2010

A Great Example of a Lean Program that Works

July 30th, 2010 No comments

Recently, I received a link from a friend about an article in the Denver Post. I found it interesting that Lean, something in which our organization believes, is being applied to solve a range of problems throughout differing industries. The applicability is endless. And, the results are profound. This just goes to show why there is such a resurgence in basic quality and process tools like Lean, and how simple, easy-to-learn skills can make a huge impact, even in organizations where change can be tough.  Let me know if you’d like more articles like this.

Categories: Lean process Tags:

Business Process Management (BPM) – Process Stability as a Prerequisite to Process Improvement

July 29th, 2010 No comments

After a long business cycle that saw the creation and expansion of performance improvement programs, we have undergone tremendous change that has forced every initiative at every company to re-evaluate its goals and validate its existence.  At some companies, continuous improvement has been repatriated to operations.  At others, it has mistakenly been eliminated and will undoubtedly have to reconstitute at a later date. And for a lucky few, economic changes are providing an opportunity to start for the first time or reorient their efforts to contribute to a new set of challenges. 

Those that seek to prosper in the new normal get excited by the prospect of implementing or applying a responsive system that offers such promise. It is a pretty appealing prospect and there are a number of books that paint this picture as attainable using a variety of methodologies (i.e. Lean, Six Sigma, etc).  The challenge is that with all the turmoil of the last several years few have the infrastructure needed to really identify or sustain high value improvements, and this presents a major dilemma.  

So, how can you overcome this dilemma? If you want to implement any improvement methodologies effectively, there are some pre-requisites must exist, possibly even before you attempt your first improvement project.  You can’t put an improvement in place if staff doesn’t follow standard work in a disciplined way – improvements rely on control to actualize the planned benefit.

The very arguments that support the exciting prospects of improvement methodologies often neglect to mention these issues, perhaps because they assume that the desire to improve makes you “ready”.   But sometimes that’s not the case and you must build a foundation before you try to put up the building.  The term that’s normally used for being “ready” is Basic Stability. It means that you can pretty much rely on your people and equipment to do what they are supposed to do, and you have a way (i.e. metrics) to verify.  Basic Stability usually involves establishing (or re-establishing) standard work processes and key process metrics.  Everything need not be perfect, but operations should repeat in a consistent manner or any change will soon be lost and thus the effort will prove to have been worthless.  

A good Business Process Management (BPM) program establishes the cornerstones of repeatability and thus Basic Stability.  Along with establishing alignment and cross-functional thinking, it  identifies and characterizes processes, identifies data sources, identifies key metrics, and provides for process analysis and control.  If this is in place, soon enough you will get to the place from which you can make those improvements and have them stick.  

And, the good news is that establishing a foundation Business Process Management (BPM) does not have to be overly expensive or resource-consuming.  See more about our BPM approach with our complimentary power point download or contact me directly if you want to discuss.

What Can Yellow Belts Do … Really?

July 22nd, 2010 No comments

Yellow Belt TrainingAs a followup to my recent post titled Trained Yellow Belts Think Differently, I thought I would spend a little time talking about what yellow belts can actually DO.

In a traditional six sigma deployment, yellow belts play a critical role in supporting higher level black belt and green belt projects.  They are trained in the foundation of the DMAIC problem solving process and can speak the language of Six Sigma.  They can handle some of the lower level tasks of process mapping, data collection, setting up measurement systems, establishing and maintaining control systems , and may actually be subject matter experts. Basically, they allow the black belts and green belts to focus on the more complex analytical aspects of the project.  If yellow belts are used effectively, they can improve the productivity of black belts and green belts in a BIG way.

BUT, what can they do outside of supporting higher level belts?   What if you don’t even have higher level belts?  What can a yellow belt trained employee do for the organization? 

Six Sigma purists might argue that Yellow Belts should not be trained, without Black Belts and Green Belts, and that their role is to support higher level belts.  I don’t agree with this at all.   Again, I have to hedge by saying that I’m talking about the level of capability that yellow belts trained by SSQ have (i.e. 4-5 days of training).   So, what can Mr. Yellow Belt do?

  • Characterize Processes.  Process mapping and characterization is a skill that should not be taken lightly.  All too often,  improvements are made to processes when we don’t know how the current process really operates, the current state.  These so-called improvements, in many cases, add unnecessary complexity and create more problems than they fixed.  We call this tampering and it is a sure-fire recipe for disaster.  A great example of where process characterization is an invaluable skill is with large-scale enterprise software implementations.   It seems common sense that we should understand exactly how a process works before we try to systemize/automate with software, right?  How often is there really a focused effort to characterize and optimize processes?   I would argue not enough of the time and this is readily apparent in the big $’s spent on configuration, customization, tweaks, etc.
  • Establish/validate measurement systems. Yellow belts learn the basics of Six Sigma and its focus on using data to understand problems and get to the root cause.  The learn the basics of what makes a good measurement system, and what does not.    The can certainly help establish measurement and data collection systems that are actionable, and validate (or invalidate) existing ones.
  • Establish Process Control Systems.  This is a key yellow belt skillset and its importance should not be overlooked.  Yellow belts learn how to set up process control systems to assure that processes function as expected by the customer.  Spec limits are establish, as are response plans when an indicator goes out of control 
  • Execute small scale improvement projects in their own areas.   Will they have the deep statistical analysis skills that well-trained green belts or black belts have?  No, they will not.  But they will have a solid problem solving foundation around DMAIC and they will have a working knowledge of the basic tools in D-M-A-I-C.  They know what a well scoped project looks like, they know the basic measure and analyze graphical tools, they know how to use a structured approach to select improvements, and they definitely know about process control systems.   Let’s not lose site of the fact that these basic tools will likely be sufficient to address a significant portion of the process problems you’ll face.  

Some may think of Yellow Belts as team members, data collectors, or assistants to Black Belts.  I strongly question this view and think, in reality, a Yellow Belt’s role should be much deeper than that.  Yellow Belts practice a Process Management approach (control and manage processes using metrics and data) and can solve real business problems using basic, but proven, quality tools and a systematic approach.  

Yellow belt skills are valuable at any level of the organization, from managers to the lowest level process operators, and the processes they improve are usually the ones they work in day in and day out.  Many years back the term daily process management was in vogue.  The term has certainly faded a bit, but it’s hard to argue against the value of actively managing and improving processes on a daily basis.

Contact me if you’d like to talk about how yellow belts might be able to help your organization.  And, if you haven’t already, download our yellow belt training manual to see for yourself the rich skillset a yellow belt acquires.

The Case for Business Process Management

July 16th, 2010 No comments

Companies often deny they have a process or admit they don’t follow the processes they’ve developed.   In today’s economic environment, many attribute this behavior to a lack of resources.  Oddly enough, this behavior and explanation often comes from professionals that know the cost of not establishing or following processes.  Leaders have created a seemingly endless list of reasons for dismantling process efforts and eliminating process improvement projects.  Let’s examine those reasons and how to respond to them:

Reason No. 1: “I can’t do just a couple of processes. I’ve got to improve them all, and I’ll never get that done.“

Response: Concentrate first and foremost on the processes that touch the customer.

Reason No. 2: “Process improvement takes too long. “

Response: Not every process requires the same level of resources or attention to build, design or repair.  And not every process carries the same importance.  Also, most processes can be fixed or redesigned in weeks, and some should be finished in days.  Pick the ones that provide the most juice for the squeeze.  Get them 80 percent right and get it done. Resort and prioritize frequently.  You eat an elephant a bite at a time.

Reason No. 3: “All processes require a blank-sheet approach to redesign. “

Response: Not true. Some portion of the process can always be salvaged and reused in the new version.

Reason No. 4: “Modeling my process is complicated and it won’t get me anywhere. “

Response: Software is available to perform modeling and save hours of frustrations. It runs the process in the confines of the computer before it’s unleashed on the organization.

Reason No. 5: “We don’t need to spend time understanding the current process. I already know what the new process needs to look like. “

Response: Take the time to understand the current environment. This is by far the best technique for ensuring a smooth transition to the future.

Reason No. 6: “We’ve already improved our processes. “

Response: Process improvement is never done.  It is constantly on-going as people, technologies, customer requirements and competitor offerings change.

The point of this discussion is that if your company has responded to profit pressures by dismantling its process management and improvement efforts in favor of simply responding to immediate needs, you must revive mission before the undeniable problems come home to roost.  In restarting, reviving or keeping such efforts alive, adjust to the realities of our new economic environment.  Reduce what is being done to the available resources and focus on the customer.  Then continue to make the business case and document the ROI\ which reminding what has happened in the past when these efforts have been abandoned.  The case is as strong now for process improvement as its ever been.

If you would like to see how SSQ recommends its clients hone in on what is important and ensures a high ROI on the efforts, either download our slide presentation on BPM or contact me.

Trained Yellow Belts Think Differently

July 15th, 2010 No comments

We’ve been offering a complimentary download of our Yellow Belt training manuals on our website for a couple of weeks and the response has been extremely positive.   Of course, some people just want to download something that is free.  However, the majority of people are genuinely interested in Six Sigma and process improvement in general, and are looking for ways to bring some foundation capability into their organizations.  From the conversations I have, it is clear that the need for basic process improvement hasn’t gone away, but the way companies are willing to build the capability has certainly changed.  I did a recent post that talks about how companies are moving back to the basics when it comes to CI, basics that are inexpensive and deliver results to a broad base of the organization.

Now, many of the people that are downloading have heard the term yellow belt and are curious about what a yellow belt skillset is.  But I’m seeing that a lot of people don’t have a good feel for exactly what a yellow belt does and how it can benefit the organization.  So, I’m going to provide some thoughts here and on some subsequent posts. 

As a disclaimer, there is really no standard out there for what a yellow belt knows.  I’m talking about our (Qualtec’s) definition of a yellow belt skillset.  For us, yellow belt training is usually delivered as 4-5 days of training.

Yellow Belts really should think and act differently after training so, let’s first talk about what yellow belts should be thinking about after training:

  • Analyzing real data to drive business decisions, analyzing root cause to drive implementation of the right solutions, and understanding that CI (Lean, Six Sigma, BPM, etc) is all about improving business performance in terms of voice of the customer.
  • Identifying and tracking the right metrics (primary, secondary, etc), really understanding process capability and process performance.
  • How to practically get and use data and a scientific approach to solve a problem?
  • Understanding what a problem is really costing the business, the real cost-of-poor-quality (COPQ)
  • Putting in the proper process control mechanisms to sustain improvements over time
  • The project selection and prioritization process of the company to assure that the right things are being targeted, things that will make an impact.

The Yellow Belt skillset is a foundation set of quality improvement and process control tools.  It is something that can be applied anywhere in the organization and on any process to yield wide-ranging improvements.  It is one approach, and an effective one for many, to building a solid foundation for CI in their organization.

Contact me if you want more info or would like to discuss in more detail ….

Pull Learning in Business Process and Performance Improvement

July 15th, 2010 No comments

These days with such lean workforces, it’s very difficult if not impossible to take workers off the floor, but we clearly need to continue to develop skills and knowledge, and put that into action as it is needed.  We often talk about Action Learning as learning on the job; now it can really focus on Action.  People should be able to use decision tables to identify the right tools for a problem and then learn how to use them now, when they really need them.  Having that with available on-demand expert support can be an exceptional solution. Think about allowing people to quickly and easily find and view sample projects attacking similar issues.  Think of this new generation as one of Pull-Learning …. learning something exactly when and how it is needed.

Every once in a while I watch the U-tube video “Did you Know“.  The Millennials use technology differently from us.   If they need to learn to do something they are going to U-Tube to find a video; they are googling; they are on Facebook asking friends.

Professionals are getting more and more socially connected too,  through LinkedIn for example. No more borrowing the tool from the guy down the street or chatting over the garden fence.  Think about this in conjunction with turnover statistics and predicted future turnover.  There will be no Old Sarah with 30 years experience in that industry to share knowledge. Almost all knowledge will be new in the sense that it will be continually learned.  How exciting for an expert training organization.  I think training organiztions that understand and embrace the new world we live in can become indispensable to a learning organization. 

If you’d like to talk about these ideas, contact me.

On Demand Performance Improvement

July 6th, 2010 No comments

A new reality of today’s workplace is how stretched we are as a workforce. Reported productivity increases have posted consecutive gains few thought could be attained. Weekly hours worked are at just about the same level as when the economic expansion was at its peak. While the slack in the broad economy has never been greater, workers are stretched.

At the same time, for reasons I wrote about in my June 23rd post entitled Why VOC and Customer Experience are Front & Center?, the goods and services we buy and what we require is changing. Reacquiring customer requirements and redesigning goods and services, as well as the processes that deliver those goods and services takes people and work. So as productivity skyrockets, the demands on the workforce rise just as fast.

To give these people the skills and support while recognizing the demands on their time, the transfer of knowledge must become more efficient. Content must be modular and interchangeable based on the needs of individuals. Instruction must include both the benefits of human interaction and asynchronous delivery. Support must be on-demand and micro-targeted to specific learning challenges. And it must all be at a cost that fits today’s demands for value.

Years ago this list of requirements would have been unthinkable as functionality and cost pulled in opposite directions. But today, technology, a tremendous stored warehouse of intellectual property and new working relationships make these things attainable. A massive library of content across the spectrum of subjects throughout the economy, blogs, podcasts, collaboration tools and a highly skilled and flexible base of experienced people allow us to structure On Demand Performance Improvement at an investment level company’s can’t afford not make.

Give your people the new skills and support they need to meet the escalating demands on their time. The returns are there as the projects have breakthrough opportunity and the investment is affordable. Break the paradigm with which you’ve been training and supporting your people. Use the wave of technologies, content and people available. The time is now. 

Contact us to discuss how you might implement an on demand  model for business performance and process improvement.

How Important is Benchmarking for your Process Improvement Efforts?

July 2nd, 2010 1 comment

As my focus is on process improvement, I often get into dialogues about benchmarking and the importance of it.  Wikipedia describes benchmarking as the process of comparing one’s business processes and performance metrics to industry bests and/or best practices from other industries. Dimensions typically measured are quality, time, and cost.   Just how important are benchmarks to the success of business and process improvement efforts?

Let me pose another question … which is more important: 1)  to meet your customers needs and expectations now or 2)  to look in the rear view mirror and find out how well you stacked up against the competition? I am obviously biased to #1.  Don’t get me wrong, I understand that some companies require benchmarking to justify the investment in a process improvement, but I submit that, if you look closely, you might find that those organizations aren’t as customer-centric as they need to be.

For me, customer feedback (VOC) is more important and, in many cases, it’s far easier to get good data from customer than it is to get good benchmark data. When customers give you consistent feedback over time to tell you that a process does or does not measure-up, that should be all the proof that is needed.

I’m interested in your thoughts. Have you been successful driving a large-scale complex improvement project without benchmarks? Have you used benchmarks successfully to get sponsorship and funding? Have you been able to use the customer voice solely as your rationale for improving?