Powerful Phrases for Situations You Cause

Core idea

Every workplace has a difficult coworker. Statistically, sometimes that coworker is you. The same five-step model the book has been training you to use on others — think first, gain understanding, define the problem, offer a solution, agree on resolution — works just as well when run in reverse. The mechanics are symmetric; only the direction of accountability flips.

This topic completes the model by treating self-repair as a peer of other-repair. Two scenarios make up the work:

1. You know you caused harm. You take the initiative — you do not wait to be confronted. You go to the other person, apologise first, define what you did, and propose a way forward.
2. Someone confronts you about something you did. You regulate the urge to defend, listen all the way through, and lead the conversation through the same five steps — even when the other person delivered the feedback badly.

Author's argument: When you cause the problem, the first words out of your mouth should always be a phrase of apology, followed by a specific definition of what you did. Owning a mistake quickly tends to produce a fast, positive response and keep the working relationship intact.

The least instinctive direction for most people is defending less and owning more. The chapter's value is making that move structured and low-cost.

Why it matters

Defensiveness is the default reaction to feedback. It feels protective in the moment and corrosive in the medium term: the relationship strains, the misunderstanding compounds, and the original mistake becomes secondary to the bad exchange that followed. The Jodie–Ted scenario in the source shows this exact arc — Jodie's initial, defensive response sours a relationship over a small concrete issue that a single owned conversation could have resolved.

The reframe matters for three reasons.

You are a difficult coworker to someone

Self-awareness is asymmetric: you notice when others snap, miss deadlines, or break confidences far more readily than when you do. Assuming you are never the cause is statistically wrong. Treating self-repair as a routine skill rather than a rare event makes the move available.

Owning early is cheaper than owning late

A quick, voluntary apology — delivered before the other person has to confront you — preserves goodwill. A reluctant apology delivered after a confrontation arrives loaded with whatever defensive exchanges came before it. The cost grows with delay.

Negative feedback is a growth signal you cannot manufacture

You cannot see your own blind spots from the inside. Someone telling you what you did wrong — even badly, even in anger — is information you would otherwise pay good money for in coaching. The price of admission is the ability to receive it without flinching.

Key takeaways

Mental model

The five-step process from topic 3 runs the same way when you are the cause — only the roles flip. The diagram below shows both directions side by side: the left lane is what to do when you know you caused harm; the right lane is what to do when someone confronts you about something you did.

Copy sourceZoom

Practical application

The categories below cover the most common self-caused situations. For each, the move is the same: apologise first, define what you did with specificity, acknowledge the impact, then commit to a concrete change. What changes is the language.

When you missed a commitment

Missed deadlines, forgotten promises, follow-through that never came — all sit in the same family. The temptation is to explain (the calendar slipped, the meeting ran long, the other thing was urgent). Explanations function as defenses; they shift attention from impact to intent.

Opener: "I owe you an apology. I committed to send you the revised draft by Friday and I did not. I let you down."

Avoid:

• "I meant to but…"
• "It was on my list, but the X thing came up…"
• "I did not realise it was that urgent."

Repair: Acknowledge the downstream cost ("I know this pushed your timeline out by a day"), then commit to a specific behavioural change you can actually deliver — block the calendar, send a delivery date you can keep, propose a check-in cadence.

When you made a mistake that hurt someone else's work

This is the costliest scenario because the harm is concrete and visible. The pull is to minimise ("it is a small thing"). Resist it; let the other person decide whether it is small.

Opener: "I made a mistake in the report and it affected your section. Specifically, I overwrote your edits when I merged my draft. I am sorry."

Avoid:

• Diminishing the impact.
• Framing the mistake as a process problem rather than your action.
• Promising a vague "I'll be more careful."

Repair: Offer to do the corrective work yourself. Ask the other person what would actually help. Then make the specific change to your workflow that prevents the repeat (a checklist step, a review pass, a tool setting). Tell them what the change is — accountability is sharper when the fix is named.

When you spoke sharply

Snapping in a meeting, a curt reply over chat, a tone that landed worse than you meant. The instinct is to disclaim ("I did not mean it that way"). Intent is not the relevant variable; impact is.

Opener: "In the meeting yesterday, I cut you off when you were presenting the budget numbers. That was rude of me. I am sorry."

Avoid:

• "I did not mean to be sharp."
• "Sorry if I came across that way" — the "if" makes the apology conditional and lands as a non-apology.
• Justifying the tone with whatever was stressing you.

Repair: Name the behaviour, not the feeling that drove it. If the harm was public, the repair should also be public — or at least visible enough that the people who witnessed the original moment can see the correction.

When you broke trust

Broke a confidence, took credit you did not earn, dismissed something that mattered to someone. This category is the hardest because the harm is to the relationship itself, not to a specific task.

Opener: "I told Sam about the situation you confided in me last week. You trusted me and I broke that trust. I am sorry."

Avoid:

• Explaining why you did it.
• "It came up in conversation" — the passive voice that lets you off the hook.
• Promising it will not happen again without saying what you will do differently.

Repair: Acknowledge that trust is not rebuilt by an apology — it is rebuilt over time, by the absence of the same behaviour. Ask the other person what they need from you going forward. Accept that they may need distance for a while, and that this is part of the repair, not a sign that the apology failed.

Receiving feedback you did not see coming

When someone confronts you and you had no idea anything was wrong, the urge to defend is overwhelming — the accusation feels unfair because it is, from your point of view, news.

Example

You are leading a project review meeting on a Tuesday morning. Your colleague Priya is walking through the timeline slide. Mid-sentence, you cut her off — "Yes, yes, but the real question is the dependency on the data team" — and pivot the discussion. The meeting moves on. You notice, two slides later, that Priya has gone quiet. You feel the flush of having done something rude.

Two paths are open. Most people take the first.

Path A — the defensive default. Tell yourself the interruption was justified because the dependency really was the more important issue. Notice the discomfort. Avoid Priya for the rest of the day. Hope she didn't notice. Discover next week that she has stopped volunteering input in meetings you run.

Path B — the structured repair. After the meeting, send Priya a short message: "Got a few minutes after lunch? I owe you an apology about the meeting this morning." When you find her, lead with the specific behaviour:

"I cut you off in the middle of the timeline slide. That was rude and it was the second time this month — I noticed it as I was doing it, and I'm sorry. Whatever I thought I was getting to faster wasn't worth interrupting you for. Can I ask: did it land the way I'm afraid it landed?"

Note what this opener does:

• Names the specific action ("cut you off in the middle of the timeline slide"), not the category ("was a little impatient").
• Acknowledges the pattern, since it was the second time — owning the pattern is the part that builds back credibility.
• Does not say "I did not mean to". Intent is irrelevant.
• Asks Priya to describe the impact rather than assuming it.

Priya might say it was fine; she might say she was frustrated; she might say she'd noticed the pattern too. Whatever she says, the move now is to acknowledge the impact in her words, and commit to a specific change — "In meetings I'm running, I'm going to wait until someone finishes the slide they're on before redirecting. If I catch myself doing it again, please call it out in the moment."

The whole exchange takes four minutes. The cost of not having it compounds for months.

Related lessons