Luyện nói tiếng Anh bằng Shadowing qua video: What is the 8D report? (problem solving tools)
Đang tạo bài học...
1
Hi, my name is Florian from Quality Guru where I answer your questions and share knowledge quality management
2
Today I would like to talk about the AD Report.
3
The 8D problem solving methodology is a very common approach in many industries.
4
And many people like it because it's straightforward, logical and very transparent.
5
That makes it so powerful in the internal and external communication, either with your own teams or with your customer. If you.
6
send out some defect parts and you got a complaint to your company.
7
8D stands for the eight disciplines and basically refers to an eight -step process.
8
which you have to go through in order to analyze your problem, take corrective action, verify them, and then hopefully close the problem.
9
Stop it forever.
10
So let me take you quickly through the eight steps and let's see.
11
what it looks like.
12
First of all is, the team identify the team that means who is working on this problem
13
You should never work alone on a problem solving.
14
Their philosophy is basically that you get many people together from different areas who have a different perspective on the problem.
15
So if you're for example in a manufacturing company, there should be somebody from quality, from production, maybe from logistic, from engineering, so that different people from different perspectives.
16
can look at the problem and help you to make a better root cause analysis and identify better corrective actions, because if you have
17
A deeper root cause analysis and better corrective actions will help you to be so much more efficient in stopping this.
18
problem as soon as possible.
19
Step number two is: Identifying the problem.
20
And here we need to be as specific as possible.
21
That means we should say, what was the problem, where did it happen, how did it happen, maybe you have photos, Maybe you have specific times.
22
Maybe you have Everything what you have basically regarding the problem should be as specific as possible
23
so that later you don't
24
confuse it with other problems which happen maybe or other issues which happen the same Really be as specific as possible,
25
gather all the data regarding this particular event what you have to really nail it down as good as possible.
26
Then step number three is you want to contain the problem.
27
So now, for example, if you find a problem in a production process for example.
28
Unless you solve it completely, you still have the risk that you are continuously producing this kind of defect or problem into your products.
29
So you cannot be sure that what you send out and what you are selling at the moment
30
is safe for your customer.
31
and it's a potential risk for them, but also for you, because you will get the customer dissatisfaction.
32
and you will probably get then problems.
33
with regards to complaints and then also financial impacts.
34
So you want to stop as soon as possible.
35
How can you contain a problem in the manufacturing process?
36
You can, for example, put a filter on your production line.
37
It means you could sort the parts with a visual inspection if it's possible or with a test
38
100 % and let them go through this filter so that you can filter out with the right method.
39
all the problematic parts with the information you already have.
40
Once you protect it, the customer and the market and yourself you can go to step number four, which is the root cause analysis.
41
And here you should try to identify with the team what is the root cause of the problem.
42
And here you should use something like problem -solving tools, for example, a 5Y diagram,
43
a fishbone diagram, and many other problem -saving tools can be used here.
44
But, You should document it.
45
in a way and try to identify all the possible root causes and not stop at the first one.
46
The more root causes we can identify, possible root causes, We can then later verify or that we can correct and stop all of these root causes
47
but at the moment we don't know which one is the true one.
48
So we want to be very creative and we want to allow the team to issue
49
all the ideas at this moment in order to have a very complete root cause analysis
50
and have all the ideas and possibilities on the table.
51
So, once you have identified maybe one or several possible root causes, Then we need to take Step number five,
52
which is Take corrective actions.
53
So we want to correct the problem.
54
And we need to define now some measures to do this.
55
So we have our identified root causes and we can put for every one of the root causes one or several
56
corrective actions.
57
That means actions which help us to stop the root cause.
58
Once we have this, we go to step number six and then over time we will validate now
59
that the actions we have defined here in step number five are really solving the problem.
60
How can we know this? we can see if more problems are coming.
61
And by this, we can see if the actions are effective and if they are affected, effective, then we can check also this box,
62
step number six and say,
63
okay, now I know all the actions are effective and I don't have a risk for this problem anymore.
64
Once I do this, the problem is under control.
65
Now I want to go to step number seven, which is "How can I prevent that in the future,
66
this problem will not happen again?" And here I should do some lessons learned and look into my quality management system
67
For example, into my FMEA, as a tool and see if I have this problem identified in my processes.
68
If I have it identified, I need to review if my risk assessment for this problem is adequate.
69
And if I have not identified it, I need also to update my FMEA
70
and then by this also take it over into my control plan and with the control plan then
71
bring it down into the shop floor with the identified new controls.
72
So I need to define new inspections or controls if adequate
73
in order to avoid that this problem goes undetected in the future.
74
And last but not least, once I have finished my step number seven, I can go to step number eight,
75
which is congratulate the team everybody who has contributed say thank you This is good for the team building,
76
it motivates and it helps the team to get confident that you can work together and solve any problem in the organization.
77
Let me know your experience.
78
Have you ever tried working with an AD report?
79
What is your experience?
80
Is it easy?
81
Is it difficult?
82
Do you have any questions?
83
Post them right in the comments.
84
and looking forward to reading about it and see you in the next video.
📺 Cùng kênh
✨ Video gợi ý
B23
118 câu
8D Reports Made Simple: How to Solve Problems at Work—and at Home
Business EnglishWorking Adults
C18
45 câu
Types of Surveys to Run Throughout the Design Process
Business EnglishUniversity StudentsWorking Adults
C12
236 câu
The 7 Quality Control (QC) Tools Explained with an Example!
Business EnglishUniversity StudentsWorking Adults
C11
443 câu
Functional-Oriented Documentation in Automation - Eplan & IEC 81346 Explained
Business EnglishUniversity StudentsWorking Adults
C11
120 câu
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table
Business EnglishUniversity StudentsWorking Adults
C12
43 câu
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
Business EnglishUniversity StudentsWorking Adults
B22
35 câu
How to Use the Socratic Method (for Dialogue, Debate and Critical Thinking)
Business EnglishUniversity StudentsWorking Adults
C12
100 câu
How to Answer Situational Questions for Product (PM) Behavioral Interview | Framework + Solution
Business EnglishInterview EnglishUniversity Students
C11
70 câu
Ricardo Vargas Shows How to Implement Governance During Project Execution
Business EnglishUniversity StudentsWorking Adults
C11
745 câu
WORK - HRM Lecture 08
Business EnglishUniversity StudentsWorking Adults
C149 câu
Working as a Fire Protection Engineer - First Six Months Experience
Business EnglishUniversity StudentsWorking Adults
Từ vựng và ghi chú luyện nói cho bài học này
Video này có 84 câu và 1171 từ để luyện shadowing. Phần lời nói dài 7:25. Người nói nói với tốc độ tự nhiên, khoảng 158 từ mỗi phút, gần với hội thoại hằng ngày. 90% số từ nằm trong 3.000 từ tiếng Anh thông dụng nhất; phần còn lại nên xem trước khi luyện.
Từ vựng quan trọng trong video
15 từ đáng học trong video, kèm phiên âm và nghĩa:
| Từ | Phiên âm | Nghĩa |
|---|---|---|
| solve động từ | /sɒlv/ | giải quyết |
| filter danh từ | /ˈfɪltɚ/ | máy lọc |
| complaint danh từ | /kəmˈpleɪnt/ | phàn nàn |
| inspection danh từ | /ɪnˈspɛkʃən/ | sự kiểm tra |
| adequate tính từ | /ˈæd.ə.kwɪt/ | đủ, đầy đủ |
| verify động từ | /ˈvɛɹɪfaɪ/ | xác minh, xác thực |
| diagram danh từ | /ˈdaɪ.ə.ɡɹæm/ | giản đồ, biểu đồ |
| defect danh từ | /ˈdiːfɛkt/ | tật, lỗi |
| lesson danh từ | /ˈlɛs.ən/ | bài, bài học |
| contribute động từ | /kənˈtɹɪb.jut/ | đóng góp |
| discipline danh từ | /ˈdɪsəplɪn/ | kỉ luật |
| nail danh từ | /neɪl/ | móng, móng tay |
| transparent tính từ | /tɹænsˈpæɹənt/ | trong suốt |
| analyze động từ | /ˈæn.əˌlaɪz/ | phân tích |
| motivate động từ | /ˈmoʊ.tɪ.veɪt/ | khích lệ, động viên |
Phát âm cần chú ý
Người nói dùng 4 dạng rút gọn, ví dụ don't, you're. Hãy nói theo dạng ngắn đúng như bạn nghe.
- Âm “th”: gather /ˈɡæðɚ/, methodology /ˌmɛθ.əˈdɑ.lə.d͡ʒi/
- Âm “sh” và “zh”: inspection /ɪnˈspɛkʃən/, efficient /ɪˈfɪʃənt/, dissatisfaction /dɪsˌsætɪsˈfækʃən/
- Từ dài — đặt trọng âm cho đúng: continuously /kənˈtɪnjuəsli/, problematic /ˌpɹɑ.bləˈmæt.ɪk/, methodology /ˌmɛθ.əˈdɑ.lə.d͡ʒi/, congratulate /kənˈɡɹæd͡ʒ.ʊˌleɪt/, dissatisfaction /dɪsˌsætɪsˈfækʃən/
Cách luyện với video này
- Nghe hết video một lần, chưa cần nói, và ghi lại những từ bạn chưa biết.
- Bắt đầu ở tốc độ 0,75×, nói đuổi từng câu, rồi quay lại tốc độ bình thường khi đã quen.
- Ghi âm giọng mình rồi so với bản gốc, chú ý các từ như solve, filter, complaint.
Ngữ pháp trong video
Những cấu trúc người nói dùng nhiều nhất, kèm đúng cụm từ trong video:
| Cấu trúc | Trong video |
|---|---|
| Thì hiện tại hoàn thành have/has + quá khứ phân từ — việc đã xảy ra nhưng còn liên quan đến hiện tại | have identified · have defined · have not identified |
| Mệnh đề quan hệ who / which + mệnh đề — thêm thông tin về người hoặc vật | four, which is · seven, which is |
Phương Pháp Shadowing Là Gì?
Shadowing là kỹ thuật học ngôn ngữ có cơ sở khoa học, ban đầu được phát triển cho chương trình đào tạo phiên dịch viên chuyên nghiệp và được phổ biến rộng rãi bởi nhà đa ngôn ngữ học Dr. Alexander Arguelles. Nguyên lý cốt lõi đơn giản nhưng cực kỳ hiệu quả: bạn nghe tiếng Anh của người bản xứ và lặp lại to ngay lập tức — như một "cái bóng" (shadow) đuổi theo người nói với độ trễ chỉ 1–2 giây. Khác với luyện ngữ pháp hay học từ vựng bị động, Shadowing buộc não bộ và cơ miệng phải đồng thời xử lý và tái tạo ngôn ngữ thực tế. Các nghiên cứu khoa học xác nhận phương pháp này cải thiện đáng kể phát âm, ngữ điệu, nhịp điệu, nối âm, kỹ năng nghe và độ lưu loát khi nói — đặc biệt hiệu quả cho người luyện IELTS Speaking và muốn giao tiếp tiếng Anh tự nhiên như người bản ngữ.