Official Blog
podcast
+7

The Data Storytelling Skills Data Teams Need

In this episode of DataFramed, we discuss the role of data storytelling when driving change with analytics, and the importance of the analyst role within a data-driven organization.

Adel Nehme, the host of DataFramed, the DataCamp podcast, recently interviewed Andy Cotgreave, Technical Evangelist at Tableau.

Introducing Andy Cotgreave

Adel Nehme: Hello. This is Adel Nehme from DataCamp, and welcome to Data Framed, a podcast covering all things data and its impact on organizations across the world. You know, oftentimes when we discuss the value data science brings to the table, a lot of the focus shifts to difficult to achieve machine learning and artificial intelligence. I'd argue though that 80% of the value when doing data science comes from data driven decision making at scale. This is where business intelligence comes into the picture, equipping decision makers with the proper context and insight to make better decisions with data.

Adel Nehme: This is why I'm excited to speak to Andy Cotgreave on today's episode of Data Framed. Andy is the co-author of The Big Book of Dashboards, and is Technical Evangelist at Tableau. He is the host of the If Data Could Talk podcast, co-host of the Chart Chat podcast, and he's also a columnist for Information Age. He was on the 2021 Data IQ Top 100 Most Influential People in Data. With over 15 years of experience in the industry, he has inspired thousands of people with technical advice and ideas on how to identify trends in visual analytics and develop their own data discovery skills.

Adel Nehme: And I had an awesome conversation with him today. Throughout the episode, Andy discusses his background, the skills every analyst should know to equip organizations with better data driven decision making, his best practices for data storytelling, how he thinks about data literacy and ways to spread it within the organization, the importance of community when creating a data driven organization, and more.

Adel Nehme: Also we'd absolutely love your feedback on how we can make Data Framed a better show for you, and which guests you think we should bring on the show. Fill out the survey link in the episode description, make sure to fill it out as I greatly appreciate it.

Adel Nehme: Andy, it's great to have you on the show.

Andy Cotgreave: Thanks for having me on the show Adel.

Adel Nehme: You're someone who has a very prolific career in the data space and are a fountain of knowledge when it comes to data visualization and data storytelling. I'm excited to discuss all of that with you today, but I'd love to first start off by discussing your background. Being a Technical Evangelist at Tableau, I'm sure you get a lot of questions of what that entails and how did you end up here? So I'd love to first learn about your background, specifically what was the path you took that led you here?

Andy Cotgreave: So I'm Technical Evangelist at Tableau. I've been at Tableau for 10 years, and I first downloaded Tableau in November 2007. The product didn't do very much back then, but it was still the best piece of software on the market. It blew my mind and it enabled completely new things that we were not able to do. So it's been an incredible 14 year journey.

Andy Cotgreave: Prior to that, so I was an analyst at the University of Oxford at that time, trying to track student data, and we just needed tools that were better, but how did I get there? Prior to that, I was working for a business research company. And at that company, my boss was always asking me questions about progress from my project. And my colleagues was just giving them reams of word documents. And I was like, "There must be a better way."

Andy Cotgreave: And I ended up building this front page on an Excel spreadsheet, which had a bunch of charts on it and summarized what was going on. I didn't even know they were called dashboards at that point, but I was like, "Well, here you go boss, it's one page." And somewhere along that process, I learned the that's called dashboard. I was like, "Oh, that's quite interesting. It's worth summarizing information."

Andy Cotgreave: My earlier part of my career, I'd left school wanting to go into art and do comics, but I ended up doing geography. Then I ended doing computer science. I was a software engineer. I did business research, and I basically did this whole gamut of skills, art, creativity, engineering, database, communication, design. Then when I finally got to Tableau and really dug into what a data analyst should be, I realized that I'd somehow amassed all the skills that you need to really do this role to the full. It's five years since I became Tableau's Technical Evangelist, and that job is essentially using my wisdom and expertise to bring that expertise and passion to the field to as many people as I can, and then hopefully bring them to Tableau because that's my favorite platform of choice. Yeah, so that's the career summary in a nutshell.

What is the role of the data analyst?

Adel Nehme: That's awesome. And there's definitely a lot of wisdom to unpack here. So preparing for this interview was quite difficult because there's a lot of different angles by which we can approach this conversation. However, one thing I definitely wanted to pick your brains on is really the importance of data storytelling, is what is the role of the data analyst in a modern data driven organization?

Adel Nehme: I think we often talk about data scientists as the primary role for bringing value from data in an organization, but I'd argue scaling the amount of data driven decisions an organization makes is 80% of the value in the data pyramid. And this is something owned by analysts as much as the data scientists.

