[MUSIC] Now that you've seen an example of going through and making a dashboard with some bells and whistles, we need to take a step back to think about important considerations we go into when we create dashboards, that will lead into storytelling. The first consideration is the mechanical process that is used in Tableau. Everything that we've done up until this point has been in worksheets. I only created three in those long lessons that we went through before. Then I use all three of those in my dashboard. However, let's be clear, that's actually not realistic. In fact, you are likely to create dozens of worksheets and only use a handful of them at most for really, really big projects. In fact, the project that I'm working on now has over 100 worksheets, but only 15 of them are used in dashboards. A lot of those worksheets are either tests or looking at different ways of visualizing things, or they're ad hoc requests that come in. So I'll create a worksheet just to be able to respond to that ad hoc request. Those are often not going to be used in the dashboard but they could be the seed of something useful that may end up in a dashboard eventually. Sometimes, a worksheet is just a worksheet and that's okay. Don't hesitate to create worksheets as you need them or to experiment. Only a select few worksheets get to become dashboards. That means you have to be clear on why you are putting a visualization into a dashboard. I hope it's obvious that just because something looks cool, that doesn't mean it needs to be in the dashboard. As Kelly Martin wrote on her blog VizCandy, not pretty, not cool, but beautiful. I might not go as far as beautiful, but a dashboard must be visually appealing, so that the audience is drawn in to see the insights presented in your visualization. Designing bad dashboards is really, really simple, it's much easier to do than designing good ones. Even if the individual visualizations themselves are amazing, our second consideration is making it accessible. The lessons that we learned in our previous courses come into play more than ever. When a user sees a dashboard, it should be easy for her to quickly access the information. Maybe even get the dashboard into her iconic memory space, a term we talked about in a previous course. Our third consideration is the most difficult, it is purpose, who is the user and what is their role? How will they be viewing the dashboard and what will they do with the dashboard? How comfortable are they with the technology? What value will the dashboard bring to them? Will it help management define what's important? Will it educate people in a company? Will there be flags to deal with outliers? What type of dashboard am I creating? Is the dashboard specific or organization wide? Is this strategic or operational? Will it be historical, real-time or snapshot? You really need to think about the answers to these questions as you're designing the dashboards.