Wednesday, December 12, 2012

Online statistics training from Minitab has great animation and examples

Minitab statistical software is one of the most powerful and popular programs around, especially for those in the Six Sigma realm.

They recently released a suite of online training courses called Minitab Quality Trainer.



The training is very good, much better than what can be done by an instructor in a classroom. That is because the words have been streamlined, and the animation enhances the concepts being discussed. Online training can reduce the training time by 50% or more compared to traditional classroom training. Minitab has a lot of experience teaching these concepts, so it's no surprise. You can view a sample of Quality Trainer on their website.


There are nine chapters, covering the following topics:


Chapter 1: Descriptive Statistics and Graphical Analysis (60 mins)
Chapter 2: Statistical Inference (60 mins)
Chapter 3: Hypothesis Tests and Confidence Intervals (180 mins)
Chapter 4: Control Charts (75 mins)
Chapter 5: Process Capability (100 mins)
Chapter 6: Analysis of Variance (ANOVA) (60 mins)
Chapter 7: Correlation and Regression (60 mins)
Chapter 8: Measurement Systems Analysis (150 mins)
Chapter 9: Design of Experiments (120 mins)



One of the issues with their training is that there aren't any estimated times for each chapter. We like to solve problems, so we took the time to breakdown the chapters and sections, to give you and your employees a better idea how to schedule and plan for the training courses (see above). Completing all nine chapters takes about 15 hours, with some chapters as short as 50 minutes, while others are as long as 3 hours. For a detailed breakdown of each chapter section, download the estimated times here (.XLSX file).

The cost is also very reasonable. For an individual, they can have access to the training for only $30 per month (or $300 per year). If you have a network version of Minitab at your company, you can also add unlimited access to Quality Trainer for only a couple hundred dollars per licensed user.



To learn more about Minitab Quality Trainer, visit their website at http://www.minitab.com/en-US/products/quality-trainer/default.aspx

Friday, November 30, 2012

Free Green and Black Belt training?

BMGi is one of the largest process improvement consulting companies around. I've had some friends attend training from them, and they have had positive comments about them.

Due to their size and reputation, I was a little surprised when they opened up a large amount of their online Lean and Six Sigma training for free.

At first I thought it would be some teaser videos on basic concepts only, and you had to pay for the really good stuff, like SPC, Design of Experiments, and DFSS. However, they have an entire Green Belt and Black Belt program you can take. Did I mention it was free?

We obviously can't compete with that option, so instead we decided to make it easier to figure out which exact modules you should take.

Six Sigma certification is highly sought-after, yet very expensive to obtain. You can either attend a one or two week long course, or you can self-study for hours and hours, in order to pass the certification exam.


ASQ offers a Green Belt and Black Belt certification, if you meet the experience and project requirements.  Since ASQ has one of the more popular certification programs around, we decided to align the Green Belt body of knowledge to the BMGi online modules, so you can learn a majority of the content on the Green Belt exam for free, without taking every single module.

Here is the Green Belt Body of Knowledge, along with the links to BMGi's free online training on that topic.

http://www.biz-pi.com/certification.asp?id=10

To learn more about Green and Black Belt certification, visit our website at http://www.biz-pi.com/certification.asp and answer the questions, to determine if you are ready for the certification or not.

You might be wondering, "what's in it for us"? Why would we promote another company's training material instead of our own?

Learning about a topic is just the first step. After a class, you still need to translate the learning into something personal, that applies to the work you do today. That is where we come in. We can help translate the tools and help explain how they fit into your job or company. When you try and apply the training to your work and get stuck, we can help you out, and get you moving in the right direction. That is the value we can bring with our experience, which is more important than providing education and teaching.

It is much more rewarding for us to help you address a specific problem, than stand up in front of a room and talk about concepts and ideas that may not translate into something useful to you. Don't get us wrong. Training is very important, but it's what happens after the training where the real value and learning comes to fruition, and that's where we want to be involved to help you out.

View the list of content you'll need to know to get your Green Belt certification: http://www.biz-pi.com/certification.asp

If you want help studying for the ASQ exam, check out our helpful guide: 8 steps for passing the ASQ Six Sigma Green Belt or Black Belt exam

Wednesday, November 28, 2012

How many of the 50 Best Practices for Process Excellence has your company implemented?

Lee Pollock and Mark Kiemele are authors of a new book, Reversing the Culture of Waste – 50 Best Practices to Achieve Process Excellence. The book provides a list of best practices that companies use to become stronger in process improvement. Not every company excels at all 50, but the companies that apply most of the suggestions are much further ahead. You can even assess your company, to see how mature your process improvement approach is today.




The book is divided into 10 chapters, and each chapter identifies a few best practices. Where you see the term "process excellence" you can replace it with your company's initiative (Lean, Lean Six Sigma, Continuous Improvement, etc). Explanations of each best practice are provided in a concise summary, usually 1-2 pages in length.

