# Own the service after deployment

Taiga Learning · Worksheet
https://taiga.training/en/lessons/operations/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Define a service signal from the user’s perspective.
- Separate incident coordination from technical investigation.
- Plan maintenance and recovery as continuing responsibilities.

## Exercise
Write a one-page operating note for the fictional customer export. Include one user-facing signal, its target, an alert recipient, a safe first response, a recovery limit, and a maintenance owner. State what the monitoring cannot detect.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
Production use creates ongoing work. Name the service owner, response path, recovery method, and maintenance capacity before users depend on it.

## Sources
- [Google SRE: Implementing SLOs](https://sre.google/workbook/implementing-slos/)
- [Google SRE: Incident Response](https://sre.google/workbook/incident-response/)
- [Google SRE: Example Error Budget Policy](https://sre.google/workbook/error-budget-policy/)

This worksheet supports learning. Completing it does not itself authorize a production change.