You made a call that didn’t pan out. Or you were sharp with someone in a meeting last week and you’ve been half-thinking about it ever since. Or you told a member of your team something was going to happen, and then it didn’t, and neither of you has brought it up.

Nobody puts “professional apologizer” on a résumé. But lead people long enough and it’s a real part of the job — and it doesn’t get easier as you get more senior. It gets harder. The stakes get bigger, the audience gets larger, and the gap between how you think you’re handling it and how your people think you’re handling it gets wider. One survey found that 49% of employees say their boss never or rarely apologizes, while nearly 60% of managers believe they always do. Seventy-one percent of those managers admitted they avoid it out of fear of looking incompetent — even though both groups agreed that owning a mistake is one of the most trust-building things a leader can do.

That’s the trap. The thing you’re avoiding to protect your credibility is the thing that would build it.

And when researchers have picked apart what actually makes an apology work, the answer isn’t eloquence or timing. It’s a clear acknowledgment of responsibility — plus, when it’s on behalf of an organization, a concrete signal that something changes as a result. Reform carries more weight than fault. Which means most failed apologies fail for the same small reason: there’s a “but” hiding in the middle of them.

Over a career you’ll owe roughly nine of these. They sort into three groups, and each group fails differently:

• “I was wrong.” The ones for things you actually did. Apologizing for the wrong call is three steps — admit it, name what specifically went wrong, say what you’re doing differently — with no context-setting that quietly becomes an excuse. Apologizing for how you showed up (you snapped, you cut someone off) should be short and should never rehash what frustrated you, or it becomes a second helping of the offense. And apologizing for breaking trust — a promise you couldn’t keep — means saying the actual thing, not “sorry if you were disappointed.” Get these wrong and nobody quits dramatically. They just stop telling you things.
• “I should have.” The ones for what you didn’t do. Waiting too long on a bad hire or an obvious conflict is so predictable it has a research literature behind it — once we commit, we tend to pour more in as things fail, not less — so this apology has to name the delay itself, not just the outcome. Not seeing what was happening has to arrive with a system attached, because noticing is your job: 1:1s that open on the person, not the project. And not listening — when someone did raise it and nothing happened — has to acknowledge the pattern, then actually go back and engage with what they said. A week late still counts.
• “I’m responsible.” The ones you own without having caused. For someone else’s mistake, be specific with whoever was harmed — what broke, what’s changing, by when — and be discreet with your team: naming the individual to protect yourself doesn’t make them careful, it makes them anxious. For a necessary decision made above you, apologize for the cost without distancing yourself from it; “this wasn’t my call” feels like honesty and reads as abandonment. And for the organization, drop the personal defense entirely and go straight to what happened and what changes.

You don’t need to work on all nine. Pick the one you recognized while reading this — the one you’ve been carrying around for a couple of weeks. Because apologizing well isn’t really a communication skill. It’s the willingness to be briefly uncomfortable so somebody else doesn’t have to stay uncomfortable indefinitely.

I go through all nine, with the actual language for each, in this week’s video — worth a watch if one of these landed a little too close.

or article or podcast​

Here's some more resources I recommend:

Boundaries Create Breakthroughs: Most of us assume the path to better work runs through more—more options, more resources, more freedom. And yet total freedom has a way of paralyzing us, and unlimited resources rarely produce the biggest breakthroughs. In Inside the Box, David Epstein digs into the science and practice of constraints: when guardrails actually help, and how self-imposed boundaries can unlock focus and innovation you didn't know you had. He tells the stories of people and organizations that embraced limits to transform themselves—and a few that struggled without them. He even taught me that a study I've heard referenced often doesn't exist! If you're leading a team with fewer resources than you'd like, this one reframes the problem entirely. Click here to learn more.​

Navigating Change as a Team: Change isn't the problem—unmanaged change is. When teams face rapid change without a clear plan, the emotional and logistical strain adds up fast, and performance suffers. In my LinkedIn Learning course, I walk through how to build a shared vision and clear priorities for change, how to reassign roles and responsibilities to support the effort, and how to set communication norms that keep things transparent instead of chaotic. You'll also learn how to gauge your team's capacity and resilience so you can sustain performance for the long haul. If your team is navigating change right now, this one's built for you. Click here to get started.​