A postgraduate seminar on why apologies succeed or fail. Students diagnose real apologies for their components, motives, timing and power, then design and defend responses of their own, building toward what a perfect apology would even mean.
12
teaching weeks
3
assessments
10
sessions
7
movements
What you will do
Every week you take a real apology — public or personal, someone else's or your own — and put it through the same four-stage cycle. It isn't a formula to memorise; it's the shape of the thinking every assignment in this course asks for. What changes week to week isn't the cycle itself but the complication layered on top of it: whose apology it is, who's watching, who holds the power, and what's actually owed once "sorry" has been said.
Stage 01
Read the situation
You start with what actually happened: who was harmed, who's speaking, and whether an apology is even the right response. Nothing gets drafted before this is settled.
Stage 02
Build the apology
Acknowledgement, responsibility, explanation, and repair are separate moving parts, and timing decides how they land. You assemble a version where each piece is actually doing work.
Stage 03
Stress-test it
The same wording can succeed in private and fail in public, or the other way round. You check it against audience, power, and context, and look for the phrasing that would make things worse.
Stage 04
Revise and deliver
Feedback exposes what the first draft missed. You revise tone, medium, and timing until it's something you'd actually be willing to send — not just something that reads well.
The anatomy of an apology
Weeks 2 and 3 take the four-stage cycle apart and look at what "build the apology" is actually made of. These four components nest inside each other rather than sitting in a list — pull one out and the others still stand, but the apology reads differently, which is exactly the ablation test Week 3 runs on real examples.
Acknowledgment of harm
Naming specifically what happened and who it affected — not “mistakes were made,” but what was actually done.
Acceptance of responsibility
Owning the action without deflecting it onto intent, circumstance, or the person it landed on.
Expression of regret
The part that reads as feeling something about the harm, rather than only reporting on it.
Commitment to repair
A concrete, checkable change — the piece that turns the apology into something other than words.
How the semester unfolds
The course doesn't front-load a formula and spend twelve weeks applying it. Each movement complicates the central question again — first what an apology is, then what it's made of, then why it fails, then how context, power, and aftermath change everything that came before.
- A
Week 1
What is an apology?
- B
Weeks 2–3
What is an apology made of?
- C
Weeks 4–5
Why do apologies fail?
- D
Weeks 6–7
How does context change an apology?
- E
Weeks 8–9
Who has the power to apologise, demand one, or reject one?
- F
Weeks 10–11
What happens after sorry?
- G
Week 12
Can a perfect apology exist at all?
Who it is for
This isn't only for people who want to get better at apologising personally — it's for anyone who ends up designing, evaluating, or responding to apologies as part of what they do. If one of these sounds like you, the material has somewhere to land.
For writers & communicators
Communicators
If you already think about how wording and framing change what a message does, apology is one of the clearest cases to study — the stakes make every choice visible.
For product & service people
Designers and builders
Products, services, and systems fail. This course is about exactly the moment after that — the support message, the public statement, the incident report — and what makes it land or backfire.
For team members & leads
Team members and leaders
Conflict, feedback, and responsibility come up in every team. This course gives you a way to think about who owes what to whom, and why some corrections land while others don't.
For the curious
Curious skeptics
You've noticed some apologies land and others make things worse, and you want a real account of why — the actual mechanics of what's said and what it does, not generic reassurance.
Same mistake, two responses
The difference between these isn't tone — it's structure. The left column is what Week 4 spends a whole session pulling apart: hedged acknowledgment, no ownership, no repair. The right column is why Weeks 2 and 3's four components hold up under the same pressure.
Same mistake, hedged
- I'm sorry if anyone was upset by what happened.
- That's not really how I remember it going, though.
- Anyway, let's just put this behind us.
Same mistake, owned
- I missed the deadline and didn't tell you until it was too late.
- That's on me — I should have flagged it a week earlier.
- Here's what I'm changing so it doesn't happen again.
