Week 11: When Not to Apologise

A team lead says "sorry if anyone was affected by my decision" within the hour — before anyone knows what decision, or whether it was theirs

3 May 2027

Slides: pending upload

A complaint surfaces on a team. Within the hour, the team lead posts: “I’m sorry if anyone was affected by my decision.” At this point, no one — including the team lead — has established what decision caused the problem, or whether it was the team lead’s call at all.

The conditional “if” here isn’t Week 4’s evasion. It’s what happens when an apology is issued before there’s anything specific yet to acknowledge — the vagueness is a symptom of timing, not of dishonesty. And it carries two real costs. First, it can settle the question of who is responsible before that question has actually been investigated, foreclosing the version of events that would let anyone say anything specific. Second, if the facts turn out different — someone else made the call, the harm was of a different kind entirely — the apology has to be revised or withdrawn, which reads worse than saying nothing yet would have.

A costlier version of the same mistake: a company, after a safety incident, issues a full public apology and a remedy commitment the same day, before any investigation. The investigation later finds a different root cause. The remedy they promised turns out to be aimed at the wrong problem, and the company now has to explain, publicly, why its own fix doesn’t fix anything — a worse position than having said, initially, “something went wrong, we’re finding out what.”

This isn’t an argument for silence#

A different case shows the opposite failure. A person clearly at fault already knows they’re at fault, and delays anyway — behind language like “we’re still looking into it” — not to learn anything, but to manage their own legal or reputational exposure while the harmed party is left without any acknowledgment at all. That wait is its own harm: being kept in suspense reads as being ignored.

The test that separates this from Week 7’s legitimate delay is what the time is actually being spent on. Week 7 defended delay that produces real understanding the apology needs. This delay produces nothing except distance between the incident and any response to it — the facts are already known, and the wait serves only the person who caused the harm.

Between “apologise immediately” and “say nothing,” there’s a third move this week is actually arguing for: acknowledgment without a full apology. “Something went wrong. I don’t yet know the details, but I take it seriously and I’ll find out” commits to nothing false, closes nothing prematurely, and still tells the harmed party they haven’t been ignored.

Two identical calls, two different outcomes#

Two team leads, in unrelated incidents, face the same decision under the same time pressure and make the same call: acknowledge without a full apology, and investigate before saying more. One investigation finishes in an hour and confirms a version everyone could have guessed; the delay cost nothing, and the fuller apology that follows lands well. The other investigation surfaces something genuinely unexpected two days later, by which point the harmed party has spent two days assuming the worst and reads the delay itself as evidence of evasion, regardless of what the investigation eventually found. Both leads followed this week’s reasoning correctly at the moment they made the call — the process was sound in both cases. Only one produced a good outcome, because how long an investigation actually takes isn’t knowable in advance. Judging the decision by the outcome would blame the second lead for a delay that was the right call given what they knew when they made it.

Every week before this one treated the apology as something that should already exist, waiting to be built, fixed, or better delivered. This week is the one place that assumption gets challenged directly: sometimes the task isn’t producing a better apology. It’s recognising that one shouldn’t be produced yet.