[latexr]

> having this kind of data can make for better decisions.

It can also make for worse decisions.

2% of millions of users is still tens of thousands of people. Maybe that feature is terribly useful but only a handful know about it. Cutting it would be a mistake; it should be made more prominent.

Maybe the 20% feature is annoying and that’s why 80% of people actively avoid it. Giving it more prominence would be a mistake; it should be cut.

No amount of telemetry will tell you users are deeply unhappy with the move to an Electron app and the removal of local vaults. You only know that from direct feedback and speaking to them.

[filchermcurr]

That's the trap Firefox fell into, I think. Relying so much on telemetry that only tells a very small part of the story. So they cut features that are useful, but people didn't even know they existed. It seems like this data-driven approach should go: Collect data, form conclusion, try to increase awareness of feature, collect more data, form new conclusion, cut if awareness didn't pan out.