Why performance ensures usability in Tableau - Business Case Study

Scenario Mode

👤 Your Role: You are a business intelligence analyst at a retail company.

📋 Request: Your manager wants you to demonstrate how dashboard performance impacts user experience and usability.

📊 Data: You have sales data by region, product category, and month for the last year. The data includes sales amount, number of transactions, and customer counts.

🎯 Deliverable: Create two Tableau dashboards: one with optimized performance and one with poor performance. Show how faster loading and responsiveness improve usability.

Sample Data

Month	Region	Product Category	Sales Amount	Transactions	Customers
Jan	North	Electronics	12000	150	140
Jan	South	Clothing	8000	100	95
Feb	North	Clothing	9000	110	105
Feb	East	Electronics	15000	160	155
Mar	West	Clothing	7000	90	85
Mar	South	Electronics	13000	140	135
Apr	East	Clothing	8500	95	90
Apr	North	Electronics	14000	155	150
May	West	Electronics	16000	170	165
May	South	Clothing	7500	85	80
Jun	East	Electronics	15500	165	160
Jun	North	Clothing	9200	115	110

1

Step 1: Connect the sales data to Tableau and create a simple bar chart showing total Sales Amount by Region.

Rows: Region; Columns: SUM([Sales Amount])

Expected Result

Bar chart with 4 bars representing North, South, East, West with their total sales.

2

Step 2: Create a second chart showing Sales Amount by Product Category with filters for Month.

Rows: Product Category; Columns: SUM([Sales Amount]); Filter: Month

Expected Result

Bar chart showing sales for Electronics and Clothing, filterable by month.

3

Step 3: Build a dashboard combining both charts and add all months filter. Use quick filters for Region and Product Category.

Dashboard with two charts and filters for Month, Region, Product Category.

Expected Result

Dashboard with interactive filters and charts.

4

Step 4: Optimize performance by limiting data to last 6 months, use extracts instead of live connection, and minimize quick filters.

Data source: Extract filtered to last 6 months; Filters: Remove Region filter; Use context filter for Month.

Expected Result

Dashboard loads faster and filters respond quickly.

5

Step 5: Create a second dashboard with all data, many quick filters, and live connection to simulate poor performance.

Data source: Live connection full data; Filters: Month, Region, Product Category, Transactions; Multiple quick filters enabled.

Expected Result

Dashboard loads slowly and filters respond with delay.

6

Step 6: Compare both dashboards by measuring load time and user interaction speed.

Use Tableau Performance Recorder to measure load and filter response times.

Expected Result

Optimized dashboard loads under 3 seconds; unoptimized dashboard takes over 10 seconds.

7

Step 7: Present findings to manager explaining how faster dashboard improves usability by reducing wait time and frustration.

Summary report with performance metrics and user feedback notes.

Expected Result

Manager understands importance of performance for usability.

Final Result

Dashboard Performance Comparison

+----------------------+---------------------+
| Optimized Dashboard  | Unoptimized Dashboard|
+----------------------+---------------------+
| Load Time: 2.5 sec   | Load Time: 12 sec    |
| Filters respond fast | Filters respond slow |
| Smooth user experience| User frustration     |
+----------------------+---------------------+

✓Optimized dashboards load faster and respond quickly to user actions.

✓Faster dashboards improve user satisfaction and usability.

✓Too many filters and live connections can slow down dashboards.

✓Using data extracts and limiting data improves performance.

Bonus Challenge

Add a calculated field to show average sales per transaction and include it in the optimized dashboard with performance considerations.

Show Hint

Create a calculated field: [Sales Amount] / [Transactions] and add it as a tooltip or a small chart to avoid slowing down the dashboard.

Practice

1. Why is dashboard performance important for usability in Tableau?

easy

A. Because fast dashboards keep users engaged and productive

B. Because slow dashboards look more professional

C. Because performance only matters for developers, not users

D. Because dashboards with many colors are always faster

Solution

1. Step 1: Understand user experience impact

   Users prefer dashboards that load quickly and respond fast to interactions.

