Shadowing Practice: NPI Process 2: New Product Development Process (Why Planning Before Prototyping Saves Time) - Learn English Speaking with Video

Les maken...
1
Hi this is Renan Joran
2
and I keep going with this series about the new product
3
introduction process here I'm covering the time spent in planning before starting prototyping work
4
so have a lot of clients come to us
5
and they say here's our product design idea maybe a sketch
6
may be very crude prototype please build a prototype ASAP well
7
what we found is this is really a recipe for a lot of trial
8
and error and sometimes going back and wasting a lot of time
9
so first product testing what will be required for compliance
10
and for reliability also of the product in the field we
11
need to know this from the very beginning we've had some cases where the client had not
12
thought of that and it was not clarified at the beginning
13
and then a lot of time was spent on doing design work on making prototypes
14
and then realizing that it would not be compliant
15
it means going back to square one that's a massive waste of time
16
so this is really something
17
that needs to be clarified from the very beginning um a lot of things need to be started from the beginning
18
okay here's an overall idea of the the process really of all this this planning
19
so first what is the design intent what does the designer
20
want to achieve with the product how is it supposed to be used in what circumstances with what objectives
21
and so on okay then if some design was already done by the inventor,
22
let's say, does a review, we can often find some potential issues.
23
Then really, what is possible in China?
24
Sometimes a design does not call for China manufacturing.
25
Is this really something that is a good fit for China?
26
Or maybe it's better done somewhere else?
27
Cost and compliance needs to be thought of from the beginning
28
if it looks like the cost of the widget is going to be ten dollars
29
but it's supposed to be sold on the market for eight
30
dollars there's a big problem okay think of the options propose
31
some options once things are a little bit clearer go into
32
the details of the design then work on the entire design and start work on the first prototype.
33
This is not a process that is applicable everywhere all the time
34
but this gives you an idea of a good process that's applicable to a lot of electronic and all mechanical products. So
35
if we think of a checklist for this initial planning before
36
prototyping what would it be first as i say design intent
37
has to be very clear everybody needs to grasp what it is okay
38
if a product supposed to be used outdoor
39
but this is not documented anywhere maybe the project manager knows about it
40
but then the purchaser doesn't know about it
41
and then the supplier is not going to know about it
42
and they're going to use materials
43
that are the raw materials it's just an example okay requirements need to be very specific okay
44
If you say the finishing has to be as good as an Apple product, this means something.
45
But if you say very high-end level of finishing, it doesn't mean very much.
46
Sometimes the inventor, the designer thinks of something that's really over-engineered.
47
But this doesn't make sense usually for a first version,
48
especially if you are doing the development of a shoestring budget and if the timelines call for a very fast go-to-market.
49
I already expanded on this,
50
but we need to be realistic what kind of product design will allow you to be done within your budget
51
and within your timelines.
52
China manufacturing yes no sometimes again it doesn't call for China manufacturing is not a good fit
53
so this needs to be thought about also verification
54
and validation two very important keywords here for quality management
55
and I'm mentioning this here because it needs to be planned from the beginning
56
so verification okay objective tests that will have to be passed by the prototype.
57
If a prototype is made but does not pass these objective tests, it does not pass the verification, it doesn't count.
58
The prototype cannot be verified and confirmed.
59
Similarly, when the end users play with the prototype,
60
give their feedback, often very subjective,
61
it feels right, it operates right it's got a good feeling in the hand these kind of things
62
if it passes then it's fine it's good
63
if it doesn't pass it doesn't count okay
64
but this needs to be communicated from the beginning because again
65
if the engineers don't know about this how can he make a prototype
66
that passes these requirements and the last concept I want to touch on is the feasibility study
67
if it's a new product there will be some challenging aspects
68
okay maybe it's a very new application of a new technology maybe the engineering team is not familiar with
69
that kind of applications.
70
Okay, do a feasibility study, sometimes it will pass, it will go through a proof of concept prototype,
71
sometimes maybe on CAD software, you know, ProEngineer and the others,
72
do some simulations to see if it falls down, is it a shock like this, or if there's a torsion force,
73
is it going to break easily, and so on.
74
And also, sometimes some further design work is needed just to see a little bit more clearly into the design
75
and really what will the product look like and how will it work.
76
It's not just technical risks.
77
If you are the company that wants to design and develop a new product,
78
always keep in mind the market risk is what kills most startups okay you might make something
79
that works very well but that people are not ready to buy
80
or maybe not buy for that kind of price
81
so it might make sense to make what they call an MVP in the lean startup approach by the way
82
if you haven't read this book
83
I would advise you you grab a copy it will help
84
you think of what what the first version of your product should be
85
and how to discover what your key users typical users really need
86
and want to buy okay so a lot of planning here and and poor planning will lead to a failed project.
87
So take this very seriously.
88
Okay, that's the end of this video.
89
I hope you like it.
90
Don't hesitate to subscribe, leave some comment, ask some questions.
91
Thank you.

