シャドーイング練習: The 7 Quality Control (QC) Tools Explained with an Example! - 動画で英語スピーキングを学ぶ

Hey guys, Andy here with CQE Academy

and in today's video I want to talk about a really important topic which is the seven QC tools.

Now whether you just want to get better at work

and use these tools in your everyday job

or you're preparing for something like the green belt exam or the black belt exam or the CQE exam, today's lecture is for you.

All right, let's hit it with the computer and get started.

All right, let's go ahead and jump in right into the agenda.

So we're going to start with a brief intro of the seven QC tools, kind of talk about all of them and how they fit into the problem solving process or the improvement process.

And then we're going to go through each one.

We're going to start with the flow chart, the check sheet, the Pareto chart, the cause and effect diagram, scatter diagram, histogram, and then the control charts.

And then along the way, as we go through this, we're actually going to work a problem using all seven tools

and we're going to reduce the number of defects associated with our toaster.

All right, let's go and get started.

So the seven QC tools, I love this quote from Keoru Ishikawa who said,

as much as 95% of quality problems can be solved with seven fundamental tools.

And I absolutely agree with that.

I think these tools are probably the seven most powerful tools, whether you're talking about Greenbelt or Blackbelt or quality engineering, it doesn't matter.

These seven tools are incredibly powerful for solving problems and making improvements.

And this is a really important topic.

By the way, as we go through this, I'll make sure to talk about where we're at in something like the plan, do, check, act, or the DMAIC cycle.

We're going to solve a problem with our toaster, and we'll use either the DMAIC or the plan, do, check, act process to do it.

All right, let's get into it.

All right, so the very first tool is the flowchart.

And what a flowchart does is it's a visual tool that helps you depict the flow or the sequence of a process.

This could be things like the flow of information or the flow of tasks or material or people or decisions.

It doesn't matter.

The reason that a flowchart is

so incredibly valuable is it makes a really complex process simple and it promotes a common understanding of a process.

Anytime you get more than one person in a room to talk about a process, there's likely going to be disagreement about how the process works.

And I love using this analogy.

Oftentimes when we sit down to analyze a process, there's what management thinks is happening, There's what the procedure says is happening.

There's what's actually happening on the production floor.

And then there's what could be happening.

And the beauty of a flowchart is it does just that.

It gets everyone on the same page about what's actually happening.

And I love this quote from Dr. Deming who said, if you can't describe what you're doing as a process, you don't know what you're doing.

And the best way to describe what you're doing is to use a flowchart.

And that's why this tool is so powerful.

If you're in the planning phase or the define phase, it's really good to use a flowchart, define your process, and then use that flowchart to plan out your experiment

and plan out how you're going to make an improvement.

So let's do just that.

Let's say we're talking about our toaster and we want to make an improvement, right?

And so the first thing we're going to do is we're going to start with the boundaries.

We want to analyze a process, but we want to start with the boundaries first.

So we're going to go from receiving a work order to completing a work order.

That's the boundaries of our flowchart.

Now, I've got the team here because all of these activities, all of these tools are all team-based.

So imagine you're sitting down with your team

and the first thing you're going to do is brainstorm all of the steps in the process, right?

Talk to the experts.

How does the process work?

Use Post-it notes, right?

Don't try to do this in some software.

Use Post-it notes.

Write down all the activities.

And then once you're done brainstorming, organize those thoughts into that logical flow or that logical sequence of activities for your process.

Now that we have our process here, we're in that planning phase and we wanna create a target, right?

What sort of improvement are we gonna make?

And we wanna reduce defects by 25%.

Now, we can't make an improvement and we can't solve a problem without data.

And we know that most of our defects happen during final testing.

So now we need to collect a little bit of data and this is where the check sheet comes into play.

So the check sheet is a very simple tool for collecting, organizing and analyzing data.

Every problem you solve or every improvement you make should be based on data

and the check sheet is probably the most powerful tool for collecting data.

Now there's something wrong with the check sheet

that I'm showing you here on the screen and that problem is it doesn't have any metadata.

If you're collecting data and you want to make a high quality decision using that data, you also need metadata.

