I am designing a portal that allows the user to add mutiple widgets/modules to their personalized dashboard. I've done extensive user research, but I am unsure if the widgets/modules should be pre-populated with data. The argument against this is the widgets/modules are highly customizable to the point where it is hard to predict what a particular user type needs in each widget/module.
I've been tasked with developing the requirements and UX for an
Intranet. The IT folks are talking about a portal model with the
multitude of legacy applications fully integrated as portlets.
I think that a personalized dashboards with single sign-on and links
to apps is OK with info feeds to the dashboard as appropriate.
My fear is that the portlet approach is too complex to successfully
design and implement. This sounds like the type of project destined
to fail. I was wondering if anyone has evidence-based POVs on Portals
vs. Dashboards from a UX / Usability / Project success viewpoint.
I am designing a Dashboard for keeping track of trainings that users have to
go through. The dashboard has 4 modules. I am using red, yellow, and green
colored rounds to show status. Can I make the legend circles smaller so that
users focus more attention on the their staus circle? What do you think?
Moreover, if you can point me to some resources on Dashboard design that
would be great.
We have been working on a portal type application and have the notion of a
customizable dashboard. So far in usability testing 6 out of 6 users have no
idea why we have a page call dashboard. It doesn't quite seem a problem
in function, but in metaphor.