---

title: "Post-Mortem Conversations with Clients"

module: 10

module_title: "Crisis & Recovery"

order: 4

access: "paid"

summary: "How to run the follow-up conversation after something goes seriously wrong: a transparent timeline, a blameless root-cause analysis, one clear acknowledgment of responsibility, and specific prevention measures. Done well, this conversation strengthens trust rather than reopening wounds."

related:

• "delivering-bad-news-effectively"
• "turning-criticism-into-collaborative-problem-solving"
• "following-through-on-commitments"
• "rebuilding-trust-after-mistakes"

---

Post-Mortem Conversations with Clients

After something goes seriously wrong on a project, there's a conversation that needs to happen. Not the crisis response (that's separate), but the follow-up: here's what happened, here's what we learned, here's what we're doing so it doesn't happen again.

Most people dread this conversation. I've come to see it as an opportunity. Done well, a post-mortem actually strengthens trust, because it shows maturity, transparency, and genuine commitment to improvement. Done poorly, it reopens wounds or creates new anxiety.

Why this matters

If you skip the post-mortem, clients are left wondering whether you learned anything and whether it'll happen again. If you handle it defensively, they wonder if you're taking it seriously. If you do it well, they walk away thinking "okay, they messed up, but they handled it like professionals."

The principles

Analyze blameless internally first. Before talking to the client, understand what actually happened. Focus on systems and processes, not individual failures.

Be transparent about what happened and why. Clients respect honesty. A clear, factual timeline builds credibility.

Own mistakes without overdoing it. Take responsibility where it's yours. Don't grovel. One clear acknowledgment is more effective than repeated apologies.

Focus heavily on prevention. What clients really want to know is: will this happen again? Specific prevention measures matter more than detailed explanations of what went wrong.

What a good post-mortem looks like

"I want to walk you through what happened last week, what we learned, and what we're changing.

What happened: [clear timeline of events]

Root cause: [honest assessment, focused on systems not blame]

Impact: [what was affected, for how long]

What we did well in the response: [specific positives]

What we could have done better: [honest self-assessment]

What we've changed:

1. [Specific technical improvement]
2. [Process change]
3. [Monitoring or alerting enhancement]

All three are already implemented. We'll review their effectiveness in 30 days.

What questions or concerns do you have?"

Tips

1. Wait until emotions have cooled before holding the post-mortem
2. Prepare a written summary to share
3. Focus on "what" and "how," not "who"
4. Be specific about prevention, not "we'll do better"
5. Acknowledge the impact on them
6. Follow up 30 days later: "Here's what we implemented and how it's working"

How this connects

Post-mortems draw on delivering bad news (similar honesty and structure), turning criticism into problem-solving (the client may still be frustrated), following through (you must actually implement what you promise), and building long-term relationships (how you handle failure defines the relationship as much as how you handle success).

Things to try

• After your next significant incident, schedule a formal post-mortem with the client
• Use a blameless framework: timeline, root cause, prevention
• Prepare a written summary before the meeting
• Be specific about what changes you're making
• Set a 30-day follow-up to report on the effectiveness of changes

Template: Client Post-Mortem Summary

Use this when: the crisis is over, emotions have cooled, and you're walking the client through what happened and what's changed.

Channel: Document

```template

[PROJECT] Post-Mortem — [INCIDENT] on [DATE]

What happened

[TIMELINE OF EVENTS]

Root cause

[ROOT CAUSE ASSESSMENT]

Impact

[IMPACT DESCRIPTION]

What we handled well

[RESPONSE STRENGTHS]

What we could have done better

[HONEST GAPS]

What we've changed

1. [TECHNICAL IMPROVEMENT MADE]
2. [PROCESS CHANGE MADE]
3. [MONITORING ENHANCEMENT MADE]

All of the above are [already implemented / in progress with a target of DATE]. We'll review how they're holding up in 30 days and report back.

Responsibility for [THE PART THAT WAS OURS] sits with us, and we've taken it seriously.

What questions or concerns do you have?

```