Adel Nehme: With that content, I'd love to learn what you think are the main skills needed to be a successful data analyst today?

Andy Cotgreave: It's a really interesting question, and my top answer is curiosity, right? It's not even a technical skill. In order to be a data analyst, you've got to be able to hunt out what it is the data is telling you. You've got to be able to hunt out what it is your users are asking for. And you've got to be able to explore and iterate to find the best articulation of those two things. What's the data telling you, how should it be communicated?

Andy Cotgreave: So that curiosity feeds a sense of empathy as well, right, because I could be a hardcore data nerd, but if I can't actually express that to other people, express what I'm finding on my insights then, well then what's the point, right? I think sometimes we can over-focus on the technical skills and forget that it's like, "Okay, you've collected your data. You've prepared it, you've done something really wizzy technically, but can people see and understand what it is you found?" And if they can't, then you missed it out. So curiosity and empathy are kind of the core skills underpinning that, the balance of engineering and design skills are also really important. But I think maybe we can explore that a little bit deeper in a moment, but yeah, curiosity, I'm going to say.

Adel Nehme: 100%. And you mentioned here technical skills, engineering skills, and I'm excited to unpack all of those with you. I'd love to expand on what you think are the technical skills needed for a successful day analysis today, and where do you think Tableau fits in the picture in the wider tool ecosystem analysis needs to know?

Andy Cotgreave: Fundamentally, you need to get up to date on your database skills. So learning SQL clearly a going to be a huge skill. When I started in this field, it was really only relational databases, so understanding data structures and SQL, fantastic. Obviously since the world has developed, there's not unstructured data, there are many more different types of data models, so really getting [inaudible] on your XML, all of that stuff is going to really help you.

Andy Cotgreave: To be a successful data analyst and data scientist, you don't have to be super, super deep into those skills. There are different paths you could take within the data analyst career. But you have to have a good foundation in that knowledge because otherwise none of what you're going to do is going to be ... or you're not going to understand any of what you're going to do.

Andy Cotgreave: So I think that's a real challenge right then, so that's kind of data structure, data architecture. You're going to do a lot of data preparation, cleaning, and at that point your database structure is going to be great, but then you've got to think what tools do I need to do this? Obviously we have Tableau Prep. I love using Tableau Prep, but again, getting your head around merging fields, processing data, and transformations, pivots, that kind of thing is also key.

Andy Cotgreave: And then the higher or the more front end customer end, you've got the analytics tools. So then it's there are many tools in the market, obviously Tableau's amazing, but as you say [inaudible] Python, these are all great skills to get into your portfolio. For anybody who's really early in their career, just start developing skills in one tool of choice, and as your career grows, the paths of your career might steer you towards one or other newer tools.

Adel Nehme: Obviously technical skills are very important, but data visualization skills are also extremely important for data analysts. I've seen you speak about this. You've written a book on this, and you've even extended this to say that data specialists should think like designers. I'd love it if you can expand that notion and what you think thinking like a designer means, and what are the design skills data experts need to know to be successful in data visualization?

Andy Cotgreave: So this is something I'm so passionate about. And there's a woman called Kim Reese, she co-founded Periscopic, which is a nonprofit data visualization consultancy in Oregon, in the U.S. And she sat on an episode of Policy Biz, which is another great podcast about five years ago. She said, "Data visualization is a language, a means to convey an opinion or an argument."

Andy Cotgreave: And that quote, I mean that has stuck with me and sort of become one of my north star pieces of inspiration because it captures the fact that at our peril, we think charts are truth. It's like, "I have aggregated the data and I've made a bar chart. And therefore that bar's bigger than that one. It's true. It's an un-controvertible fact. It's like no, because that aggregation in that visualization in a certain way, and you can make charts, tell hugely different stories with subtle choices of aggregations or design or color choice, orientation, the title, annotations, all of these things can change how the end users interpret the chart.

Andy Cotgreave: And I find that absolutely fascinating. And the reason why design skills are so important is that you need to be able to wield that power deliberately, right? You could wield that power and frame arguments accidentally. Some people deliberately deceive with the way they frame charts. So to be super powerful at this, you have to know when to turn some of these levers up or down to push an opinionated thing or to try and be neutral, and also to be able to critique other people's works and see when they might've inadvertently swung you one way or another and have that critique.

Andy Cotgreave: So design, it's just absolutely fundamental to things. Think about dashboards. I co-wrote The Big Book of Dashboards, 28 real world case studies that we are dissected and sort of described how they worked. And you are creating an object that is consumed by other people. That's what Apple does with iPhones, that's what Samsung does with TV remote controls. Even your kettle, even your washing machine, they are designed objects that have to satisfy various different levels of processing.

