Skip to content
Workout Wednesday
  • Tableau Challenges
    • Challenge Insights
  • Power BI Challenges
  • Track & Review
    • Participant Overview
    • Track
  • Contributors
  • Meet The Community
  • Search
Workout Wednesday
  • Tableau Challenges
    • Challenge Insights
  • Power BI Challenges
  • Track & Review
    • Participant Overview
    • Track
  • Contributors
  • Meet The Community
  • Search

2019 Week 4: Headcount Tracking

5 Comments / Tableau, Workout Wednesday / By Curtis Harris

Hello and welcome to week 4 of Workout Wednesday 2019, and my first contribution as an official team member! This week’s challenge should be on the easier side, and forces us to think a little bit about data prep, before we get to producing our Workout Wednesday visualization.

I was recently challenged at work to product additional rows of data between two dates, all while staying within the confines of Tableau. Assuming you don’t have Alteryx, SQL skills/tools, or other data prep tools… how would you use Tableau and every day applications (Excel, Google Docs, etc) to enhance your data set? For this week’s challenge, I want you to use Tableau Desktop’s data source page to enhance your base data set. Keep an eye on the number of records, it is a key requirement this week!

Click image to view on Tableau Public

Requirements

  • Data prep requirements
    • I’ve provided a scaffold of dates in the file that should be used to extend the employee level data
      • Using the data source page, combine the employees data and the dates data into a single data source
      • Important… bring in only dates that fall between an employee’s hire date and termination date. If an employee has no termination date, use today’s date. Example: employee 2 should have 141 records before extracting (every date between 3/1/2018 and 7/19/2018)
      • Your final extract should have exactly 5,947 records
  • Dashboard requirements
    • Dashboard size: 1000 x 600, and should contain no more than 3 sheets
    • Create a summary number that represents how many active employees we have on the latest date left in the data after data prep is complete
    • Create a line and dot combo chart with a mark for every day. When there are gains in employees, highlight that date with a gray circle. When there are losses in employees, highlight that date with a red circle. Size the circles by the absolute volume of the gain/loss.
    • Create a volume chart below the line chart that shows employee gain/loss by day
    • Match formatting, colors, and tooltips as closely as possible
      • Note the positive, neutral, and negative number format in the tooltips. Gains should be displayed as +n, 0 gain/loss days should be displayed as 0, and losses should be displayed as -n. Do not create three fields to accomplish this behavior.

Dataset

This week uses fake headcount data stored in Google Drive.  Connect to the data in Tableau by using the Google Sheets connection, and this link: https://docs.google.com/spreadsheets/d/1DO9bKM4dFVc4q_cID3VACoxVn3mQ5ipbd8owNXXprrY/edit?usp=sharing

Attribute

When you publish your solution on Tableau Public make sure to take the time and include a link to the original inspiration.

Share

After you finish your workout, share on Twitter using the hashtag #WorkoutWednesday2019 and tag @AnnUJackson, @LukeStanke, @lorna_eden, and @curtisharris_!

Track your progress

Also, don’t forget to track your progress using this Workout Wednesday form.

Post navigation

← Previous Post
Next Post →

5 thoughts on “2019 Week 4: Headcount Tracking”

  1. rincon
    January 25, 2019 at 6:49 pm

    Hi Curtis,

    great challenge. It reminds me the presentation of Mrs Ganeshalingam and Singh during TC ” Solving tought time based problem with skeleton tables!

    Reply
  2. Hatem Kotb
    January 27, 2019 at 3:05 am

    I tried to do use the Date field for the joins twice but it didn’t work, had to use Excel for my workaround. Nice challenge Curtis & thanks for the video on the prep – smart!

    Reply
  3. Watsa Chaodee
    January 28, 2019 at 9:38 am

    My first #WorkoutWednesday2019 Week 4 is complete. Thanks for the challenge @curtisharris.
    BTW, I am not sure that the data source in Google Doc is different from the data source in the challenge. The data in Google doc does not have any gain or loss on Dec 16. Therefore mine does not have lost employee on Dec 16. Is it correct?
    https://public.tableau.com/views/WW-2019W4/WW2019W4?:embed=y&:display_count=yes&publish=yes

    Reply
  4. MARCO DEGOLA
    February 1, 2019 at 10:24 am

    Hi Curtis, this was an iteresting one , even if simple on the Tableau Side.

    Here my shot:
    https://public.tableau.com/profile/marcodegola#!/vizhome/ItalianWorkoutWednesday2019/2019w04-ww?publish=yes

    Welcome Aboard!

    Reply
  5. Faisal Akbar
    February 18, 2019 at 7:41 pm

    Interesting one, here is mine:
    https://public.tableau.com/views/WorkoutWednesday2019Week4_6/WorkoutWednesday2019Week4?:embed=y&:display_count=yes&publish=yes

    Reply

