Difficult Conversations

Navigate the conversations you have been postponing. Internalize the Three Conversations framework (What Happened / Feelings / Identity) and use it to structure the harder conversations of your life — feedback, conflict, declining a client, repairing a rupture, the family conversation about money or time. Stop confusing the content of a difficult conversation with the structure of difficult conversations in general; once you see the structure, the content gets easier. The blameless post-mortem is the engineering-context Difficult Conversation: treat the incident as a system failure rather than a personal failure (third-story framing); separate what happened from what people felt from what it means about the team's competence (the three layers, implicit in the template). Code review is the daily practice: "this is wrong, fix it" engages only the What Happened layer, while the reviewer's actual content — frustration at the recurring mistake, anxiety about the engineer's trajectory — leaks out as terseness. Senior engineers who review well are running difficult-conversations practice without naming it. Where the lens lies, precisely: post-mortems happen after the incident, when both parties are already committed to learning. Difficult conversations happen during the disagreement, when the other person may not agree the conversation should even be happening — or wants to have a different one. The post-mortem structure assumes shared goals; the difficult-conversation structure cannot. That case is harder than any post-mortem you've run.