Andy Cotgreave: Another great book is Don Norman's The Design of Everyday Things, another huge influence on me. And in that book, Don Norman says that any object that is designed is processed in three ways by every end user. There is a visceral level of processing, a behavioral, and a reflective. That visceral is the first millisecond of experience with that object, where people judge it on how it looks. It's inescapable. So if your dashboard looks awful, you've already lost half your audience. So you've got to make something look good. iPhones look great for a reason, right. Nice kettles look really nice when they're, when they're really nice and designed.

Andy Cotgreave: And then the behavioral level is okay you've got this object, can the person trying to use that object do the thing they want to do with it, right? Or is it too complicated? Don Norman has the example of doors in buildings that the design to be pushed, but they have a pull handle on them, right, and that's a sort of a confusing user experience, because it looks like a pull handle and so behaviorally it's a bit confusing. But again, you've got to put that into your dashboards. Can people actually work out how to interact with that dashboard to answer the questions?

Andy Cotgreave: And finally after that, they will reflect and think, "I did or I didn't like that dashboard." And if that reflection is successful, they will come back. So it's no good being an engineer and just thinking the power of my engineering will succeed because you've got to think like a designer to get the human experience to be a success too. So I could do an hour and a half on that conversation.

Adel Nehme: Definitely, we can expand on this. So you've mentioned here the power of design skills and conveying messages, and it could be used deceptively. So we've especially seen the power of design on display in 2020 with COVID charts, climate change charts. So with that, what do you think are the weapons, to use that analogy, in the hands of designers that they can use to convey their message impactfully? What are the tactics that they can employ?

Andy Cotgreave: I mean there's a really famous example from Simon Scarr. This was a chart called Iraq's Bloody Toll, it came out in 2012, and it's data about deaths in Iraq from conflict. And what Simon Scarr did was point the bars downwards and color them a very evocative blood red and use the title Iraq's Bloody Toll at the top, so when you look at it, it looks like a smear of blood dripping down the screen, it's really emotive. And so what did he do? He used color and orientation. Should a bar chart point upwards or downwards? Well, normally it would go up, but he pointed them down. And then he used the color to create a visual metaphor.

Andy Cotgreave: But then also importantly, he gave it a title, right. Just think about how reactive we are to titles these days. If you go to YouTube, the wording of a YouTube video title is so click-baity these days. "You won't believe the things," and I'm a sucker for that. I'm like, Oh, better watch that." Research shows that the first thing people look at when they look at a visualization is the title, so you have this moment to grab people's attention and tell them what you want them to take from a chart, right?

Andy Cotgreave: Now, that's extremely powerful when I'm building dashboards or building PowerPoints that my CEO might see or that he or she might even deliver because the chart appears, everybody reads the slide, the chart title, and then there's the chart that proves the point. Then when you think about this in 2020, obviously coming through the pandemic, ... Well, sorry. So that's an example of some of the techniques you have. Color, orientation, size, all of that of the techniques.

Andy Cotgreave: And what the pandemic has shown us is how carefully one must wield that power. I'm based in the UK. Our government has had regular press conferences that have led with charts. The prime minister would say some words, and then he hands over to the chief scientific advisors who update the country, a nervous country, about this horrible pandemic. And that team in the Cabinet Office in the UK had to work extremely hard to make sure the charts were neutral because any perceived bias or influencing in that data visualization will get pounced upon by the opposition or by the media. And they'll say, "They're trying to make us think X and Y." And maybe they are, right, but they can't be seen to be in press conferences.

Andy Cotgreave: So what's been interesting in the UK is that experience of seeing the effort to reduce all the dials back to zero on anything that is not neutral. They're going, "Here's the facts. We're trying to express them without opinion." And so that's kind of the spectrum of power. You can go from Iraq's Bloody Toll, which is full on in your face, you're going to think blood smearing down the screen, to COVID pandemic charts. It's like, "We're just presenting the facts and there's a lot of uncertainty, and we're making decisions based on needs."

Adel Nehme: That's perfect. And it really depends on the situation, which is your work context, and what is the desired impact analysts want based on their visualization analysis, right?

Andy Cotgreave: That's not universal, right? Because if I'm building an exploratory dashboard that people can log onto and interact to track website visits or staff turnover, in that case things have to be neutral because you're not really expressing an opinion about the data. It's just like, "Here is an object you can use to track what's happening in the organization." But a huge part of business is I'm going to go to my managers and convince them based on evidence to make a decision to change the organization, or I'm going to go to colleagues or my own team and say, "We need to make a change." In that case, I am going to use persuasive charts because I've got an opinion and an argument to convey. So I can then in a business situation use that framing technique to sell my argument.

