For knowing how to improve the software, I would like to write public comments to criticize it so that they can improve it from that (and so that others can publicly criticize my public criticism too if desired).
The benefit of a product that is paid for by personal data is immediate and real to me - I use this product and get benefit about it.
The risk of said personal data being used against me is currently hypothetical. So far, I haven't experienced any drawbacks.
For anything that is privacy sensitive, I use a dedicated privacy oriented software.
To a lot of people that means no telemetry. Look at what happened with the Go compiler telemetry. I think that's the only time I've seen someone actually listen to customer desire and remove telemetry.
Fwiw I'd never work somewhere that was doing telemetry driven development, so at least in my case this isn't true.
If the software is critical, then yes. And I'll opt out. And I'll keep scouting around for a suitable replacement.
Are product people supposed to chant and perform esoteric rituals to gain telekinetic insight into how the product is being used?
I see it as a violation of privacy. I also don't think it leads to good products.
> Are product people supposed to chant and perform esoteric rituals to gain telekinetic insight into how the product is being used?
They should be knowledgeable in their field and leverage their experience to solve problems with the product. No telemetry was used to create the iPhone for instance, it was a product built with a strong vision. When you do telemetry driven development it's super easy to get trapped in local maxima. It also removes the creative process from product design.
Enterprise product features are best off led by sales. What helps sell? What are customers complaining about? The UX bar is low for enterprise so the "too many cooks in the kitchen" model is passable there as long as the functionality matches the market.
I usually try to avoid the later.