Skip to main content

Week 8 Lecture: Friendship and Group Communication

The six real components of an effective apology, which matter most, and the incident-report format

Week
8
Date
27 April 2027
Lab
Friendship and Group Communication
Reflection due
4 May 2027

Open the slides

Introduction

“I’m sorry you felt that way, but if you’d actually let me finish—” — read aloud, verbatim. What’s wrong with it, before we explain it? Effective apologies have been studied directly; today’s scope is listening, apologies, and the incident-report format only, the clearest, most directly actionable research in the course.

Definitions

Apology (noun)
a statement acknowledging fault, distinct from a statement acknowledging that the other person has feelings.
Group chat (noun)
a shared messaging thread among several people, notable for periods of total silence followed by sudden, simultaneous activity.
Listening to someone (verb)
to give conscious attention to someone speaking, not while thinking about video games or your coding project.

Body

Check-in: Could you repeat back the last full sentence your neighbour said before this lecture started?

Check-in: Which component does 'I'm sorry you felt that way, but—' completely skip?

Check-in: If you only had time for one component, which one does the research say to keep?

Check-in: Which of the six components is missing from this apology on purpose, and why does the study say that's fine?

Check-in: Why does the format ask for a process failure specifically, instead of just asking 'whose fault was it'?

In-lecture activity

In-lecture activity

Split the room in half. One half drafts a bad apology, missing acknowledgment of responsibility on purpose; the other drafts a fix. Read two or three aloud.

Conclusion

A good apology has real, identifiable components, and some matter more than others — this turns “be a better friend” into a checklist. You can now tell the difference between listening and waiting for your turn, name exactly what a bad apology is missing, assemble a real one, and write up a mix-up as an incident report that traces the actual reason instead of assigning blame. Coming up: this week’s lab (the ghosted-reply role-play and incident report), and Assignment 2 (Touch Grass Field Study) due this Friday at 12:00.

This week’s reflection, due 12:00 Tuesday of week 9: name your friend group’s actual load-bearing member — the person whose absence from a plan is most likely to cancel it — and describe why.

References

Teaching team