Running Effective Post-Mortems: Productivity AI Prompts

Post-mortems are either a 'blame-game' or a 'learning-factory.' This template makes it a learning-factory. By framing the goal as 'improving our process,' you remove the defensiveness and make the team feel safe to speak up about what went wrong and how to fix it next time.

The Core Blueprint

Software Environment: Outlook (Enterprise AI: Copilot, ChatGPT, Claude, etc.)
Role Focus: Productivity
Execution Complexity: Standard
Taxonomy Tag: #PRODUCTIVITY

PROMPT TEMPLATE

"Compose an invitation. Acknowledge the project completion, state the goal (learning/improving), and suggest a time."

780 RUNS

Strategic Use Cases

This correspondence constraint acts as a direct communication architect. It forces the language model to maintain professional warmth while driving action for Productivity scenarios:

Scheduling a post-mortem for a project that faced significant delays.

Inviting the team to reflect on the lessons from a recently shipped feature.

Execution Workflow

Streamline your inbox architecture with this execution flow:

1
Define the project scope and the meeting's focus (lessons learned).
2
Open your team communication channel.
3
Run the post-mortem-invite template, focusing on growth.

Advanced Optimization

Ensure your correspondence drives immediate resolution by editing the prompt's behavioral tags:

The 'Learning-Factory' Frame
...'This is about process improvement, not assigning blame'—this phrase is crucial for safety.
The 'Success-and-Failure' Balance
...'We'll look at what went well, and where we can improve'—keep the balance.
The 'No-Prep' Promise
...'No prep needed, just bring your honest perspective'—keep it low-barrier.