Performance is fairly concrete to measure, mostly as part of click responsiveness. https://developers.google.com/web/fundamentals/performance/rail https://deve

Performance is fairly concrete to measure, mostly as part of click responsiveness. https://developers.google.com/web/fundamentals/performance/rail https://developers.google.com/web/fundamentals/performance/r... They can also measure it live in the website, the median response time of API calls and so on. Github has said this: "We’re quite obsessed with performance. We want to make sure the site is always performant and continually fast. For a Rails app, github.com is a really, really quick site and we have a motto that “It’s not shipped until it’s fast.”" https://medium.com/s-c-a-l-e/github-scaling-on-ruby-with-a-nomadic-tech-team-4db562b96dcd https://medium.com/s-c-a-l-e/github-scaling-on-ruby-with-a-n... They can create a performance measurement team, assign tickets based on what they find and prioritize them as part of ticket management. If something is too slow, then maybe it's time to refactor the underlying architecture or subsystem thats making things slow.