쉐도잉 연습: QC 7 tools – Cause and Effect Analysis (Fishbone) Diagram Introduction - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
Hello everyone, this is Working Bear.
2
Today I want to introduce you to something called the Fishbone Diagram, also known as a Cause and Effect Analysis Diagram.
3
Many of you might already know what a Fishbone Diagram is, but do you know how to actually draw one?
4
And what should you watch out for when creating one?
5
As the name suggests, the diagram looks like the skeleton of a fish.
6
That's where it gets its nickname.
7
Its formal name is Cause and Effect Analysis Diagram, because it's used to trace a problem, effect, back to its possible causes.
8
Originally, fishbone diagrams were used in product design to analyze causes of failure, or in manufacturing to find the root cause of quality issues and come up with solutions.
9
Nowadays, people use it in many industries to solve everyday work and life problems, too.
10
Some people also call it the Ishikawa Diagram, named after Dr. Kaoru Ishikawa, a Japanese quality control expert who developed this tool.
11
Drawing a fishbone diagram is actually very simple.
12
The basic version just uses a few arrows.
13
If you're someone who likes a little more creativity, check out Working Bear's YouTube video, How to Draw a Unique Fishbone Diagram in PowerPoint.
14
When quality instructors teach us how to draw fishbone diagrams, they usually mention that there are two main styles, based on the direction the fish's head points.
15
When the fish head points to the right, it's a cause-oriented fishbone diagram.
16
The head represents the problem, and the bones show possible causes.
17
So you write the problem that has already occurred at the fish's head.
18
The topic usually starts with why or directly names the issue, like, oh, why am I often late to work?
19
Oh, why is the SMT component attrition rate so high?
20
Then list the possible causes along the bones of the fish.
21
When the fish head points to the left, it's a solution-oriented fish bone diagram.
22
The head represents a goal, and the bones list potential solutions or actions.
23
The topic often starts with how to improve, prevent, solve, like, oh, how to avoid being late to work, oh, how to reduce the SMT component attrition rate,
24
then write possible countermeasures along the bones.
25
When used correctly, a fishbone diagram can be a powerful tool to solve tough problems.
26
In everyday life or at work, we often face issues.
27
Some problems are simple.
28
You can identify the cause right away, so no diagram is needed.
29
But other times, the cause is hidden and hard to figure out.
30
Our thoughts may become too scattered or unfocused to find the real root.
31
That's when a fishbone diagram comes in handy.
32
It helps you sort out all those scattered thoughts, narrow them down, and find the main possible causes.
33
After that, you can collect data, use stratification analysis, or prioritize the possible causes, verify them one by one,
34
and finally take action with a solid long-term solution.
35
So, before you draw a fishbone diagram, you should already have some ideas about what might be causing the problem.
36
Actually, whether you have ideas or not, Working Bear strongly recommends gathering a cross-functional team for a brainstorming session.
37
List all possible causes based on the problem, then use the fishbone diagram method to organize and discuss the likelihood of each cause.
38
As the saying goes, two heads are better than one, and this kind of teamwork helps prevent blind spots or tunnel vision.
39
Now let's walk through how to hold a meeting to create a fishbone diagram.
40
One, gather the right people.
41
Bring together everyone related to the issue or those with relevant knowledge or experience.
42
Avoid having just one person draw the diagram alone.
43
A good group size is around 4 to 10 people.
44
Two, use a whiteboard or large sheet of paper.
45
It's a good idea to have several colored markers.
46
Each person can use a different color.
47
These days, many people also use mind mapping software to draw the diagram digitally.
48
Three, start drawing the fishbone diagram.
49
Begin by sketching a basic fishbone shape on the board or paper, with the head pointing to the right, arrow to the right.
50
Write the problem clearly at the head of the fish.
51
Be sure to describe the issue in detail, its characteristics, symptoms, or signs, so everyone understands the context.
52
Label the main bones with major causes, the branches with subcauses, and the small tips with minor causes.
53
If you're analyzing design or manufacturing issues, many experienced teams use the classic 6M categories for the major causes,
54
manpower, method, material, machine, measurement, and mother nature, also call environment.
55
These six categories usually cover all types of causes and often relate to different departments, helping the team think broadly and clarify responsibilities.
56
Of course, you're free to group your main causes differently.
57
It doesn't have to follow the 6M structure.
58
Also, remember to place more likely or direct causes closer to the fish's head
59
and less likely or distant causes nearer the tail.
60
This helps focus attention on the most probable causes.
61
The goal is to make it easy for others, especially people unfamiliar with the issue or decision makers, to quickly see which causes are major and which are minor.
62
After all, reports are often made for others, so if your fishbone diagram is clear, there's less need for further explanation.
63
Four, take turns sharing causes.
64
Each participant should take 15-20 seconds to say one possible cause.
65
Keep going without interruptions.
66
No criticizing or questioning allowed during this phase.
67
The host or a note taker writes down each point on the diagram.
68
5. Time Limits Limit each person's speaking time to 20 seconds before moving to the next.
69
After a few rounds, once you've gathered 60-80 potential causes or people stop contributing, wrap up the brainstorming.
70
Try to keep the whole session under 30 minutes.
71
6. Prioritize the causes Now go through the list of causes.
72
Have each participant pick the ones they believe are most significant.
73
Circle these in red on the diagram once the group agrees.
74
Seven, narrow down the key causes.
75
Next, go through the circled causes again.
76
Let everyone pick out the most critical ones from the red circles.
77
Mark those with a second colored circle.
78
Repeat this process until no more can be added.
79
Finally, review the entire fishbone diagram.
80
The causes with the most circles are likely the main culprits behind the problem.
81
Now it's time to take action and find solutions based on those key causes.
82
Now, let's take a look at this fishbone diagram example.
83
Why have I been showing up late to work recently?
84
This is a typical right-facing fishbone diagram,
85
used to trace the possible causes of a problem problem.
86
And here's another one.
87
How can I avoid being late to work?
88
This is a left-facing fishbone diagram that focuses on finding solutions.
89
The next example is something Working Bear previously shared on the blog, a fishbone diagram about the source of oil contamination on keypad circuits.
90
Back then, Working Bear explained that a product at a previous company had a serious DOA, dead on arrival, complaint.
91
Most of the defective units had unresponsive keypads, specifically on the 3, 6, and 9 keys.
92
The root cause turned out to be oil contamination.
93
My company formed a temporary task force to investigate, even sending engineers to the contract manufacturer's factory.
94
To their credit, the factory was cooperative and had already done some internal troubleshooting on their own.
95
After a detailed investigation and summarizing findings with a cause and effect diagram,
96
the most likely root cause pointed to an operator mistakenly using flux instead of IPA, isopropyl alcohol, as a cleaner.
97
This flux was applied directly to the keypad contact circuits on the PCB.
98
Even though the source of the oil was identified, verifying it became another challenge.
99
Here, Working Bear briefly explained the two-part verification process simply.
100
First, we sent the returned defective units to a lab for chemical analysis.
101
We used FTIR, Fourier Transform Infrared Spectroscopy, because EDS, Energy Dispersive X-ray Spectroscopy,
102
only detects elements, not compounds.
103
The results showed a mixture of IPA and flux.
104
Second, we simulated three possible contamination scenarios.
105
A mixture of IPA and flux, we applied each substance to the PCB circuit,
106
then assembled the units immediately and let them sit for 24, 48, and 72 hours.
107
The results showed that the flux-only samples looked most similar to the actual oil stain issue, but didn't show any white powder.
108
The IPA and flux mixture did produce white powder, but didn't recreate the oily appearance.
109
So the likely culprit was a flux-heavy mixture of IPA and flux.
110
Eventually, the contract manufacturer admitted that their operators may have mistakenly used flux instead of IPA.
111
And during our on-site audit, we found that both flux and IPA were stored in the same cabinet.
112
To a new operator, the two containers might have looked the same, which made it easy to confuse one for the other.
113
This mix-up likely led to cross-contamination and the use of the wrong cleaning agent.
114
If you're interested in this oil contamination case, check out Working Bear's video.
115
The case study, oil and white powder contamination on PCB keypad contact, circuits causing keypad failures.
116
That's it for today's sharing.
117
If you're interested in electronics manufacturing, be sure to subscribe to Working Bear's YouTube and podcast channels.
118
Don't forget to like, subscribe, and share.
119
And if you can, please leave us a five-star review on Apple Podcasts.
120
It helps more people discover Working Bear's show.
121
All related links can be found in the episode description.
122
That's it for now.
123
Bye bye!
📺 같은 채널
B23
8D Reports Made Simple: How to Solve Problems at Work—and at Home
Business EnglishWorking Adults
B25 Key Mindsets Before You Start Writing an 8D Report
Business EnglishWorking Adults
C11
什麼是屏蔽罩(shielding can)？工程師對屏蔽罩的愛恨情仇
Business EnglishUniversity StudentsWorking Adults
C12
What is IMC (Intermetallic Compounds) part I? The role of IMC plays in the soldering
University StudentsWorking Adults
C12
What is IMC (Intermetallic Compounds) part II? The different between IMC, alloy, eutectic
University StudentsWorking Adults
C14
What is IMC (Intermetallic Compounds) part III? Explain Alloy, Eutectic in detail
University StudentsWorking Adults
C12
Deep Dive: Investigating Thermal Cycling Failures Cracked MSOP Solder Joints
Business EnglishUniversity StudentsWorking Adults
C12
What Are PCB and PCBA? What’s the Difference Between Them?
Business EnglishUniversity StudentsWorking Adults
C1How to evaluate whether an 8D report is well written
Business EnglishWorking Adults
✨ 추천 영상
C12
236 문장
The 7 Quality Control (QC) Tools Explained with an Example!
Business EnglishUniversity StudentsWorking Adults
C16
35 문장
Results Framework and Logframe: MEAL DPro Starter
Business EnglishUniversity StudentsWorking Adults
C1166 문장
AI Animation Pipeline: How I Make Cartoons 100% With AI
Business EnglishUniversity StudentsWorking Adults
C11
29 문장
VMM I O-INSPECT I Curve
Business EnglishUniversity StudentsWorking Adults
C13
84 문장
What is the 8D report? (problem solving tools)
Business EnglishUniversity StudentsWorking Adults
C13
28 문장
0925.2 financial statements and ratios
Business EnglishUniversity StudentsWorking Adults
C1178 문장
Data Presentation, Step-by-Step | Google Data Analytics Certificate
Business EnglishUniversity StudentsWorking Adults
C11
92 문장
How Things Are Made | An Animated Introduction to Manufacturing Processes
Business EnglishUniversity StudentsWorking Adults
C15
94 문장
Your AI broke the layout. Now what?
Business EnglishUniversity StudentsWorking Adults
C11
50 문장
0.0.1 How to become a CAE Engineer CAE | What are the ways to become a CAE Engineer as a fresher
Business EnglishUniversity StudentsWorking Adults
C12
100 문장
How to Answer Situational Questions for Product (PM) Behavioral Interview | Framework + Solution
Business EnglishInterview EnglishUniversity Students
이 영상으로 영어 말하기 연습하면 좋은 이유
이 영상은 '피시본 다이어그램'이라는 주제를 구체적으로 설명하며, 일상적이면서도 전문적인 컨텍스트를 제공해줍니다. shadow speech 연습에 적합한데, 발표나 회의에서 사용하는 논리적인 말투와 구조를 익힐 수 있습니다. 특히 IELTS 스피킹 준비생들에게는 문제 해결 과정을 설명하는 능력을 기르는 데 도움이 됩니다. 영상 속 자연스러운 발화 패턴을 따라하면, 실제 의사소통에서 필요한 흐름과 강조점을 배울 수 있어 영상 영어 공부의 효과가 배가됩니다.
문맥 속 문법과 표현
- "As the name suggests" – 이름에서 알 수 있듯이. 비슷한 구조로 "As you might know"도 자주 사용됩니다. 설명문에서 주제를 도입할 때 유용한 표현입니다.
- "When used correctly" – 올바르게 사용될 때. 수동태를 간결하게 사용하여 조건을 나타내는 패턴입니다. "If used properly"와 바꿔쓸 수 있습니다.
- "Let everyone pick out the most critical ones" – 모두가 가장 중요한 것을 골라보게 하다. "Let + 사람 + 동사원형" 구조는 권고나 지시를 부드럽게 표현할 때 사용됩니다.
발음의 함정 주의하기
영상에서 주의해야 할 발음이 몇 가지 있습니다. "Ishikawa"는 일본식 발음으로 [이시카와]에 가깝지만, 영어로는 [이쉬카와]로 발음하기도 합니다. "Attrition"은 [어트리션]이 아니라 [어트리션] (t가 약하게 발음됨)입니다. 영어 발음 교정을 위해선 이런 세부 사항을 주의해야 합니다. 또한 "stratification"은 [스트라티피케이션]으로, 긴 단어도 부드럽게 발음하는 연습이 필요합니다. shadow speak를 할 때는 발음 뿐만 아니라 억양과 강세도 따라하는 것이 중요합니다.
이 영상의 문법
화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.
| 문형 | 영상 속 표현 |
|---|---|
| 수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점 | is needed · is hidden · are often made |
| 현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때 | has already occurred · you've gathered |
| 관계절 who / which + 절 — 사람이나 사물에 대한 추가 정보 | someone who likes · and which are |
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.