Investment Platform Dashboard

When we begin to design dashboards, we ask ourselves one important thing :
Is it really required?

Only after we are absolutely clear that the dashboard does add value to the whole equation is when we move forward to think about it.

Do you need a dashboard?
Most products that are designed to solve one problem can still serve the goal they wish to without a dashboard - and in a very decent way, too.

Take for example the most frequent products we use, for instance - Google, Amazon, Airbnb, or even the browser , they all don't come with a dashboard out of the box.

But we don't feel the lack of a dashboard when we use them. Right?

Think of the ramifications when Amazon introduces a dashboard. Think about the stress it puts on you when it says "Overall purchase value - $89,000. Last updated a minute ago" Scary isn't it?

If you do need a dashboard, when?
In contrast, few products can't function without a dashboard. Take for example Google analytics. It would mean nothing without a dashboard showing metrics.

So, the bottom line(s) is (are)
1. Dashboards are not your "should have" features/screens.
2. For products that are designed to solve one pain point, dashboards don't necessarily add a lot of functional value.
3. For products that focus on insights and information as compared to performing an action, say, booking a flight ticket, dashboard does have quite a weight.
4. When a client pushes you to add a dashboard as a part of the product, reason with them. Dig deeper into understanding the purpose before understanding the purpose.

It's always good to not design something that is not important.