Woordenschat en spreektips bij deze les

Deze spreekles op niveau C1 is gebaseerd op de video “NPI Process 2: New Product Development Process”. Deze woorden komen het vaakst terug: product, design, prototype, beginning, planning. Deze video bevat 91 zinnen en 1096 woorden om na te spreken. Het gesproken deel duurt 7:42. De spreker praat in een gelijkmatig tempo van ongeveer 142 woorden per minuut, prettig om te shadowen. 87% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden; de rest kun je beter vooraf bekijken.

Belangrijke woorden in deze video

De 15 moeilijkste woorden uit de video, met uitspraak en betekenis:

WoordUitspraakBetekenis
prototype zelfstandig naamwoord/ˈpɹəʊtətaɪp/prototype
feasibility zelfstandig naamwoord/ˌfiːzɪˈbɪlɪti/haalbaarheid
inventor zelfstandig naamwoord/ɪnˈvɛntɚ/uitvinder
startup zelfstandig naamwoord/ˈstɑɹtˌʌp/opstart, opstarting
clarify werkwoord/ˈklæɹ.ɪ.faɪ/klaren
checklist zelfstandig naamwoord/ˈt͡ʃɛklɪst/afvinklijst, controlelijst
compliant bijvoeglijk naamwoord/kəmˈplaɪənt/buigzaam, medewerkend
keyword zelfstandig naamwoord/ˈkiː.wɜːd/sleutelwoord
purchaser zelfstandig naamwoordkoper, koopster
widget zelfstandig naamwoord/ˈwɪd͡ʒ.ɪt/dingetje, prul
circumstance zelfstandig naamwoord/ˈsɝ.kəmˌstæns/omstandigheid
validation zelfstandig naamwoord/ˌvæl.əˈdeɪ.ʃən/validering
subjective bijvoeglijk naamwoord/səbˈd͡ʒɛktɪv/subjectief
hesitate werkwoord/ˈhɛz.ə.teɪt/aarzelen
supplier zelfstandig naamwoord/səˈplaɪə/leverancier

Phrasal verbs die je zult horen

WoordUitspraakBetekenis
fall down werkwoord/fɔl ˈdaʊn/neervallen
go back werkwoordteruggaan

Uitspraak om op te letten

De spreker gebruikt 14 samentrekkingen en verkorte vormen, zoals doesn't, don't, I'm. Spreek ze kort uit, zoals je ze hoort.

  • De klanken “sh” en “zh”: verification /ˌvɛ.ɹə.fɪˈkeɪ.ʃən/, shoestring /ˈʃustɹɪŋ/, torsion /ˈtor.ʃɪn/, validation /ˌvæl.əˈdeɪ.ʃən/, simulation /ˌsɪm.jəˈleɪ.ʃn̩/
  • Lange woorden — let op de klemtoon: verification /ˌvɛ.ɹə.fɪˈkeɪ.ʃən/, feasibility /ˌfiːzɪˈbɪlɪti/, validation /ˌvæl.əˈdeɪ.ʃən/

Klanken die Nederlandstaligen lastig vinden:

  • Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: keyword /ˈkiː.wɜːd/, subjective /səbˈd͡ʒɛktɪv/, propose /pɹəˈpəʊz/, crude /kɹuːd/, subscribe /səbˈskɹaɪb/
  • /æ/ — opener dan de Nederlandse “e”: clarify /ˈklæɹ.ɪ.faɪ/, circumstance /ˈsɝ.kəmˌstæns/, validation /ˌvæl.əˈdeɪ.ʃən/, grasp /ɡɹæsp/
  • /w/ — met ronde lippen: keyword /ˈkiː.wɜːd/, widget /ˈwɪd͡ʒ.ɪt/

Zo oefen je met deze video

  1. Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
  2. Spreek zin voor zin na op normale snelheid en herhaal elke zin tot je ritme gelijk is aan dat van de spreker.
  3. Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als prototype, feasibility, inventor.

Wat is de Shadowing-techniek?

Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.

Shadowing-techniek: lees de volledige stap-voor-stap-gids →