I just started working for an enterprise software company, and I'm having a hard time integrating validation to see "what works" for the user.
I'm used to working for more consumer-based software, and they aren't "forced" to use the software. However, how do you validate it when your users are forced to use it?
For example, let's say I have 2 sets of tool buttons to A/B Test. One with just icons, one with just words. How would I validate what is the best? In a b-to-c solution, you can often tell by how often the buttons are clicked, how long they stay with the software, how much they use the software -- but what about at an enterprise solution when the users are forced to use the software? How do you design validation in this situation?