Playbooks are a great way to create any kind of document that can help speed incident resolution. We can see them as a collection of instructions broken down as simple as possible to empower someone to resolve a particular incident (even if they have minimal experience.)
Playbooks are automatically attached to incidents when they match configured condition (for example: severity, service, functionality, team impacted ). You can see these fields in the screenshot below. If you have Playbooks or supported documentation hosted internally you can link to them in the "External URL" field, and you can provide detailed instructions in the content field.
On the above example, the Database outage playbook will be attached to any incident with the SEV2 severity or the customers-postgresql-db microservices. Please note that this is all OR logic currently, meaning this playbook will be attached to an incident that has just one of those matching condition, such as SEV2 severity for example.
Additionally, at the bottom of the Playbook details page you have the ability to append any relevant tasking that needs to be done during the incident.
Playbooks are a great way to prevent a single person from becoming the de facto expert on how to resolve a particular problem. We don't want one person on the team to be the only one to know how to bring a critical system back online.