So when you're creating your check sheet, don't forget to include things like who and when and where.

All those key elements of data integrity and data accuracy are really important for making high quality decisions.

Okay, so we've got the team together.

And again, we did a little bit more brainstorming.

We said, okay, at final testing, we have eight defects that we want to collect some data on.

So we create this check sheet, we've got our metadata here, we hand this off to the team, and they come back to us a week later with a bunch of data.

Now this is fantastic.

We finally have some data that we can analyze.

And the question is, which defect do we focus on?

I want to improve our target.

So we originally said we want to reduce defects by 25%.

Well, now that we have a little bit of data, we can actually create a target.

So we have 145 defects across a whole week.

That's seven days.

That means we're averaging about 20 to 21 defects per day.

Now, if we can reduce that by 25%, we will eliminate five defects per day.

Now, we obviously can't focus on all these defects.

So the real question is, how do we know what to focus on?

And that's where the Pareto chart comes into play.

So the Pareto chart is another QC tool that allows you to analyze your data in search of the Pareto principle.

So what is the Pareto rule or what is this 80-20 rule?

So this is a natural phenomenon that was discovered by a guy named Vilfredo Pareto.

He's an Italian researcher who was studying land ownership and wealth distribution in Italy and in Europe.

And what he found is that 80% of the land was owned by 20% of the people.

And this 80-20 rule and this 80-20 phenomenon was also experienced by a guy named Joseph Duran.

Now, he gave credit for the tool to Vilfredo Pareto, but he was the one who popularized this idea of the 80-20 rule and this idea of the Pareto chart.

and what he told us and what he taught us is

that a Pareto chart helps you separate the vital few from the trivial many.

Now, what did Duran mean?

What he means is when you're solving a problem, there's often one or two key issues,

key root causes or key defects that you need to focus on to have a major impact on that particular situation.

100

And that's exactly what you see here.

101

When we take our data from the check sheet and we put it into this Pareto chart, we see that control PCB issues accounts for nearly 40% of our defects.

102

You can see if we come across here, we've got 40% of our defects coming directly from control PCB.

103

Now there's two things happening on this graph.

104

Obviously there's the blue bars, which are simply just the frequency or the count of defects that occurred throughout the week.

105

And then this black bar is actually the cumulative line.

106

So this first defect accounts for 40% and then we go up and up and up all the to 100%.

107

Now that we have this Pareto analysis, we know that control PCB is our primary issue.

108

It tells us what to focus on.

109

Now, we still don't understand why these issues are happening.

110

And this is where something like the cause and effect diagram can be incredibly useful.

111

So this is the fishbone diagram or the Ishikawa diagram.

112

There's all sorts of different names for it, but it is a cause and effect diagram.

113

And the way this works is we start with the effect that's over here on the right.

114

That's the head of the fish here in orange.

115

This is our effect.

116

And so step one of the cause and effect diagram is to start with a really well-written problem statement.

117

So I've put in PCB failures, but in reality, you want to have a much more descriptive problem statement than this.

118

And once you have this effect, you can start working through the fishbone process to analyze all of the potential causes and failures.

119

Now I'm showing here what's called the 8Ms.

120

And this is the beauty of the fishbone process is that it's a well-structured approach to root cause analysis.

121

It forces you to think about all of the potential different categories

122

or scenarios or causes that might be contributing to your problem.

123

Now, along with the cause and effect diagram are a number of tools that you should be using.

124

So I would recommend you get out your flow chart, look at your process, use your flow chart and ask yourself,

125

how might each step in the process fail and contribute to the effect that we're seeing.

126

Teamwork is also a must here.

127

You're not going to be a subject matter expert in all of those 8Ms

128

and you need people from operations and engineering and quality

129

and R&D and marketing

130

and maintenance to really do a thorough analysis in each of those areas to truly understand the root cause.

131

And then of course, brainstorming.

132

You're going to have to creatively think about and talk about

133

and discuss potential root causes that maybe you're not even aware of.

134

And then the five why analysis.

135

I love the five whys.

136

It really helps you go from a high level symptom down to the true root cause and really ask why, why, why to truly get to those, those real root causes that you need to address.

