```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE,
warning = FALSE,
result = TRUE,
message = FALSE,
comment = NA)
```
\
# Introduction
A dashboard is a collection of several (interactive) graphics that allow viewers to compare a variety of data simultaneously in one place. For example, in the presidential election data, we can create a county-level election map and a state-level map and place both of them on the same graphical page and both maps are coordinated simultaneously. In other words, we can create a dashboard that displays all the views at once, rather than navigate to separate Tableau graphics.
If data in sheets and dashboards is connected to a real-time database, both sheets and dashboards will update in real-time with the latest available data from the data source. There are different types of dashboards used for different purposes.
**Operational Dashboards** – provide a comprehensive snapshot of the performance of a business process that allows us to incorporate a large amount of detail without using too many drill-downs.
**Analytical Dashboards** – use historical data to identify future trends for decision-making. Users with a level of technical understanding of data can interact with the data on an analytical dashboard.
**Strategic Dashboards** – track performance in relation to key performance indicators, to better align actions with strategy.
You can name other different dashboards that are used on different occasions.
# Dashboard Design and Case Study
This section provides some details on dashboard type, designs, and implementation with a widely used data set.
## Some Design Considerations
Several considerations need to be kept in mind when designing an analytical dashboard.
**Audience/Users** - the types of audience and target users determine the level of granularity of information and technical complexities.
**Important and Related Information** - what is the key information? What other information explains or augments the key information? relevant patterns impacted by the key information, etc.
**Appropriate Charts** - refer to the directory of graphics and maps to create individual graphics and put them together to make a dashboard. Each individual graphic should designed based on the basic principles of visual designs that include but are not limited to titles, labels, annotations, color schemes, use of marks and channels, movement, interactivity, etc.
**Dashboard Layout** - is about how to place different but related graphics on the appropriate spots so that the dashboard is easy to understand for users and can effectively deliver coherent information among individual charts. As a convention in analytic dashboards, the key information should be placed on the top, and supporting information should be at the bottom of the dashboards.
**Filters and Animations** - are good for displaying more granular information. However, they should be used only if it is necessary.
**Avoid Cluttered Dashboards** - It is easy to overload a dashboard designer because too much important information is worth being displayed, in particular, when a data set contains rich information. However, dashboard clutter will decrease the efficiency of delivering the key information.
## Working Data Set
We use a widely used Stationery Superstore data set to illustrate the logic and common practices in designing an analytical dashboard.
```{r}
SuperStore = read.csv("https://pengdsci.github.io/STA553VIZ/w10/SuperstoreOrdersData.csv")
summary(SuperStore)
```
There are three types of variables related to Product information, order information, and sales information. Some variables can be used as geo-variables.
## Superstore Profits and Sales
The following dashboard was designed based on the following considerations:
**Users/Clients**: sales manager or similar roles
**Key Information**: Look at the process generation from different perspectives and identify the patterns for making business decisions. For example,
* Sales KPI
* Total revenue (profit)
* Total sales by time period
* Revenue per sale
* Revenue by product types
* Market penetration
* Revenue generation by customer segments
* Average customer lifetime
* Customer satisfaction (net promotor scores, etc.)
* Number of sales lost to competition
* Revenue by territory (regions, customer segments, etc.)
* Revenue by market
* Ratio of selling cost and revenue generation
* and more.....
\
\
**Critiques and Recommendations for Improvement**
\
* Selection of information for visualization
* Design perspectives
+ individual charts
+ Overall design of dashboard (layout)
+ orchestration of individual charts
+ design aesthetics
# Tableau Story Points
Tableau can create a form of presentation of the existing individual chart so we can tell the story based on the individual Tableau charts. In terms of design, it is relatively less challenging since the `story point` uses a sequence of logically connected individual Tableau visual sheets to tell a data story.
Although a little design effort is needed for the story point, the same level of significant design effort needs to be put into individual visual sheets.
The following is an incomplete sample of a story point based on the previous dashboard. Each individual visual sheet should have a brief and descriptive caption about the information.
\
# Assignments of This Week
This assignment focuses on Tableau dashboards and story points. You can choose a data set that has both numerical and categorical variables so you can create several charts such as histograms, scatter plots, frequency tables, pie charts, etc. using both types of variables.
## The Minimum Requirements
I will not give you a data set for this assignment. You can find a data set from any sources including my project data page () that meets the following requirement.
1. Choose a data set with at least two numerical variables so you can construct a histogram and scatter plots.
2. The data set should have at least three categorical variables so you can create pie charts, bar plots, etc.
3. You are expected to use at least one filter that updates all charts in the dashboard (reactive dashboard).
4. Give a descriptive title and axis labels to individual charts and dashboards respectively.
5. Adjust the margins of the individual chart and make the dashboard tidy and informative.
6. Create a story point and provide informative captions for storytelling.
7. (optional) If you have geo-information in your data set, you can create maps including animated maps.
8. (optional) If you want to use more advanced topics such as derived variables and parameters to enhance your dashboard, you are very welcome to do so.
## Submission Requirements:
1. Publish your dashboard and story point on the Tableau Public server.
2. Write a report using an RMD document to include both the Tableau dashboard and story-point on the same web page.
3. You publish the report on either RPubs or placed it in your GitHub repository.
4. update your online CV with the link to your assignment (optional).
5. Submit the URL of your HTML report generated from RMD and make sure your RMD source is downloadable from your HTML report.
## Suggested YAML Header Output Set-up
````{verbatim}
---
title: "You Report Title (concise and descriptive)"
author: "Your Name"
date: "West Chester University"
output:
html_document:
toc: yes
toc_depth: 4
toc_float: no
code_folding: hide
code_download: yes
smooth_scroll: yes
number_sections: yes
theme: readable
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE,
warning = FALSE,
result = TRUE,
message = FALSE,
comment = NA)
```
````
