商業英文：Slack / PR / 非同步
Async 溝通是台灣 PM 在矽谷公司最容易踩雷的地方——不是文法錯，是 tone 跟文化全錯。 這份教你 Slack 該多隨意、PR 該多嚴謹、Notion comment 該多結構化。
為什麼 async 溝通比同步難
同步（會議、電話）：
- 表情語氣可以救你
- 講錯立刻可以 clarify
- Tone 是模糊的
Async（Slack、PR、email）：
- 對方靠字面意思 + emoji + 標點判斷你的 tone
- 一條訊息發出去就是「永久記錄」
- 文化差異最容易爆雷的場域
→ Async = 你的「文字 EQ」決定一切。
Slack：矽谷溝通主戰場
Slack tone 光譜（從錯到對）
❌ 太正式（會被當機器人）
Dear Sarah,
I would like to inquire about the status of the Q3 planning document. Please advise at your earliest convenience.
Best regards, Maki
❌ 太隨便（會被當不專業）
yo wassup hey wheres the Q3 doc lol
✅ 矽谷 tone
Hey Sarah, quick Q — got an ETA on the Q3 planning doc? 🙏 Need it for Thursday's exec sync.
規則：
- 句首大寫（Hey 而不是 hey）
- 標點正常（句號 / 問號要有，但結尾不一定要）
- Emoji 適量（🙏 = please / 👀 = looking / ✅ = done）
- 不要 lol / lmao / fyi 全大寫（除非熟）
Channel vs DM vs Thread：每個都有規則
| 場景 | 用什麼 | 範例 |
|---|---|---|
| 全 team 都該知道 | #channel | Shipped v2.3 — release notes inside 🚀 |
| 兩人之間 | DM | Hey, got 5 min for a quick Q? |
| 對某條訊息回覆 | Thread | (在 thread 內回覆) |
| Casual chat | DM 或 #random | weekend plans? |
| 急事 | DM + tag | @Sarah — prod alert, take a look? |
新人最常踩的雷：
- 在 #channel 開新訊息討論 thread 內的事 → 永遠用 thread reply
- DM 問完一個小問題又 DM 一個 → 連續訊息合併在 thread 裡
- 在大 channel 講私事 → 搬去 #random 或 DM
@here vs @channel vs @<name>
| Mention | 影響 | 何時用 |
|---|---|---|
| @<name> | 一個人 | 90% 情境 |
| @here | 線上的人 | 中等急事，例：「@here who's on-call?」 |
| @channel | 所有人（含離線） | 真的緊急 — outage / launch 倒數 / 全員投票 |
禁區：
- 在 #engineering 用 @channel 問「lunch 吃什麼」→ 全公司會討厭你
- 在 50 人 channel 用 @channel 講非緊急事 → 等於騷擾
- 連續 @同一人 3 次以上 → 對方會封鎖你
Pro tip：如果不確定要不要 @channel，就不要。
Slack Status / Working Hours
Status emoji 是文化：
| Emoji | 意思 |
|---|---|
| 🍵 | In a meeting |
| 🥗 | Lunch |
| 🚶 | AFK / 走開一下 |
| 🌴 | OOO / vacation |
| 🤒 | Sick |
| 🧠 | Heads-down / focus time |
| 🎧 | DND - 戴耳機別吵 |
設 Status 的禮儀：
- 每天進辦公室 / 開電腦時 set
- Lunch / 開會 / 走開要設
- 離開公司 set 🌴 + 寫「Back Tomorrow 9am PST」
Slack 必背句型
提問
| 場景 | 句型 |
|---|---|
| 簡單問題 | Quick Q — [question]? |
| 需要 context | Hey, got a sec? Working on [X], stuck on [Y]. Any thoughts? |
| 求救 | Stuck on [X] — anyone seen this before? Posting in thread to keep noise down. |
| 確認 | Just to confirm — [restate]? Want to make sure before I move forward. |
回應
| 場景 | 句型 |
|---|---|
| 收到 | Got it 👍 |
| 我來處理 | On it. ETA [time]. |
| 我要去查 | Let me check and circle back. |
| 我也不知道 | Not sure — pinging @[expert] who'd know. |
| 不同意但禮貌 | Hmm, I'd push back on this — [reason]. WDYT? |
道歉 / 認錯
| 場景 | 句型 |
|---|---|
| 回覆慢 | Sorry for the late reply — was heads down on [X]. |
| 弄錯了 | My bad — I had [X] wrong. Correction: [Y]. |
| 漏看訊息 | Missed this — looking now. |
| 出 bug | This is on me — pushing fix now. Postmortem to follow. |
報好消息 / 壞消息
| 場景 | 句型 |
|---|---|
| Win | 🎉 Just shipped [X]. Thanks @[team] for the help. |
| Update | Status update: [status]. Next milestone: [X] by [date]. |
| Heads-up | ⚠️ Heads-up — [issue]. Investigating, will update in 30 min. |
| Outage | 🚨 [service] is down. War room: [link]. |
PR Review：矽谷工程師的 Code Review 文化
三種 review comment 標籤
| 標籤 | 意思 | 範例 |
|---|---|---|
nit: | 雞毛蒜皮，可改可不改 | nit: missing trailing newline |
suggestion: | 建議改，不擋 merge | suggestion: extract this into a helper? |
question: | 純問，不一定要改 | question: why not use the existing util here? |
blocker: | 必須改才能 merge | blocker: this leaks PII to logs |
praise: | 稱讚 | praise: nice abstraction! |
Pro tip：每個 PR 至少留 1 個 praise: — 文化健康度差別很大。
Code review 句型
提建議
What if we [alternative]? Might be cleaner. Have you considered [pattern]? Trade-off is [X]. Could we extract this into a util? Feels like we'll reuse it.
質疑
Help me understand — why this approach over [alternative]? Is there a reason we're not using [existing util]? Curious about the perf here — have we benchmarked?
反對（要改）
Blocker: this can cause [specific bug]. We need to [fix]. I'd push back on this approach because [reason]. Suggest [alternative]. This breaks the [contract / convention] we agreed on in [link]. Let's chat.
同意 + LGTM
| 強度 | 句型 |
|---|---|
| 簡短同意 | LGTM 👍 |
| 同意 + 小建議 | LGTM with one nit — [nit] |
| 強同意 | LGTM, ship it 🚢 |
| 同意但不熟領域 | Code looks good to me but I'm not the domain expert — would love @[expert] to weigh in. |
收到 review comment 時
接受建議
Good catch — fixed in [commit hash]. Agree, makes sense. Updated. Hadn't thought of that. Refactored.
Push back（不接受建議）
Thought about this — went with [current approach] because [reason]. Open to changing if you feel strongly. Actually have a reason for this — [explain]. Let me know if that doesn't address your concern.
不確定
Not sure I follow — could you elaborate? Maybe with a code example? Want to make sure I get this right — pinging in [chat thread] to discuss?
Async Standup（沒會議的早會）
矽谷越來越多公司用 async standup 取代會議。標準格式：
**Yesterday**: shipped feature X, fixed bug Y
**Today**: working on PRD for Q3, design review at 2pm
**Blockers**: waiting on @sarah for design specs (asked Mon, ETA?)
台灣 PM 常見錯誤：
- ❌ 寫成日記：「Yesterday I worked on many things including...」
- ❌ 寫太細：列 20 項
- ❌ 不寫 blocker（怕被當無能）
正確做法：
- 三段都用 bullet
- 每段 1-3 個 item
- Blocker 一定要寫 — 沒 blocker 反而可疑
進階版（含 metric / signal）
**Yesterday**:
- ✅ Shipped pricing v2 (5% conversion lift)
- ✅ Reviewed Q3 OKRs with eng
**Today**:
- 🚧 PRD for tiering feature (target: draft by EOD)
- 📞 Customer call at 11am
**Blockers**:
- ⏸️ Need design specs from @sarah (blocker since Mon)
**Signals**:
- 🔥 Customer X churned — postmortem doc inside
Notion / Confluence Comment
不同於 Slack 的 quick chat，Notion comment 是留下來給未來閱讀的。
結構
**Concern**: [一句話講出 concern]
**Why it matters**: [explain stakes]
**Proposed fix**: [actionable suggestion]
**Open Q**: [optional, what you need from author]
範例
Concern: Section 3 says we'll support OAuth2 but doesn't mention SSO. Why it matters: Enterprise customers (Acme, Globex) require SAML SSO. If we ship without it, we'd lose those deals. Proposed fix: Add Non-goal: "v1 does not support SAML SSO. v2 timeline TBD." Open Q: Are we OK pushing SSO to v2?
Emoji 速查表（PM 必懂）
| Emoji | 意思 | 用在哪 |
|---|---|---|
| 👍 | Acknowledged / agree | 短回應 |
| ✅ | Done | 任務完成 |
| 👀 | Looking / reviewing | 我在看了 |
| 🙏 | Please / thanks | 拜託 / 感謝 |
| 🚀 | Ship / launch | 上線 |
| 🔥 | Urgent / on fire | 急 / 燒起來了 |
| 🚨 | Alert / outage | 緊急 |
| 🎉 | Celebration | win / launch |
| 🤔 | Thinking / unsure | 思考中 |
| 💯 | Strong agree | 100 分 |
| 🧠 | Heads-down / focus | 專心做事 |
| ☕ | Coffee chat | 約 1:1 |
| 🛑 | Stop / blocker | 擋住了 |
禁區：
- 不要 over-emoji（每句一個 emoji = 像 Gen Z 不專業）
- 不要用容易誤解的 emoji（🍆 🍑 🥒 = 性暗示，職場禁用）
- 不要用 ❤️ 在 work channel（曖昧）
中式英文陷阱（async 專用）
| 中式 | 改寫 |
|---|---|
| Please reply me. | Reply when you can / Get back to me by [date]. |
| FYI only. | (just delete "only") |
| Pls help to check. | Could you take a look? |
| Kindly review. | Mind reviewing? |
| Noted with thanks. | Got it, thanks. |
| Pls advise. | What's your call? |
| As per discussed. | Per our chat / As we discussed. |
| Revert back to me. | Get back to me. |
| Discuss offline. | Let's take this offline / Chat 1:1? |
| TIA (Thanks In Advance) | Thanks 🙏 |
Cheat Sheet（一頁回顧）
| 場景 | 黃金規則 |
|---|---|
| Slack tone | 句首大寫 + 適量 emoji + 不要 dear/regards |
| Channel vs DM | 全 team 該知道用 channel，否則 DM |
| Thread | 回覆訊息永遠用 thread |
| @channel | 真的緊急才用 |
| PR review | 至少 1 個 praise: 加 nit / suggestion / blocker 標籤 |
| Async standup | Yesterday / Today / Blockers 三段 + blocker 一定寫 |
| Emoji | 適量、不曖昧、不性暗示 |
| 不要寫 | Dear / Pls kindly / Noted with thanks / Revert back |
面試會考的 async 題
- 「How do you communicate with a remote team across time zones?」 → 講 async-first 心態 + over-document + 標準化 Slack/PR template
- 「How do you give feedback on a PR you disagree with?」 → blocker 標籤 + 解釋 reason + 提 alternative + 留 open question
- 「Walk me through how you'd run an async standup.」 → Yesterday/Today/Blockers + 強調 blocker 必寫 + signal section optional
📚 延伸閱讀：