2019.10.30
英文メールの書き方：業務フローを確認する
こんなシチュエーション、お仕事でありませんか？
プロジェクトの業務フローについて同僚と認識が合っているか確認したい。
英文メールで「業務フローを確認する」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
ユミさん、
今回のプロジェクトの業務フローについて私の認識が合っているか確認させてください。今後以下の手順で進めていく予定でしょうか
1. Justinと詳細のすり合わせ
2. 部内で企画をプレゼン、承認を得る
3. 全関連部署との会議にて企画を共有、意見交換
4. 企画を修正・改善し、部内で再度プレゼン
何か変更すべき点などお気づきになったら教えてください。
———————
今後の仕事での英語メールの参考になれば幸いです。
【動画内の”CC”ボタンをクリックして英語字幕を表示！】
【過去の動画を見るにはYoutubeページへ！Subscribe！】
0:00:04.220,0:00:09.450
Hello everyone. Welcome to E-mail Picks.
Lately, I've been entrusting some
0:00:09.450,0:00:14.219
projects to my junior colleagues and
through that, I'm learning how to
0:00:14.219,0:00:19.230
delegate, or assign tasks better. But it
usually doesn't go well the first time
0:00:19.230,0:00:24.840
because I need to really get to know
what each person is good at and not good
0:00:24.840,0:00:28.680
at, and then think of the best way to
have them work together. Now I've asked
0:00:28.680,0:00:32.610
my junior colleague Yumi to become
the project manager of one of our newer
0:00:32.610,0:00:37.829
projects. That means she is supposed to
make sure the project moves forward. But
0:00:37.829,0:00:43.290
this is her first time doing this, so she
may not be 100% sure of the steps we
0:00:43.290,0:00:47.340
need to take in order to complete this
project. So today, I'd like to write to
0:00:47.340,0:00:54.300
her to confirm the project workflow. Here
goes. Hi Yumi, Let me confirm if my
0:00:54.300,0:00:58.320
understanding of the workflow is the
same as yours. Are the steps below our
0:00:58.320,0:01:03.210
plan in the coming weeks? 1. Meet with
Justin to settle details. 2. Propose the
0:01:03.210,0:01:07.380
plan in our department and get approval.
3. Have a meeting with all the relevant
0:01:07.380,0:01:11.970
departments to share the plan and get
input. 4. Revise the plan and propose it in
0:01:11.970,0:01:15.390
our department again. Let me know if
there is anything you think should be
0:01:15.390,0:01:21.210
changed. Kyota. OK, so I went straight
into the main point: "Let me confirm if my
0:01:21.210,0:01:26.070
understanding is the same as yours."
And then I listed out the steps in the
0:01:26.070,0:01:30.180
workflow that I have in mind. So
basically, the part of the project
0:01:30.180,0:01:35.490
workflow I'm confirming with Yumi here
is refining of the plan. We need expert
0:01:35.490,0:01:38.759
knowledge and also different
perspectives to see if there is any room
0:01:38.759,0:01:43.590
for improvement in the plan. At least
this is the basic project workflow we
0:01:43.590,0:01:48.659
follow here at our company. So there you
go. An e-mail to confirm the workflow of a
0:01:48.659,0:01:54.780
project. My junior colleagues learn very
quickly so I'm hoping they'll acquire
0:01:54.780,0:01:58.229
new skills through this project. Anyway,
that's it for today. Thank you for
0:01:58.229,0:02:01.520
watching and I'll see you next week.
Hello everyone. Welcome to E-mail Picks.
Lately, I've been entrusting some
0:00:09.450,0:00:14.219
projects to my junior colleagues and
through that, I'm learning how to
0:00:14.219,0:00:19.230
delegate, or assign tasks better. But it
usually doesn't go well the first time
0:00:19.230,0:00:24.840
because I need to really get to know
what each person is good at and not good
0:00:24.840,0:00:28.680
at, and then think of the best way to
have them work together. Now I've asked
0:00:28.680,0:00:32.610
my junior colleague Yumi to become
the project manager of one of our newer
0:00:32.610,0:00:37.829
projects. That means she is supposed to
make sure the project moves forward. But
0:00:37.829,0:00:43.290
this is her first time doing this, so she
may not be 100% sure of the steps we
0:00:43.290,0:00:47.340
need to take in order to complete this
project. So today, I'd like to write to
0:00:47.340,0:00:54.300
her to confirm the project workflow. Here
goes. Hi Yumi, Let me confirm if my
0:00:54.300,0:00:58.320
understanding of the workflow is the
same as yours. Are the steps below our
0:00:58.320,0:01:03.210
plan in the coming weeks? 1. Meet with
Justin to settle details. 2. Propose the
0:01:03.210,0:01:07.380
plan in our department and get approval.
3. Have a meeting with all the relevant
0:01:07.380,0:01:11.970
departments to share the plan and get
input. 4. Revise the plan and propose it in
0:01:11.970,0:01:15.390
our department again. Let me know if
there is anything you think should be
0:01:15.390,0:01:21.210
changed. Kyota. OK, so I went straight
into the main point: "Let me confirm if my
0:01:21.210,0:01:26.070
understanding is the same as yours."
And then I listed out the steps in the
0:01:26.070,0:01:30.180
workflow that I have in mind. So
basically, the part of the project
0:01:30.180,0:01:35.490
workflow I'm confirming with Yumi here
is refining of the plan. We need expert
0:01:35.490,0:01:38.759
knowledge and also different
perspectives to see if there is any room
0:01:38.759,0:01:43.590
for improvement in the plan. At least
this is the basic project workflow we
0:01:43.590,0:01:48.659
follow here at our company. So there you
go. An e-mail to confirm the workflow of a
0:01:48.659,0:01:54.780
project. My junior colleagues learn very
quickly so I'm hoping they'll acquire
0:01:54.780,0:01:58.229
new skills through this project. Anyway,
that's it for today. Thank you for
0:01:58.229,0:02:01.520
watching and I'll see you next week.
