This explanation of better understanding why it is important to try to hit the target and to better understand that the trend is very important.

I like the idea of looking at the percentage of on target as a new wy of looking at the quality of a product. Less variation is what should be the aim.

A good way to explain the differences between QC and QA, including how they work and their pit falls.

A great way to get started and understand how a different perspective can create a better experience for the customer.

It makes sense that monitoring the output has limited value - in our company's case it is also not feasible for many of our highest volumes part to be reworked.

The time component of analysis is very important in better understanding the situation.

I appreciate that the color coding of the bands helps to tell a better story of what is occurring and to drive the behavior we want to see.

Good video on why just studying numbers every day and not seeing the big picture can cause bad decisions to be made.

Interesting information about QA and QC. It’s a good place to reflect on the current state of or business and places that we could improve our own quality systems

this video shows and explains in detail how important run charts and histograms can be.

These high and low data points are good indicators when slight changes need to be made to try and stay within the limits.

this video shows how important it is to be using charts, and how they can help out with managing.

To avoid defects, there should definitely be QC checks within the process. Avoiding rework and scrap should always be a top priority for an organization. Ultimately, the goal should be to fix the root causes if possible.

Greate visualization as to why histograms do not tell the whole story. I understand the purpose of a run chart more than I did in the past.

This is why is really important to have charts.

In-line or intermediate inspections are critical so that defects can be caught early on in the process. However, that is not sufficient. When defects are discovered, there should be an analysis performed to identify the root cause(s) of the defect. Once the root causes(s) is(are) discovered, preventative measures and corrective actions should be put in place to minimize the likelihood of those root causes triggering those defects again in the future.

It's clear that hitting a target with minimal variation is the modern standard for high quality. We need to be able to determine the trend of results so that we can anticipate future results with better accuracy.

Consistent to a target, not a range, reinforced the reason to focus on the process, not just the product or result.

Histograms are not free of biases and often lead to wrong conclusions about data. Thanks for explaining the differences between control and run charts.

Great explanation on the use of control charts to monitor progress and keep on target.

Find the root cause and minimize the QA & QC reactionary activities. Thanks for clarifying the QA & QC differences.

Well explain Francisco. It is a great way to approach defects in such a proactive way.

I like this, a lot to learn on this video for zero defects.

Having to catch a bad product right before it is to be shipped to the customer is expensive and can result a late shipment of parts. Fixing defects right at the source is the most efficient way to go.

I like the thinking of being on target rather than just having zero defects. It is less costly and risky.

This video was helpful in describing both QC and QA. I’m very familiar with both of them. But I found it interesting to learn that both of them are problematic because they focus on the product already made or the service already delivered. But I do agree that seeking to build quality in every step of the production process would be a great way to go.

I would have never thought that looking at quality as good or bad would ignore the fact that things tend to get worse overtime. To go beyond zero defects by setting a target and continually aiming for it with minimal variation is something we all should adapt.

I had not considered QC and QA as separate entities. While the additional inspections between operations do help catch the defects prior to additional value being added to the parts, it does not address that quality needs to be built into the process. It is still treating quality as a separate process and demonstrates why we need to be using dmaic tools to reveal the root cause of problems so they can be addressed.

I appreciate this topic. i had not realized that data would/could be manipulated (by opening open tolerances) to reflect 0 defects. This hides that there is too much variance until people become complacent enough that the data eventually outgrows the opened tolerances as well. This video highlights the importance of setting a target, not a range.

Nice video explaining QC and QA! I do feel that having an intermediate inspection is crucial to saving time and labor in the long run! Even though it takes time but will save scrap cost and wasted labor!

I like the phrase of looking at quality as “good or bad” ignores trends! I hear the phrase as in is in a lot and we don’t look past that! But we can actually look into it to what can make this more consistent each time we see this problem!

Good representation to show how fast managers overreact to numbers! But having this chart gives them the visibility needed on how good or bad the process is being done!

Good explanation between the 2 types of charts! Run chart is definitely a better view of the layout of the numbers where histogram is just a summary or the values!

We look at a lot of data every day. I always find when there is a dashboard for that data, it has so much more meaning and clarity.

I knew there was going to be more than just the histogram, but I like how this is done in way to show the evolution of the analysis and the why.

A good look into how a company needs to be realistic about their numbers and step back to see the bigger picture.

I now understand the difference between both QC and QA. Both are problematic and costly; we need to focus on the product that has already been made the 1st time. We should look to build quality in every step of the process to prevent many reworks, should be fixed at the root cause from the beginning.

while QC and QA can be effective it would be more beneficial to catch the quality defect as early as possible hopefully even in the production process

Very detailed explanation of zero defects and how it is the first step of quality to lowering cost and risk. Specs are derived from listening to the customers concerns to achieve balance and satisfaction.

its an interesting way to look at it as trying to hit a target as often as possible instead of just being in a range

A good description of how fixing the problem doesn't end with the outliers, but continuous improvements and effort put into the process.

I like how this explains QC and QA and then says this is not how we should be doing things. There is a better way. I think many people and companies still follow the QC and QA methods. Going to watch the next video.

This is very relevant to a discussion we just had and it helps to provide a better way of looking at the issue we are trying to resolve. Let's look at how we do it right versus just not doing wrong.

good example of how sometimes numbers and stats are not always as they seem unless used properly

nice explanation of run chart vs histogram and the benfits and use for both

QC and QA have been the assumed means of ensuring defect-free products for most people. This is a nice detailed explanation of why a better approach is needed. However, aren't the QC and QA methods the means by which many educational classes are run? We only find out that Johnny wasn't understanding algebra or history when he failed the tests and quizzes.

Living by an acceptable range of deviation without constant monitoring can easily lead to going out-of-spec and not having the ability to recover in time. (Similar to driving very close to either stripe defining a traffic lane. Any unexpected obstruction may force us out of our lane and into danger.) Better is to monitor deviation from a target in order to stay close to it. Then unexpected events may not necessarily push us out of the acceptable or safe zone.

I am starting to see how this data will be used in a control chart. You need the run chart to track the stability/instability of your process to start.

I appreciate the use of the control chart. I would like more detail on how to filter out the noise from normal variations that are reflected in the data. It sounds like the control limits should reflect a certain tolerance for variation. But how do you account for this tolerance if the target is given to you rather than a target based on historical data? Can you annotate the occurrences in the chart somehow?

This video in my opinion is a good example of how easy it can be for managers to over-react when looking at the numbers regarding operational expenses. As was pointed out in this video, it’s the control charts that truly show the behaviors of an operation, because it’s the control chart that filters out the noise so that action can be taken upon real signals.