137

And then as you have that team discussion and you, you go through the process, you can identify potential root causes and contributing factors to the problem you're trying to solve.

138

Now, obviously, again, it's, we have to go back to that pretty principle.

139

We can't focus on everything.

140

We have to talk about the most likely root causes and the most likely contributing factors.

141

So again, at the end of your cause and effect diagram, you might identify three or four issues that you need to study further.

142

Now, I want to talk about this one, high humidity during assembly.

143

Now, as we were working through the cause and effect diagram process, the engineer who was helping us looked at our check sheet and noticed an interesting pattern.

144

What they noticed here, and I've highlighted here in yellow, is that Sunday, Monday, Tuesday, we only had a few defects, right?

145

Six and four and one.

146

Whereas on Wednesday, Thursday, Friday, you'll notice that our defect rate jumped up a little bit.

147

And what the engineer remembered is

148

that we had a rainstorm come through on Tuesday night and the humidity level in the facility really jumped up.

149

And so what the hypothesis here is that humidity is affecting our defect rate.

150

So I created this little table here to show the days of the week along with the defects and the humidity.

151

Now to truly understand this relationship, we have to create a scatter diagram.

152

So here's exactly what that scatter diagram looks like.

153

What we do here is we're plotting pairs of data.

154

So for example, on Sunday, we had six defects and 18% humidity.

155

You can see that right here.

156

That's this data point right here.

157

We had six defects, 18% humidity.

158

Now the way this scatter diagram works, or you might hear this called an XY scatter plot, is here on the x-axis, we put our controllable variable,

159

our independent variable, and then on the y-axis we put our response variable.

160

So here we believe that relative humidity is the independent variable that is affecting our response variable, which is defects.

161

And you can see here that there appears to be some relationship between PCB failures and humidity.

162

Now, it's really important when you're looking at a scatter diagram not to assume that this relationship is a causal relationship, right?

163

There's this really important concept that you can have correlation without causation.

164

Two parameters or two variables can correlate without having a cause and effect relationship.

165

So let's assume, though, let's assume that we've done a DOE here

166

and we've proven that humidity has an effect on our PCB defects.

167

We could come back to the scatter diagram.

168

We could say, OK, our target for PCB defects is five or less.

169

Let's call it five or less.

170

And so we come down here to humidity and say, okay, we want to control humidity to around 20% to keep our defects low.

171

Does that make sense?

172

And this is a great way, a scatter diagram is a great way to understand the relationship between two possible variables.

173

Now, once you've done your scatter diagram, you can quantify the relationship between those two variables.

174

So what I'm showing here is the Pearson correlation coefficient.

175

And this coefficient ranges from positive one all the way over

176

here on the left to negative 1 all the way over here on the right.

177

And that ranges from a perfectly positive correlation here.

178

You can see that as x changes, y changes identically.

179

And then same thing here with r equals minus 1.

180

This is a perfect negative correlation.

181

Now as we get closer to 0, we start to lose that relationship.

182

So an r value of 0 means there's no correlation between those two parameters.

183

As x changes, y basically does whatever it wants.

184

There's no relationship between those two variables.

185

Now, the next thing we could do in our analysis is to look at relative humidity over time.

186

So let's say we go out, we talk to our facilities engineers, we say, okay, give us the relative humidity within our environment, you know, every six hours for the last six months.

187

And we can take that data and we want to plot it because we need to understand

188

how relative humidity is changing within our facility.

189

And one of the ways you could analyze that data is with a histogram.

190

So a histogram is just a very simple bar chart that graphs the frequency of occurrence of continuous data.

191

And again, this is a great way to talk about your process.

192

Every process or every product

193

or every quality attribute out there has some level of random normal variation that will often occur in a pattern.

194

And as engineers, we need to understand what is the pattern associated with our outputs or our process.

195

And a histogram is a great way to understand the pattern or the variation in your process.

196

Now, you might grab this data and you might get like a skewed distribution or maybe a bimodal distribution or exponential distribution.

197

There's all sorts of distributions you might get, but it's great to know how your process is behaving.

198

