# Example 05 — Postmortem Lite

## Scenario

A launch or feature underperformed, and the team needs a lightweight but useful review.

## Input

> "We launched a feature last month and adoption was weaker than expected. Help me write a lightweight postmortem."

## What good output looks like

A strong `pm-workbench` response should:

- compare expected vs actual clearly
- identify root causes, not just symptoms
- avoid blame-heavy language
- extract specific lessons and next actions
- produce a review format the team can reuse

## Expected output shape

**Postmortem Lite**

## Example response shape

- what was reviewed
- original goal
- outcome summary
- expected vs actual
- what worked
- what did not work
- root causes
- key lessons
- action items
- reusable takeaway

## Why this is useful

Postmortems are often either too shallow or too blameful. This template helps teams learn in a way that improves future product decisions.
