< Return to Video

Business English Writing Lesson for ESL - ET 04: Bad News Messages

  • 0:00 - 0:01
  • 0:01 - 0:03
    [TOOLS WHIRRING]
  • 0:03 - 0:05
  • 0:05 - 0:07
    ANNOUNCER: Welcome
    to Email Tune-Up,
  • 0:07 - 0:11
    the video podcast to help you
    improve your business writing.
  • 0:11 - 0:16
  • 0:16 - 0:18
    PROFESSOR: Now, here,
    we have a short email
  • 0:18 - 0:23
    from Jenny, who is responsible
    for her company's IT services.
  • 0:23 - 0:26
    She's written this email to give
    her colleagues some bad news.
  • 0:26 - 0:29
    The office email server
    will be down later today
  • 0:29 - 0:32
    because of some
    technical problems.
  • 0:32 - 0:34
    When a server goes
    down, it means
  • 0:34 - 0:38
    that it has been taken offline
    or down for maintenance
  • 0:38 - 0:40
    or because of a problem.
  • 0:40 - 0:44
    Before we look at the mechanics,
    style, and tone of this message,
  • 0:44 - 0:46
    let's talk a little
    bit about the best way
  • 0:46 - 0:49
    to deliver bad news in an email.
  • 0:49 - 0:52
    When you're writing to
    someone outside your company,
  • 0:52 - 0:55
    it's a good idea to
    use an indirect style,
  • 0:55 - 0:58
    although you should also make
    sure your reader understands
  • 0:58 - 1:01
    and accepts the bad news.
  • 1:01 - 1:05
    But in this case, Jenny is
    writing to her own colleagues.
  • 1:05 - 1:07
    For this internal
    bad news message,
  • 1:07 - 1:09
    it's best to use a
    more direct style
  • 1:09 - 1:13
    since the company wants to
    deal with problems efficiently.
  • 1:13 - 1:16
    At the same time, she
    needs to be polite
  • 1:16 - 1:18
    and to show understanding
    for her colleagues
  • 1:18 - 1:20
    receiving the bad news.
  • 1:20 - 1:23
    Regardless of which
    method you use,
  • 1:23 - 1:26
    you should always try
    to buffer or sandwich
  • 1:26 - 1:31
    bad news with some neutral
    material before and after.
  • 1:31 - 1:35
    All right, let's start with
    the mechanics of this email.
  • 1:35 - 1:38
    As you can see, we
    have a subject line--
  • 1:38 - 1:42
    Server Restart Inform.
  • 1:42 - 1:44
    Let's first correct the
    grammar in this line.
  • 1:44 - 1:48
    We can't use inform
    as a noun in this way.
  • 1:48 - 1:51
    So we'd better change it
    to something like "notice."
  • 1:51 - 1:54
  • 1:54 - 1:56
    And since we don't have
    an opening salutation,
  • 1:56 - 1:59
    we can add something
    neutral and professional,
  • 1:59 - 2:02
    like "Dear Colleagues."
  • 2:02 - 2:05
  • 2:05 - 2:08
    Now, when we look at
    the body of the email,
  • 2:08 - 2:10
    the first thing we notice
    is that the entire message
  • 2:10 - 2:14
    is just one sentence long.
  • 2:14 - 2:15
    And it's a run-on sentence.
  • 2:15 - 2:18
    That is, it's really
    several separate sentences
  • 2:18 - 2:21
    that have been incorrectly
    strung together with commas.
  • 2:21 - 2:24
  • 2:24 - 2:27
    Let's start by replacing all
    these commas with periods
  • 2:27 - 2:29
    so that the sentences
    stand on their own.
  • 2:29 - 2:33
  • 2:33 - 2:36
    And we'll need to
    capitalize the first word
  • 2:36 - 2:37
    in each of these new sentences.
  • 2:37 - 2:42
  • 2:42 - 2:45
    Now that we've broken
    the sentences apart,
  • 2:45 - 2:47
    let's go through them
    one by one and make sure
  • 2:47 - 2:49
    the grammar is correct.
  • 2:49 - 2:52
    In the first sentence, Jenny
    writes that the company will
  • 2:52 - 2:59
    have to restart the server from
    17:15 PM to 18:00 PM today.
  • 2:59 - 3:03
    Since Jenny is using
    24-hour time here,
  • 3:03 - 3:08
    she doesn't need PM
    after 17:15 or 18:00.
  • 3:08 - 3:11
    This sentence also has
    a subordinate clause--
  • 3:11 - 3:14
    "because of the backup tape
    equipment has some problems."
  • 3:14 - 3:19
    Here, we need to change
    "because of" to "because."
  • 3:19 - 3:22
    Remember that "because of"
    is always followed by a noun
  • 3:22 - 3:24
    or a noun phrase.
  • 3:24 - 3:27
    But what we have here
    is a complete sentence,
  • 3:27 - 3:30
    "the backup tape equipment
    has some problems,"
  • 3:30 - 3:33
    which takes "because" by itself.
  • 3:33 - 3:35
    We can also see that
    this last sentence,
  • 3:35 - 3:41
    "Any questions please call 588,"
    is actually a sentence fragment.
  • 3:41 - 3:43
    We'd better turn it into a
    complete sentence by making
  • 3:43 - 3:48
    the first part into a clause,
    "If you have any questions,"
  • 3:48 - 3:52
    and then setting it
    off with a comma.
  • 3:52 - 3:54
    And finally, we should think
    about structuring the email
  • 3:54 - 3:58
    into separate paragraphs.
  • 3:58 - 4:02
    I think the best way to do this
    is to begin a new paragraph with
  • 4:02 - 4:04
    "Sorry for the inconvenience."
  • 4:04 - 4:08
    This gives us two paragraphs
    with separate ideas, one
  • 4:08 - 4:10
    that explains what's
    happening and one
  • 4:10 - 4:12
    that apologizes
    to Jenny's readers
  • 4:12 - 4:17
    and gives them an opportunity
    to ask for more information.
  • 4:17 - 4:22
    Now, let's move on to
    the style of this email.
  • 4:22 - 4:25
    When you're writing a
    message to deliver bad news,
  • 4:25 - 4:29
    one good strategy is to
    buffer the news, that is,
  • 4:29 - 4:33
    to put some neutral material
    at the beginning and the end
  • 4:33 - 4:36
    of the email and also
    at the beginning and end
  • 4:36 - 4:40
    of each paragraph
    containing bad news.
  • 4:40 - 4:42
    This makes the
    delivery less abrupt
  • 4:42 - 4:44
    and helps avoid giving
    a negative impression
  • 4:44 - 4:46
    to the reader.
  • 4:46 - 4:49
    As you can see, Jenny
    hasn't followed this rule.
  • 4:49 - 4:51
    She goes straight
    to the bad news.
  • 4:51 - 4:54
    We will restart our mail server.
  • 4:54 - 4:59
    And only afterwards does she
    explain the reason for the news.
  • 4:59 - 5:02
    Let's rearrange this paragraph
    to put the explanation first
  • 5:02 - 5:07
    so the readers understand why
    they are being inconvenienced.
  • 5:07 - 5:11
    We can begin by
    saying something like,
  • 5:11 - 5:23
    "We have discovered that
    the backup tape equipment
  • 5:23 - 5:30
    for our mail server
    has some problems."
  • 5:30 - 5:33
  • 5:33 - 5:38
    And then cut out the second
    clause of the original sentence.
  • 5:38 - 5:40
    This puts the bad news
    in the second sentence
  • 5:40 - 5:43
    of the paragraph.
  • 5:43 - 5:45
    But we should
    probably add a clause
  • 5:45 - 5:47
    that explains the connection
    between the equipment
  • 5:47 - 5:49
    problem and the server restart.
  • 5:49 - 5:52
  • 5:52 - 6:02
    Let's start by saying, "For
    this reason, we will restart."
  • 6:02 - 6:05
  • 6:05 - 6:07
    And we can just
    say, "the server"
  • 6:07 - 6:11
    in this sentence since we've
    identified the system already.
  • 6:11 - 6:14
  • 6:14 - 6:16
    The last sentence
    in this paragraph
  • 6:16 - 6:19
    gives the reader some
    additional bad news.
  • 6:19 - 6:20
    Jenny is telling
    them that the company
  • 6:20 - 6:24
    may lose its email connection
    for a long time this afternoon.
  • 6:24 - 6:27
    But since we know that the
    repairs should be finished
  • 6:27 - 6:32
    by 18:00, we can rephrase
    this news in a positive way.
  • 6:32 - 6:38
    Where Jenny writes "from
    17:15 to 18:00," let's say,
  • 6:38 - 6:45
    "beginning at 17:15 today" and
    end the second sentence there.
  • 6:45 - 6:48
    This gives us the chance
    to end the paragraph
  • 6:48 - 6:50
    on a positive note.
  • 6:50 - 6:54
    Instead of saying, "We expect to
    restart the server many times,"
  • 6:54 - 7:03
    the final sentence can say,
    "We expect the server to be
  • 7:03 - 7:09
    available again after 18:00."
  • 7:09 - 7:12
    When an email has
    to deliver bad news,
  • 7:12 - 7:14
    it's also helpful
    to emphasize how
  • 7:14 - 7:17
    readers can benefit
    by cooperating
  • 7:17 - 7:20
    or by accepting the situation.
  • 7:20 - 7:22
    So let's have Jenny
    add a new sentence
  • 7:22 - 7:24
    in a separate
    paragraph, explaining
  • 7:24 - 7:27
    why this temporary
    interruption of service
  • 7:27 - 7:31
    will make things easier for
    her colleagues in the long run.
  • 7:31 - 7:40
    She can say, "These repairs
    to the server will make
  • 7:40 - 7:52
    your Internet and email
    connections more reliable
  • 7:52 - 7:52
    in the future."
  • 7:52 - 7:55
  • 7:55 - 7:58
    In the next paragraph,
    Jenny is right to use
  • 7:58 - 8:01
    apologetic phrasing,
    since this ends the email
  • 8:01 - 8:03
    in a less negative way.
  • 8:03 - 8:06
    But we should make some
    changes to her language
  • 8:06 - 8:08
    so it sounds less abrupt.
  • 8:08 - 8:12
    A sentence beginning with
    "Sorry" sounds very informal,
  • 8:12 - 8:15
    which probably isn't a good idea
    if she wants to show sympathy
  • 8:15 - 8:17
    for her colleagues.
  • 8:17 - 8:24
    Let's change it to "We apologize
    for the inconvenience."
  • 8:24 - 8:28
    And we don't really need
    this final "to you."
  • 8:28 - 8:36
    And we can change "call 588"
    to "call me on extension 588,"
  • 8:36 - 8:40
    again, making the sentence less
    abrupt and more informative
  • 8:40 - 8:44
    and emphasizing that Jenny is
    personally involved in solving
  • 8:44 - 8:46
    this problem.
  • 8:46 - 8:51
    And finally, let's review
    the email for tone.
  • 8:51 - 8:54
    The first and second
    paragraphs have a neutral tone,
  • 8:54 - 8:56
    which is appropriate
    for delivering
  • 8:56 - 8:59
    bad news in an internal memo.
  • 8:59 - 9:02
    But in the third paragraph,
    we should add some language
  • 9:02 - 9:05
    to make Jenny's apology
    sound more sincere
  • 9:05 - 9:10
    by expressing concern for
    the needs of her colleagues.
  • 9:10 - 9:12
    Jenny wants to make
    her readers feel
  • 9:12 - 9:15
    welcome to ask for more
    information about the server
  • 9:15 - 9:16
    problem.
  • 9:16 - 9:19
    So let's begin by
    adding "or concerns"
  • 9:19 - 9:22
    to this final sentence.
  • 9:22 - 9:27
    So it becomes
    "questions or concerns."
  • 9:27 - 9:32
    And we can change "please call"
    to "please feel free to call,"
  • 9:32 - 9:36
    again, to create a
    more welcoming tone.
  • 9:36 - 9:39
    Finally, we should
    add a closing sentence
  • 9:39 - 9:41
    to show appreciation for
    the reader's problems
  • 9:41 - 9:45
    and their willingness to
    cooperate in solving them.
  • 9:45 - 9:54
    Let's write something like
    "Thank you for your patience
  • 9:54 - 9:56
    and understanding."
  • 9:56 - 9:59
  • 9:59 - 10:04
    This sentence, "We apologize
    for the inconvenience,"
  • 10:04 - 10:06
    may not really be necessary.
  • 10:06 - 10:11
    Some of you may feel it makes
    the email too apologetic.
  • 10:11 - 10:14
    So I think we can let our
    listeners decide for themselves.
  • 10:14 - 10:17
    Does Jenny need
    this apology or not?
  • 10:17 - 10:21
    Now, let's take one
    final look at this email.
  • 10:21 - 10:24
    Jenny has taken a problem that
    might cause a lot of annoyance
  • 10:24 - 10:26
    to her readers, and
    she's explained it
  • 10:26 - 10:31
    in a way that's direct,
    professional, and sympathetic.
  • 10:31 - 10:34
    She's making the best of
    a bad situation, which
  • 10:34 - 10:38
    is a very important skill
    in any business setting.
  • 10:38 - 10:40
    So let's hit the Send button
    and get this message out
  • 10:40 - 10:43
    to Jenny's colleagues.
  • 10:43 - 10:50
Title:
Business English Writing Lesson for ESL - ET 04: Bad News Messages
Description:

more » « less
Video Language:
English
Duration:
10:50

English subtitles

Revisions