What does this doc do
When running services, there are always possibilities for things to go wrong, leading to incidents. This doc is used to keep track of all the incidents.
How to use this doc
Copy this doc:
Copy this doc
Clear demo data:
Clear demo data
Tweak pages under
to set up the doc
Familiarize yourself and others with
Delete or hide this page, and start managing incidents the easy way!
Who could use this doc
: to organize incident reponses
: to collaborate on incident investigation and mitigation efforts
: to keep track of ongoing incidents and manage communications to external customers
: to keep track of ongoing incidents
Why use this doc
This doc can facilitate incident resolution by:
Having a centralized place to track all incidents
Allowing anyone to follow along with ongoing incidents, avoiding repeated escalations of the same incident and inquiries of current incident status
Coordinating incident responses between multiple teams, preventing incident responders from stomping on each other
Keeping a detailed log and timeline, facilitating postmortem creation
Utilizing automations to reduce administrative overhead, leaving valuable time to put out the fire
Coda's ritual of innovation: How we created (almost) 100 Packs in one day
The best methods for leading a scrum sprint planning meeting
How Appetiser grew from $2M to $8M in 2 years with Coda
Project Brief with Jira
How To Run A Sprint Retrospective Meeting [+Template]
How to Run a Virtual Hackathon - Coda
Jira + Project Brief
Jira Backlog (template for tutorial)
Epics and issues
Software Quality, Bugs, and SLAs
Redefining HR for the Post-Covid Future of Work
Iterative project management: What is it & when to use it?
Coda's Bug Tracker
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (