Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Critical user flow inventory for one service
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Every SLO is only as useful as the user experience it measures, and most teams start by measuring whatever their metrics system already exports.
First tasks
- Write down every action a user can take against the service in one sitting
- Pull the last quarter of support tickets that mention this service
- Rank each flow by impact and frequency with the product owner
- Commit the ranked flow list to the service repository
Shared SLO glossary for the team
Teams argue for weeks when one person means uptime, another means success rate and a third means the contractual SLA. A one-page glossary defining SLI, SLO, SLA, error budget, burn rate, compliance window and good event versus valid event settles the vocabulary before any target is set. New joiners then read one page instead of three books.
First tasks
- List the reliability terms the team already uses inconsistently
- Write one definition and one local example per term
- Ask a product manager to check the glossary reads clearly to them
- Link the glossary from the handbook and onboarding checklist
First availability SLI from request logs
Availability is the natural first SLI, but the definition hides real choices: which requests count, whether a 4xx is the user's fault or yours, and where you measure. Writing the SLI as good requests divided by valid requests, with each term defined precisely and the query saved, gives the team one number everyone computes the same way.
First tasks
- Choose the measurement point for the service's highest-ranked flow
- Write the good and valid event filters in plain words first
- Translate the filters into a saved query or recording rule
- Hand-check 50 raw requests against the query's classification