User testing and analytics are completely different tools and their purposes should not be conflated. Analytics are for quantitative analysis of the entire UI

User testing and analytics are completely different tools and their purposes should not be conflated. Analytics are for quantitative analysis of the entire UI. For example, if I want to see what tools are and are not being used, only observing 5 workflows would be massively insufficient. Sure, it doesn’t tell me how people feel - but that’s what user testing is for. Analytics can tell me if nobody is using the shiny new button that we put into the menu (at which point I’d do user testing to examine why this is happening), or that many users make heavy use of an item buried three levels deep in sub menus that we thought wasn’t important (but maybe turns out to be essential to some specialized workflow).