2020.01.22
英文メールの書き方：新メンバーに現状を説明する
こんなシチュエーション、お仕事でありませんか？
プロジェクトに途中参加した新メンバーに、プロジェクトの現状を共有したい。
英文メールで「新メンバーに現状を説明する」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
ジャスティン、
プロジェクト完了おめでとうございます！もうあの件について苦心することがなくなって安心しているかと思います。
そこで今回参加いただくプロジェクトについて苦心していただければと思いますので、詳細を共有させてください。23日の木曜日の14:00にミーティングを設定させていただきました。
本件のスケジュールや現状についてお話しできればと思います。
地獄までご一緒していただけると思うとうれしいです！
———————
今後の仕事での英語メールの参考になれば幸いです。
【動画内の”CC”ボタンをクリックして英語字幕を表示！】
【過去の動画を見るにはYoutubeページへ！Subscribe！】
0:00:04.549,0:00:10.080
Hello everyone. Welcome to E-mail Picks. Did you get to see snow last weekend? It was
0:00:10.080,0:00:14.880
just for a few minutes but it was the
first time to see snow this year here in
0:00:14.880,0:00:19.890
Tokyo. Anyway, one of my colleagues has
just finished a project he was working
0:00:19.890,0:00:24.630
on for a long time. So that's great, and
in our last department meeting, he was
0:00:24.630,0:00:29.970
told to join my project. A project I've
been working on for a long time. And of
0:00:29.970,0:00:34.200
course he's been given general
information about the project since
0:00:34.200,0:00:36.570
before but now that he's a project
member,
0:00:36.570,0:00:41.250
he needs details. So today, I figured I
should set up a meeting with him to go
0:00:41.250,0:00:46.800
over the objectives, the schedule, and the
tasks to be done for our project. So
0:00:46.800,0:00:52.440
here's the e-mail that I'm gonna write. Hi
Justin, Congratulations on completing
0:00:52.440,0:00:55.980
your project! You must be relieved that
you don't have to worry about it anymore.
0:00:55.980,0:01:00.300
So let me give you details on another
project you can worry about. I have
0:01:00.300,0:01:04.799
scheduled a meeting with you on Thursday the 23rd at 2 p.m. Let's go over the
0:01:04.799,0:01:06.640
schedule and status of the project
together.
0:01:06.640,0:01:10.080
Thanks for accompanying me on this journey to slow death! Kyota
0:01:10.080,0:01:14.070
So I started the e-mail by congratulating
my colleague on his most recent
0:01:14.070,0:01:20.100
accomplishment. And then, I invited him to worry together about our project. In the
0:01:20.100,0:01:24.210
next paragraph, I communicated the date
and time of our meeting, and then I closed
0:01:24.210,0:01:28.829
the e-mail with a little joke. I wrote
"Thanks for accompanying me on this journey
0:01:28.829,0:01:32.790
to slow death!" so that it gives the
impression that this project is not
0:01:32.790,0:01:38.490
going so well or not going well at all.
The reality is, there's no big problem.
0:01:38.490,0:01:43.290
But if I set Justin's expectations low,
then he'll probably feel good about
0:01:43.290,0:01:48.659
joining this project once he finds out
it's actually going very well. So there
0:01:48.659,0:01:52.229
you go. An e-mail to fill a colleague in about a project he just
0:01:52.229,0:01:57.210
joined. It's going to be a tough project
but now that I have some company. I''ll be all
0:01:57.210,0:02:02.000
right. So thank you for watching and I'll
see you next week.
Hello everyone. Welcome to E-mail Picks. Did you get to see snow last weekend? It was
0:00:10.080,0:00:14.880
just for a few minutes but it was the
first time to see snow this year here in
0:00:14.880,0:00:19.890
Tokyo. Anyway, one of my colleagues has
just finished a project he was working
0:00:19.890,0:00:24.630
on for a long time. So that's great, and
in our last department meeting, he was
0:00:24.630,0:00:29.970
told to join my project. A project I've
been working on for a long time. And of
0:00:29.970,0:00:34.200
course he's been given general
information about the project since
0:00:34.200,0:00:36.570
before but now that he's a project
member,
0:00:36.570,0:00:41.250
he needs details. So today, I figured I
should set up a meeting with him to go
0:00:41.250,0:00:46.800
over the objectives, the schedule, and the
tasks to be done for our project. So
0:00:46.800,0:00:52.440
here's the e-mail that I'm gonna write. Hi
Justin, Congratulations on completing
0:00:52.440,0:00:55.980
your project! You must be relieved that
you don't have to worry about it anymore.
0:00:55.980,0:01:00.300
So let me give you details on another
project you can worry about. I have
0:01:00.300,0:01:04.799
scheduled a meeting with you on Thursday the 23rd at 2 p.m. Let's go over the
0:01:04.799,0:01:06.640
schedule and status of the project
together.
0:01:06.640,0:01:10.080
Thanks for accompanying me on this journey to slow death! Kyota
0:01:10.080,0:01:14.070
So I started the e-mail by congratulating
my colleague on his most recent
0:01:14.070,0:01:20.100
accomplishment. And then, I invited him to worry together about our project. In the
0:01:20.100,0:01:24.210
next paragraph, I communicated the date
and time of our meeting, and then I closed
0:01:24.210,0:01:28.829
the e-mail with a little joke. I wrote
"Thanks for accompanying me on this journey
0:01:28.829,0:01:32.790
to slow death!" so that it gives the
impression that this project is not
0:01:32.790,0:01:38.490
going so well or not going well at all.
The reality is, there's no big problem.
0:01:38.490,0:01:43.290
But if I set Justin's expectations low,
then he'll probably feel good about
0:01:43.290,0:01:48.659
joining this project once he finds out
it's actually going very well. So there
0:01:48.659,0:01:52.229
you go. An e-mail to fill a colleague in about a project he just
0:01:52.229,0:01:57.210
joined. It's going to be a tough project
but now that I have some company. I''ll be all
0:01:57.210,0:02:02.000
right. So thank you for watching and I'll
see you next week.
