2018.11.14
英文メールの書き方：仕事の進め方の変更を提案する
こんなシチュエーション、お仕事でありませんか？
プロジェクトがうまく続かず、時間ばかりが過ぎていきます。仕事の進め方を変えなければとても期日に間に合いません。プロジェクトマネージャーにメールで変更を提案したい。
英文メールで「仕事の進め方の変更を提案する」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
ポールさん、
前回の提案についてはうまく行かず、残念でしたね。この調子だと商品を予定通り発売できないのではないかと心配しています。
プロジェクトをより円滑に進めるために、ひとつ提案させてください。次の会議まで待つだけの時間をあまり作らないように、定例会議を週一回ではなく、二回行うのはいかがでしょう？
より頻繁にコミュニケーションを取ることでプロジェクトの進捗と商品の質両方に良い効果があると思います。
———————
今後の仕事での英語メールの参考になれば幸いです。
【動画内の”CC”ボタンをクリックして英語字幕を表示！】
【過去の動画を見るにはYoutubeページへ！Subscribe！】
0:00:04.609,0:00:09.330
Hello everyone! Welcome to E-mail Picks.
I've been having a little problem with
0:00:09.330,0:00:15.540
my project lately. My team hasn't made
any progress for the past three weeks so
0:00:15.540,0:00:21.539
we can't move anything forward unless we
get approval from our president and we
0:00:21.539,0:00:26.430
tried to have a meeting every week to
plan the next proposal. But two weeks ago,
0:00:26.430,0:00:31.859
we made a proposal to the president,
which then got rejected. In the following
0:00:31.859,0:00:37.559
week, we discussed within our team and
revised the proposal. This week, we made a
0:00:37.559,0:00:42.570
proposal again, which unfortunately got
rejected again. So our team is going to
0:00:42.570,0:00:48.329
meet again next week and make a proposal
again the following week. You see...
0:00:48.329,0:00:52.379
everything gets pushed back two weeks
every time we get a rejection, so we're
0:00:52.379,0:00:55.829
losing too much time in this planning
stage, so we need to do something about
0:00:55.829,0:01:01.680
this. So my idea is to have two regular
meetings every week, then we can adjust
0:01:01.680,0:01:06.900
our plan more quickly and we can get
approval earlier. So I want to suggest
0:01:06.900,0:01:11.580
this idea to the project manager, Paul. So
let me show you what that e-mail will
0:01:11.580,0:01:17.189
look like: Paul, it's too bad our last
proposal didn't go so well. I'm concerned
0:01:17.189,0:01:20.939
that at this rate, it's likely that we
will not be able to launch the product
0:01:20.939,0:01:25.680
in time. I have a suggestion to help move
things forward more quickly. Do you think
0:01:25.680,0:01:29.040
it would be a good idea if we had a
regular meeting twice a week instead of
0:01:29.040,0:01:33.030
one so that we won't waste too much time
waiting for the next meeting to decide
0:01:33.030,0:01:37.590
on things? I feel that increasing the
frequency will do good for both speed
0:01:37.590,0:01:43.170
and quality. Let me know what you think.
Kyota. Okay so in the first paragraph, I'm
0:01:43.170,0:01:48.750
voicing my concern about not making
progress in our project. "At this rate"
0:01:48.750,0:01:53.820
means "at this pace" - there's no difference
in meaning. In the second paragraph, I'm
0:01:53.820,0:01:59.040
making the suggestion. I used a rather
indirect question to ask for Paul's
0:01:59.040,0:02:04.439
opinion. I wrote: "do you think it'll be a
good idea if...?" because I
0:02:04.439,0:02:08.569
don't want my message to sound like I am
forcing him to accept my suggestion. And
0:02:08.569,0:02:13.240
then I close the e-mail by requesting an
action. I wrote:
0:02:13.240,0:02:17.710
"Let me know what you think." This way Paul will
understand what action I'm expecting
0:02:17.710,0:02:22.480
from him after reading this e-mail.
So there you go, an e-mail to suggest a
0:02:22.480,0:02:27.520
change in approach. I'm not sure if
having more meetings is the solution but
0:02:27.520,0:02:31.870
I'm sure I can come up with a better
idea with Paul. So anyway that's it for
0:02:31.870,0:02:35.760
today. Thank you for watching and I'll
see you next week.
Hello everyone! Welcome to E-mail Picks.
I've been having a little problem with
0:00:09.330,0:00:15.540
my project lately. My team hasn't made
any progress for the past three weeks so
0:00:15.540,0:00:21.539
we can't move anything forward unless we
get approval from our president and we
0:00:21.539,0:00:26.430
tried to have a meeting every week to
plan the next proposal. But two weeks ago,
0:00:26.430,0:00:31.859
we made a proposal to the president,
which then got rejected. In the following
0:00:31.859,0:00:37.559
week, we discussed within our team and
revised the proposal. This week, we made a
0:00:37.559,0:00:42.570
proposal again, which unfortunately got
rejected again. So our team is going to
0:00:42.570,0:00:48.329
meet again next week and make a proposal
again the following week. You see...
0:00:48.329,0:00:52.379
everything gets pushed back two weeks
every time we get a rejection, so we're
0:00:52.379,0:00:55.829
losing too much time in this planning
stage, so we need to do something about
0:00:55.829,0:01:01.680
this. So my idea is to have two regular
meetings every week, then we can adjust
0:01:01.680,0:01:06.900
our plan more quickly and we can get
approval earlier. So I want to suggest
0:01:06.900,0:01:11.580
this idea to the project manager, Paul. So
let me show you what that e-mail will
0:01:11.580,0:01:17.189
look like: Paul, it's too bad our last
proposal didn't go so well. I'm concerned
0:01:17.189,0:01:20.939
that at this rate, it's likely that we
will not be able to launch the product
0:01:20.939,0:01:25.680
in time. I have a suggestion to help move
things forward more quickly. Do you think
0:01:25.680,0:01:29.040
it would be a good idea if we had a
regular meeting twice a week instead of
0:01:29.040,0:01:33.030
one so that we won't waste too much time
waiting for the next meeting to decide
0:01:33.030,0:01:37.590
on things? I feel that increasing the
frequency will do good for both speed
0:01:37.590,0:01:43.170
and quality. Let me know what you think.
Kyota. Okay so in the first paragraph, I'm
0:01:43.170,0:01:48.750
voicing my concern about not making
progress in our project. "At this rate"
0:01:48.750,0:01:53.820
means "at this pace" - there's no difference
in meaning. In the second paragraph, I'm
0:01:53.820,0:01:59.040
making the suggestion. I used a rather
indirect question to ask for Paul's
0:01:59.040,0:02:04.439
opinion. I wrote: "do you think it'll be a
good idea if...?" because I
0:02:04.439,0:02:08.569
don't want my message to sound like I am
forcing him to accept my suggestion. And
0:02:08.569,0:02:13.240
then I close the e-mail by requesting an
action. I wrote:
0:02:13.240,0:02:17.710
"Let me know what you think." This way Paul will
understand what action I'm expecting
0:02:17.710,0:02:22.480
from him after reading this e-mail.
So there you go, an e-mail to suggest a
0:02:22.480,0:02:27.520
change in approach. I'm not sure if
having more meetings is the solution but
0:02:27.520,0:02:31.870
I'm sure I can come up with a better
idea with Paul. So anyway that's it for
0:02:31.870,0:02:35.760
today. Thank you for watching and I'll
see you next week.