Chapter 1 - Executive Ownership and Leadership Alignment
1. Establish ownership at the executive level.
2. Develop and communicate the need, vision and plan.
3. Train leadership first.
4. Link compensation to involvement and success.
5. Continuously assess what is working and what is not and adjust.

Chapter 2 - Effective Support Infrastructure

6. Designate a well-respected Deployment Champion early.
7. Commission and use a guiding coalition.
8. Partner with a capable and reputable service provider.
9. Integrate key stakeholders into the plan.
10. Create position descriptions that mandate a pull for excellence.
11. Quickly attain a critical mass of practitioners.

Chapter 3 - Integration with Existing Business Improvement Initiatives

12. Maximize the synergy of multiple initiatives.

Chapter 4 - The Right Projects and Studies and People to Lead Them

13. Establish criteria for project selection and prioritization.
14. Use quick-hitting studies to accelerate results.
15. Select top-tier candidates for first waves of training.

Chapter 5 - Integrated Training and Software

16. Use motivational and experienced instructors and coaches.
17. Keep the software simple and easy to use.
18. Use a blended approach to learning.

Chapter 6 - Financial and Implementation Responsibility

19. Use a consistent, simple and straightforward approach.
20. Generate successes early and communicate them.
21. Plan the service provider's exit strategy.
22. Develop internal subject matter experts.
23. Manage the expectations of every practitioner.
24. Define and use a meaty certification process.
25. Train all ares of the organization.
26. Apply the training immediately.
27. Provide expert coaching on all projects and studies.
28. Scope projects carefully.
29. Establish and follow rules for assessing benefits.
30. Publicize and use savings wisely.
31. Regularly review projects and act based on the assessment.
32. Conduct refresher sessions for leaders and practitioners.
33. Connect and use Champions to upgrade the initiative.
34. Make everyone aware of what is going on.
35. Design and use standardized templates.
36. Anticipate and manage position loss resulting from projects.
37. Include team-oriented "soft" tools.
38. Develop transfer functions to predict, optimize, and assess risk.
39. Make innovation systematic.
40. Solve new problems using trained resources and trumpet successes.
41. Make process excellence part of the human resource succession plan.
42. Integrate process excellence into all mergers and acquisitions.
43. Update the implementation plan based on feedback and results.

Chapter 7 - Reward and Recognition
44. Recognize people who execute successful projects.

Chapter 8 - Enterprise-Wide Knowledge Sharing

45. Establish a project-tracking database and keep it current.
46. Schedule benchmarking sessions.

Chapter 9 - Customer and Supply Chain Involvement

47. Involve suppliers and customers early on.
48. Implement a fact-based process for assessing the Voice of the Customer.

Chapter 10 - Change Management: Leveraging Cultural Strengths and Managing Its Weaknesses

49. View process excellence as a mindset, not just a toolset.
50. Leverage cultural strengths that promote change.




To assess your company on their maturity in process excellence, determine your ranking from 0-2 for each item.

0 = No implementation of that best practice whatsoever.
1 = Some areas exist where it is done
2 = We do that very well  

You can use decimals (like 0.5 or 1.5), but they suggest using integers only. Next, sum up the total score for each chapter, and enter the results on the Air Academy website: http://www.airacad.com/bestpractices.aspx  

Your total points will give you an idea where you rank against 500+ companies involved in a 2011 study. For example, if you scored a 32 or less, you are in the 10th percentile. If you scored a 48, you are in the 33rd percentile. If you scored a 59, you are the 50th percentile. If you scored an 82, you are in the 90th percentile. There were very few companies scoring above 90 (maximum score is 100 points). Exact percentiles are provided in the book.  

After reviewing your scores, we would recommend determining which best practices could provide your company with the biggest gains, and develop an action plan to address the gaps.  

Leave us a comment if you filled out the assessment, and how your company scored.

Friday, August 17, 2012

Reducing your time might seem like lean, but you can easily anger your customers

Lean is about increasing value to your customer. Often times, this requires you to eliminate waste in the process. However, if you don't understand your customer needs, you might sub-optimize the process in an attempt to make your work easier. However, if you are not careful, you can actually ADD waste to your customers, thus decreasing the value you provide. That is the complete opposite impact you intended, even though you had the right intentions.

Here are some good examples of sub-optimization that you can share in training classes or conversations. I'm sure you have some good examples of your own. Please share them in the comments section below. 

