Service ownership map for paging
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Pages go to the wrong person when nobody has written down which team owns which service, queue, cron job and third-party integration. A single table that lists every production component, its owning team and the rotation that gets paged for it ends the 3 a.m. guessing game.
First tasks
- Export the list of services and scheduled jobs from your deployment platform
- Add an owning team and paging rotation column to every row
- Raise each unowned component with the engineering manager by name
- Link the finished map from the paging tool's service descriptions