Steven's Knowledge

Apologizing & Owning Mistakes

How to acknowledge mistakes in English without over-apologizing or under-owning (用英文承认错误,既不过度道歉也不推卸)

The Calibration Problem (校准问题)

Asian/Chinese speakers often over-apologize for small things and under-own big things (treating them as "not my fault"). Native English workplaces have a different calibration.

亚洲/中文母语者常常对小事过度道歉对大事推卸责任(觉得"不是我的错")。英语职场的校准方式不同。

The principle 原则: Save real apologies for real mistakes. When you do apologize, be specific, take responsibility, and move to fix.

真正的道歉留给真正的错误。一旦道歉,要具体、要担责、要去修。

Stop Over-Apologizing (停止过度道歉)

Over-apology (过度道歉)What to say instead (用什么代替)
"Sorry for the late reply." (when 1 day)"Thanks for your patience."
"Sorry to bother you.""Quick question when you have a sec."
"Sorry for asking again.""Just following up on..."
"Sorry, my English is bad."(just speak — don't preface)
"Sorry, I have a question.""Quick question — ..."
"Sorry, can I jump in?""Mind if I jump in?"
"Sorry for taking your time.""Appreciate the time."

Over-apologizing makes you sound insecure. Native English speakers rarely apologize for normal interactions.

过度道歉显得没自信。母语者很少为正常互动道歉。

Owning Small Mistakes (承认小错误)

Quick, no-drama acknowledgments. Don't dwell.

简短、不戏剧化地承认。不要纠缠。

  • "My bad, fixing now." — 我的锅,正在修。(my bad = 非正式但常用)
  • "That's on me — I'll get it sorted." — 这是我的责任——我来搞定。(on me = 我承担)
  • "Good catch — I missed that." — 好眼力——我漏了。(catch = 抓到=发现)
  • "You're right, I dropped the ball there." — 你说得对,那个我没接住。(dropped the ball = 没接住球=失误)
  • "Apologies — I'll re-send." — 抱歉——我重发。
  • "Oops, totally my mistake." — 哎呀,完全是我的错。

Owning Bigger Mistakes (承认较大错误)

Real ownership, no excuses, focus on what's next.

真正担责,不找借口,聚焦下一步。

Structure: acknowledge + impact + fix + prevent (结构:承认 + 影响 + 修复 + 预防)

[What happened]: I deployed the bad config.
[Impact]: Caused a 20-minute outage for staging.
[Fix]: Rolled back, service is healthy now.
[Prevent]: I'll add a config validation step before deploy.

Phrases (短语)

  • "I want to own this — I made the wrong call when I [X]." — 我要担起这个——我在 [X] 时做了错误判断。
  • "This was my mistake. Here's what happened and how I'm fixing it." — 这是我的错。下面是经过和我的解决方法。
  • "I should have caught this earlier. I'm sorry for the impact on the team." — 我应该早点发现的。给团队造成的影响我很抱歉。
  • "I take full responsibility for the slip." — 这次延期我负全责。

Apologizing for Impact, Not Just Action (为影响道歉,不只为行为)

Mature apologies acknowledge how it affected others, not just what you did.

成熟的道歉会承认对别人的影响,不只是你做了什么。

"Sorry I missed the meeting." — 浅。 ✅ "Sorry I missed the meeting — I know that wasted your prep time. I'll catch up async and won't make you re-explain." — 承认影响并补救。

"Sorry the bug went out." — 浅。 ✅ "Sorry about the bug — I know it cost the support team a busy morning. I've added monitoring to catch this class of issue." — 承认对别人的影响。

Apologizing in Writing (书面道歉)

Quick Slack apology (Slack 快速道歉)

Hey — quick apology. The PR I merged broke staging for ~30 min. 
Already rolled back. Adding a check so it can't happen again. 
Sorry for the noise!

Email apology (邮件道歉)

Subject: Apology for the missed delivery on Project X

Hi team,

I want to acknowledge that we missed the Friday delivery on Project X.
This is on me — I underestimated the integration complexity and didn't
flag the risk early enough.

What we're doing now:
- New target: end of next Wednesday (committed)
- I'll send daily updates until we ship
- Postmortem on what to change in our estimation process

Thanks for your patience. Happy to discuss if useful.

— [Name]

What NOT to Do (不要做的事)

Don't make excuses (不要找借口)

"Sorry, but the API team didn't give me what I needed." — 听起来在甩锅。 ✅ "This is on me. I should have escalated the API blocker earlier." — 担责。

Don't apologize and then defend (不要道歉后又辩解)

"Sorry, but I was really busy and you didn't tell me clearly..." — "Sorry but" 等于没道歉。 ✅ "You're right, that wasn't acceptable. I'll do X to fix it." — 干净的道歉。

Don't over-grovel (不要过度卑微)

"I am so so so sorry, this is terrible, I feel awful, I can't believe I did this..." — 让对方反过来安慰你,本末倒置。 ✅ "I'm sorry. Here's what I'm doing to fix it." — 简洁、专业。

Don't apologize for things that aren't mistakes (不要为不是错误的事道歉)

"Sorry for disagreeing with you." — 不同意不是错。 ❌ "Sorry for asking questions." — 提问不是错。 ❌ "Sorry I have a different opinion." — 有观点不是错。

Receiving Others' Apologies (接受别人的道歉)

Gracious responses (得体回应)

  • "No worries — happens to all of us." — 没事——大家都会遇到。
  • "Appreciated. Let's move on." — 谢谢。继续吧。
  • "Thanks for owning it. What can I do to help?" — 谢谢你担责。我能帮什么?
  • "All good. Glad you flagged it." — 都好。多亏你提了。
  • "Don't sweat it." — 别担心。(sweat it = 出汗=焦虑)

When the mistake had real impact (当错误真的有影响时)

Don't pretend it didn't matter. Acknowledge, then move forward.

不要假装没事。承认一下,然后向前看。

  • "I appreciate the apology. The bigger thing is what we change going forward — let's talk about that." — 谢谢你道歉。更重要的是接下来怎么改进——我们谈谈这个。
  • "Thanks. I know it was rough. Let's focus on the postmortem." — 谢谢。我知道挺糟的。我们聚焦在 postmortem 上吧。

Public vs. Private Apologies (公开 vs. 私下道歉)

When to apologize publicly (何时公开道歉)

  • The mistake affected the whole team or org.
  • 错误影响了整个团队或组织。
  • Visible action makes others feel safer admitting mistakes too.
  • 可见的行动让别人也敢于承认错误。

When to apologize privately (何时私下道歉)

  • The harm was to one specific person.
  • 伤害是针对某个具体的人。
  • Public apology would embarrass them.
  • 公开道歉会让他们尴尬。

Cultural Notes (文化提示)

"Sorry" in British vs. American English (英式 vs. 美式 "sorry")

  • British English: "Sorry" is used constantly for tiny things ("Sorry, could you pass the salt?"). It's social lubricant, not real apology.
  • British 英语:"Sorry" 用得很多,几乎是社交润滑剂。
  • American English: "Sorry" is more often a real apology. Use "excuse me" for small interruptions.
  • American 英语:"Sorry" 更接近真道歉。小打扰用 "excuse me"。

Owning > apologizing (担责 > 道歉)

Western tech values ownership over regret. "I own this" is stronger than "I'm sorry."

西方科技公司更看重担责而非遗憾。"我担这个"比"我抱歉"更有力。

Blameless culture (无指责文化)

In good engineering teams, mistakes are treated as system failures, not personal failures. Ownership is about fixing the system, not flagellating yourself.

在好的工程团队,错误被视为系统失败,不是个人失败。担责是修复系统,不是自我鞭笞。

  • "This shouldn't have been possible — let's fix the system that allowed it." — 这本不该发生——我们修一下让它发生的系统。

Don't apologize for things outside your control (不要为不可控的事道歉)

Native speakers will read this as low confidence or unclear thinking.

母语者会觉得这是不自信或思路不清。

"Sorry the build is slow." (when you didn't write the build) ✅ "Build's slow today — looking into it."

Tips (小贴士)

  • Apologize once, then act — Repeated apologies feel performative. 道一次歉就够,然后行动。
  • Specific > generic — "Sorry I missed the deploy" beats "sorry for everything." 具体优于笼统。
  • Skip "but" — "Sorry, but..." undoes the apology. 别用"sorry but"。
  • Focus on impact and fix — That's what people actually care about. 聚焦在影响和修复上。
  • Don't apologize for normal asks — "Sorry to ask" makes you sound junior. 别为正常请求道歉。

On this page