Though you have to be careful not to fall into the https://xkcd.com/1172/ trap.

Sometimes a user might think they need feature A to make task B easier when in reality instead of doing B they actually want to do C but they never thought of it that way.

If you implement A, you take on maintanance burden when C would be way easier to implement and potentially much more useful for the majority of your users.

The way to tell whether the user needs feature A or C is by talking with them, and watching them use your product in context of their overall work. Telemetry does neither, and will not reveal to you that the user needs C instead of A. On the contrary, it's likely to make you double down on A, because that's what shows up in the data.