Week 6: Public and Private Don't Apologise the Same Way

The same incident, two apologies — one specific and private, one vague and public — and neither wording choice is simply better

29 March 2027

Slides: pending upload

Same incident, two apologies.

Sent privately, to the person it happened to:

I shouldn’t have brought that up in front of everyone. That was out of line, I’m sorry, and I get why you’re upset.

Released publicly, about the same incident:

I want to address recent comments of mine that some found hurtful. I take that feedback seriously and am committed to doing better.

The private version names the act plainly, because the recipient already knows what happened and needs it acknowledged, not described. The public version is vaguer on every count: “comments… that some found hurtful” describes an effect without naming the act, in a construction close enough to Week 4’s passive deflection that it’s worth asking whether it’s the same failure. It usually isn’t. Full detail in the public statement would mean re-describing, to strangers, exactly what was said to the person it was said to — which re-exposes them, not the speaker. The vagueness here can be doing something other than evasion: protecting the harmed party’s privacy at the cost of the observers’ need for specifics.

Two addressees, one sentence#

A public apology has at least two audiences at once: the harmed party, who needs the act named and answered to; and observers, who need enough information to judge whether accountability actually occurred, plus reassurance that the behaviour has consequences. These pull in different directions. Full specificity serves observers’ need to judge and can violate the harmed party’s need not to be re-exposed. Vagueness protects the harmed party and reads to observers as evasive — which is exactly why Week 4’s passive-voice diagnosis doesn’t automatically transfer here: the same surface move can be deflection in one case and privacy protection in another, and telling them apart requires asking who the vagueness is actually protecting.

Week 5’s four functions don’t disappear once there’s an audience; they split across addressees. Reputation management targets observers. Repair targets the harmed party. “I take that feedback seriously” is built to register as an accountability signal for observers while carrying almost no specific content for the one person who already knows what was said and needed something else entirely — one sentence, two jobs, aimed at two different listeners.

When vagueness stops protecting anyone#

The privacy reading only holds if the vagueness is actually buying the harmed party something. A harder case: the same public statement, released after it becomes known that the company also stayed vague in its private message to the harmed party — who therefore learned the specifics of what was done to them from a leaked internal document, not from the company. Once that’s known, “some found hurtful” no longer reads as privacy protection, because the person it would have protected was never given the specific version either. The test isn’t whether the public statement is vague; it’s whether the specificity the harmed party needed was actually delivered somewhere, privately, at all. Vagueness that’s uniform across every audience, including the one person entitled to the full account, isn’t protecting that person from anything — it’s just withholding, dressed the same way privacy protection would be.

This doesn’t resolve the tension between the two audiences, only names it. Week 7 asks whether timing and medium can shift which audience’s needs end up mattering more.