I had the pleasure of working with teams that couldn’t even figure out how to use analytics in their product. They had zero idea who was using it and how many people were using it. They ignored the thousands of DB deadlock messages in the logs; well, they just ignored the logs completely, actually. All they cared about was shipping the next feature and getting the one QA guy to agree it was working correctly so the ticket could be closed.

This is much more common than you might think.

Your example is hilarious; it sounds like the team understands analytics just fine if they're solely working towards one metric.

That describes more than just one POS (Point of Sale) company I know of.

This is the default. I have a few teams like this under my charge, currently.

I ask them to protect themselves by logging what data they will need to troubleshoot a new feature.

Next release comes around and there is an issue and guess what...devs asking for access to prod to troubleshoot because they don't have logs.

It is really difficult to contain oneself when getting on a call to quiet three endless chat threads because someone failed to log basic shit.

Days long anxiety-filled shit storms for absolutely no reason.

I have had other teams that would do this and they had to have the fear of God put into them to wake up and start logging. We have real problems to solve without confounding ourselves...