The Cross-Team Postmortem Pattern

When two teams' systems combine to cause an incident, the postmortem must include both. The format that prevents finger-pointing and produces shared action items.

Setup

Setup determines whether the meeting becomes analysis or finger-pointing. Senior leads with authority to commit to action items, a neutral facilitator from outside both teams, a pre-read so attendees arrive with shared facts, a time-boxed agenda so the conversation does not sprawl.

• Both teams' leads attend. Senior-enough to commit to action items on the spot. Accountability lands at the meeting.
• Neutral facilitator. Platform team or external runner, never a member of either involved team. Reduces team-vs-team dynamics.
• Pre-read distributed. Timeline and impact circulated before the meeting. Time gets spent on analysis, not catch-up.
• Time-boxed agenda. Explicit "we cover X in 60 minutes" structure. Catches sprawl into territorial debate.

Framing

System-first, not team-first. Frame the question as "how did our two systems combine to produce this?" rather than "whose fault was it?" Each team surfaces its own contributing factors; shared action items go to whichever fix needs both teams to act.

• Combined-systems framing. "How did our two systems combine?" rather than "whose fault?" Forces shared analysis.
• Own-team contributing factors. Each team's lead surfaces their own factors first. Other team listens rather than assigning.
• Shared action items where the fix needs both. Explicit joint ownership for cross-team fixes; clearly owned by one team otherwise. No diffuse "we should..." items.
• Visible language guide. Blameless-language reminder shown at the meeting. Catches old habits before they land in the writeup.

Avoid

Three failure modes turn the cross-team postmortem into the thing it is supposed to prevent: async-only execution where tone gets lost, one-team domination of the conversation, vague action items that nobody actually owns.

• Async-only postmortems. Tone gets lost in writing; tensions escalate. Cross-team work needs synchronous time.
• One-team domination. Facilitator enforces equal speaking time. Both teams' perspectives matter equally to the analysis.
• Vague action items. "Improve communication" is not specific. Every action item names what, who, when.
• Quarterly follow-up retro. Cross-team action-item review per quarter. Catches stalled joint work before it becomes the next incident.