I'm currently running some monthly data where a list of records is assigned a KPI indicator like G/Y/R. I've been asked to produce a follow-up piece that would show "movers" from the prior month's data, just in a simple text view. So I guess what I need to try and do is figure out how to do a lookback/compare from prior month data to see who went from Y/R to G on the positive change side and who went from G to Y/R on the negative side.What Brian didn't realize was that answer to his question was pretty much in the question itself; he needs to use to LOOKUP() function. I sent Brian a solution, but decided to fancy it up a bit more and add some more functionality using parameters:
August 25, 2014
August 22, 2014
My first stop was back at my old stomping grounds at the Atlanta Tableau User Group, where Andy Piper and John Hoover of Norfolk Southern hosted over 100 people. A few days later I was preaching again to a group of about 50 at the San Diego Tableau User Group, where Matt Shoemaker of Interactions Marketing and Ben Sullins of Pluralsight hosted the event.
Tuesday marked the culmination of the mini-tour, with 2014 IronViz contestant Jeffrey Shaffer of Unifund and Jonathan Pickard, the leader of the Cincinnati Business Intelligence & Analytics group, hosting the event at the amazing Linder College of Business at the University of Cincinnati. They really have something special going on at UofC in the business analytics space. If you're looking for great analytical talent, they definitely need to be on your list of places to visit and connect with.
There were about 100 people in attendance, all armed with Tableau Public, data about airline delays, great questions and an incredible appetite to learn.
- Hour 1: Presentation – Building a data viz & Tableau culture; How we did it at Facebook & how you can do the same
- Hour 2: Tableau Training - Fundamentals for analyzing an unfamiliar data set
- Hour 3: Group exercise and viz presentations
One of the things I like to do when giving these talks is to ask the audience why they are there. This way, I can customize the talk along the way to make it more suitable for them and to ensure they get the most value out of it. The drawback of this approach is that the talk tends to go on longer than one hour, which was the case Tuesday.
To accommodate for my long-windedness, we decided as a group to skip the group activity and focus on the Tableau training. The fact that every person in the audience came prepared with Tableau installed was a HUGE help and a big time-saver. When I teach, my goal is to overwhelm the class. I have always felt that when learning Tableau, you should drink from the fire hose. I move very fast in the training, yet I don't leave anyone behind. The class will often feel that I'm moving way too quickly at the start, but I do that intentionally, so that they learn how easy it is to build in Tableau.
The class of 100 was comprised of only a handful of people that had been using Tableau for more than one year, with about 80% of the class getting a taste of Tableau for the very first time. In 90 minutes, we build 17 different worksheets and one interactive dashboard. You can download the workbook here. This training session was really fun because I had to hold a mic the whole time; this meant I was teaching and building vizzes one-handed. We covered a few major areas, while using the Show Me only once (I like to teach people how to build visualizations without it):
- Bar charts: Ranked bars, Small multiples, Stacked bars, Side by side bars, Stacked % of Total, Bar in bar, histograms
- Line charts: Basic line chart, Multiple lines, Year over year, Small multiples, Forecasting, Moving avg, Area chart
- Maps: Dot maps, Colored dot map, Sized dot map, Sized and colored dots
August 18, 2014
Saturday Down South is a website dedicated to all things SEC football. This past Thursday, they published this list of the salaries for each coach in the SEC (except for Vanderbilt who does not publish their coach's salary).
This list is simple enough, yet when I saw it, I felt like there was more of a story in there. You can clearly see, just from the table, that Nick Saban is a huge outlier. He's a winner, and he gets paid to win. Keep in mind that these are only their base salaries too. Bonuses, appearance fees, etc. are not included.
I decided to use Tableau's story points for the first time to answer a couple of key questions:
- How much of an outlier is Saban compared to his peers in the SEC, to other coaches in other sports and to other college football coaches?
- How widespread is this level of pay for college football coaches and how does the SEC stack up?
- Is Saban worth the money?
- If you want to tell a story, know the questions you want to answer ahead of time. This will help you plan the beginning, middle and end of the story.
- As I answered questions, I was led to more questions, which led to finding more data, which led to a better story. Be prepared to iterate.
- Story Points are pretty inflexible. You can't do any formatting of you viz once you're inside the Story Point. You have to go back to the original worksheet to change anything. I had expected this to work more like editing a viz on a dashboard.
- I feel like I'm not quite using Story Points as they were intended. I feel like I'm missing their intent in this attempt because I could have done all of this same formatting with multiple dashboards and tabs. I need to learn more about the “idea” behind Story Points.
August 12, 2014
That's all there is to it! Super simple! Download the sample workbook here.
July 21, 2014
- There are 20 slices in each pie.
- Each slices contains way too much content: team logo, team name and revenue, yet it lacks the percentage each team takes in, which is more meaningful than the revenue in this case.
- The image is blurry.
- The fonts are tiny.
I chose a lollipop chart because I wanted to show the data in a bar chart view, but accentuate the end points. I then color-coded the dot on the end of the lollipop by the revenue and kept the range consisted across the leagues. In addition:
- I kept the scales for the bars the same on both charts so that you could see how the leagues compare to each other.
- I converted the Pounds to Euros (1 british pound sterling = 1.26 Euro) to make the data more comparable.
- I included the share of revenue as a label on the lollipop.
- There are only two teams that matter to TV networks in Spain.
- The Premier League is very, very rich. The team will the lowest revenue allocation is higher than the third highest team in La Liga.
June 30, 2014
- I converted the circles to bars, making comparisons much easier.
- I added the % of total time spent online to the end of the bars to give additional context.
June 16, 2014
- A horizontal bar chart would be easier to read
- The sorting is backwards
- They're not doing enough to show the geographic distribution
June 9, 2014
This chart seems innocent enough, yet I found myself having to constantly reference the legend because they didn't bother including the labels directly on the chart. A more understandable alternative might look like this:
- Added labels for the bars
- Removed the legend and the different colors for each Chromebook
- Made the bar horizontal bars so that the labels are easier to read. I also find it easier to compare the length of the bars on horizontal bar charts, but that's a personal preference.
- Added a metric to show how much slower the other Chromebooks are compared to Wirecutter's recommendation (Dell Chromebook) and colored the bars by the % difference. This helps provide more context to the speed comparisons and I don't have to do the math in my head.
June 5, 2014
I can think of only one reason why QlikView would do this: Tableau must be killing them!
QlikView is obviously grasping for straws. While I'm sure Tableau is having to do some unplanned firefighting, they might see this as a compliment. Only competitors that are getting their asses kicked would resort to these tactics. All you have to do is look at the latest Gartner Magic Quadrant to see that Tableau is the leading platform.
I like to tell Tableau, and I know many other people tell them this too, that we chose them because they are the best end-to-end solution on the market. But they need to be aware of complacence. If another tool comes around that better meets my needs, you can be sure that I will switch. In the end, I want a tool that makes me look good.
Performance remains my #1 concern with Tableau. Tableau is not an exclusively in-memory solution like QlikView, so Qlik comparing their performance to Tableau's is not an apples-to-apples comparison. I like to tell the Tableau execs that if they can make Tableau fast for data at Facebook's scale, imagine what they can do for the more typical customer. I am extremely confident that Tableau is listening and are actively working to address my performance concerns.
Here are some random thoughts about why I love Tableau:
- One of the reasons I respect Tableau, its management and its employees so much is that they would never use anything I say without asking my permission. Tableau has quoted me quite often: on their blog posts, on their website, as part of ads, in sales presentations. But Tableau has asked permission EVERY SINGLE TIME.
- I have never seen an example where Tableau has acted in the manner in which QlikView has.
- I chose Tableau because it's the best overall data visualization tool on the market.QlikView, I didn't choose you because you simply can't compete. If you want to win, make a better tool.
- Tableau listens unlike any other vendor I've ever known. They care about their customers. Customers drive feature development. Two great examples of Tableau listening to their customers are: (1) the upcoming Mac client and (2) the Apply button on multi-select drop-downs. I personally worked with Tableau to help create the Apply button, which they initially called the “Andy” button internally. They took the time to personally reach out to me and gather my feedback and showed me prototypes along the way.
- Tableau has a community of users unlike any other product I've used. If you've ever been to one of their conferences, you know what I mean. If you haven't been to one, you must go. Tableau's forums are completely user driven. If you ever have a question, ask on the forum and you're all but guaranteed to get a high-quality response...for free! There are people like Joe Mako and Jonathan Drummey that hold working sessions with users to help them learn. I write this blog because it's a way that I can share with the community. The number of wonderful Tableau bloggers is astounding. Do you ever hear of other vendors having their users promote their product like Tableau's users do? I think not!
- They have a mission and vision that matches my own.
- I've spoken at four Tableau Customer Conferences with two more planned this year. I've spoken at their annual company meeting. Why would I speak on their behalf if I wasn't their biggest advocate?
- Without Tableau, there's no way I would be working at Facebook. I have some incredible success stories from my days at Coke (like using Tableau with buyers and making $30M in 10 minutes). And the success stories have continued here at Facebook.
If there are any companies or customers that are seeing this slide from QlikView and it's making you question which tool you should use, then consider why they would be resorting to such tactics. Only companies that are playing catchup behave like this. Think about why they would do this. Question their sales staff.
I've always been more than happy to talk about the pros and cons of BI tools as I know them. If you are a prospective customer comparing QlikView and Tableau and have any questions, feel free to email me. I'd be more than happy to answer any questions you have.
6/6/2014 - I need to recognize Maria Scurry from QlikTech for being so responsive to my concerns. Maria left a comment shortly after this blog post went live. In addition, she has been very responsive to my emails and she has confirmed that she found the source of the slide in question and it will not be used publicly or internally from this point on.
June 2, 2014
I've been experimenting with Tableau for Mac quite a bit. This past week I've been focusing a lot on live connections to MySQL to replace some existing internal dashboards with more insightful ones. The great thing about our MySQL environment is that it's super fast and I can turn around a dashboard built on a template in less than an hour. While this has been awesome for proving the value of Tableau for Mac, I learned a lesson over the weekend about the Tableau Server cache.
We're at a luxury here at Facebook that we can have a separate environment for the 8.2 beta. In production, we all share a single server, so it's unlikely that you hit the cache. However, on the beta server, there are only a handful of us using the Server, which led to email over the weekend from my users that their dashboards with live connections are not showing the latest data. Why? Tableau is using the cache (as it should).
To solve this, all I have to do is force the dashboard to refresh every time the user hits the server. I accomplish this by adding the ":refresh" parameter to the URL. My URL now looks like:
The refresh option on the end is what tells Tableau Server to re-render the view. Of course, you don't have to have the embed and toolbar parameters in the URL, but I like the way my view looks on Tableau Server when I include those options. For a full list of embed parameter, go to this link.