2018.02.21
英文メールの書き方：上長に企画提案の機会を請う
こんなシチュエーション、お仕事でありませんか？
会社の課題を解決するため、企画を練りました。上長にプレゼンさせてもらいたい。メールで提案の機会をもらえないか聞いてみよう。
英語メールで「上長に企画提案の機会を請う」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
トラヴィスさん、
前回の全体会議で検討が先送りになっていた戦略の問題点に関して、ご提案があります。
問題の解決案が思い浮かびましたので、たたき台を作り、関連する全部署に意見を伺いました。
来週のご都合の良い時間に企画提案の機会をいただけませんでしょうか？
———————
今後の仕事での英語メールの参考になれば幸いです。
【動画内の”CC”ボタンをクリックして英語字幕を表示！】
【過去の動画を見るにはYoutubeページへ！Subscribe！】
0:00:04.970,0:00:10.200
Hi everyone, welcome to E-mail Picks. I hope
you're all doing well. Here at Bizmates,
0:00:10.200,0:00:16.020
we have a general meeting once a week to
discuss any pressing issues or share any
0:00:16.020,0:00:21.029
interesting ideas. Everyone needs to join
this meeting no matter what department
0:00:21.029,0:00:25.859
you work for. So, in our last general
meeting, there was a presentation on one
0:00:25.859,0:00:29.910
of our business strategies and it
sounded really good until the Q&A
0:00:29.910,0:00:35.690
session. During Q&A, someone pointed out a
critical problem in the strategy. That
0:00:35.690,0:00:42.570
problem was pretty big and no one
could figure out how to fix it. Then time
0:00:42.570,0:00:48.030
was up, so we had to end the meeting and
the issue was left up in the air. "Up in
0:00:48.030,0:00:53.460
the air" means not decided, so basically
we ended the meeting without making any
0:00:53.460,0:00:57.270
decisions on what to do with that
problem. You know, I thought a lot about
0:00:57.270,0:01:02.910
it. I discussed the problem with many
colleagues and a few days ago, I came up
0:01:02.910,0:01:08.580
with a solution, so then I shared the
idea with my colleagues again, got their
0:01:08.580,0:01:14.189
feedback, made some changes to the idea
and finally, I was able to make a
0:01:14.189,0:01:20.759
proposal. Now I want to give the proposal
to a person with authority. Travis is the
0:01:20.759,0:01:25.350
head of our business planning department
and I got permission from my boss to
0:01:25.350,0:01:28.590
talk to him. So now I'm ready to write
him an e-mail.
0:01:28.590,0:01:33.869
So in this e-mail, I need to do two things:
number one, I need to make sure Travis
0:01:33.869,0:01:38.369
understands that this is not just an
idea that popped up in my head right now.
0:01:38.369,0:01:44.100
It's a very well-planned proposal; and
number two, I want to set a meeting date
0:01:44.100,0:01:50.490
to go over my proposal.
Alright so here goes: Hi Travis,
0:01:50.490,0:01:54.990
this concerns the problem in our
strategy, which was left up in the air in
0:01:54.990,0:01:59.549
the last general meeting. I believe I
have come up with a way to resolve this
0:01:59.549,0:02:03.990
issue. I have put my idea to the test by
asking for feedback from all the
0:02:03.990,0:02:08.069
departments that are involved. As a
result, I have gained enough confidence
0:02:08.069,0:02:11.920
to put together a proposal. Could you
please spare some time to listen to my
0:02:11.920,0:02:17.770
proposal next week? Please let me know if that
will be possible. Kyota. OK so in the
0:02:17.770,0:02:22.420
first paragraph, I'm reminding Travis
about the bitter general meeting we had
0:02:22.420,0:02:27.520
last week. In the second paragraph, I'm
saying that I have gathered opinions
0:02:27.520,0:02:33.760
from all our departments, so this idea is
not just my idea. In this case, I "put my
0:02:33.760,0:02:38.530
idea to the test" means that I asked
everyone for their opinion on how good
0:02:38.530,0:02:44.110
or bad the idea was. And lastly, I'm
asking Travis if we could set up a
0:02:44.110,0:02:47.260
meeting to go over my proposal. So there
we go,
0:02:47.260,0:02:52.239
an e-mail to ask a supervisor for a
chance to make a proposal. If Travis
0:02:52.239,0:02:58.150
declines the idea, that's okay, I'll just
make revisions to it and ask for another
0:02:58.150,0:03:03.220
chance to make the proposal and continue
this cycle until we have a good solution,
0:03:03.220,0:03:06.519
so wish me luck. Thank you for watching
and I'll see you next week.
Hi everyone, welcome to E-mail Picks. I hope
you're all doing well. Here at Bizmates,
0:00:10.200,0:00:16.020
we have a general meeting once a week to
discuss any pressing issues or share any
0:00:16.020,0:00:21.029
interesting ideas. Everyone needs to join
this meeting no matter what department
0:00:21.029,0:00:25.859
you work for. So, in our last general
meeting, there was a presentation on one
0:00:25.859,0:00:29.910
of our business strategies and it
sounded really good until the Q&A
0:00:29.910,0:00:35.690
session. During Q&A, someone pointed out a
critical problem in the strategy. That
0:00:35.690,0:00:42.570
problem was pretty big and no one
could figure out how to fix it. Then time
0:00:42.570,0:00:48.030
was up, so we had to end the meeting and
the issue was left up in the air. "Up in
0:00:48.030,0:00:53.460
the air" means not decided, so basically
we ended the meeting without making any
0:00:53.460,0:00:57.270
decisions on what to do with that
problem. You know, I thought a lot about
0:00:57.270,0:01:02.910
it. I discussed the problem with many
colleagues and a few days ago, I came up
0:01:02.910,0:01:08.580
with a solution, so then I shared the
idea with my colleagues again, got their
0:01:08.580,0:01:14.189
feedback, made some changes to the idea
and finally, I was able to make a
0:01:14.189,0:01:20.759
proposal. Now I want to give the proposal
to a person with authority. Travis is the
0:01:20.759,0:01:25.350
head of our business planning department
and I got permission from my boss to
0:01:25.350,0:01:28.590
talk to him. So now I'm ready to write
him an e-mail.
0:01:28.590,0:01:33.869
So in this e-mail, I need to do two things:
number one, I need to make sure Travis
0:01:33.869,0:01:38.369
understands that this is not just an
idea that popped up in my head right now.
0:01:38.369,0:01:44.100
It's a very well-planned proposal; and
number two, I want to set a meeting date
0:01:44.100,0:01:50.490
to go over my proposal.
Alright so here goes: Hi Travis,
0:01:50.490,0:01:54.990
this concerns the problem in our
strategy, which was left up in the air in
0:01:54.990,0:01:59.549
the last general meeting. I believe I
have come up with a way to resolve this
0:01:59.549,0:02:03.990
issue. I have put my idea to the test by
asking for feedback from all the
0:02:03.990,0:02:08.069
departments that are involved. As a
result, I have gained enough confidence
0:02:08.069,0:02:11.920
to put together a proposal. Could you
please spare some time to listen to my
0:02:11.920,0:02:17.770
proposal next week? Please let me know if that
will be possible. Kyota. OK so in the
0:02:17.770,0:02:22.420
first paragraph, I'm reminding Travis
about the bitter general meeting we had
0:02:22.420,0:02:27.520
last week. In the second paragraph, I'm
saying that I have gathered opinions
0:02:27.520,0:02:33.760
from all our departments, so this idea is
not just my idea. In this case, I "put my
0:02:33.760,0:02:38.530
idea to the test" means that I asked
everyone for their opinion on how good
0:02:38.530,0:02:44.110
or bad the idea was. And lastly, I'm
asking Travis if we could set up a
0:02:44.110,0:02:47.260
meeting to go over my proposal. So there
we go,
0:02:47.260,0:02:52.239
an e-mail to ask a supervisor for a
chance to make a proposal. If Travis
0:02:52.239,0:02:58.150
declines the idea, that's okay, I'll just
make revisions to it and ask for another
0:02:58.150,0:03:03.220
chance to make the proposal and continue
this cycle until we have a good solution,
0:03:03.220,0:03:06.519
so wish me luck. Thank you for watching
and I'll see you next week.