Andy Cotgreave: And in a healthy data culture, that's as powerful as me using emotive words. "I think it's going to be a great idea if we put this podcast in front of a million viewers," right? I can say those words and you can go, "Well." we can have an argument with words. We can do that with data too. So it is possible to do that in a business environment. But again, wielding the power without being deceptive and also everybody having the fluency with data to know how to sort of counter, how to process those arguments and have a data driven conversation is powerful.

Best Practices on Data Storytelling

Adel Nehme: I'm excited to unpack data electricity with you. But before we do that, obviously data visualization skills, engineering skills, design skills are all super important. But the last mile of analytics is really the narrative you weave, as you said here, with words. This is what has often been called data storytelling. Can you share your thoughts and best practices on data storytelling, and how analysts can gain better adoption of their solutions?

Andy Cotgreave: There's a couple of things that make my blood boil. One of them is when somebody copies and pastes a chart from one medium, and then paste it into PowerPoint. And the first thing that drives me mad is when they don't even make it fill the screen, right. They just go copy, paste, then they present it, right? I'm 50 years old. My eyes are not what they were when I was 20. And this was a problem when we were in live meeting rooms. It's a problem now out when we are looking on our laptops and these things. If somebody says, "As you can see on this chart, blah, blah, blah," if I can't see that, it's like you have failed in your job as a storyteller because I can't see your blooming chart.

Andy Cotgreave: And so often I've been in presentations where a chart comes on screen and they say, "Oh, it's a bit small on the screen." And I'm like, "If you have to say that, you are lazy because you have not thought about the storytelling power of actually using this data to drive change." So that just drives me potty. So if you do nothing else with any chart on a PowerPoint slide, at least make it fit the screen, right?

Andy Cotgreave: Secondly, it is when they say, "Oh, this chart's a bit complicated, but it shows blah, blah, blah, blah, blah." And I'm sitting there going, "You've literally copied and pasted a dashboard onto a PowerPoint. It's got 10 charts on it and 96 pieces of information. How the hell am I supposed to know which bit of that you're referring to?" The words coming out of your mouth might be, "It shows that sales are down and we need to do X." And I'm just looking at a mass of information. I have no idea what I'm doing.

Andy Cotgreave: The reason these make my blood boil is because as a storyteller, if I'm going to convey information in a meeting, in a presentation, in a keynote, in anything, or an email, how does the end user know what they're supposed to be looking at on that screen at the time you look at it, right? So thinking about storytelling is what is your narrative through any visual you put on a screen? If you're going to put a chart on a screen and that slide's only going to be visible for three seconds, then that chart has to be understandable in about one and a half seconds. If it can't be, it's the wrong chart.

Andy Cotgreave: If you really want to show a complicated chart that takes two minutes to explain it, spend two minutes explaining it, and bring each element of the chart forward one at a time. It's like, "This is what the axis is. This is what the X axis is. Each mark represents a country and the color represents the continent and the size represents population." And then you're bringing the audience along so that you can actually explain the point.

Andy Cotgreave: If anybody wants to see the done the best way possible, go check out Hans Rosling's Ted Talks because he was the master at this. And I mean there are loads of different texts, there's loads of different techniques. But storytelling is absolutely vital because you're using data to try and drive change in your organization by sharing insights. Every single visual you show has to be part of the narrative flow of that conversation point. So yeah, sorry, don't make my blood boil. If you ever do a presentation and say to me, "This chart's a bit complicated, but," then I'm like, "Ah, you've let me down."

Adel Nehme: In terms of driving that narrative, I think something that data scientists struggle with is fitting a narrative and finding that narrative structure to their data or to their exploration. Is this something that can be templatized or is this a highly specific ad hoc problem that needs a highly specific ad hoc solution?

Andy Cotgreave: Yeah, yes and no, right? Because it's difficult to say ... I can't tell anybody what the right narrative process is for the thing they're doing because it all depends on what their specific process is, right? But that's not very helpful to somebody learning out, is it?

Andy Cotgreave: My good friend Ben Jones, he used to be at Tableau and now runs Dataliteracy.com. He did a great set of content about the seven different types of story. And anybody who's familiar with fiction might know there are seven different types of story: the quest, the ... Yeah, right. And he sort of did some work to think how could you tell different data stories based on different approaches? Do you start out with a big picture and zoom in, do you start zoomed into a really low level piece of detail and then zoom out, do you show progression over time? And if showing progression over time, can you bring drama about one data point through this?