Example #1 - Scrap Report
The Finance department provides a weekly and monthly scrap report to the production managers. The data is in a single spreadsheet file, with filters on the top of key columns (work center and manager). Each manager goes in and searches the report to filter by their name, look at the scrap items, and review them. Some of them create their own pivot table to be able to sort and filter all the data. Each month is separated into unique tabs (pretty common in finance reports), which makes it difficult to look at data over the whole year. The finance person did not want to spend an extra 10 minutes each time creating the pivot table report and combining the new data with the existing data for the entire year in one spreadsheet. However, when we look at the full impact of time for the entire company, each production manager is required to create their own pivot table (5 minutes each), or they spend extra time filtering the data (not as efficient as a pivot table), or they completely ignore the report, since they find it hard to analyze. So the finance person saves themselves ten minutes each week, but this time adds at least an hour to the entire organization, and not everyone is taking action on the data, which is an even bigger waste.


Example #2 - Procedure Updates
Each month, an email is generated from the document control group with a list of procedures that were revised recently. At least 1000 people are sent this list. They were asked to provide a quick summary of the change made in each document, so we could decide if it was something we needed to investigate or read in more detail, or if we could ignore it. He said it would add about an hour's worth of his time to do that, so he refused. However, if we assume that 10% of the distribution is actually interested in these changes, that means at least 100 people are clicking each of the procedures and scanning through to find the revision change summary. If we assume that takes 5 minutes to complete, then 500 minutes (8 hours) have been wasted in the company. So the document control group saved themselves one hour of work, but added 8 hours of work to the company, and many people did not get the updates they needed, which is a huge waste. If they did provide a summary, they might actually increase the number of people on the distribution who learn about the revisions, and therefore proceed to click the links to read the updates.

Example #3 - IT help desk ticket
I needed to have a website updated, so I contacted the information technology (IT) person responsible for the task. I have this task performed a couple times per year, so it is infrequent. The individual said they could take care of it, but I need to submit a ticket for them to work on it. I agreed, and called the help desk line to submit the ticket. After 30 minutes of discussion with the help desk support person, I finally got the ticket submitted. I was very frustrated. The company wasted 30 minutes of my time, and 30 minutes of the help desk's time to get the ticket entered correctly. This was due to the complex nature of the work being done. The person who was going to be doing the work could have probably entered the ticket themselves in about 5 minutes, since they knew exactly what was needed to be done. So they saved themselves five minutes of work, but added one hour of waste to two other individuals.

As you can see, the key message is to understand what things you do that are valuable (value added) to your customer, and what things are not valuable (non-value added). Only eliminate the non-value added, or you could make your customer's upset and frustrated.

Thursday, July 26, 2012

Problem solving is critical for any business

Does your company have a problem solving process, like PDCA or 8-D?

If so, do people use it? How do you know?

Simple, ask for documentation. If an employee or improvement team is really working on a problem, and they aren't writing down or documenting what you're doing, then how well are they following the process? If the process is "in their head" then it's either a really simple problem, or they're probably missing some steps.

Example A3 Report
Here are some simple questions you can ask people in your company, to see if they are following the process and structure, if they can't provide documentation to prove it. 

What is the problem you are trying to solve?


Many teams cannot clearly articulate the problem, so they will struggle solving the problem if it is not well defined. This step can take a long time to complete, depending on the complexity of the problem. Teams often skip through this step quickly, so they can get to root cause right away and have some answers from management. Encourage them to take their time and make sure the problem statement is clear before moving on.

What step of the problem solving process are you in?


This will help you understand whether your employees are following the process or not, and help you understand how far along they are with this problem/issue. If they struggle answering the question, they may not be very knowledgeable about the process, or jumping around steps and working out of order. 

What data did you use to determine the root cause?


This will help you understand how well the root cause was investigated. If little to no data was used, then the solution will have much less chance of being successful, so the odds that they are actually addressing the right cause is slim to none. I find that teams that give up on collecting data and skip ahead to solutions are also less likely to adhere to the problem solving process.

Is your solution addressing the long term?


Many solutions address the immediate need, or contain the problem in the short term only, but they do not complete the entire 8-step process to prevent the problem from recurring. This happens often because after containment is in place, management stops asking about the issue, so the teams get pulled into the next "fire" instead of completing the problem solving process on the issue. This will be evident when you ask about different problems they've worked on, but they can't explain what actions were taken to prevent the problem from coming back. If the problem hasn't recurred, but no improvements were made, then don't be surprised when it does come back as next month's "fire".

There are many other questions you can ask, but these will give you a pretty good indication.

Finally, don't just ask the quality organization about problem solving around product failures. These departments may have contractual reasons to follow the process, as it probably gets submitted to the customer. Instead, talk to your HR department, your shipping department, Invoicing department, and even your Lean/Six Sigma organization (yes, we don't even follow our own recommendations all the time for our own issues). Problem solving is a company-wide process that everyone should be using on their top problems.

Tuesday, July 24, 2012

We don't need any help, we are already lean!

"Lean and Six Sigma are only for manufacturing organizations!"
"Our processes/company is unique, so that won't work here!"
"We're already lean because we're working so hard and so many hours!'

