如何用英文釐清誤會，又不讓對方覺得被責怪？
英文裡出現誤會時，別急著證明誰說錯。用 Two Maps → One Map：中性指出落差、說明你的理解、確認對方原意，再把正確日期、範圍或下一步說清楚。
釐清誤會時，先比較兩邊的 interpretation，不急著判誰造成問題。把你的理解說成「我的理解」，邀請對方說明 intended meaning，最後再把 corrected fact 和 shared next step 明確確認。
你以為 deadline 是 Friday，對方卻在等 Monday。這時 That’s not what you said. 很容易把 conversation 變成「誰記得比較對」。更有用的是先把兩張理解攤開。
Two Maps → One Map
- Name the Gap：I think there may have been a misunderstanding.
- Show My Read：I understood the deadline to be Friday.
- Invite / State Your Meaning：Did you mean Monday? / What I meant was...
- Confirm One Map：Just to make sure we’re on the same page...，再講 exact fact 和 next step。
核心不是「永遠說得很軟」，而是：soft on blame, precise on facts.
Misunderstanding 比較像 alignment problem，不是立刻找 culprit
Misunderstanding research 把 repair 描述成雙方一起重新 negotiate meaning 的工作：人們會改寫、補充、建議或澄清，讓 shared understanding 回來。查看 misunderstanding-repair research。
Everyday-conversation research 也把 misunderstanding 看成 interaction 裡會被監控、協商、修復的現象，而不是只有「懂／不懂」兩個固定狀態。查看 everyday misunderstanding study。
所以如果事實還沒清楚，你不需要第一句就決定「是你說錯」還是「是我聽錯」。先把兩張 map 放到同一張桌上。
Name the Gap：先說「我們的理解不一樣」，不要先說「誰搞錯了」
Original practice example
I think there may have been a misunderstanding. I understood the deadline to be Friday. Did you mean Monday?
There may have been a misunderstanding 先中性標記 mismatch；接著把 Friday 明確標成自己的 understanding，再邀請對方提供 intended version。
meeting date、deadline、appointment、handover time 等 scheduling misunderstanding。
拿一個 Friday / Monday mismatch，先禁止自己使用 You said...，用 gap + my read + question 說一次。
- I think we may be talking about different things.
- I think we may have understood this differently.
- There may have been some confusion about the deadline.
Show My Read：說「我怎麼理解」而非「你就是這樣說」
比較：
You said the deadline was Friday.
I understood the deadline to be Friday.
第一句不是禁語。當你需要引用紀錄、確認 exact wording、或事實脈絡很清楚時，You said... 可以完全正常。但在 disagreement 裡，它有時會把焦點推向「證明對方說過什麼」。第二句則把焦點放在你拿到的 interpretation。
Pragmatics research 對 disagreement 的研究也提醒：disagreement 本身不是自動等於 impolite；relational/face effect 取決於 formulation、context 和 interactional expectations。查看 disagreement pragmatics overview。
Original practice example
When you said “final version,” I understood that to include the appendix. Is that what you meant?
這句沒有假裝原話不存在，也沒有宣判對方 fault。它把 source wording 和你的 interpretation 分開。
task scope、deliverable、definition、工作範圍理解不同時。
選一個 ambiguous phrase，例如 final version，先說 source，再說你的 reading，最後問對方 intended meaning。
四種「誤會」說法，責任和 certainty 不一樣
I misunderstood you.
這是比較強的 ownership：你明確說「是我理解錯了」。如果你已經知道自己確實 misunderstood，很自然；如果責任還不清楚，就不必為了禮貌硬認。
I may have misunderstood.
保留 uncertainty：你承認「我的理解可能有偏差」，但沒有宣稱自己一定是造成誤會的人。
There may have been a misunderstanding.
source-neutral。它先標記 mismatch，不先分配 responsibility。
I think we were talking about different things.
把問題放在兩邊 reference/frame 沒對齊，適合真的像在講不同 scope、version、stage 時。
沒有一個版本可以獲得固定「禮貌分數」。Context、evidence、relationship 和你真正知道多少，都會改變最誠實的選擇。Face/politeness research 本身也強調這類互動高度依 context 而定。查看 face and disagreement study。
如果是對方 misunderstood 你，也不用直接說 “You misunderstood me”
You misunderstood me. 文法完全正常，有時也確實準確。但如果你的目標是先把 alignment 修回來，可以把第一步放在自己的 intended meaning 上：
Original practice example
I may not have been clear. What I meant was that we should review the draft, not approve it yet.
這裡 speaker 沒有假裝對方 interpretation 合理或不合理，也沒有猜對方 motive；只是把自己的 intended meaning 說清楚。
task instruction、approval stage、scope、email wording 被理解成另一個 action 時。
把 You misunderstood me 改寫成「我的 wording 可能不夠清楚 + what I meant was...」。
如果你並不認為自己說得不清楚，也可以更中性：
I think we may have understood that differently. What I meant was...
不要替對方重建 motive：不知道 intent，就問
You were trying to criticize my work.
除非對方已經明確說明，這是在替他們宣告 intent。更穩健的 repair 是把你的 interpretation 和他們的 intended meaning 分開：
I took that as criticism. Was that what you intended?
或者當你要澄清自己的 tone：
What I meant was that I was concerned about the timing, not criticizing your work.
你可以很 direct 地說你的 experience 或 intended meaning；不要把無法知道的 internal motive 當成 fact。
Confirm One Map：誤會修完，最後一定要把 shared version 說出來
如果 conversation 最後只剩：
Okay, no problem.
但你仍然不知道到底是 Friday 還 Monday，alignment 還沒完成。
Original practice example
Just to make sure we’re on the same page, I’ll send the revised file by Friday at 3 p.m., and you’ll review it before Monday. Is that right?
Face-saving 到這一步要讓位給 factual precision。把 date、time、responsibility 和 next step 明確重述，讓對方 confirm 或 correct。
deadline、quantity、scope、handover、approval、任何會影響下一個 action 的 practical detail。
把一個 vague Okay, got it 改成包含 exact date + action + confirmation question 的版本。
2025 年的 interaction research 也顯示，speakers 會主動 pre-empt potential misunderstandings，以維持 intersubjectivity，避免後續 action 建在錯 interpretation 上。查看 pre-emptive repair study。
High-pressure rule：soft on blame，不代表 soft on facts
如果 stakes 高，clarification 可以非常直接。你只需要把「誰的錯」和「現在的正確 fact」分開。
- 不知道 intent：問，不要猜。
- deadline 未確認：不要承諾交付。
- scope 未確認：不要承諾完成某個 deliverable。
- number / quantity 未確認：不要用最可能的數字自己補空白。
I have 15 in my notes. What number do you have?
Just to confirm, the final quantity is 50, correct? I won’t place the order until we confirm that.
Face-sensitive wording 不能把 15 和 50 變成一團 polite fog。
七種會讓 alignment 變 blame game 的說法
That’s not what you said.
有時事實上可能正確，但它立刻把 conversation 推向 evidence contest。若目前目標是先修 misunderstanding，可先說你的 interpretation，再確認 intended meaning。
You misunderstood me.
可能是正確描述，但它直接分配 responsibility。若責任還沒確認，先描述兩邊 versions。
直接替對方說 motive
You wanted to make me... / You were trying to... 在 intent 未確認時容易越界。問對方 intended meaning。
用 sarcasm 代替 clarification
Oh, so now it’s Monday? 可能讓 factual repair 變成 relational fight。直接確認 Monday 即可。
一直道歉，卻沒把 fact 說清楚
Sorry, maybe it was my fault, sorry... 不會自動產生 shared map。Apology 若需要，可以短；接著仍要確認 fact。
假裝 agreement
如果你其實還不確定 scope，說 Yes, sure 只會把 mismatch 推到下一個 action。
還沒 confirm 就先 promise
尤其 deadline、scope、number、requirement 尚未對齊時，不要用承諾掩蓋 uncertainty。
Two Maps Rewrite Lab：把 blame-heavy lines 改成 alignment language
Round A — Scheduling：That’s not what you said. You said Friday.
I think there may have been a misunderstanding. I understood the deadline to be Friday. Did you mean Monday?
Confirm One Map： Just to confirm, the deadline is Monday at 10 a.m., correct?
Round B — Scope：You told me the appendix was included.
When you said “final version,” I understood that to include the appendix. Is that what you meant?
Next step： So for this version, I should include the appendix, right?
Round C — They misunderstood you：You misunderstood me. I never said approve it.
I may not have been clear. What I meant was that we should review the draft, not approve it yet.
Confirm： So the next step is review only, with no approval yet. Is that right?
Round D — Tone：You took it the wrong way. I wasn’t criticizing you.
I can see that my message may have sounded critical. What I meant was that I was concerned about the timing, not criticizing your work.
這句澄清的是 speaker 自己的 intended meaning；它沒有宣稱知道對方 motive。
Round E — High-stakes detail：你有 15，對方似乎有 50
I think we may have different numbers. I have 15 in my notes. What number do you have?
Confirm before action： Just to confirm, the final quantity is 50, correct? I won’t place the order until we confirm that.
“I think we have a misunderstanding” 文法可以，但未必是你想要的 nuance
學習者說法： I think we have a misunderstanding.
分類：文法可能成立，但 context-dependent；have a misunderstanding 有時會讓人聯想到 ongoing disagreement / quarrel，而不只是一次 communication mix-up。
聽者會理解：你認為雙方之間存在某種 mismatch、disagreement 或 conflict。
更自然的 neutral repair： I think there may have been a misunderstanding. / I think we may have misunderstood each other.
Context note：have a misunderstanding with someone 並不是錯英文；它可以表示與某人發生誤會或爭執。只是要中性指出這一次 message mismatch 時，there may have been... 通常更精準。
一個小練習：把 You 換成 Interpretation
拿一句 blame-heavy sentence，例如：
You told me the deadline was Friday.
改兩版：
- I understood the deadline to be Friday.
- There may have been a misunderstanding about the deadline.
比較它們在 responsibility 和 certainty 上實際 claim 了什麼。不要急著選「最禮貌」；選最符合你知道的 facts 的版本。
Soft on blame, precise on facts
誤會已經形成時，你不必在第一句就判定 culprit。先做 Two Maps → One Map：Name the Gap、Show My Read、Invite / State Your Meaning、Confirm One Map。
可以保留 uncertainty，但不要猜 intent；可以顧及 face，但不要把 deadline、scope、number 或 requirement 說模糊。尤其在 action 會產生後果時，先確認 shared map，再 promise next step。
真正好的 clarification 不是讓誰輸掉，而是讓兩個人離開 conversation 時，拿著同一個版本。