Retrospectives: Do We Need Them & Why?
Retrospectives: Do We Need Them & Why?
Featuring Matthew Dodge
.png)
Retrospectives: Do We Need Them & Why?
Retrospectives: Do We Need Them & Why?
A retrospective (or post-mortem) is a critical part of Incident Response. If you don’t document, share, and learn, everyone misses out on a critical learning opportunity. Retrospectives are designed to help teams collectively learn, iterate, and improve. It involves taking the time to story-tell exactly how an incident took place and discussing how to do better next time. The key is to shine new light on processes, tools, and systems so that you know how to fine-tune.
Description
A retrospective (or post-mortem) is a critical part of Incident Response. If you don’t document, share, and learn, everyone misses out on a critical learning opportunity. Retrospectives are designed to help teams collectively learn, iterate, and improve. It involves taking the time to story-tell exactly how an incident took place and discussing how to do better next time. The key is to shine new light on processes, tools, and systems so that you know how to fine-tune.
A retrospective (or post-mortem) is a critical part of Incident Response. If you don’t document, share, and learn, everyone misses out on a critical learning opportunity. Retrospectives are designed to help teams collectively learn, iterate, and improve. It involves taking the time to story-tell exactly how an incident took place and discussing how to do better next time. The key is to shine new light on processes, tools, and systems so that you know how to fine-tune.
Speakers
Matthew Dodge
Read Bio
Matthew Dodge
Matthew provides onboarding, training, troubleshooting, and overall account strategy for Blameless customers.
.svg)
Video Description
A retrospective (or post-mortem) is a critical part of Incident Response. If you don’t document, share, and learn, everyone misses out on a critical learning opportunity. Retrospectives are designed to help teams collectively learn, iterate, and improve. It involves taking the time to story-tell exactly how an incident took place and discussing how to do better next time. The key is to shine new light on processes, tools, and systems so that you know how to fine-tune.