Super User
Super UserMartin_D
Thank you for your feedback, and great question.
Of course, I don't sabotage anyone's reports without their knowledge
Work on the right visualization starts already in the definition stage if I start working on a new report/dashboard. At this stage, I delve into the business process for which the dashboard is being built, the required metrics, their granularity, what is a good range, and what is a range that requires improvement/immediate response.
The question I don't ask at any stage is how the user wants their reports to look. This is my expertise and "headache".
If the situation is the optimization of other reports, a conversation is still conducted with the user about the processes, and of course I update him that the visual appearance of the reports will change.
In the event of resistance to one visualization or another, and this happens because I don't build reports that everyone is used to.
I show him two options: his preferred option and the one that should be, and ask an informative question (not what he likes more), and then he realizes for himself what is the most efficient way and flows with me.
Here is a more natural-sounding translation:
Of course, I would never sabotage someone's reports without their knowledge.
The process of creating the right visualization starts in the definition stage, when I'm first starting work on a new report or dashboard. At this stage, I take a deep dive into the business process that the dashboard will be used to analyze. I identify the required metrics, their granularity, and what constitutes a good range of values. I also identify any areas that need improvement or immediate attention.
I never ask the user what they want their reports to look like. This is my expertise and responsibility.
If I'm optimizing existing reports, I still have a conversation with the user about the business processes involved. I also let them know that the visual appearance of the reports will be changing.
If a user resists a particular visualization, it's usually because it's not what they're used to. In these cases, I show them two options: the option they prefer, and the option that I believe is the most effective. I then ask them an informative question that helps them see the benefits of the more effective option.
In most cases, this approach is successful in getting the user to agree to the more effective visualization.
I hope this is helpful! Let me know if you have any other questions.