Discussion: Dashboard cards and functions
See prototype: https://xd.adobe.com/view/e2ac3e6e-113d-4d77-a71d-c2b19526e9cc-b7ff/?fullscreen
In our weekly meeting, lots of questions came up, such as:
- are the counts totals?
- should they be totals for some timeframe (1 day, 1 week etc)
We should determine what is the purpose of the dashboard and how to get the most value out of it?
We could certainly start it with the prototype design and gather user feedback from our UAT sessions.
As long as the main purpose of this software is demonstration, we probably don't have lots of partners, credentials etc. Hence I'd say total counts are appropriate at this stage.
However, most important is information that requires attention/interaction. So we could make the open tasks also more prominent on the dashboard