Leave a Comment Cancel Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

#WOW2021

vinkaranvinodh venkatraman@vinkaran·
50m

#wow2021 #week13 #powerbi #custombookmark
#PowerBI @JSBaucke, @MMarie, @shan_gsd @dataveld

Reply on Twitter 1381627604550234113Retweet on Twitter 1381627604550234113Like on Twitter 1381627604550234113
sarajlic_asimAnto Barić@sarajlic_asim·
3h

"Non paper" me podsjeća na ono kad nestane tariguza, a i česma pokvarena, pa kontaš daj šta daš, samo spasi. #BiH #Raspad #wow2021

Reply on Twitter 1381597090510475267Retweet on Twitter 1381597090510475267Like on Twitter 13815970905104752671
vinkaranvinodh venkatraman@vinkaran·
4h

#wow2021 #week12 #powerbi #customsorting
#PowerBI @JSBaucke, @MMarie, @shan_gsd @dataveld

Reply on Twitter 1381585622746419202Retweet on Twitter 1381585622746419202Like on Twitter 13815856227464192021
sue_bayessusan bayes@sue_bayes·
5h

#WOW2021 Week 10 #PowerBI Inspired by and motivated by @alexdupler , here's my week 10 submission. One and day and I'll be back on track @JSBaucke @MMarie @shan_gsd @dataveld. In my defence, had to learn about #paginatedreports which are very cool.
https://app.powerbi.com/view?r=eyJrIjoiYmMzZjkwYWUtNTA2NC00YzIxLWE5MTItYzVmNjEwNzFhYmQ5IiwidCI6IjIxNjk0MzYyLTI0ODItNDlhNC1iNjk1LThiODM2Y2ViMDg4MyJ9

Reply on Twitter 1381565474023047170Retweet on Twitter 1381565474023047170Like on Twitter 13815654740230471702
KAO79922715KAO@KAO79922715·
6h

My practice for #WOW2021 Week 6 | Tableau: Can you build a Fancy Text Table?

https://public.tableau.com/profile/christine.kao2744#!/vizhome/WorkoutWednesday2021Week6TableauCanyoubuildaFancyTextTable_16182217270020/1_1?publish=yes

#tableaupublic
thank you
#WOW2021 and @AnnUJackson, @ItsCandraM, @LukeStanke, @_Lorna_Brown and @HipsterVizNinja

Reply on Twitter 1381548780781068290Retweet on Twitter 1381548780781068290Like on Twitter 13815487807810682901
Load More...

Recent Posts

  • 2021 Week 14 | Power BI: Accessibility Enhancements
  • 2021 Week 14 | Tableau: Can You Recommend Profitable Return Customer Bundles?
  • 2021 Week 13 | Tableau: What percentage of sub-orders are profitable?
  • 2021 Week 13 | Power BI: Create a Bubble Chart with a Custom Overlay
  • Week 12: Can you do Comparative Quantity Analysis?

Categories

  • community
  • Power BI
  • Solution
  • Tableau
  • Uncategorized
  • Workout Wednesday
April 2021
M T W T F S S
 1234
567891011
12131415161718
19202122232425
2627282930  
« Mar    

Tags

Actions bar chart calculations chart types cluster cohort Color Dates Distance dual axis emoji Extension formatting histogram Index KPI labels Level of Detail lods Log measure names Mobile parameter parameter actions Parameters pareto pictogram Power BI reference line Relationship retention set actions sets sheet swapping Small Multiples Solution sort sorting Spatial Tableau data model table calculation table calculations union window_sum workout
Supported By:




Copyright © 2021 Workout Wednesday
Scroll to Top