Shadowing Practice: QC 7 tools – Cause and Effect Analysis (Fishbone) Diagram Introduction - Learn English Speaking with Video

Ders oluşturuluyor...
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!

Bu dersin kelimeleri ve konuşma notları

Bu C1 seviyesindeki konuşma dersi “QC 7 tools – Cause and Effect Analysis (Fishbone) Diagram Introduction” videosuna dayanıyor. En çok tekrarlanan kelimeler: diagram, fishbone, flux, issue, Ipa. Bu videoda gölgeleme çalışması için 123 cümle ve 1609 kelime var. Konuşma bölümü 9:25 sürüyor. Konuşmacı dakikada yaklaşık 171 kelimeyle, günlük konuşmaya yakın doğal bir hızda konuşuyor. Kelimelerin yalnızca %79’i İngilizcede en sık kullanılan 3.000 kelime arasında, bu yüzden kelime dağarcığı zorlayıcı.

Bu videodaki önemli kelimeler

Videodaki en ileri düzey 15 kelime, telaffuzu ve anlamıyla:

KelimeTelaffuzAnlam
diagram isim/ˈdaɪ.ə.ɡɹæm/şema
fishbone isimkılçık
contamination isim/kənˌtæm.əˈneɪ.ʃən/bulaşma
keypad isim/ˈkiːpæd/tuş takımı
attrition isim/əˈtɹɪʃən/yıpratma
brainstorming isimbeyin fırtınası, fikir fırtınası
culprit isim/ˈkʌlpɹɪt/mücrim, suçlu
mistakenly zarf/mɪˈsteɪ.kən.li/yanlışlıkla
prioritize fiil/pɹaɪˈɒɹ.ə.taɪz/önceliklendirmek
scatter fiil/ˈskætɚ/dağılmak, yaymak
defective sıfat/dɪˈfɛktɪv/hatalı, kusurlu
participant isim/pɑːɹˈtɪsəpənt/katılımcı, iştirakçı
verify fiil/ˈvɛɹɪfaɪ/doğrulamak
subscribe fiil/səbˈskɹaɪb/abone olmak
interruption isim/ˌɪntəˈɹʌpʃən/sekte

Duyacağınız deyimsel fiiller

KelimeAnlam
check out fiilgözden geçirmek
figure out fiilaçığa çıkarmak
show up fiilortaya çıkmak
wrap up fiilpaketlemek, (bir şeyi) sarmak

Bu videodaki dil bilgisi

Konuşmacının en çok kullandığı yapılar, videodaki sözcüklerin aynısıyla:

YapıVideoda
Edilgen yapı be + fiilin üçüncü hâli — kimin yaptığı değil, ne olduğu önemliis needed · is hidden · are often made
Present perfect have/has + fiilin üçüncü hâli — geçmişte olan ama şimdi de önemli olan bir eylemhas already occurred · you've gathered
İlgi cümlecikleri who / which + cümle — bir kişi ya da şey hakkında ek bilgisomeone who likes · and which are

Dikkat edilecek telaffuzlar

Konuşmacı you're, didn't, doesn't gibi kısaltılmış biçimleri 10 kez kullanıyor. Bunları duyduğunuz gibi kısa söyleyin.

  • “sh” ve “zh” sesleri: contamination /kənˌtæm.əˈneɪ.ʃən/, attrition /əˈtɹɪʃən/, countermeasure /ˈkaʊ̯ntəmɛʒə/, interruption /ˌɪntəˈɹʌpʃən/, verification /ˌvɛ.ɹə.fɪˈkeɪ.ʃən/
  • Uzun kelimeler — vurguyu doğru yere koyun: contamination /kənˌtæm.əˈneɪ.ʃən/, mistakenly /mɪˈsteɪ.kən.li/, prioritize /pɹaɪˈɒɹ.ə.taɪz/, participant /pɑːɹˈtɪsəpənt/, countermeasure /ˈkaʊ̯ntəmɛʒə/

Türkçe konuşanların zorlandığı sesler:

  • Kelime başındaki ünsüz kümesi — araya ünlü eklemeyin: flux /flʌks/, prioritize /pɹaɪˈɒɹ.ə.taɪz/, scatter /ˈskætɚ/, criticize /ˈkɹɪtɪsaɪz/, stain /steɪn/
  • /æ/ — “e”den daha açık: diagram /ˈdaɪ.ə.ɡɹæm/, contamination /kənˌtæm.əˈneɪ.ʃən/, keypad /ˈkiːpæd/, scatter /ˈskætɚ/, analyze /ˈæn.əˌlaɪz/

Bu videoyla nasıl çalışılır

  1. Videonun tamamını konuşmadan bir kez dinleyin ve bilmediğiniz kelimeleri not edin.
  2. 0,75× hızla başlayın, cümle cümle tekrar edin ve kolaylaşınca normal hıza dönün.
  3. Kendinizi kaydedin ve orijinaliyle karşılaştırın; diagram, fishbone, contamination gibi kelimelere özellikle dikkat edin.

Gölgeleme Tekniği Nedir?

Gölgeleme, başlangıçta profesyonel tercüman eğitimi için geliştirilen ve çok dilli Dr. Alexander Arguelles tarafından popüler hale getirilen, bilim destekli bir dil öğrenme tekniğidir. Yöntem basit ama güçlüdür: ana dili İngilizce olan bir sesi dinler ve hemen yüksek sesle tekrar edersiniz — konuşmacıyı 1-2 saniye gecikmeyle takip eden bir gölge gibi. Pasif dinleme veya dilbilgisi alıştırmalarının aksine, gölgeleme beyninizi ve ağız kaslarınızı gerçek konuşma kalıplarını eşzamanlı olarak işlemeye ve yeniden üretmeye zorlar. Araştırmalar, telaffuz doğruluğu, tonlama, ritim, bağlı konuşma, dinleme anlama ve konuşma akıcılığını önemli ölçüde geliştirdiğini göstermektedir — bu da onu IELTS Konuşma hazırlığı ve gerçek dünya İngilizce iletişimi için en etkili yöntemlerden biri yapar.

Shadowing tekniği: adım adım eksiksiz rehberi okuyun →