2. Step 2: Connect performance to usability

   Fast dashboards reduce frustration and help users make decisions efficiently.

3. Final Answer:

   Because fast dashboards keep users engaged and productive -> Option A

4. Quick Check:

   Performance = Usability [OK]

Hint: Fast dashboards improve user happiness and productivity [OK]

Common Mistakes:

• Thinking slow dashboards are acceptable
• Ignoring user experience in performance
• Believing colors affect speed directly

2. Which Tableau feature helps improve dashboard performance by limiting data load?

easy

A. Increasing the number of dashboard actions

B. Adding more worksheets to the dashboard

C. Using many quick filters on all fields

D. Using Extracts instead of Live connections

Solution

1. Step 1: Identify performance optimization methods

   Extracts store a snapshot of data, reducing query time compared to live connections.

2. Step 2: Evaluate options for limiting data load

   Extracts limit data load and improve speed, unlike adding filters or worksheets which can slow down performance.

3. Final Answer:

   Using Extracts instead of Live connections -> Option D

4. Quick Check:

   Extracts = Faster data load [OK]

Hint: Use extracts to reduce data load and speed up dashboards [OK]

Common Mistakes:

• Adding many filters without considering impact
• Believing more worksheets improve speed
• Confusing dashboard actions with performance boosts

3. Given a Tableau dashboard with 5 data sources and 10 quick filters, what is the likely impact on performance?

medium

A. Performance will improve because more data sources mean faster queries

B. Performance will slow down due to multiple data sources and many filters

C. Performance stays the same regardless of data sources and filters

D. Performance will be faster if filters are removed but data sources don't matter

Solution

1. Step 1: Analyze impact of multiple data sources

   Multiple data sources increase query complexity and load time.

2. Step 2: Consider effect of many quick filters

   Each filter adds queries and processing, slowing dashboard response.

3. Final Answer:

   Performance will slow down due to multiple data sources and many filters -> Option B

4. Quick Check:

   More sources + filters = Slower performance [OK]

Hint: More data sources and filters usually slow dashboards [OK]

Common Mistakes:

• Assuming more data sources speed up queries
• Ignoring filter impact on performance
• Thinking performance is unaffected by dashboard complexity

4. You notice a Tableau dashboard is very slow. Which change will most likely fix the performance issue?

medium

A. Replace live connections with extracts

B. Add more quick filters to narrow data

C. Increase the number of dashboard actions

D. Use more complex calculated fields

Solution

1. Step 1: Identify common causes of slowness

   Live connections query data on demand, which can slow dashboards if data is large or network is slow.

2. Step 2: Choose the best fix

   Replacing live connections with extracts reduces query time and improves speed.

3. Final Answer:

   Replace live connections with extracts -> Option A

4. Quick Check:

   Extracts improve speed by reducing live queries [OK]

Hint: Switch live to extracts to boost speed [OK]

Common Mistakes:

• Adding filters without testing impact
• Increasing dashboard actions thinking it helps
• Using complex calculations without optimization

5. You want to improve a slow Tableau dashboard used by sales teams. Which combined approach best ensures usability through performance?

hard

A. Use many quick filters, complex calculations, and multiple data sources

B. Add more worksheets, use live connections, and increase dashboard actions

C. Use data extracts, limit quick filters, and optimize calculations

D. Remove all filters and use only text tables

Solution

1. Step 1: Identify best practices for performance

   Using extracts reduces data load; limiting filters reduces query complexity; optimizing calculations reduces processing time.

2. Step 2: Evaluate options for usability

   Use data extracts, limit quick filters, and optimize calculations combines these best practices, improving speed and user experience.

3. Final Answer:

   Use data extracts, limit quick filters, and optimize calculations -> Option C

4. Quick Check:

   Extracts + fewer filters + optimized calcs = Best performance [OK]

Hint: Combine extracts, fewer filters, and optimized calcs for speed [OK]

Common Mistakes:

• Adding complexity instead of reducing it
• Ignoring calculation optimization
• Removing filters completely harms usability