3 ms·
We've started using it at our org in early 2019. Each product team has developed, or is developing a list of 3 SLOs to be treated as high priority. This means
by amacalac 7y ago
We've started using it at our org in early 2019. Each product team has developed, or is developing a list of 3 SLOs to be treated as high priority.
This means when we miss our SLO targets, that team drops all in progress work to fix what it broken.
Some teams actually started with broken SLOs, which meant pausing the roadmap to tackle performance concerns.
It's been working well. Improvements against SLO targets have been seen to have measurable impact with users. This has been in the form of "completing more steps successfully" while they use our product.
The aim overall has been to decrease user frustration, and improve user satisfaction – and to that end it's been very effective.
- tnolet 7y agoThis sounds like a great trajectory. Like how starting with a broken SLO is fine. Bit like starting with a failing test and making it pass. Did you have trouble using tooling to measure and report these SLO’s?