Andy Cotgreave: So there are ways in which you can think of the story. They will often lend themselves to presentations or narratives if you're doing reports. What is the narrative through a report? In dashboards, story's slightly strange in dashboards because the dashboards are largely exploratory facets. "I'm going to go to the company sales dashboard to see what's happening in sales." But for me, a lot of the inspiration for dashboards comes essentially from comic books, or wanting to be a comic artist when I was 18. And a lot of the learnings from the world of comics is how they use a layout on a page to create a flow of time and direction. And I mean, if you get into the study of comics, it is amazing seeing the different ways they can create narrative flows with that page and frame structure.

Andy Cotgreave: So on a dashboard, the top left is where people are going to look out first, and then you can largely follow a left to right, down a bit, left to right structure. The Gutenberg Diagram is another design principle from print about how people look at pages. So you kind of want your most important thing in the top left, and then more granular levels of detail out towards the bottom and towards the right. It's not universal though because you can play around with that kind of stuff.

Adel Nehme: Given that we just discussed the data visualization and design skills needed to be successful data analysts, I'd love to pivot more to discuss how this looks like from an organizational point of view. Obviously bridging the gap between reality and what's possible in terms of making use of data at scale is very important for organizations. However, I'd argue that data literacy is the biggest obstacle to that value being realized. And we can discuss that. I'd love to hear your thoughts on how you define data literacy, and what it means to be a data literate organization for you.

Andy Cotgreave: So this is really important, and I think there's various sort of levels of data literacy. I think largely as a definition, being data literate is being able to do some or all of read, consume, and critique. Read, consume critique, and create visualizations, right? Not everybody needs to be able to do that. I would say everybody in an organization needs to be able to be comfortable reading, looking at and understanding what charts are showing. And it's not a hard skill, but a lot of people just have not been taught that skill. The subtleties of the way color can be used to influence things, which is the appropriate type of chart, is an important skill to learn to read. So being able to read and consume those, but also being able to critique them.

Andy Cotgreave: There's a lot of research going that shows that people see charts as truths, right? It's hard to criticize a chart. Maybe I could criticize your paragraph of text, but you put it in a chart so it must be true. So yeah, absolutely. So being able to look at these and have that critical mindset that you don't need to mistrust things, but you need to be able to question them, and then produce charts as well.

Andy Cotgreave: Should every single person in the organization be able to use tools to produce visualizations? I mean ideally I'd say yes, but realistically probably not. So they're the four key pillars, and how do you test where your organization is in that ability? It's really hard for people to self admit that they are not data literate. I mean I don't have a problem with the term data literacy, but some people I think legitimately do because it's like, "Are you telling me I'm illiterate in this thing?" So there's negative connotation to being illiterate. So another phrase could be data fluency because fluency sort of has a baseline with which is I'm not very fluent and I'm really fluent, but I can still be at the baseline.

Andy Cotgreave: But the reason I raised that is because it's actually quite hard to assess your organization's baseline. You can survey users, you can ask them to self-assess, which is useful and that can create a benchmark which you can then change. Yeah, so I think that's a definition of data literacy. Trying to benchmark your organization is key. Well then, the next step is how do you improve that fluency?

Andy Cotgreave: What we've found at Tableau over many years is that one of the great things is creating a community. Tableau has this crazily excited and excitable community of analysts and geeks who just love using Tableau and love the field of analytics and the field of communication and engineering. And we have seen that that generates a momentum in and of itself. We often say that our Tableau community won't let you fail. When people start getting involved, they ask questions and there's forums and Twitter and social media, video series. People will offer help, and there are many, many solutions out there.

Andy Cotgreave: And what we now see is when customers try and enable an internal community, then that is a really good way of creating a virtuous circle that sort of builds its own momentum. One example, something I do at Tableau, we do what's called a Viz Club. And what we do is we, we find a chart from the world and once a month we just sit around and critique it. And the reason I run that is because it's a super low level barrier to entry, right? Anybody can come in and say what they like or dislike about a chart. And it's really not intimidating for people who are lower down on that fluency track.

Andy Cotgreave: I could do a club and say, "Hey, it's the monthly Let's Hack Tableau club." And instantly, I'm going to eliminate 90% of people because they're like, "Oh, I'm not very good at Tableau yet. Or I'm not comfortable at analytics," and so it's really high barrier of entry and quite intimidating. So you can take really small baby steps. Formally training strategies, build what is your data literacy program, how are you going to fulfill or improve those four criteria. And there are plenty of training materials. We have a free data literacy course, obviously Data Count has loads of things. So yeah, it's about building that strategy to improve everybody's level.

Adel Nehme: That's really interesting when you mention the community building aspect of it. I think a lot of organizations sometimes forget the aspect of building a learning ecosystem rather than just dumping training courses onto their workforce. This involves live trainings, meetups, expert talks, hackathons, and we found that works best even on our side with DataCamp customers, especially when creating a data culture.

