These are such great points. I know many executives that need to see #4, getting distracted by sparkly interactivity. If I had a dime for every time I heard 'it would be great if we could have an interactive dashboard' I'd be rich ;)
Great video! One mistake that I made in the past is not checking if everyone that should have access to the dashboard did have access and license to the software. Going along with this is to ensure that each user will see the dashboard in its initial state, without filters or any selection (I once had a dashboard in Excel online that when one person was filtering it affected the view of the other person viewing it at the same time).
Oooh what good additions! The access thing is tricky, especially when you explore non-everyday programs (Excel is relatively easy for everyone to access; Tableau isn't). I get that Tableau Reader exists, but it's an extra step. And the real-time filtering! I haven't run into this personally (phew) but can see how this is a very real hurdle to overcome. Sigh. Onwards!
I love all of these points!! For #9 - Keep it in-house...what are your thoughts on outsourcing the creation of the dashboard but then training and transferring "ownership" to somebody internal? That would allow the organization to make the [inevitable] changes necessary going forward (see #10).
Thanks Ann. I'm actually working on a dashboard right now and have been trying to shove everything on one page. I'm glad to hear I don't really have to do that! OMW to give my dashboard components a little breathing room.
If it's static (like a PDF'd one-pager), you can always use one more page. If it's interactive, you can always use one more screen/tab. Or, better yet, as part of the editing process -- keep the most helpful graphs, and let the rest go. That's the toughest mental hurdle for a lot of us, though.
![What Type of Dashboard Do We Need? [4 Types to Consider & Diagram to Download]](http://i.ytimg.com/vi/Hf57j2xcR0g/mqdefault.jpg)
These are such great points. I know many executives that need to see #4, getting distracted by sparkly interactivity. If I had a dime for every time I heard 'it would be great if we could have an interactive dashboard' I'd be rich ;)
I'm so relieved to hear all the data people agreeing with that one!
We can desperately use this approach in our healthcare systems
Yes, agree, unfortunately...
Great video! One mistake that I made in the past is not checking if everyone that should have access to the dashboard did have access and license to the software. Going along with this is to ensure that each user will see the dashboard in its initial state, without filters or any selection (I once had a dashboard in Excel online that when one person was filtering it affected the view of the other person viewing it at the same time).
Oooh what good additions! The access thing is tricky, especially when you explore non-everyday programs (Excel is relatively easy for everyone to access; Tableau isn't). I get that Tableau Reader exists, but it's an extra step. And the real-time filtering! I haven't run into this personally (phew) but can see how this is a very real hurdle to overcome. Sigh. Onwards!
I love all of these points!! For #9 - Keep it in-house...what are your thoughts on outsourcing the creation of the dashboard but then training and transferring "ownership" to somebody internal? That would allow the organization to make the [inevitable] changes necessary going forward (see #10).
YES YES YES. This is a great strategy!!!!!
Thanks Ann. I'm actually working on a dashboard right now and have been trying to shove everything on one page. I'm glad to hear I don't really have to do that! OMW to give my dashboard components a little breathing room.
If it's static (like a PDF'd one-pager), you can always use one more page. If it's interactive, you can always use one more screen/tab. Or, better yet, as part of the editing process -- keep the most helpful graphs, and let the rest go. That's the toughest mental hurdle for a lot of us, though.
Very insightful! Thank you Ann!
Thanks, Grace!