Now, the other beautiful part about a histogram is you can take this data and let's overlay some some specification limits, right?

199

Now what we have is the beginnings of process capability.

200

So the histogram is a fantastic tool to quantify and understand how your process behaves.

201

And if you compare that against the specification limits, we can now start talking about process capability.

202

Okay, so we're on to the very last and final QC tool.

203

Let's assume we now control for humidity, and we want to make sure that that change has been effective over time.

204

A control chart is the right tool or the perfect tool to do that.

205

So what is a control chart?

206

It is essentially a tool that allows you to confirm that your process is in control.

207

Now, when I say in control, what I mean is that you're only experiencing normal variation.

208

When your process is experiencing normal cause variation, your data should fall within those control limits.

209

By the way, if you're new to SPC, I have a whole separate video on control charts.

210

You can go check it out.

211

I've got both the X bar our chart as well as attribute data.

212

And a control chart is a fantastic tool to use at the end of a project to monitor

213

and control your process and make sure that your changes were effective.

214

And let's take a look at what this looks like for our particular process.

215

So here's our process, right?

216

The first week of data, you can see we're really all over the place and our control limits are really wide because we're not controlling for humidity.

217

And we've got all this data and you can see on average, we have about eight defects per day, right?

218

And we're really jumping around here.

219

And then let's say on day nine, we start controlling for relative humidity.

220

And we've got our control chart and we're collecting data.

221

And you can see that for the next 20 plus days, our defect rate has dramatically fallen.

222

In fact, our new mean defects per day is around three.

223

So essentially, we've gone from eight defects per day down to three defects per day.

224

And we've hit our target of reducing defects by 25%.

225

We've gone from 20 plus defects a day down to about 15, all by controlling relative humidity in our process.

226

All right, that's it for today.

227

I hope you enjoyed it.

228

If you did, hit that like button.

229

Also, if you're serious about becoming a CQE, I've got a free course.

230

Go check it out.

231

It's at cqeacademy.com slash free course, where I cover the top 10 topics on the CQE exam.

232

And I also give you a bunch of great free practice exams to help you on that journey.

233

All right, I hope you enjoyed it.

234

Thanks so much.

235

I'll see you again.

236

Bye.

✨ おすすめ動画

123 文

このレッスンの語彙とスピーキングのポイント

このC1レベルのスピーキングレッスンは、動画「The 7 Quality Control (QC) Tools Explained with an Example!」を教材にしています。繰り返し出てくる語は次のとおりです：process, defect, tool, humidity, diagram。この動画には、シャドーイング用の文が236文、単語が3208語あります。音声の長さは16:03です。話す速さは速く、1分あたり約200語です。音のつながりや弱く発音される音が多くなります。単語の84%は英語の頻出3,000語に含まれます。残りは練習の前に確認しておきましょう。

この動画の重要語彙

動画の中で特に難しい単語15語を、発音と意味つきで紹介します。

単語	発音	意味
defect 名詞	/ˈdiːfɛkt/	欠陥, 欠点
humidity 名詞	/hjuːˈmɪd.ə.ti/	湿度, 湿気
diagram 名詞	/ˈdaɪ.ə.ɡɹæm/	ダイヤグラム, 図表
scatter 動詞	/ˈskætɚ/	散る, 散らばる
analyze 動詞	/ˈæn.əˌlaɪz/	分析する
correlation 名詞	/ˌkɔɹ.əˈleɪ.ʃən/	相関
variation 名詞	/ˌvɛəɹiˈeɪʃn̩/	変動, 変化
brainstorming 名詞		ブレインストーミング, ブレーンストーミング
metadata 名詞	/ˈmɛt.əˌdeɪ.tə/	メタデータ
toaster 名詞	/ˈtəʊ̯s.təː/	トースター
coefficient 名詞	/ˌkoʊ.ɪˈfɪʃənt/	係数
parameter 名詞	/pəˈɹæm.ə.tɚ/	媒介変数, パラメーター
specification 名詞		仕様, スペック
attribute 名詞	/ˈæt.ɹɪˌbjut/	性質
organize 動詞	/ˈɔɹɡənaɪz/	組織する

