- Sun Jun 29, 2014 6:37 am
#3
We’ve been playing around with a few dashboard designs in our office but I have to say we are still trying to figure this out and would appreciate any experience other organizations may have. What we have learned so far is that it helps to map out all of the users in the office, what are their levels of decision making and what is a particular user’s main reason for visiting the dashboard? Is the user making a decision or reacting to specific events or situations? What triggers a user’s visiting the dashboard? Is there some information the user would routinely review at the start of a work day for example? Or would they visit once a week or several times a day? Would a user go to the dashboard in response to something? What critical decisions do each of the users have to make? Do we need to set up some special conditions where users need to be alerted if a parameter becomes critical? For example, an industrial control dashboard might alert the user that a critical parameter is out of range (similar to the gas gauge or engine-temperature gauge on a car’s dashboard). Good luck playing around with your organization’s dashboard.