This isn't a rant against designing pretty stuff, let it just be clear. However, on operational dashboards especially, the goal is to create something that is coherent with the jobs to be done, that is useful and usable over any aesthetic goals.

It all depends on who is end user. hence my questions on the goals to achieve and the users supposed to use this.

Stripe mobile dashboard (a pro dashboard) is a great example a really well executed useful dashboard that is also insanely pretty.

Bloomberg dashboard is also a pretty great example of a really well executed and useful dashboard that is also insanely ugly.

I'm under the impression that a part of the designer community is confusing detailed answer and pretty designs with meaningful answers and usable designs.

You're raising a very interesting topic, but I'm not saying they are.

Meanwhile, aesthetic over usability is the real issue of this design proposal.

Thanks for getting back.

I don't think you have properly understood my questions.

In order to carry on a design job, you need to have a very strong understanding and opinions about what, for who, and why you're working on this. Way before firing up Photoshop.

Your answers do not show an understanding of these. I could have pasted that on any other design to explain it and it would(n't) work.

I have trouble, considering the reference you're giving, believing DB is actually using something even remotely derivative from that in production. I'd be happy to see the finale product you shipped to them.

Again, this is only a feedback for you to get on to where the real work is. And there are plently of insanely interesting questions to be answered in the dashboard spectrum.

No offense, but:

• What is the point of this UI?
• What issue is this solving?
• What help is this giving to its users?
• What are the core actions for them?
• The core infos to take from it?

Real exploitation dashboards for such purposes aren't pretty, they are usable, and useful.

This is pretty.