跟讀練習: QC 7 tools – Cause and Effect Analysis (Fishbone) Diagram Introduction - 通過影片學習英語口語
選擇練習模式
每種模式都會開啟全屏練習室。
123 句
如果句子過短或過長，請點選 Edit 進行調整。
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)？工程師對屏蔽罩的愛恨情仇
Daily ConversationUniversity StudentsWorking Adults
C12
What is IMC (Intermetallic Compounds) part I? The role of IMC plays in the soldering
Daily ConversationWorking Adults
C12
What is IMC (Intermetallic Compounds) part II? The different between IMC, alloy, eutectic
Daily ConversationUniversity StudentsWorking Adults
C14
What is IMC (Intermetallic Compounds) part III? Explain Alloy, Eutectic in detail
Daily ConversationUniversity 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
FOR YOU
推薦影片
C12
236 句
The 7 Quality Control (QC) Tools Explained with an Example!
Daily ConversationUniversity StudentsWorking Adults
C11
42 句
Every Sushi Explained
Daily ConversationWorking Adults
C16
35 句
Results Framework and Logframe: MEAL DPro Starter
Daily ConversationWorking Adults
B21
136 句
day in the life working as a business analyst | my business analysis workflow
Daily ConversationWorking Adults
B21
105 句
Learn to Draw FASTER Than Others (SECRET Chinese Method)
Daily ConversationWorking Adults
C12
112 句
DFM And DFA Explained
Daily ConversationWorking Adults
C12
118 句
The Anatomy of Fraud
Daily ConversationUniversity StudentsWorking Adults
C14
140 句
PCB Inspection Methods & Common PCB Defects
Daily ConversationWorking Adults
C15
94 句
Your AI broke the layout. Now what?
Daily ConversationWorking Adults
C12
43 句
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
Daily ConversationUniversity StudentsWorking Adults
C13
122 句
How To Read A Datasheet - Electronics with Becky Stern | DigiKey
Daily ConversationWorking Adults
B21
49 句
Learn UX Storyboarding in 5 Minutes: w/ Steps and Examples | UXtweak
Daily ConversationUniversity StudentsWorking Adults
真實場景：如何用魚骨圖解決工作難題？
想像一下，你在工作中遇到了棘手的問題，比如“為什麼最近總遲到”或“產品不良率居高不下”，卻不知從何下手。這時，影片裡介紹的魚骨圖就能幫你理清思路。它不僅是質量管理工具，更是日常問題解決的好幫手。通過繪製魚骨圖，你可以像偵探一樣，一步步追溯原因或尋找解決方案，讓混亂的思緒變得清晰。
實用表達&搭配
- 魚骨圖：即因果分析圖，影片中反覆提到的核心工具，記住它的英文表達“Fishbone Diagram”也很有用。
- 頭腦風暴：團隊合作解決問題時常用，英文是“brainstorming”，搭配“cross-functional team（跨職能團隊）”效果更佳。
- 根本原因：問題的關鍵所在，英文“root cause”，比如“找到根本原因”可以說“identify the root cause”。
- 優先順序排序：處理多個原因時的必要步驟，英文“prioritize”，例如“對原因進行優先順序排序”。
你的影子跟讀挑戰
現在就開啟影片，挑選一段關於“如何繪製魚骨圖”的講解（比如步驟部分），進行shadow speak練習。先聽一句，暫停，模仿發音、語調甚至語速，重複3遍。重點關注“fishbone diagram”“cause-oriented”“solution-oriented”等詞彙的發音。完成後，用中文複述這段內容，檢查自己是否準確理解。堅持每天10分鐘，不僅能提高英語發音，還能鍛鍊聽力和口語表達，對雅思口語練習也有幫助哦。試試吧，你會發現shadowspeak真的很有效！
影片中的語法
說話人最常用的結構，並附上影片中的原話：
| 結構 | 影片中的用法 |
|---|---|
| 被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的 | is needed · is hidden · are often made |
| 現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事 | has already occurred · you've gathered |
什麼是跟讀法？
跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。