People don’t know how many cache misses they had, or what IO exceptions and retries led to their poor experience. They know they had a poor experience. No one

People don’t know how many cache misses they had, or what IO exceptions and retries led to their poor experience. They know they had a poor experience. No one will afford to make interviews on the scale of making good statistics. Knowing when I can sunset support for a specific OS or hardware (e.g screen resolution) would require a huge amount of expensive surveying. The telemetry that tells me 20% of my users use 4K screens now literally costs single digit dollars per month. It costs the same as one or a handful of “talking to users”. More importantly, you don’t need to waste precious time when talking to users with asking them what driver version or screen resolution they have. Because of course users are spoken to. Telemetry isn’t instead of talking to users. It’s so that a) you can focus your user conversion on human focused things and b) so that you cover a wider group than you could ever afford talking to. It’s better to be up front with the fact that software does anonymous telemetry and prudent that it actually is good (anonymous, and not using excessive resources).