2017.08.09
英文メールの書き方：資料を一読するようお願いする
こんなシチュエーション、お仕事でありませんか？
来週行う予定の重要な会議。大勢の参加者の意識合わせのために、資料が事前共有されました。
会議を有意義なものにするためには、参加者全員がこの資料を事前に目を通しておくことが肝心です。自分の部署内だけでも、資料の一読を徹底させないと！
英語メールで「資料を一読するようお願いする」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
商品開発部のみなさま、
先日お知らせがあったように、来週の月曜日に多部署合同でディスカッションが行われます。これは他部署とざっくばらんに対話できる貴重な機会になります。
管理部の赤城さんから事前共有資料が届いているかと思いますが、本会議に臨むにあたって効果的に意識合わせができるものとなっています。
必要な準備をしっかりして、ディスカッションを有意義なものにしましょう。
———————
今後の仕事での英語メールの参考になれば幸いです。
[動画内の”CC”ボタンをクリックして英語字幕を表示！]
Hi everyone! Welcome to E-mail Picks.
Today I'm feeling really good because there's
something very exciting coming up very soon.
Well our product development, sales,
marketing, IT, customer support and our
control department -- all our departments
are going to gather to have a
cross-functional discussion session.
What this means is basically we're going to
talk about our company's future all
together in one single room. This is very
exciting for me! Now although we already
work closely together, our understanding
of our company's current situation is
not the same because we work for
different departments, so Akagi-san of
our control department put together a
document that summarizes the company's
situation now. I read through it and
maybe it took only five minutes and it
was a very good summary. I'd like
everyone in my departments to read
through it before they go into
discussion because it will not be a good
use of time if we all start asking basic
questions like "how much profit do
we make last year?" or "how big is our
market?" You know those kind of things.
Again, this cross-functional discussion
session is a rare opportunity for us, we
don't want to waste any time so I'm
going to write an e-mail to remind
everyone to read that document once, but
you know in any company, there are people
who always read these kind of things and
also there are people who never read
these kind of things. So, in this e-mail
one important message
I'd like to communicate is the benefits
of reading the Akagi document, so
here I go:
Hello product development department,
as announced earlier, we will be holding a
cross-functional discussion meeting next
Monday. This will be a rare opportunity
for all departments to discuss together,
openly. Akagi-san of the control
department has sent us some great
background information.
This one-page document will help all of
us to be on the same page at the start
of the discussion and avoid those
embarrassing moments where you ask way-
too-basic questions. Let's do our part of
the homework and make the discussion a
productive one. Kyota. OK,
so the first thing I did was emphasized
the importance of the discussion session
by writing "this will be a rare
opportunity for all the departments to
discuss together, openly" and then I tried
to give a good reason to read the
document beforehand by writing "this
one-page document will help all of us to
be on the same page at the start of the
discussion." I also gave a little pressure
by writing that "we can avoid those
embarrassing moments where you ask way-too-basic questions." So, there you go
I hope that gives you an idea of how to
ask colleagues to read stuff. Anyway,
that's it for today, thank you for
watching and I'll see you next week.
Today I'm feeling really good because there's
something very exciting coming up very soon.
Well our product development, sales,
marketing, IT, customer support and our
control department -- all our departments
are going to gather to have a
cross-functional discussion session.
What this means is basically we're going to
talk about our company's future all
together in one single room. This is very
exciting for me! Now although we already
work closely together, our understanding
of our company's current situation is
not the same because we work for
different departments, so Akagi-san of
our control department put together a
document that summarizes the company's
situation now. I read through it and
maybe it took only five minutes and it
was a very good summary. I'd like
everyone in my departments to read
through it before they go into
discussion because it will not be a good
use of time if we all start asking basic
questions like "how much profit do
we make last year?" or "how big is our
market?" You know those kind of things.
Again, this cross-functional discussion
session is a rare opportunity for us, we
don't want to waste any time so I'm
going to write an e-mail to remind
everyone to read that document once, but
you know in any company, there are people
who always read these kind of things and
also there are people who never read
these kind of things. So, in this e-mail
one important message
I'd like to communicate is the benefits
of reading the Akagi document, so
here I go:
Hello product development department,
as announced earlier, we will be holding a
cross-functional discussion meeting next
Monday. This will be a rare opportunity
for all departments to discuss together,
openly. Akagi-san of the control
department has sent us some great
background information.
This one-page document will help all of
us to be on the same page at the start
of the discussion and avoid those
embarrassing moments where you ask way-
too-basic questions. Let's do our part of
the homework and make the discussion a
productive one. Kyota. OK,
so the first thing I did was emphasized
the importance of the discussion session
by writing "this will be a rare
opportunity for all the departments to
discuss together, openly" and then I tried
to give a good reason to read the
document beforehand by writing "this
one-page document will help all of us to
be on the same page at the start of the
discussion." I also gave a little pressure
by writing that "we can avoid those
embarrassing moments where you ask way-too-basic questions." So, there you go
I hope that gives you an idea of how to
ask colleagues to read stuff. Anyway,
that's it for today, thank you for
watching and I'll see you next week.
