SLO/Template instructions/Organizational

What is the service?

📝 Name it, and link to appropriate documentation. Define it clearly -- which binary or binaries are covered? If some hosts or clusters are covered but not others, be explicit. (If some requests aren't covered, we'll cover that later.)

Who are the responsible teams?

An SLO is generally an agreement between two or more teams (though a team might still benefit when solely operating a service for its own use -- and thus acting as both the service provider and the user). In order for the agreement to be useful, representatives from each team should be involved in drafting it, and must be involved in finalizing it.

The teams listed here should include everyone involved in handling or preventing incidents in the service: the people who receive production alerts, the people who write the code, and the people who build and deploy new releases. It's generally not reasonable to expect a team to reprioritize their own work to meet an SLO that was written without their participation.

Representatives from client services may also be consulted, to provide input on their service's needs.

📝 List all the responsible teams. You're probably already talking to all of them -- but if not, start that conversation before continuing to the next section.

Next, move on to Architectural.