Postmortem Renamed to Retrospective

πŸ’€ Postmortem Renamed to Retrospective

The term postmortem comes with the unwanted negative connotation of death and implies a single root cause. At Rootly, we don’t view each resolved incident as dead, but rather as an opportunity to learn and continuously improve.

To better align this approach, we’ve decided to rebrand Postmortem to Retrospective.

Traditionally, postmortems were conducted following major incidents, with the focus on identifying root-causes and how to avoid future occurrences. That’s a great start, however, we believe it would be even better to expand the coverage to all incidents and include discussions on what went well, what didn't go well, contributing factors, and what might we do differently next time.

You will find references to postmortems change to retrospectives within your Rootly app. However, all existing configurations remain the same!

If you’d like to learn more about best practices around retrospectives, please reach out to your Rootly team on Slack!

🌝 New & Improved

πŸ†• Workflow now supports conditions for specific Incident Roles
πŸ’… Rootly API keys are now prefixed with rootly_ to improve key management
πŸ’… Added pin to channel option to Send Slack Message / Send Slack Blocks workflow task to enable auto-pinning
πŸ’… Timeline now shows the previous severity when a change in severity occurs
πŸ› Default role on New Invitation page now matches value set in Team Settings page

Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.