This session makes the case for simple service level objectives based on the correctness and speed of the system from the end-user perspective. There are only two things that are critically important to users: correctness and speed. The site should behave as expected and do it promptly. If that is true, it is available. That can actually be done with data from just one or a few synthetic transactions. We’ll end by showing the power of using just a single synthetic to illustrate both correctness and performance, and build an availability chart on top of that data.