Jorge Valdano, former Argentinian striker, laments the growth of analytics in football. “Big data and mathematical projections are making their way on to the field of play to tell us things I don’t want to know,” he says. I say he’s wrong. He makes the fatal mistake of thinking that data removes intuition, and that data represents a bigger truth than anything else. He says that knowing that someone ran 15km in a match isn’t on its own a measure of success. I agree. But this data adds to a conversation the coach can have with players. Fans love the data in football. It adds flavour, just like it does in business: no decision should be 100% based on data; it helps to be informed by data.
The Russians ran further than any other team in the Group Stages. Some say this is evidence of doping. The analysis in this is very interesting, but the program fails to point out the main issue: running distance is just one factor in hundreds that would indicate doping. Correlation doesn’t equal causation; there may be many reasons Russian players ran so far. It is not possible to use one data point to make such a big conclusion. Either way, this is a fun episode to listen to.
I share this for the irony of PR stunts going wrong. It’s about the German team’s “Virtual 12th man”: SAP’s Big Data and AI-driven analytics platform which is used for player and game analysis. Sounds AMAZING. I’m sure it is. Except…. Germany got knocked out in the Group Stages for the first time since 1938! Which *definitely* proves that data is just one part of an equation in running any team, or business. 🙂
I’m delighted to present “New Ways to Visualize Time at TC Europe in London. The content is based on one of the chapters in my book, The Big Book of Dashboards.
This post contains links to all the resources shared in the session.
The trend line is amazing. It shows peaks and troughs and trends. But if you only ever use trendlines to show time, you are missing insights in your data. What’s the best way to show time in visualisation? I cannot answer that: it depends on your data, the story you want to tell, your audience, and many other things.
Which way is time?
Time can go up and down as well as left and right. Generally in the West we point forwards or to the right, but that’s not the only way. Check out these:
For further reading on how time is considered in culture and in data, check out this wonderful article, History on the Line, by Stephen Boyd Davies.
We forget (or don’t know) that even the most common chart types were once ideas waiting to be thought of. Even though we build them every day, timelines were invented. Here are the milestones I highlight in my talk
1493: People have been making chronological charts for centuries. I love the examples from Hartmann Schendel’s Nuremberg Chronicle, published in this year
1753: Jacques Barbeu Dubourg makes a chart with a fixed x-axis. Unfortunately, his chart is 54ft long! He invents a really cool scroller to deal with this problem
One of the examples I used is based on US Road Fatalities data. I used that data to create a dashboard that was comeprehensively described and deconstructed in my “Design Month” series of posts in 2014.
I wrote about a similar topic for the Huffington Post, “New ways to see time.” It has some other examples.
How do you visualize time? A line chart with time on the x-axis, right? We do this unthinkingly, but have you stopped to consider why we default to using an x-axis? Or more generally, the very “direction” of time itself? I find this topic fascinating and since just about everyone has time in their data, it’s relevant to Tableau. After reading these links, you’ll think differently every time you see or build a line chart!
I’m a dataviz history nerd, and this (long) article explores cultural directions of time, with particular focus on the first ever horizontal timeline chart, Carte Chronoraphique, by Jacque Barbeu Dubourg. This was a 16.5m (54ft) long chart of human history. It was literally ground zero for the timeline: the first time anyone put time on an x-axis. If you’re at all into the history of our field, I cannot recommend enough that you make the time to read it.
If you show Spanish and Swedish people animated lines that lengthen at different speeds, the Spanish can perceive the different rates, but Swedes cannot. Why? Because the two culture perceive time differently (Spaniards see time as “volume”, Swedes as “length”). Does this apply to animations in dataviz? Do different culture see timelines differently? That would be fun to research…
I don’t normally plug Tableau in this column, especially not my own work, but visualising time is one of the fundamental things Tableau users do. If they stick to timelines, they will miss valuable insight. The whitepaper shows different ways to visualize time: everyone exploring data should look at data from as many different angles as possible to find and articulate the best insight.
Welcome to the Sweet Spot. This week: three links that tell me we’re seeing the start of Artificial Intelligence’s drop from the top of the Hype Cycle. This is a good thing – going past the peak of inflated expectations to the trough of disillusionment is necessary for any maturing technology. The conclusions of each of these are that AI will succeed only with significant oversight from people. Further proof is in this week’s UK House of Lords level-headed report “AI in the UK: Ready, willing and able?”, which I’ll cover more next time.
Elon Musk has had to roll-back production targets for his Model 3. He cites over-reliance on too much technology, including failed attempts to automate too much. “Humans are underrated,” he tweeted. This is Tesla, world leader in automation, rolling back.
I banned my kids (8 and 10) from YouTube this month. I’ve seen for myself the descent into weird and unpleasant videos that the algorithms lead them to. And now YouTube themselves have tacitly acknowledged the problem: they are rewriting their Kids app to be human-curated because algorithmic recommendations are unsafe. This is Google, world leader in AI, rolling back. James Bridle’s essay from November 2017 is a highly recommended, disturbing, read.
Lewis Hamilton started on pole position in in F1’s season-opening race, but lost the lead due to an error in the team’s data models. The models incorrectly indicated a big enough lead to allow for Hamilton to take a pit stop. Vettel snatched first place as a result. “When you are relying on so much data, so much technology to come out with the strategy or whatever, I wish it was more in my hands,” said Hamilton. Few sports are as data-driven than Formula 1, and here it is, making hash of it.
It’s the Christmas edition of the Sweet Spot! That wraps up 12 months of, what I hope, have been inspiring and entertaining things to read/watch/listen to, all somehow related to helping people see and understand data. For the final issue of the year, some fun stuff. Still relevant. But fun. See you in 2018!
Numberphile is one of my favourite YouTube channels. This video, by the wonderful Cliff Stoll, provides a brilliant gotcha to teach you a lesson about data collection. It’s a simple lesson but one with big implications: how do people learn to trust their data? Should they trust it blindly? Are they measuring things correctly?
Our visual system is the most powerful of our senses, but our brain’s a little lazy and doesn’t remember everything with complete accuracy. This campaign from Signs.com asked people to draw logos. The results are really interesting, and they did some great data analysis and storytelling with the results. (shared by Louis Archer in Product Marketing)
“A virtual cult of the spreadsheet has formed, complete with gurus and initiates, detailed lore, arcane rituals – and an unshakable belief that the way the world works can be embodied in rows and columns of numbers and formulas.” That’s my favourite quote from this piece celebrating October 17’s Spreadsheet day (marking the 35th anniversary of Visicalc. When Tableau is 35yrs old, will people look back and reflect in the same way? (That’s 2038, by the way!)
Clearly there’s life in the old spreadsheet! This article strikes an almost romantic tone as it describes the depth and complexity of a spreadsheet that models NYC’s transport system. Read it and marvel at how far we’ve come with Tableau. I’m amazed at how this is so anachronistic and yet, somehow, appropriate? Go download the spreadsheet itself and marvel at the charts, and the maintenance nightmare this must be. Surley we could model this with a good database and Tableau?
Shall we map the entire world, every day? Why yes, why not? We’ll need a bunch of our own satellites to create 1.4 million images daily (that’s 6 petabytes of data, each day!). That’s what Planet did. Now they’ve built it, think of the possibilities of this dataset. Their promo video is crazy: imagine measuring a country’s economy by measuring the number of ships in a port each day? Or tracking natural disasters more accurately than ever before? Sure beats the Excel datasets described above! Their promo video really sets the scene.
Today Andy Kirk and I duel it out in the annual Data Debate. We tackled big and small issues in the field of data. The recording will be available here. This post contains links and further reading on the topics covered.
Are politicians emboldened to say whatever they want? If they are, is that changing society’s attitude to data? Is social polarization accelerating this trend? I fear it is.
Sir David Norgrove, Chair of the UK Statistics Authority, was driven to write to Boris Johnson in September warning him of his “clear misuse of national statistics.” William Davies writes on this in the Guardian, using GDP as an example of the end of statistics. Simon Kuper offers a glimmer of hope with advice on how to take on the populists in the FT. However, his main argument is to ditch the facts and lead with emotion and the story. Sure, that might win people over, but if there’s no role for information and data, have we lost the fight?
The case for animation
My main argument is that animation is exceptional for presenting data in a dramatic way. It enables storytelling and creates tension, surprise, and drama.
The master was Hans Rosling, who astounded us in 2006 with his first TED talk on health data, and later with his Joy of Stats
But I see a lot of people fixate on the chart they want to build rather than focus on the question or the data itself. Watch this video. The end result is a chart you’d never find this in a chart directory. But, if your question is: In which years does B outsell A, it’s a wonderful way to represent it (it’s not the only way, but it does work).
Also consider the two charts below. One shows drought index in the US and the other shows US Road Fatalities. The structure of the data is the same (month, year and state). Only one is a successful chart (the drought chart on the right). Consulting a chart directory, there’s a risk you’ll pick the small multiple and publish. But of course, the data itself drives the appropriate chart type.
Big Ass Numbers: awesome!
Which of the above dashboards conveys a headline better? The one with the BANs or without the BANs?
I came to appreciate BANs through the writing phase of The Big Book of Dashboards. I consider them the Headlines for your dashboard. A well defined set of BANs will capture your KPIs in a way you can interpret instantly. Clever use of colour or other visual indicators can show, straight away, whether they are above or below target. Once the headline is digested, then you can decide if you need to devote time to interpreting the charts in the rest of the dashboard.
This was fun! What I like about defending “bad” charts is that it emphasizes the lack of “rules” in dataviz. There are only guidelines and any binary argument of right or wrong is a failed endeavor.
My defense is simple. If your primary goal is to show the total of all categories, then a stack is fine. Yes, that comes at the expense of being able to accurately see the changes over time of the individual categories. If the primary goal is to see the individual categories, a stack is a poor choice. I believe you should consider primary/secondary goals in all assessments of charts. Remember: All charts are a compromise.
The same defense applies here. If the goal is to give the gist of the data, as they tried to in the BBC article on Apple’s Tax Bolthole, then you’re ok with bubbles. A bar chart will provide more accuracy, sure. In the case of the BBC article, I’m not convinced readers miss out by their inability to accurately see if Apple is precisely 30% bigger or smaller than another bubble.