Why sharing enables organizational adoption 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 sharing dashboards and reports helps the whole organization adopt data-driven decisions.

📊 Data: You have data on dashboard views, number of users accessing reports, and business units using the dashboards over the last 6 months.

🎯 Deliverable: Create a Tableau dashboard that shows usage trends and highlights how sharing increases adoption across teams.

Sample Data

Month	Dashboard Views	Unique Users	Business Units Using Dashboards
January	120	15	3
February	150	20	4
March	180	25	5
April	220	30	6
May	260	35	7
June	300	40	8

1

Step 1: Connect Tableau to the data source containing monthly dashboard usage data.

Use 'Month' as the date dimension, and 'Dashboard Views', 'Unique Users', and 'Business Units Using Dashboards' as measures.

Expected Result

Data is loaded and ready for visualization.

2

Step 2: Create a line chart showing 'Dashboard Views' over 'Month'.

Rows: SUM([Dashboard Views]), Columns: [Month] (continuous), Show line marks.

Expected Result

Line chart displays increasing dashboard views from January to June.

3

Step 3: Create a second line chart showing 'Unique Users' over 'Month'.

Rows: SUM([Unique Users]), Columns: [Month] (continuous), Show line marks.

Expected Result

Line chart shows growth in unique users accessing dashboards over time.

4

Step 4: Create a third line chart showing 'Business Units Using Dashboards' over 'Month'.

Rows: SUM([Business Units Using Dashboards]), Columns: [Month] (continuous), Show line marks.

Expected Result

Line chart shows more business units adopting dashboards each month.

5

Step 5: Combine the three line charts into a single dashboard with clear titles and legends.

Arrange charts vertically, add dashboard title 'Dashboard Sharing Drives Adoption', and add explanatory text.

Expected Result

Dashboard clearly shows how sharing increases views, users, and units over time.

6

Step 6: Add filters or highlight actions to allow users to explore data by month or business unit.

Add filter for Month and highlight action between charts.

Expected Result

Users can interact with the dashboard to see detailed trends.

Final Result

Dashboard Sharing Drives Adoption

Month ->

Dashboard Views: 120 - 150 - 180 - 220 - 260 - 300
Unique Users:    15  - 20  - 25  - 30  - 35  - 40
Business Units:  3   - 4   - 5   - 6   - 7   - 8

(Three line charts stacked vertically showing steady growth)

✓Dashboard views steadily increase each month, showing growing interest.

✓Unique users accessing dashboards grow, indicating wider adoption.

✓More business units use dashboards over time, proving sharing helps spread usage.

✓Sharing dashboards encourages more teams to use data for decisions.

Bonus Challenge

Add a map visualization showing which business units (by location) are adopting dashboards the most.

Show Hint

Use business unit location data and color code by number of users or views.

Practice

1. Why is sharing dashboards important for organizational adoption in Tableau?

easy

A. It slows down decision-making by limiting access.

B. It hides data from most users to protect privacy.

C. It makes data accessible to everyone who needs it.

D. It only benefits the IT department.

Solution

1. Step 1: Understand the role of sharing in accessibility

   Sharing dashboards allows all relevant users to see and use the data easily.

2. Step 2: Connect sharing to organizational adoption

   When data is accessible, teams can collaborate and trust the information, leading to wider adoption.

3. Final Answer:

   It makes data accessible to everyone who needs it. -> Option C

4. Quick Check:

   Sharing = Accessibility [OK]

Hint: Sharing means making data available to all users [OK]

Common Mistakes:

• Thinking sharing hides data
• Believing sharing slows decisions
• Assuming only IT benefits

2. Which of the following is the correct way to share a Tableau dashboard with your team?

easy

A. Publish the dashboard to Tableau Server or Tableau Online with proper permissions.

B. Export the dashboard as a PDF and email it to everyone.

C. Save the dashboard locally and ask team members to open it on your computer.

D. Print the dashboard and distribute paper copies.

Solution

1. Step 1: Identify the best sharing method in Tableau

   Publishing to Tableau Server or Online allows controlled, secure, and easy access for the team.

2. Step 2: Compare other options

   Exporting or printing is static and not interactive; saving locally limits access.

3. Final Answer:

   Publish the dashboard to Tableau Server or Tableau Online with proper permissions. -> Option A

4. Quick Check:

   Sharing = Publish with permissions [OK]

Hint: Use Tableau Server or Online to share dashboards securely [OK]

Common Mistakes:

• Thinking emailing PDFs is best
• Assuming local files are accessible
• Relying on printed copies

3. If a Tableau dashboard is shared with a team but permissions are set incorrectly, what is the most likely outcome?

medium

A. The dashboard becomes faster to load.

B. Everyone can view and edit the dashboard freely.

C. The dashboard automatically updates with new data.

D. Some team members cannot access the dashboard at all.

Solution

1. Step 1: Understand the effect of permissions in sharing

   Permissions control who can view or edit dashboards; incorrect settings can block access.

2. Step 2: Analyze the impact of wrong permissions

   Some users may be denied access, preventing collaboration and adoption.

3. Final Answer:

   Some team members cannot access the dashboard at all. -> Option D

4. Quick Check:

   Permissions control access = Denied access if wrong [OK]

Hint: Incorrect permissions block user access [OK]

Common Mistakes:

• Assuming all users get full access
• Confusing permissions with performance
• Thinking sharing auto-updates data

4. A team member reports they cannot see the shared Tableau dashboard. Which of the following is the best way to debug this issue?

medium

A. Tell the user to clear their browser cache only.

B. Check if the dashboard was published with the correct permissions for that user.

C. Delete and republish the dashboard without changing permissions.

D. Ask the user to reinstall Tableau Desktop.

Solution

1. Step 1: Verify sharing permissions for the user

   Permissions are the most common cause of access issues; checking them is the first step.

2. Step 2: Evaluate other options

   Reinstalling software or clearing cache may not fix permission-related problems; republishing without fixing permissions won't help.

3. Final Answer:

   Check if the dashboard was published with the correct permissions for that user. -> Option B

4. Quick Check:

   Debug = Verify permissions first [OK]

Hint: Always check permissions first when access fails [OK]

Common Mistakes:

• Ignoring permissions as cause
• Suggesting reinstall without reason
• Assuming cache is the problem

5. Your organization wants to improve decision-making speed by sharing Tableau dashboards. Which combination of actions best supports this goal?

hard

A. Publish dashboards with clear permissions and train teams to use them collaboratively.

B. Email static reports daily and restrict dashboard access to managers only.

C. Keep dashboards on local machines and update them monthly.

D. Share dashboards without training to encourage self-discovery.

Solution

1. Step 1: Identify actions that enable fast, trusted decision-making

   Publishing with correct permissions ensures access; training helps teams use dashboards effectively.

2. Step 2: Evaluate other options for drawbacks

   Emailing static reports limits interactivity; restricting access reduces collaboration; no training causes confusion.

3. Final Answer:

   Publish dashboards with clear permissions and train teams to use them collaboratively. -> Option A

4. Quick Check:

   Sharing + Training = Faster decisions [OK]

Hint: Combine sharing with training for best adoption [OK]

Common Mistakes:

• Relying on static reports only
• Limiting access too much
• Skipping user training