Designing a Data Literacy Program for an Organization

Adel Nehme: If you were to design a data literacy program for an organization, what would it look like? Of course this is highly persona-specific, so if you want to talk about the lower end of the data fluency spectrum. Would you focus on a tools agnostic conceptual program such as understanding use cases of data, or would you have a tool specific training in mind?

Andy Cotgreave: I'd start tool agnostic. I think for the people who aren't producing charts, for them it's how do they learn to read, right, and they will have been told hopefully basic skills at school, but not some of the more [inaudible] techniques. So it's like charts work ... A fundamental of data visualization is that the individual atoms that make up a chart, like a bar or a line or a dot, those things are called pre-attentive attributes. I mean that's a bit of a generalization. But the concept of length or position or angle are things that we cognitively see instantaneously when we look at something in front of us. And it's those pre-attentive attributes that enable us to make visualizations. Once you know things like that, it suddenly means now I know the individual pieces. I can actually understand how a chart is put together. And then once you understand that sort of super granular level of how a chart works, it makes it easier to consume it.

Andy Cotgreave: So I think teaching those fundamentals is really important. And it just allows you to then build up to words. I mean it's like learning to read. At first, you learn letters, but then simultaneously you're learning letters but you're also learning words, short words at the start. And then simultaneously you're beginning to get sentence structure. So that's how we teach kids to read, we kind of do this hodgepodge of the individual bits, the words, and the sentences. And then as you mature, it becomes writing essays, but also reading books. And then eventually you get to university and not only you're reading books, you're writing books, but you're deeply thinking about literacy and communication.

Andy Cotgreave: And that's essentially the same framework for a data literacy program. How do you learn the absolute fundamentals? Simultaneously with practice, put some of them together, maybe run a little bit before you can walk, and then eventually just add more and more depth. So I think taking that model to your own strategy is great.

Andy Cotgreave: At some point soon after the fundamental bit, then obviously you've got to become a practitioner, at which point tools become important.

Adel Nehme: Couldn't agree more. And here circling back to something that you've also mentioned, I've seen you speak about extending data literacy programs to schools in order to prepare future generations to work and think with data. Do you mind expanding on some of your thoughts here?

Andy Cotgreave: Yeah. I've got two daughters that are teenagers now, and it's been quite funny. They have slightly more advanced data skills than their peers because daddy's bored them a lot with all this data stuff. But it is interesting watching them go through the experience of the UK education curriculum, where they're encouraged to make 3D exploded pie charts because they're funky, right, and you think ah. So they have a relatively strong grounding of what ... Well, they have a grounding of what basic data is, right, and the visualization is a thing. But there's nothing about why it works, right? They're just told, "Make some numbers. Build this thing." So there's none of that foundational knowledge, and I think that's the thing that's missing. I find it more fascinating to know why something works than just do it, right?

Andy Cotgreave: So if we could change the education curriculum to be a bit more about why these things work and then, as we just in the previous answer, if we can get them more to the how to critique and be a consumer of this information, then I think it's a really important thing to do at school because it's 2021, we've just had a pandemic, we're in a world of misinformation, it's a scary time for kids coming into the world. And are we equipping them to be able to in better interpret the world around them, the avalanche of information that's coming at them? I don't think we are. We're just telling them to make 3D pie charts, when instead we could be building fluent data literate kids.

Adel Nehme: Especially when you think about it from a future workforce readiness perspective. I think that a lot of organizations are doing the heavy lifting now and preparing their workforces for the future. There needs to be modernization of the skills taught at the school level as well.

Andy Cotgreave: At Tableau, I mean we've got a great academic program, which helps students, but we've also been doing a data for kids program as well, trying to come up with funky exercises, interesting exercises to get kids thinking about data literacy. I certainly did a few during the pandemic when we were homeschooling. And it's really amazing how you can get them to come at this world of data without them going, "Oh, dad's talking about data again. Ugh." You can bring it to their lives without them quite realizing what you've done.

Adel Nehme: That's really wonderful. And we've also seen a lot of good success in DataCamp for classrooms and for colleges. I'd like to circle back to dashboards here and the role they play in the democratization of data insights, and maybe here play devil's advocate a bit. How do you view the role of dashboards in enabling organization data literacy? Similarly, what do you think are some of the drawbacks of dashboards? Do you think that there is a risk of having too many dashboards and information glut and this can hurt an organization's ability to make decisions with data and its entire data literacy program?

