商業英文 Email 寫作

學校教的英文 email 格式（Dear Sir / I am writing to inform you that...）在矽谷沒人這樣寫。 這份是英美 PM 真的在用的句型，分四段：subject → opening → ask → closing。

為什麼學校教的格式在職場是地雷

學校教：

Dear Sir/Madam,

I am writing to inform you that I would like to schedule a meeting with you next week to discuss the project status. It would be greatly appreciated if you could let me know your availability.

Yours sincerely, Maki

問題：

1. 太長、太正式 → 對方看一半就跳過
2. 「I would like to」「It would be greatly appreciated」是 100 年前的措辭
3. 沒有 specific ask（「下週」是指哪一天？）
4. 收件人讀完不知道「我現在要做什麼」

矽谷版：

Subject: 15-min sync on Q2 roadmap — Tue 2pm PST?

Hi Sarah,

Quick check on Q2 roadmap before Friday's exec review. Could we grab 15 min Tuesday 2pm PST?

Topics:

• 3 features we're cutting
• Async vs sync demo for new pricing

If 2pm doesn't work, here's my Calendly: [link]

Thanks, Maki

差別：

• Subject 直接講「要什麼 + 何時」
• Opening 一句話講 context
• Bullet 講 specific topics
• 給 fallback（Calendly link）
• 短到對方手機上 3 秒看完

Subject Line：對方只看這一行

規則：

1. 動詞開頭 > 名詞
2. 包含時間 / 數字 > 抽象描述
3. 包含具體 ask > 模糊主題

對比：

前綴標籤（讓對方掃 inbox 時秒判優先級）：

• [Action Required] — 對方必須做事
• [FYI] — 不用回，存檔用
• [Decision Needed] — 等對方拍板
• [Blocker] — 我被卡住，需要幫忙
• [For Review] — 文件 review

Opening：第一句決定對方要不要往下讀

❌ 學校式：

• I hope this email finds you well.（永遠不要寫——對方知道你是客套）
• I am writing to inform you that...
• I would like to take this opportunity to...
• It is my pleasure to...

✅ 矽谷式：

萬用開場：「Quick / Heads-up / Following up / Need your help」四選一，後面接一句話 context。

Ask：把「我希望你做什麼」放在前 50 字

結構：

[Context 1 句]
[Specific ask 1 句]
[Bullet 細節]
[Deadline]

範例：

Quick request on the Q3 PRD.

Could you review section 3 (Auth flow) by EOD Wed? Two specific things:

• Does the OAuth scope cover B2B SSO?
• Are we OK with 2-hour session timeout?

If you can't get to it, please ping me—I'll loop in Alex instead.

核心句型：

避免的軟弱措辭：

• ❌ I was wondering if maybe you could possibly... → ✅ Could you...?
• ❌ Sorry to bother you, but... → ✅ Quick Q:
• ❌ When you have a chance... → ✅ By [specific date]
• ❌ If it's not too much trouble... → ✅ (delete entirely)

Push Back：拒絕 / 反對 / 提異議

核心原則：先肯定 → 再提出問題 → 給替代方案。

❌ 直接拒絕（會被當白目）：

No, we can't do this.

✅ 結構化 push back：

Totally see why this would help [restate their goal]. Two concerns before we commit:

1. [concern 1]
2. [concern 2]

What if we [alternative]? That gets us 80% of the value at 30% of the cost.

常用句型：

面試陷阱：被問「你怎麼跟 stakeholder 反對」——能講出「先 acknowledge 再 push back」結構 = 加分。

Closing：CTA + Sign-off

結尾必有 CTA（Call to Action）：

Sign-off 選擇：

中式英文陷阱清單

文化差異：美 / 英 / 亞洲同事

英式委婉的真正意思（PM 必懂）：

三種長度模板（直接複製改）

30 秒版（quick ask）

Subject: Quick Q on [topic] — need answer by [date]

Hi [name],

[1 句 context]. [1 句 ask].

Thanks,
Maki

1 分鐘版（standard request）

Subject: [Action] [Topic] — [Deadline]

Hi [name],

[1 句 context].

Could you [specific ask] by [date]? Two things to flag:
- [point 1]
- [point 2]

If [edge case], [fallback].

Thanks,
Maki

3 分鐘版（status update / proposal）

Subject: [Project] update — [TL;DR in 5 words]

Hi team,

TL;DR: [1 句最重要的事]

What's done:
- [item]
- [item]

What's next:
- [item, with owner + date]

Blockers:
- [item, with what we need]

Decisions needed from you:
- [decision 1]
- [decision 2]

Full doc: [link]

Thanks,
Maki

Cheat Sheet（一頁回顧）

面試會考的 email 題

1. 「給我一個你寫過的 stakeholder push back email 例子」 → 用「先肯定 → 提兩點風險 → 給替代方案」結構講
2. 「你怎麼跟 engineer 解釋為什麼這個 feature 不能做」 → email 結構：context + 具體 trade-off + 提開放問題請對方回應
3. 「你怎麼跟 CEO 報告壞消息」 → TL;DR 第一句 + 具體 impact + 已採取的 mitigation + 請對方做的決策

📚 延伸閱讀：

• 商業英文：會議 / 視訊發言
• 商業英文：簡報 / Demo
• 商業英文：Slack / PR / 非同步
• 商業英文：面試英文
• 商業英文：談判 / Push-back