Best practices to define SLOs that actually reflect user experience
A marathon runner who trains obsessively on a flat track will have beautiful split times right up until race day when they discover the actual course has hills. Although the preparation was real, their strategy was flawed. This plays out in SLO teams more than anyone likes to admit. At first, numbers look fine and nothing has been triggered. Then, a support ticket comes in showing checkout has been down for 20 minutes. The SLO wasn't broken.