Andy Cotgreave: You can bash the dashboards all you want. I mean I think one of the potential downsides of having written a book, The Big Book of Dashboards about dashboards, is that people then think I am an advocate, that dashboards are the be-all and end-all of your BI strategy, and nothing could be further from the truth. I also do a whole presentation, a bit of content, there's a chapter in the book about don't build a dead end dashboard. They are the start of the journey, not the end of the journey. Right, so dashboards are amazing, right? Every organization is asking a question about their organization or their customers. Do they know they're going to ask every week or every month or even every year, right? You are going to monitor things. Is the website up or down? Is sales tracking? Is turnover getting dangerously high, or is turnover great, right? Is staff turnover good or bad? That question's, we want to know those every month, we're going to track them.

Andy Cotgreave: So whatever you call it, whatever the vehicle is, you need some sort of monitoring display so that people can keep an eye on these key performance indicators or OKRs, whatever you want to call them. That said, if that's all your business has, oh my God you've failed completely, completely. Because I mean think in your own organization, do you think in the next seven days somebody is going to ask a question that you hadn't anticipated? And if your answer to that question is no, then I mean I'd love to see your organization. Every organization is dealing with uncertainty, resilience, and ad hoc things, right? I mean the pandemic turned everybody upside down and it was organizations that were really digitally strong had great resilience because they were able to respond quickly to things they hadn't anticipated.

Andy Cotgreave: So at that point, a dashboard's useless. A dashboard answers three or four question that you asked years ago, right? What about the question today? So you need this fluid, messy, exploratory, iterative, rapid response approach to data too, and that re that requires strong data sources, skilled users, and data fluid people who can ask the questions and respond to what they're seeing very, very quickly to get to the ad hoc councils. So yeah, dashboards, holy cow. Dashboards are a part of successful analytical strategy. You are failing if you only build dashboards. Can you build too many? Yeah. That is also a big problem.

Andy Cotgreave: And we see customers that like, "We wanted to escape Excel hell and now we're in dashboard hell." It's like, "Yeah, that's not great." But again, great processes, and this is where actually not data architecture, but being able to architect a good business intelligence stack and process is really important. What we do at Tableau is anything that gets published has an expiry date, and as that's getting closer, we'll start getting notifications and emails being like, "It's going to get deleted and nobody's been looking at it." So we sunset a lot of work because we recognize dashboards die, right? They do. Dashboards die. It's ongoing creative destruction continually is really part of the strategy to keep things fresh.

Adel Nehme: That's great. I want to harp on here the importance of resilience and agility. I think not a lot of people discuss this as being a part of a data driven organization, but it's very important to kind of instill that culture of resilience and agility. So what are the ways that you think you can forge the sense of resilience?

Andy Cotgreave: Success in a data culture? There's three things. You need to have an agile system, right? So that's about creating that architecture that has the robustness of data sources, but also the ability for people to find things and respond quickly. There has to be a high level proficiency, so that's the skill base across an organization, the data fluency, but also the hard technical skills of using the platform you've implemented. And then the community is the third aspect of success, and that's about having people who are engaged.

Andy Cotgreave: In order for all of that to succeed, you also need buy-in from the top. We see customers that succeed when the executives are in on this too. They don't have to be making dashboards to be bought in, but they have to be using the data and really buy in. We see a lot of failure where something grows organically in a small part of the organization and they get kind of, "Yeah, yeah. Keep going from the top," but they don't get that organizational buy-in. Data has to be a strategic asset in order to drive that success.

Andy Cotgreave: So again, it's data literacy, data fluency, ensuring you've got the engineering skills and the architecture installed, the BI strategy to allow flexibility and rapid response. And it's hard, it's really hard.

Where do you view the role of AI and automation coming into play within organizations?

Adel Nehme: Yeah, that's awesome, especially executive buy-in and leading by example, they're so important. Now pivoting to discuss the future, where do you view the role of AI and automation coming into play within organizations? There's often a lot of discussion around intelligence augmentation and augmented analytics. Where do you fall in the automation versus augmentation debates? What are some of the key trends you're excited about in the BI and AI space?

Andy Cotgreave: I'm all in favor of AI that augments a user and gets them from A to B quicker. I think most certainly the BI industry is investing heavily in that, and Tableau is too. For example, we've got Ask Data and Explain Data are two new technologies that ... Well, actually they're many years old now, but they're really iterating fast. Ask Data, for example, is a natural language interface to a dataset that in its latest iteration, I'm really excited about it because what I fell in love with in Tableau 14 years ago was this ability to drag and drop things around this interface and just be in complete control of the data. But you had to have an analyst's mindset and an analyst skill set to really embrace that. And hundreds of thousands of millions of people have them.