What "lean" looks like to people who don't get it yet.

Have you heard these comments before? That's the first sign of a company in desperate need of process improvement. 

I'll admit, there is some difficulty in getting people in a transactional or office environment to embrace lean and six sigma concepts. The biggest issue is that they can't SEE their workflow, so they cannot easily translate a manufacturing example (often used in training materials) to their own jobs.

I'll also admit, I can lean out anyone else's process, but when I decided I needed to lean out my own work, I ran into some difficulties.

After some serious evaluation of what I actually do (when not training or consulting, those are easy), I realized that I provide "items" to my customers. Items could be book summaries, templates, training material, procedures, guidelines, reference material, examples, recommendations, graphics, just to name a few. My clients take these items, and turn them into action, which should result in an increase in value or reduction in waste or reduction in life cycle costs to their business. Therefore, I indirectly help my clients improve their processes, or directly help them (when they get stuck).

I figured out I used a very simple process to convert a request from a client into an "item".

1. Obtain needs from clients
2. Gain approval to proceed (based on cost and time frame)
3. Create draft of item
4. Review draft with colleagues/experts
5. Make revisions
6. Review revision with broader audience and client
7. Make 2nd revision
8. Release item to client
9. Follow-up with client to determine usage
10. Review success and modify process

For example, one client asked for a summary powerpoint document of basic lean tools, that they could give to their employees, to let them read through prior to a lean event. We had some of it created already, but not in one single presentation, so it needed some work.

Here is what I did:

Step 1. Discussed how many slides, what kind of detail they wanted, which tools and concepts to include, how to navigate between slides, etc.
Step 2. I came back with how long it would take, and how much it would cost. We agreed to proceed after some discussion. I also provided some sample slides, and a basic framework for the presentation.
Step 3. I created a rough draft of the training. It's easy to get 80% done, then want to start something new (get sick of working on the same thing), but this is where you need to step it up to reach 100% completion.
Step 4. I next sent it to my consultant friends and former co-workers for feedback. Some provided better slides, challenged the intent of the presentation, and gave me some ideas on what to improve.
Step 5. I made most of the revisions, and ignored those that were minor, but would add significant time.
Step 6. I next sent it out to the client and some non-expert friends, to see if they could follow along with the presentation. They would better represent my target audience.
Step 7. After getting some of their feedback, I made some final changes.
Step 8. I sent the final "item" to the client for approval, and an invoice was provided.
Step 9. After the training, I asked for feedback on how it was received, and what additional changes to make.
Step 10. If I got hung up in the process, or missed a requirement, or the item didn't get used very much, I determined what I should do better next time.

Bottom line, until you actually reach step 8 above (release product to client), you have not provided any value to your clients. You don't get "credit" or get paid until you deliver. This is my "production", which connects me back to the training material that was too "manufacturing" focused before. If you can show this connection to clients, you'll see their eyes widen, and they will start thinking of all kinds of ways to apply lean to their processes.

What I want my office to look like...
Now, in order to apply lean to this particular process, I need to gather data on the following:

1) How long does it take from step 2 to step 8 (cycle time)?
2) How many items do I complete per month (output/deliveries)?
3) How well did the item get received or used (quality)? If it was good training, I would expect it to be reused over and over again. If they never touched it again, maybe it was considered low quality. Did I have to revise the item after releasing to the client? On a 1-10 scale, how happy was the client with the item?
4) Did I complete the item when they wanted it (on-time delivery)?

Once I have this data, then I can start to apply lean and six sigma concepts to the process. Create a whiteboard and display these metrics near your desk. Include a status board for the items you are currently working on, along with a visual of which step in the process each item is located. 

When reviewing the data, if it took longer than I planned, I need to look at my other activities, to see how they impacted it. The more items I'm working on at once (work in process), the longer it will take me to deliver to my client. This has really kept me focused on working on one or two items at a time (single piece flow). I like to jump around and "multitask" but I know that slows down my process, and it takes me longer to pick up where I left off. Once I start step 2, I need to stay committed to reaching step 8, so I can minimize the time between customer request to delivery to customer without any errors. This is the heart of lean.

Quality can be a little difficult to measure in the office. I mentioned some approaches above. When I go to step 9, and look at how often my items are being used, I feel this is a true measure of how good the item is. If I send out a well-written book review, but no one reads it, then did I actually provide value that the client could take and convert into improvements to their business? If not, then I didn't succeed in my task. If I create a template, and it gets sent around the company, and 50+ employees use the template, then I feel like that item was higher quality than the book review.

In summary, making the connection between lean and the office environment can be difficult and you should expect to get push back when discussing it. However, you can practice learning how to apply lean to the office by reviewing this article, and looking at the work you currently do today. It will be easier to convince others how lean directly relates to them when you can give specific examples on how you apply it to your own work. What has worked well for you when dealing with office processes?