शैडोइंग अभ्यास: What is the 8D report? (problem solving tools) - वीडियो के साथ अंग्रेजी बोलना सीखें
पाठ बनाया जा रहा है...
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.
📺 उसी चैनल से
✨ अनुशंसित वीडियो
B23
118 वाक्य
8D Reports Made Simple: How to Solve Problems at Work—and at Home
Business EnglishWorking Adults
C18
45 वाक्य
Types of Surveys to Run Throughout the Design Process
Business EnglishUniversity StudentsWorking Adults
C12
236 वाक्य
The 7 Quality Control (QC) Tools Explained with an Example!
Business EnglishUniversity StudentsWorking Adults
C11
443 वाक्य
Functional-Oriented Documentation in Automation - Eplan & IEC 81346 Explained
Business EnglishUniversity StudentsWorking Adults
C11
120 वाक्य
Learn Data Modeling in 8 minutes: Dimensional Data Modeling, Data Vault, and One Big Table
Business EnglishUniversity StudentsWorking Adults
C12
43 वाक्य
SDLC Vs STLC: Software Development Life Cycle and Software Testing Life Cycle
Business EnglishUniversity StudentsWorking Adults
B22
35 वाक्य
How to Use the Socratic Method (for Dialogue, Debate and Critical Thinking)
Business EnglishUniversity StudentsWorking Adults
C12
100 वाक्य
How to Answer Situational Questions for Product (PM) Behavioral Interview | Framework + Solution
Business EnglishInterview EnglishUniversity Students
C11
70 वाक्य
Ricardo Vargas Shows How to Implement Governance During Project Execution
Business EnglishUniversity StudentsWorking Adults
C11
745 वाक्य
WORK - HRM Lecture 08
Business EnglishUniversity StudentsWorking Adults
C149 वाक्य
Working as a Fire Protection Engineer - First Six Months Experience
Business EnglishUniversity StudentsWorking Adults
इस पाठ की शब्दावली और बोलने के सुझाव
इस वीडियो में शैडोइंग के लिए 84 वाक्य और 1171 शब्द हैं। बोला गया हिस्सा 7:25 लंबा है। वक्ता लगभग 158 शब्द प्रति मिनट की स्वाभाविक गति से बोलता है, जो रोज़मर्रा की बातचीत के करीब है। 90% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं; बाकी शब्द अभ्यास से पहले देख लेना अच्छा रहेगा।
इस वीडियो की मुख्य शब्दावली
वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:
| शब्द | उच्चारण | अर्थ |
|---|---|---|
| solve क्रिया | /sɒlv/ | सुलझाना, हल करना |
| filter संज्ञा | /ˈfɪltɚ/ | फ़िल्टर, साफी |
| complaint संज्ञा | /kəmˈpleɪnt/ | उलहना, शिकायत |
| inspection संज्ञा | /ɪnˈspɛkʃən/ | निरीक्षण, जाँच |
| adequate विशेषण | /ˈæd.ə.kwɪt/ | पर्याप्त |
| verify क्रिया | /ˈvɛɹɪfaɪ/ | परखना, जाँचना |
| diagram संज्ञा | /ˈdaɪ.ə.ɡɹæm/ | आलेख, मापचित्र |
| defect संज्ञा | /ˈdiːfɛkt/ | दोष, खोट |
| lesson संज्ञा | /ˈlɛs.ən/ | पाठ, सबक़ |
| assessment संज्ञा | /əˈsɛsmənt/ | निर्धारण, मूल्यांकन |
| discipline संज्ञा | /ˈdɪsəplɪn/ | अनुशासन |
| nail संज्ञा | /neɪl/ | नाख़ुन, नख |
| logical विशेषण | /ˈlɑd͡ʒɪkəl/ | तार्किक |
| transparent विशेषण | /tɹænsˈpæɹənt/ | पारदर्शक, पारदर्शी |
| continuously क्रिया विशेषण | /kənˈtɪnjuəsli/ | लगातार, निरंतर |
ध्यान देने योग्य उच्चारण
वक्ता 4 बार संक्षिप्त रूपों का प्रयोग करता है, जैसे don't, you're। इन्हें वैसे ही छोटा बोलें जैसा आप सुनते हैं।
- “th” की ध्वनियाँ: gather /ˈɡæðɚ/, methodology /ˌmɛθ.əˈdɑ.lə.d͡ʒi/
- “sh” और “zh” की ध्वनियाँ: inspection /ɪnˈspɛkʃən/, efficient /ɪˈfɪʃənt/, dissatisfaction /dɪsˌsætɪsˈfækʃən/
- लंबे शब्द — बलाघात सही रखें: 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/
इस वीडियो से अभ्यास कैसे करें
- पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
- 0.75× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
- अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर solve, filter, complaint जैसे शब्दों पर ध्यान दें।
इस वीडियो का व्याकरण
वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:
| संरचना | वीडियो में |
|---|---|
| Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है | have identified · have defined · have not identified |
| Relative clauses who / which + उपवाक्य — व्यक्ति या वस्तु के बारे में अतिरिक्त जानकारी | four, which is · seven, which is |
शैडोइंग तकनीक क्या है?
शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।