動画に出てくる句動詞

単語	発音	意味
come down 動詞		降りる
get out 動詞		出て行く
go ahead 動詞	/ˌɡoʊ əˈhɛd/	どうぞお先に
go out 動詞		出る
go up 動詞		上がる, 登る
write down 動詞		書き留める, 記す

繰り返し練習したい文

動画に出てくる短く完結した文です。日常会話でそのまま使えます。

All right, let's go and get started.
All right, let's get into it.
That's the boundaries of our flowchart.
What sort of improvement are we gonna make?
We can't focus on everything.

この動画の文法

話し手がよく使っている文型を、動画の実際の表現とともに紹介します。

文型	動画での表現
現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している	I've put · I've highlighted · we've done
受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる	can be solved · should be based · was discovered
関係詞節 who / which + 節 — 人や物について情報を加える	topic which is · one who popularized · bars, which are

注意したい発音

話し手はyou're, we're, we'veなど、短縮形や弱形を79回使っています。聞こえたとおりの短い形で発音しましょう。

「th」の音: hypothesis /haɪˈpɒθɪsɪs/, thorough /ˈθʌɹoʊ/
「sh」と「zh」の音: correlation /ˌkɔɹ.əˈleɪ.ʃən/, variation /ˌvɛəɹiˈeɪʃn̩/, coefficient /ˌkoʊ.ɪˈfɪʃənt/, causation /kɔˈzeɪ.ʃən/
長い単語（アクセントの位置に注意）: humidity /hjuːˈmɪd.ə.ti/, correlation /ˌkɔɹ.əˈleɪ.ʃən/, metadata /ˈmɛt.əˌdeɪ.tə/, coefficient /ˌkoʊ.ɪˈfɪʃənt/, parameter /pəˈɹæm.ə.tɚ/

日本語話者が苦手な音：

/r/ と /l/ の区別 — /l/ は舌先を歯茎につけ、/r/ はどこにもつけない: correlation /ˌkɔɹ.əˈleɪ.ʃən/, controllable /kənˈtɹoʊləbəl/, correlate /ˈkɔɹəleɪt/, creatively /kɹiˈeɪtɪvli/, trivial /ˈtɹɪv.i.əl/
/v/ — /b/ にならないように、上の歯を下唇に当てる: variation /ˌvɛəɹiˈeɪʃn̩/, behave /bɪˈheɪv/, creatively /kɹiˈeɪtɪvli/, overlay /ˌoʊvɚˈleɪ/, descriptive /dəˈskɹɪptɪv/
/f/ — 「フ」ではなく、上の歯と下唇で出す: defect /ˈdiːfɛkt/, coefficient /ˌkoʊ.ɪˈfɪʃənt/, quantify /ˈkwɑn.tɪˌfaɪ/, graph /ɡɹæf/, oftentimes /ˈɔf.ənˌtaɪmz/

この動画での練習方法

まず声を出さずに動画を最後まで聞き、知らない単語をメモします。
まず0.75倍速で一文ずつシャドーイングし、慣れてきたら通常の速度に戻します。
自分の声を録音して元の音声と比べます。defect, humidity, diagramなどの単語に特に注意しましょう。

シャドーイングとは？英語上達に効果的な理由

シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。

シャドーイングのやり方: ステップ別の完全ガイドを読む →

シャドーイング練習: The 7 Quality Control (QC) Tools Explained with an Example! - 動画で英語スピーキングを学ぶ

QC 7 tools – Cause and Effect Analysis (Fishbone) Diagram Introduction

The easy way to keep your repos tidy.

QA Automation Interview Questions and Answers

Ricardo Vargas Shows How to Implement Governance During Project Execution

What is Quality Management? | Quality Management Tutorial | Invensis Learning

What is the 8D report? (problem solving tools)

Seven Testing Principles: Software Testing

SQF Edition 9 to 10: What changed and what you must update before 2027

7 Habits of Highly Effective People | Summary | Stephen Covey | Part 1

PLC Programming #4: Functions, Function Blocks & Organization Blocks Explained

Your AI broke the layout. Now what?

PCB Inspection Methods & Common PCB Defects