Honesty Trade-offs in PM
Public vs internal.
Overview
Postmortem honesty has different audiences. Internal postmortems need full forensic detail to drive engineering learning; public postmortems need redacted detail that respects customer privacy and competitor exposure; customer-facing emails need impact-focused summaries that respect the recipient’s time. Picking one audience and treating the others as afterthoughts produces postmortems that fail at least one purpose.
- Public versus internal. Per-postmortem the public and internal versions. Both audiences need different framings.
- Internal: full detail. Forensic depth for engineering learning. No redaction internally; the team needs the truth.
- Public: redacted detail. Customer privacy, competitor exposure, security implications all redacted with care.
- Customer email plus documented policy. Per-customer the impact-focused summary; per-team the redaction policy documented for consistency.
The approach
Three habits produce honest postmortems for every audience: write two versions, document the redaction rationale, tailor customer email per impacted customer.
- Two versions per postmortem. Internal forensic version and public sanitised version. Both come from the same incident; both serve different audiences.
- Documented redaction rationale. Why each detail was redacted. Future reviewers can challenge the decision; consistency improves over time.
- Customer email tailored. Per-customer the personalised email. Generic broadcasts fail; specific context preserves the relationship.
- Internal full detail plus documented policy. No redaction internally; per-team the redaction policy lives in the runbook.
Why this compounds
Each correctly-redacted postmortem preserves trust on both internal and external sides. The team’s incident-communication fluency deepens; the redaction policy matures into a defensible standard; engineering learning and customer trust both improve.
- Customer trust deepens. Right level of detail per audience. Customers feel respected, not patronised.
- Internal learning sharpens. Full internal detail produces real engineering insight.
- Culture reinforced. Trust on both sides preserves teams and customer relationships.
- Year-one investment, year-two habit. First dual-version postmortem is heavy lift. By the fifth, the redaction policy is settled.