Andy Cotgreave: But if you're not a data nerd who knows the difference between a discreet and a continuous data field, that's a little bit intimidating. Ask Data now lets you type in a question a bit like typing in something into Google, and you get an instant response. But what I love about what we've done with it is that as you type the sentence, it becomes something you can click on and iterate, change each part of the phrase of what you've written. And for me, it's the perfect extension of the power the analysts have putting into the hands of non-analysts, just normal business workers. And I don't know if it's an epiphany, but recently I realized that the end goal of this is that there's always going to be a space for analysts in the Tableau world, right, because there's always going to be more than this.

Andy Cotgreave: But eventually you'll get to the point where people stop being excited about using Tableau, right, or any other tool that gets there. And I'm like what [inaudible] saying, "I want a world where people are not excited to use Tableau." Huh? Let me explain.

Andy Cotgreave: I use Microsoft Word every day to write my blogs and my content, and I use PowerPoint and Google slides. I don't come out at the end of the day and go, "Oh, I had a great day using Microsoft Word." I just come out at the end of the day going, "I wrote some great content," because that's what you did, because the tool just does its job. And so with Ask Data as we put data in the hands of more people, hopefully, i think the great goal is they've been augmented to the point that they don't have to think about the tool they're using. They're just asking, "Hey, I asked them questions about my data today."

Andy Cotgreave: And AI, machine learning, really, really help empower that. And again, our integrations with Slack are going to improve to the point that you can do this all in Slack, and that's driven by AI, machine learning. And yeah, to the point that people stop thinking they're using Tableau, they're just asking questions of data, and that's great. So yeah, I think I'm saying I'm campaigning for a world where people are no longer excited about using Tableau. Yeah, that somehow seems strange, but hopefully people know what I mean.

Adel Nehme: Definitely see where you're coming from, especially when there's this kind of ready to use infrastructure to support data driven decision making through a lot of these tools that you're discussing. So given that, I also agree that there's always a place for a data analyst and an augmented data analyst, as you say. What do you think is the most useful skill that analysts need to know in a world where a lot of simple data workflows are either automated or semi-automated?

Andy Cotgreave: Well, I think another good metaphor is Instagram, right, and mobile phones. Mobile phones have made as all professional photographers. We can do filtering techniques that traditionally would've been done by true experts in the developing lab, right? They would apply things as they process photos that we can now do in the space of a click. And in some ways, that's again the goal, right? But there is still a space for professional photographers, so that's great. That is still going to be the case for analysts. There will always be the unanticipated sides of things. I suspect there will always be edge cases that natural language just won't be able to query, right? So I think the life of the analyst is not under threat.

Andy Cotgreave: In terms of skill sets, if I'm really honest, I'm not sure I have a really solid prediction of what the next skillset are going to be because much of the reality of what I is a BI industry creating really advanced technology that promises complete revolution. And I go to customers, 90% of them or thereabouts, are still using PDF and Excel data sources. And they're looking at this AI stuff and going, "I still have to copy and post a table from this PDF into a CSV file and then connect it." So much as the cutting edge of the industry is, "Wow, it's sci-fi," actually most customers it's going to take decades for them to chase. So I think the traditional skills are still going to be valid for a significant time in the future.

Call to Action

Adel Nehme: Awesome. Finally Andy, as we wrap up on an inspirational note, do you have any final call to action for today?

Andy Cotgreave: If anything, if anyone's listening to this, I would just say find a community and join it. And I mean an examples, Tableau Public is our free place where you can share visualizations. And we've got things like Workout Wednesday, Vis For Social Good, all these social projects where people hammer out and play around with data sets and share their findings together. And it's really enriching because joining that community exposes yourself to other people, it puts you in a learning mode straight away, but it also puts you in a teaching mode straight away because anytime you share some work you've done, you're going, "Well, this is my interpretation of the task."

Andy Cotgreave: And something we've learned over the years is about critiquing in a constructive way is really important, so being able to hear critique, but add critique in with the motivation of elevating everybody else is hugely beneficial. Particularly on Tableau Public, but as well you will also build a portfolio that shows the progression of your skill. And it's slightly strange that from an engineer's perspective like, "I don't need to have a portfolio of my work," but from the design perspective, graphic designers have portfolios. So yeah, join a community.

Adel Nehme: Yeah, couldn't agree more with that final flag as well. Thank you so much Andy, really appreciate you coming on Data Framed and sharing your insights.

Andy Cotgreave: It's my absolute pleasure. Thanks for having me.

Adel Nehme: That's it for today's episode of Data Framed. Thanks for being with us. I really enjoyed Andy's insights on visual ethics and data storytelling best practices. If you enjoyed this podcast, make sure to leave a review on iTunes. Our next episode will be with Vishnu Ram, VP of Data Science and Engineering at Credit Karma. I hope it'll be useful for you, and catch you next time on Data Framed.