[focusedone]

My experience is that ascertaining exactly what the report consumer wants to see on a dashboard report is, by far, the most difficult part of the process.

Often the consumer would want a visual way to confirm a vague feeling. By the time a data team can ascertain what the consumer actually needs to see, collects and wrangles the data, and builds the dashboard, the consumer may have lost interest or become frustrated and moved on.

Identifying a feeling and graphically representing it with data is an extremely difficult thing which led me to a place of great despair at a previous job.

Anyway, I don't have a good answer for this but I hope you can crack it and become wildly successful doing so!

[former-aws]

sorry a bug took me down, so could not reply earlier. Thank you for your reply and a few follow-up questions and observations. 1. I do agree with you on the challenge between "feeling" vs "what i actually want". Is this about spending more time with the report consumer to understand what they want to see? Or is there something more? 2. How did you solve this problem? I would love to learn how you addressed this, despite all the struggles. 3. If you were to revisit this same problem today, what would you do differently?