How to Test and Call Out Bad Things

The only reason that I'm okay at calling this stuff out and talking about the problems that happen is because I've made every single one of these mistakes myself. So if you do it correctly, you're way ahead of the competition really. You're making more sound decisions based on better insights as opposed to just random stuff based on broken data. But how do you get people to understand they're doing it wrong? There's an easy way which is to point out that everybody really needs to check that the collection is working in the same ways that we would calibrate the Tills in a retail environment.