쉐도잉 연습: NPI Process 2: New Product Development Process (Why Planning Before Prototyping Saves Time) - 영상으로 영어 말하기 배우기

레슨 만드는 중...
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.

이 비디오는 누구를 위한 것인가?

영어 회화 연습을 통해 비즈니스 용어나 프로세스 설명 능력을 키우고자 하는 중급 이상 학습자에게 적합합니다. 특히 IELTS 스피킹 준비나 실무에서 기술적 내용을 명확히 전달해야 하는 경우, 이 비디오의 논리적 구조와 구체적인 예시는 큰 도움이 됩니다. 짧은 시간에 프로토타이핑 과정의 중요성을 설명하는 대화를 분석하며, 실제 회화에서 필요한 체계적인 표현 방식을 익힐 수 있습니다.

빼놓을 수 없는 단어와 관용구

  • Recipe for (something): ~하기 위한 방법. "Recipe for a lot of trial and error"는 "많은 시행착오를 겪게 되는 방법"으로 번역됩니다.
  • Go back to square one: 처음부터 다시 시작하다. 프로젝트가 실패했을 때 자주 사용되는 표현입니다.
  • Shoestring budget: 아주 적은 예산. "Development on a shoestring budget"은 "적은 예산으로 개발하다"입니다.
  • Over-engineered: 과도하게 설계된. 제품이 필요 이상으로 복잡할 때 사용됩니다.

어떻게 발음을 제대로 익힐까?

이 비디오의 스피커는 명료한 미국식 발음을 사용하며, 강조하고자 하는 부분에서 조금 더 높은 톤과 긴 강세를 사용합니다. shadowspeak 또는 영어 쉐도잉 연습을 할 때는 다음 점을 주의하세요. 먼저 "compliance" (규정 준수)와 "reliability" (신뢰성)와 같은 길고 어려운 단어는 음절을 분리하여 발음하세요. "com-pli-ance"처럼 3개의 음절로 나누어 연습하면 자연스러워집니다. 둘째, "What is the design intent?"와 같은 질문형 문장에서는 끝 부분을 올리지 않고, 설명하는 구간에서는 평평한 톤을 유지하여 논리적 흐름을 강조합니다. 쉐도잉을 할 때는 스피커의 말속도와 강세를 정확히 따라하며, 특히 "as good as an Apple product"와 같이 구체적인 비교를 하는 표현은 명확하게 발음하여 의미를 전달해야 합니다. 이렇게 연습하면 실제 회화에서도 기술적 내용을 명확히 전달할 수 있는 능력이 향상됩니다.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →