Writing Clear Post-Mortems that Build Inter-Departmental Trust
Designed for Cross-functional project leads responsible for drafting post-mortems after high-impact incidents involving multiple departments (e.g., DevOps managers collaborating with QA, Product, and Customer Support). to spark real collaboration and high-energy learning.
A 90-minute hybrid workshop for mid-career professionals who regularly conduct incident reviews. The group struggles with defensiveness, unclear language, and lingering mistrust between departments after post-mortems. Attendees are technical but lack formal communication training. Session is designed with both remote and in-person participants, using collaborative digital tools and breakout spaces.
Post-Mortem Detective Challenge
Kick off by showing a short excerpt from a real, anonymized post-mortem (“A database outage caused 4 hours of downtime. QA flagged the issue, DevOps responded, and Support managed customer calls.”). Ask participants to jot down what questions they have after reading. This sparks curiosity and demonstrates information gaps.
Tap to view the full activity.
Why this works
Curiosity increases engagement by highlighting what’s missing and motivating participants to seek clarity. It also models the reader’s mindset.
Blame Game: Spot the Trap
Show two short post-mortem excerpts: one with subtle blame (“QA failed to update tests”), one with neutral, process-focused language (“Test coverage was incomplete; QA and DevOps will review together”). Ask participants: Which fosters trust? Why? Reveal that even subtle language shifts can impact perceptions.
Tap to view the full activity.
Why this works
Directly surfaces hidden misconceptions about language neutrality and demonstrates how blame can creep into reports unintentionally.
Quick-Fix Rewrite Jam
Hand out a single problematic sentence (“DevOps missed a critical alert.”). In pairs or breakout groups, spend 2 minutes rewriting it to remove blame and clarify action. Groups share their version in chat or on sticky notes, low-pressure and rapid-fire.
Tap to view the full activity.
Why this works
Low-stakes practice builds confidence and models collaboration. Short time frame prevents overthinking and keeps it fun.
Cross-Team Trust Speed Round
Run a rapid-fire activity: Each person has 30 seconds to name one thing a post-mortem could do to build trust between departments (“Show how everyone contributed to the fix,” “Highlight lessons, not blame”). The facilitator keeps energy high and moves quickly.
Tap to view the full activity.
Why this works
Fast-paced sharing energizes the room and surfaces diverse perspectives. Social proof shows that trust-building is valued and possible.
Case Study: Collaboration Crisis
Present a real-world dilemma: After a major outage, DevOps and QA have conflicting narratives in the post-mortem. Ask: ‘How would you reframe this to align both teams?’ Give 3 plausible options for framing (e.g., joint timeline, lessons learned, shared action plan). Participants vote and debate best choice.
Tap to view the full activity.
Why this works
Using an authentic dilemma grounds abstract concepts in practical reality. Voting and debating engages critical thinking.
My Trust-Building Commitment
Invite participants to privately write one concrete action they’ll take next time they draft a post-mortem (“I’ll check for blame language before sharing,” “I’ll invite another department to review my draft”). Optionally, share with a partner or post anonymously on a virtual board.
Tap to view the full activity.
Why this works
Personal commitment increases transfer of learning from workshop to workplace. Sharing builds accountability and connection.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.