Data visualization has become a red-hot analytics topic of late, but for Ford Research & Advanced Engineering's data science team, it's long been standard fare. That makes Mike Cavaretta, technical leader for predictive analytics there, the perfect go-to guy for advice on exploring and presenting data visually.
"Our perspective is that data visualization techniques add so much that it's really important in a data science effort to be able to use these techniques," Cavaretta told attendees of our live video chat on visual analytics yesterday.
Mike Cavaretta, Ford
At Ford Research & Advanced Engineering, data visualizations come into play when analysts are simply trying to understand the data, Cavaretta told us, as well as when they're exploring the data and looking for the unusual to pop out:
A visualization can help a lot. Just plotting things on a timeline can give you an idea of "are you hitting the peaks, are you hitting the valleys, are you hitting the trends in the data" -- how well the model is working that you just can't get from a simple statistic like an error rate or an R-squared or something like that.
Visualizations also help tell stories about the data, he added:
How do you synthesize what you have and show your conclusions in an easy-to-understand way? How do you present that to people who aren't statistically savvy, per se, but know data, understand data, and have a really good feeling for the business? That's really the key piece for us.
Below are five tips on working with data visualizations that Cavaretta shared during yesterday's video chat, which you can listen to on demand, here.
Start small: "Have some really good prototypes from really good proofs of concept," suggested Cavaretta, noting that starter data visualization software is readily available from companies like QlikView, Tableau Software, and Spotfire. Buy a single seat, do some experimentation, and show people the results and how dynamic the presentations and the data can be. Or do the same using the open-source R statistical tool. That'll take a bit more effort, though, since you'll need to do some programming, he cautioned.
Know your audience: Some people will have the time and ability to understand data visualizations and others won't. It behooves you to figure out which type of group you're presenting results to before you decide to package those visually. Ideally, the group will understand the data you have and have the time to sit through an animation of it, à la the dynamic visualizations at Gapminder, and so you can make your presentation interactive and iterative.
"That's the one that we'd rather do," Cavaretta said. "Those are the better presentations -- people are engaged, they can ask questions, and we can slice and dice on the fly." However, sometimes you'll only have 10 minutes at a board meeting to explain a complex project in a way that directors are sure to understand. Working with dynamic data visualizations might not be the best choice in such circumstances.
Don't assume a visual presentation is always best: When you're getting ready to share results, think about whether you really want to present your data visually or whether a textual narrative would be better. If you're making recommendations, stating "to meet your cost targets, you need to remove 10 cents from every part" may provide greater clarity than trying to show that through data visualization. "For the most part... you're not going to be able to be dynamic and have that narrative there. That's the piece that we've found really, really important."
Watch out for complexity: "The complexity of the visualization is sometimes very, very tempting -- being able to have something that puts everything together in one chart, one big graphic, so you're showing the distribution, you're showing the forecast, you're showing the six different variables you think are going to drive what's going to happen in the future," Cavaretta said. You and your team might understand what's going on in the visualization perfectly well, but "for somebody who hasn't lived with the data for the past two months, it can be very complex."
If you do decide to layer in lots of elements, then you'd best make a determined effort to be sure that you explain everything clearly so that everybody understands the complex visualization when you're done explaining it, he advised. The same best-practice applies to creating static infographics, he added. Maybe you don't put those four important elements into a single infographic but rather do two and two, for example.
Put another set of eyeballs on your results: Cavaretta and his team members make sure they validate results among one another -- and he recommends everybody do the same. "It's not necessarily a formal process, like a code review, but it is always something where we want to make sure we have fresh eyes on whatever we send out and how we communicate our results."
How are you using data visualizations in your company? Share your best-practices below.
I would think it'd also make sense to do a run-through of a presentation, including showing the visualizations that would be presented, prior to the business meeting. Do you think that happens often... or often enough?
@tomsg, you make a good point about wanting to know the assumptions. I don't know too much about other data visualization tools, but I do know that SAS Visual Analytics provides pop-ups that explain what the visualization means, assumptions, algorithms used, etc.
@kq4ym -- I think, too, it depends on the purpose, as Cavaretta said. If you want your audience to take away the information and really think about it later, text might be better remembered. Although he does say his team will use good infographics, too -- the type using lots of facts and text as well, a la the New York Times (though he says his team is not nearly as good as the NYT designers!). So static visualizations with text definitely have a place.
For some reason when I just see a visualization, I worry about assumptions and filters that may have helped make a point rather than just present the facts. I don't mind a visualization, but I always want the underlying data and a list of assumptions.
I would certainly agree to be aware that not all audiences want the visuals. I've seen way too many presentations that could have more easily be presented in text. After all, a visual is a summary in a lot of cases, and what is better to summarize than language.
As said in the blog, it is important to understand that whether the audience is that which needs to understand the nitty gritties of the topic concerned or needs final numbers and facts so that they are able to take a decision. If the audience is the former type, then analytics in the form of visuals can help else a text-based summary might suffice. In a board of directors meeting for e.g. you dont want to hear from a director "we are not interested in the details, all we need to know is that the project is to feasible or not so just give us a brief idea" hence making analytics in the form visuals completely unnecessary.