<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Neil Richards on Medium]]></title>
        <description><![CDATA[Stories by Neil Richards on Medium]]></description>
        <link>https://medium.com/@neilrichards_16079?source=rss-170fe07b66d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*e17YYRnwflIJjFyO5JQHVQ.png</url>
            <title>Stories by Neil Richards on Medium</title>
            <link>https://medium.com/@neilrichards_16079?source=rss-170fe07b66d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:27:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@neilrichards_16079/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[‘Avoiding Data Pitfalls’ — an Interview With Ben Jones]]></title>
            <link>https://medium.com/nightingale/avoiding-data-pitfalls-an-interview-with-ben-jones-e06c67bf25c4?source=rss-170fe07b66d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e06c67bf25c4</guid>
            <category><![CDATA[data-preparation]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[statistics]]></category>
            <category><![CDATA[data-literacy]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Neil Richards]]></dc:creator>
            <pubDate>Mon, 23 Dec 2019 16:19:55 GMT</pubDate>
            <atom:updated>2019-12-23T16:19:55.362Z</atom:updated>
            <content:encoded><![CDATA[<h3>‘Avoiding Data Pitfalls’ — an Interview With Ben Jones</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*wQrOb20ZbCv8ZMMQ6zv-IA.jpeg" /><figcaption><a href="https://www.amazon.com/Avoiding-Data-Pitfalls-presenting-visualizations/dp/1119278163">‘Avoiding Data Pitfalls,’ by Ben Jones</a></figcaption></figure><p>We caught up with Ben Jones, the founder and CEO of Data Literacy, and spoke to him about his recent book, <a href="https://www.amazon.com/Avoiding-Data-Pitfalls-presenting-visualizations/dp/1119278163"><em>Avoiding Data Pitfalls</em></a>. Ben’s book is described as a reputation-saving handbook for those who work with data, designed to help you avoid the all-too-common blunders that occur in data analysis, visualization, and presentation. The book explains that unless you truly understand how to work with data, there are many ways in which you can ultimately mislead and cause costly mistakes.</p><p>Our questions were from Neil Richards, Data Visualization Society’s Knowledge Director.</p><p><strong>Neil Richards: I enjoyed the book and found it really easy to read, because I felt like I was having a conversation with you about data while I was reading it. I know this book has been a labour of love for you since you’ve been working for Tableau. Tell me why you wanted to write this book in particular?</strong></p><p><strong>Ben Jones</strong>: Really for two major reasons: Firstly, most of the conversation, at least in the data visualisation community right then, centered around chart type choice. There was a list of “no-no” chart types that people would get ridiculed for using and it occurred to me that you could use a completely compliant bar chart but mislead people for totally different reasons unrelated to the encodings of the chart itself. That really hit me because the conversation wasn’t really about that, it was just about the last part in the process, which chart to use, when there had been so much done already up to that point: gathering the data, transforming it, creating calculations, blending, joining, all of these steps that could be completely full of errors that would lead you to create a nice innocent-looking bar chart that completely misled someone.</p><p>Secondly, realising that the tools were becoming so powerful (like Tableau and many others) that I sometimes didn’t feel I had the knowledge and skills to put that to good use without “driving a Ferrari into a brick wall,” so I wanted to give people a warning about things that were pretty easy to do wrong. Also I was teaching at the University of Washington at the time — some of those students were making the exact same mistakes I used to make, there was a lot of commonality there.</p><p><strong>NR</strong>: You make it quite clear that in seven chapters, the ones we think of as the chart and design elements are really just chapters six and seven, so you make the important point that five-sevenths of the stuff you really ought to be thinking about has already happened by this stage.</p><p><strong>BJ</strong>: I felt that for those last two points, a lot of really good books have already been written about them. I refer to Alberto Cairo’s new book <em>How Charts Lie</em> in that chapter itself — really recognising I didn’t want to write another book about that, but for those unfamiliar with the concepts I really couldn’t leave them out, so that’s why they are included but not given the lion’s share of attention.</p><p><strong>NR</strong>: I would have expected your first book to feature the wording and branding of Data Literacy more, and it’s interesting that it doesn’t. How does <em>Avoiding Data Pitfalls</em> fit in with your Data Literacy company?</p><p><strong>BJ</strong>: Good question. At the very end, my publisher suggested we might as well put my Data Literacy connection on the cover, but I think it’s because this project started well before I woke up to the idea that another way of affecting and improving those same issues was through the positive message of Data Literacy. At the same time, if you think about it, consider grammar: Take a sentence and pull out the comma from “Let’s Eat, Grandpa” — if you take the comma out, that completely changes the meaning. Even in literature, writing and grammar, there are very small mistakes you can make that have disastrous consequences on the overall meaning. I think the same is true in data. To me how they fit together is that data literacy is effectively speaking the language of data. A part of effectively speaking the language of data is knowing what simple common errors to watch out for and avoid similar grammatical errors.</p><p><strong>NR</strong> So Data Literacy is the positive and <em>Avoiding Data Pitfalls</em> is the negative — the carrot and the stick?</p><p><strong>BJ</strong> Yes — what to do versus what not to do.</p><p><strong>NR</strong> When I picked the book up, before I’d even opened it, my first question would have been “how many of these errors have you made yourself?” but you make it quite clear right from the start that you have made them all. I know I certainly have too, so I guess it was important to make it clear that everyone does?</p><p><strong>BJ</strong>: We have this culture where mistakes are dragged out into the open — I don’t know if we have a climate right now where people can raise their hand and say “<em>mea culpa</em>” but with data now it’s so common and it’s dangerous to have that culture because now we can’t help others learn, we have to cover those mistakes up. I think that would get in the way of helping others become data literate if they felt like every time they made a mistake they weren’t allowed to say they’d done something wrong (even if they were an author, an expert, or whoever) — but yes, if I say I’ve made many of these mistakes before, maybe it’ll help people in some small way to think yes it’s ok to say that. That’s part of the goal to recognise that: data’s not perfect, but really neither are we.</p><p><strong>NR</strong>: I love the way it’s set into seven chapters (I particularly liked Epistemic Errors, as director of knowledge I learned the new word Epistemology, I might use a new title!)</p><p>They are all alliterative, obviously that was deliberate, and we’re quite well known in the Tableau community for our alliterative projects such as Makeover Monday and Sports Viz Sunday. Were there some that missed the cut?</p><p><strong>BJ</strong>: Oh my gosh — when you have as many as are in there, you get shackled — more than one time I wondered why I went down this path and thought now I have to figure out a decent alliteration.</p><p><strong>NR</strong>: Alliteration in subsections as well as chapters, you were committed!</p><p><strong>BJ</strong>: There were more than one that were really stretching — I thought people would really love or hate it!</p><p><strong>NR</strong>: It really helps from a mnemonic point of view — you talk about having a checklist at the end of a book, perhaps you’re more likely to remember “Graphical Gaffes” and “Analytical Aberrations.”</p><p><strong>BJ</strong>: Hopefully it sticks a little bit, exactly.</p><p><strong>NR</strong>: Were any messages strongest, that you feel people had paid least attention to — we mentioned how much attention have typically been paid to the topics of the last two chapters, but were any that you felt were more important, or more overlooked, than others?</p><p><strong>BJ</strong>: I would have loved to have had more time to develop Chapter 2: Technical Trespass — if I ever did a revision that might have some more contact, for sure. For ones that people think of the least, we’re all painfully aware of Statistical Slip Ups, that’s well known: p values, hypothesis testing, people generally have that experience in “Stats 101” in college where they go “this is complicated” — I don’t think that was brand new and many other books have been written that expand on this. Graphical Gaffes was around chart choice but I tried to change the focus of that so it was less around chart choice and more around this idea of how do we consider these alternatives we have in this arsenal of visuals and encoding to apply and how do we think about making use of all of those or the right ones.</p><p>This idea of “optimising vs. satisficing” is one that I pulled out from operations research and tried to bring to the dataviz world in a blog post a few years ago, and it’s really in response to people saying, “You need to make the best chart choice” versus saying “I’ve got one that’s good enough,” and realising that most fields recognise there is room for both of those approaches. That’s not a choice that you necessarily have to take exclusively. We live in a world where there are some people figuring out the very best ways to do things and all nuances of what works well and pros and cons, but we also need a world where practitioners are able and free to go with what works and also have some ability to not be shackled by those constraints. That is an idea I was really excited about when I came across it because I think it came across really well.</p><p>Also the last one, the eighth one, that didn’t even make the lists, that’s something we’re only really beginning to wake up to, that there’s so much bias in the world we live in. Many voices are not heard and that can affect our data. That even affected my data in trying to write the book — trying to look for quotes and not encountering that many by women.</p><p><strong>NR</strong> My eyes are really opened in a good way by that — you and I and many others are passionate about this, but I read that on the very same day that I went to a user group that was 90% male and I was thinking “Why am I wearing my Data Plus Women shirt here — the women aren’t here to read that message?” It feels like at least in smaller pockets there’s still so much more for us to do.</p><p><strong>BJ</strong>: I think it’s a long journey to chip away at those walls and barriers that are keeping a more diverse group of people from participating in the data dialogue. I at least try to say in the spirit of the book that “Hey, wow, I got it wrong myself right here in the writing of the book” so that was something I was shocked to find out. You have to look at this and go “how did this happen?” We are not as far along as we think we are.</p><p><strong>NR</strong>: We get influenced by the past, don’t we? If books from two years ago only have texts and influencing quotes by male people then it’s hard to find those things, we need to break out.</p><p>I feel like it was a really personal journey for you — you put in quite a lot of personal and professional anecdotes through the book. One example which put you even higher in my own personal estimation was that you once had to get toilet paper for Hans Rosling. I would have that on a T-shirt if that was me!</p><p><strong>BJ</strong>: I took a screenshot of the text! The stressful thing was I forgot my charger at home, so I had the message saying “Ben do you have the toilet paper for Hans?” and the battery on the screenshot is down to 2%! I literally ran to the drug store through the streets of Seattle with a roll of toilet paper and back to the conference so it was a high moment for me for sure, a great honour to be a part of that presentation.</p><p><strong>NR</strong>: I won’t put more spoilers on but that’s definitely something I’d recommend reading in the book right there!</p><p>It was one of those books that was such an easy read that I was able to go right through in the knowledge that there would be bits I wanted to go back and re-focus on, and in this case I wanted to go back to the bit about intuition again. That’s the bit I wanted to understand — intuition versus analysis. I think you were breaking new ground, offering a different opinion that said we are not replacing intuition with analysis, we need to use them side by side. Can you explain that a bit more?</p><p><strong>BJ</strong>: I feel strongly about this — I feel we do a disservice to data and analytics when we have this idea that somehow the data is going to tell us what to do. That’s overselling the value of data, it doesn’t just make the decisions for you, there’s a human in the loop. That’s a really important message especially for people who maybe are dataphobic — we’re not saying that data needs to replace you, your experience, your ideas of what should happen, your notion, your gut — those are not bad things. Those are things we need to incorporate into a multifaceted view along with data. Sometimes the data is going to tell you your intuition is dead wrong, that definitely happens. But sometimes the opposite happens, you just have the intuition that the data is wrong, something is not right, you can’t really describe what it is, you look into it further and, lo and behold, you do find out what it is describing is pretty much the opposite of reality because of one of the issues/possible errors arising.</p><p>Not just that, that intuition is going to tell you what’s wrong with data, that’s one part of it. The other part is telling you what to do next, where to go. What do we do now we know these facts? Maybe we need to look somewhere else, think about what this means in a different way? Even implying there is meaning there, assessing and assigning value to routes and goals, these are all human endeavours. They are intuitive in the sense they are not always fully thought out logically with a prescribed process, it might just be the sense we have.</p><p><strong>NR</strong>: “Sucker Punches?”</p><p><strong>BJ:</strong> Yes — like Jonas Salk, discoverer of polio vaccine: “Intuition told me where to look next” — data doesn’t always tell you that, it might raise a question you didn’t have, but maybe the next question is outside of the data. Maybe I need to talk to someone — these are all valuable parts of the process that allow us to steer a ship in the right direction (a company, family, city). Recognising that data is not replacing human intuition is something I think it’s really important to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qG5wgBbMUJXDs0qfVjMW5Q.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e06c67bf25c4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nightingale/avoiding-data-pitfalls-an-interview-with-ben-jones-e06c67bf25c4">‘Avoiding Data Pitfalls’ — an Interview With Ben Jones</a> was originally published in <a href="https://medium.com/nightingale">Nightingale</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Encode 2019 Roundup: Takeaways for Data Storytellers]]></title>
            <link>https://medium.com/nightingale/encode-2019-roundup-takeaways-for-data-storytellers-2fc0a1f5ea49?source=rss-170fe07b66d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fc0a1f5ea49</guid>
            <category><![CDATA[data-journalism]]></category>
            <category><![CDATA[data-humanism]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[information-design]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Neil Richards]]></dc:creator>
            <pubDate>Mon, 28 Oct 2019 10:31:02 GMT</pubDate>
            <atom:updated>2019-10-28T10:31:02.418Z</atom:updated>
            <content:encoded><![CDATA[<h3>Encode 2019: Our Round-up of Round-ups</h3><h4>A dispatch from the two-day conference exploring the future of data-driven stories</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5CaVB-nFAIxpn-sc5kwmdw.jpeg" /><figcaption>Encode Entrance (Photo: Jason Forrest)</figcaption></figure><p>Last month, the inaugural Encode conference took place in London. The conference focused on the pillars of design, education, and journalism within data visualisation. A preliminary day of hands-on workshops was followed by two full days of presentations and panel discussions. Set in the Oval Space between London’s up-and-coming areas of Shoreditch and Hackney, under the rare London September backdrop of intense, blue, cloudless sky, it was the new dataviz event on the block that everyone wanted to be part of. But how did it shape up?</p><p>Several members of the Data Visualization Society were there in attendance — condensing all of their thoughts and takeouts from a jam-packed conference was not easy, but here are just some of their thoughts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*isps4hadjTe5GsnYDPVckg.png" /><figcaption>Conditions of Entry (Photo: Marian Eerens)</figcaption></figure><h3><strong>James Smith</strong></h3><p>James is an analytics consultant for Biztory in London, a co-leader of the #sportsvizsundday initiative and also produces great sports visualisations at his <a href="https://www.sportschord.com/">Sportschord</a> website. James condensed his takeaways into four main areas:</p><p><strong>1. Drawing with data</strong></p><p>Inspired by the pre-conference workshop from Federica Cocco and John Burn-Murdoch, James commented that hand-drawn visualisations allow the focus to be on the data’s story, rather than the precision of the numbers. Both presenters demonstrated this point by drawing visualisations in front of the audience and we were able to watch the story unfold as the visualisation took shape. Pen and paper was also the inspiration behind Valentina d’Efilippo’s workshops, showing much more about the culture and geographic knowledge of participants than otherwise possible, and of course the process of inspirational visualisations from Miriam Quick and Stefanie Posavec. All in all, James felt that returning to pen and paper was a great resource not just for prototyping, but for finished visualisation projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*E1lT03HMrMD1JmLt1y5-dQ.png" /><figcaption><em>John Burn-Murdoch and Federica Cocco at FT Workshop (Photo: James Smith)</em></figcaption></figure><p><strong>2. Sonification</strong></p><p>Sonification was showcased in a number of presentations (the <em>New York Times</em>, <em>Financial Times,</em> and <em>Dataveyes</em>, to name a few) and referenced in Andy Kirk’s State of the Union 2019 presentation. We saw examples where sonification elements reflected the data points to powerful effect, and we saw more abstract elements of sound adding to data art installations, an important distinction. But the relatively new element of data sonification was one left ringing in James’s ears after the conference!</p><p><strong>3. Passion projects</strong></p><p>So many talks referenced real passion projects for the designers and studios behind them. It was impossible not to be inspired by such projects but important to understand the amount of work and hard graft on non–passion projects that each of the speakers had put in to get to that point. James referred to Malcom Gladwell’s “10,000 hours to mastery” rule and wondered if that would also apply in the field of data visualisation. But, let’s celebrate some of these amazing passion projects! Below is the Millennium Falcon, part of David Sheldon-Hicks’s presentation about his work in the film and video game industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*Mtv3uoWgl17wwMnOHA_sUw.png" /><figcaption>David Sheldon-Hicks (Photo: James Smith)</figcaption></figure><p><strong>4. Collaboration and diversity</strong></p><p>Diversity in the field of data visualisation was highlighted by Marie Segger’s inspirational talk — Marie not only highlighted the challenges posed to minority and underrepresented groups in the industry but provided her own calls to action. Diversity of projects, roles, and tools was also a highlight, though in the case of tools, this was noticeable only in its absence. Because tools weren’t discussed at length, the implication was wider, that the only constraints are in creativity, not tool use, with a call out especially to the work of Shadi El Hajj of Refraction Labs. <em>(Data Visualization Society welcomes users of all viz tools and loves to be tool agnostic for that very reason!)</em> Finally, there were many stellar examples of collaboration, including Stefanie Posavec and Miriam Quick, who showcased many of the projects where they have worked together, prompting James to call out for future collaboration work!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*A4bQC1cOVs4BHMd0Mc1StA.png" /><figcaption>Gas Tanks at the Oval Space (Photo: Jason Forrest)</figcaption></figure><h3><strong>Tom Worville</strong></h3><p>Tom is a senior data analyst with sports data firm Perform in London who also does bits with sports data providers Opta, and he summarised his recap with three takeaway thoughts of his own from the conference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*3lZwpbaHSHp-FqIfIN_pPQ.png" /><figcaption>Hand-drawn Sketch (Photo: Tom Worville)</figcaption></figure><p><strong>1. Sketching</strong></p><p>Like James, Tom featured the importance of hand-drawn sketching first of all, referring to it as the most powerful tool we all have access to. Tom’s take on this is that whatever your tool of choice, we all have access to the ability to sketch (it doesn’t matter how badly). If “writing is thinking” then “design is decision-making,” and we should be encouraged to sketch out our prototypes in the future</p><p><strong>2. Focus on the moments that matter</strong></p><p>This was a specific takeaway from Gert Franke, co-founder of Clever Franke. The moments that matter are the moments that matter to the people who are using your tools. First you must identify those people and their needs, and then consider the “moments that matter” to them. A great individual takeaway is, as Tom says (relevant to his field of expertise in football analysis): “What good is a product if, in a key a part of the decision-making process, it’s not providing the right information to coaches, analysts and directors of football?”</p><p><strong>3. Dataviz is getting more “informal”</strong></p><p>Tom considered this in his final takeaway, as well as the rise of sonification and “participation” — again citing Andy Kirk’s references. The move away from traditional bars and lines is bringing about a wealth of sound and physical-based visualisations. In addition, chart titles are getting much more informal. This can only help engage with users and help them understand what they are looking at, since we as users don’t want to look at “dry graphics with dull titles.” Tom’s takeaway was that the blend of data visualization and information design is a powerful one for telling memorable stories and he was inspired to leverage these trends to create more engaging content that we currently consume.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*mdJ6qYep7RxwGCO1Thpfhw.png" /><figcaption>Attendees awaiting the first presentation of the day. Photo: Jason Forrest</figcaption></figure><h3><strong>Neil Richards</strong></h3><p>My own background is as a Tableau Consultant at Groupon, a former Tableau Zen Master, a current Director of the Data Visualization Society, and a dataviz <a href="http://questionsindataviz.com/">blogger</a>; I made the trip down from Derbyshire in the UK. I went a lot more granular with my takeaways — coming up with 20 in all. You can check out the full list in the blog referenced below, but here are a few which differ from those mentioned so far:</p><p><strong>1. Keep a healthy backlog of ideas</strong></p><p>Inspired by Caitlin Ralph from the Pudding, it’s important to record ideas that you have into a personal “backlog,” however unusual they may seem at the time. We all face a shortage of ideas from time to time, and the ability to refer to a few ideas you had on a train journey 18 months ago might just be the creative spark needed to come up with a whole new project.</p><p><strong>2. Present each other’s work</strong></p><p>There were tips and tricks shared, particularly at the Education themed panel discussion, around running workshops for newcomers and students of data visualisation. Many great tips came from Valentina d’Efilippo, not least her suggestion of participants sketching their visualisations on A4 paper, and then positioning them within the larger A3 size, therefore allowing room for instructions and explanation. The favourite suggestion was that of presenting each other’s work — a simple suggestion (in theory) which focuses the designer on making sure that their work is understandable to the layman picking it up for the first time, and focuses the user on taking the time to understand the visualisation in front of them. Plus, any presentation experience is good experience. A win-win tip.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*vGVItu6tCvAp85wNgNGGqA.png" /><figcaption>Education Panel Discussion (Photo: Neil Richards)</figcaption></figure><p><strong>3. “Data is both a structure and a jumping-off point”</strong></p><p>This quote from Miriam Quick summarised the idea that you don’t just need to visualise and present your data in a formulaic way. You can structure, report and aggregate your data to the most functional or engaging visualisations, but that doesn’t have to be all. Miriam’s projects would often then take that data only as a starting point as we consider how then to represent it. Specifically, Miriam showcased her Sleep Songs project — a choral piece which used data from sleep patterns as its starting point. This has opened up the idea of further such “secondary” visualisation projects.</p><p><strong>4. “Be like the worst tabloid at the front and the Academy of Science in the back”</strong></p><p>A Hans Rosling quote which sums up a number of Neil’s sub-points around how to gain traction and visibility to your visualisations while ensuring their accuracy and validity. This underlies the difficulty faced by many, particularly women and those under-represented in the field. Also featured was the pre-conference talk from Rachel Ara and Julie Freeman (recorded here <a href="https://www.youtube.com/watch?v=e8jf9X3sMa8">https://www.youtube.com/watch?v=e8jf9X3sMa8</a>) — as talented data artists they have had to work so hard not just to promote their work but to be involved in almost every step of the process while holding down regular IT jobs because financial support is just not available. We all need to understand how to get the right balance between publicity/engagement and rigorous visualisations, but we also need to ensure that the opportunity to do so is equally open to all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*iopxA6P6RbTi6RKuJsVuYg.png" /><figcaption>Marie Segger — The Economist (Photo: Neil Richards)</figcaption></figure><h3><strong>Marian Eerens</strong></h3><p>Marian joined us from near Antwerp in Belgium where she is an operations and intelligence leader at her current role with SUEZ Water as well as a co-leader of the Belgium Tableau User Group. She shared her thoughts with us after the event too — again with three great takeaways:</p><p><strong>1. Don’t think you have to be better than anyone else</strong></p><p><strong>2. Happiness promotes curiosity and an explorative mindset so make sure you have plenty</strong></p><p><strong>3. Work on projects you are passionate about, they are your ambassadors</strong></p><p>In Marian’s words: “I wasn’t sure what to expect when I got my tickets for encode. Considering I see myself as a ‘novice’ practitioner still and come from a very different background then most attendees (yes — I let my imposter syndrome get the better of me); I had this idea I would spend two days being inspired and leave with some new ideas but I left with so much more than that. For me encode was/is all about the people.</p><p>“I had so many great conversations with folks that were really open about sharing their knowledge and experiences, and got to meet a few people I have been admiring from afar and would never have connected with outside of the conference; so I’m very grateful for that. Being around that much creativity has been incredibly exhilarating and I couldn’t possible summarize all the great content in a single paragraph.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*IM-UDBJSQkS7E5LZfaSEAg.png" /><figcaption>“Encode was all about the people.” (Photo: Jason Forrest)</figcaption></figure><h3><strong>Mollie Pettit</strong></h3><p>Mollie joined us all the way from San Francisco where she is a senior data analyst with Netflix. She was the co-organiser of the recent <a href="http://visfest.com/unconf2019/">visfest unconf</a> in Chicago and is Data Visualization Society’s Events Director (formerly Knowledge Director). She doesn’t have a blog write-up but has the most thorough review of all under the #encode19 twitter hashtag — see photos and a summary of every talk and every major project included within. Here are just a few which cover elements not mentioned in this round-up yet:</p><p><strong>1. The emotionally powerful and philanthropic work of Beyond Words Studio</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*lYXPwRJxqI4QuOdpSLPMCQ.png" /><figcaption>Rebecca Conroy — Beyond Words (Photos: Mollie Pettit)</figcaption></figure><p><strong>2. The Power of collaboration to enable ideation and brainstorming ideas, focusing on quantity over quality (from Stefanie Posavec and Miriam Quick) — expressed in inimitable fashion!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*3cz8YR4rHqxXWY0ri9iKJw.png" /><figcaption>Sucking it Up! (Photo: Mollie Pettit)</figcaption></figure><p><strong>3. The blurring of lines between reality and abstract result in surreal and captivating works of data-inspired art, as demonstrated by Quayola</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*QIR84Q3fHjiCeh5fR9xCrg.png" /><figcaption>Work from Quayola (Photos: Mollie Pettit)</figcaption></figure><p><strong>4. The evolution of projects from Clever Franke studios (from Gert Franke’s talk) resulting in an upcoming Cirque du Data project featuring smartphone orchestras and data magicians, no less:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*KBqeYT9VymuFs8F6GS4Mhg.png" /><figcaption>Photos: Mollie Pettit</figcaption></figure><p><strong>5. And returning to data journalism, Krystina Shveda spoke about the connection between data literacy in journalism and public trust, pointing to how too often journalism amounts to repeating someone else’s claims rather than digging into the data oneself to check.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*1FWHHjtl8A0PepV-zbMjXQ.png" /><figcaption>Krystina Shveda (Photos: Mollie Pettit)</figcaption></figure><p>The recordings for all talks and sessions are due to be out shortly, and we’ll be sure to post details. Want to see more?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*KA8ZE5LWMdKMjiCPUSWi9g.png" /><figcaption>Outside Venue Street Art (Photo: Marian Eerens)</figcaption></figure><p><strong>Check out these reviews in full from our members:</strong></p><p>Neil Richards <a href="https://questionsindataviz.com/2019/09/22/what-did-i-learn-from-encode-2019/">https://questionsindataviz.com/2019/09/22/what-did-i-learn-from-encode-2019/</a></p><p>James Smith <a href="https://www.sportschord.com/post/decoding-encode-2019">https://www.sportschord.com/post/decoding-encode-2019</a></p><p>Tom Worville <a href="https://worville.github.io/jekyll/update/2019/10/04/What-I-decoded-from-Encode-(a-data-visualisation-conference).html">https://worville.github.io/jekyll/update/2019/10/04/What-I-decoded-from-Encode-(a-data-visualisation-conference).html</a></p><p>Molly Pettit <a href="https://twitter.com/search?q=%40mollzmp%20%23Encode19&amp;f=live">https://twitter.com/search?q=%40mollzmp%20%23Encode19&amp;f=live</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ark2VGHhBACwM0lQ8DPzng.png" /><figcaption>A shout-out from Andy Kirk for Data Visualization Society (Photo: Neil Rihcards)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qG5wgBbMUJXDs0qfVjMW5Q.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fc0a1f5ea49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nightingale/encode-2019-roundup-takeaways-for-data-storytellers-2fc0a1f5ea49">Encode 2019 Roundup: Takeaways for Data Storytellers</a> was originally published in <a href="https://medium.com/nightingale">Nightingale</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we’re all Slackers in Data Visualization Society]]></title>
            <link>https://medium.com/nightingale/why-were-all-slackers-in-data-visualization-society-bd9fea795214?source=rss-170fe07b66d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd9fea795214</guid>
            <category><![CDATA[data-visualisation]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[otto-and-marie-neurath]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Neil Richards]]></dc:creator>
            <pubDate>Fri, 17 May 2019 16:37:43 GMT</pubDate>
            <atom:updated>2019-05-17T16:37:43.135Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why We’re all Slackers in Data Visualization Society</h3><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*MNQIGkQzDy9T2nWTkc1xTQ.png" /></figure><p>Since the Data Visualization Society (DVS) was founded, its membership has grown far more quickly than could have been anticipated. Within just a few months, the membership had grown to over 5600+ members and the numbers continue to rise.</p><p>We quickly needed an open communication platform, and before long the decision was made to go with Slack. In order to join the <a href="https://www.datavisualizationsociety.com/">Data Visualization Society</a>, opt into joining Slack and before long you will receive an email invite to join. Slack is one of those platforms that is growing ever more ubiquitous, which in itself is a pretty good reason to adopt it. But we know that there will be people who are not big fans, as well as plenty of people who are unfamiliar with it.</p><p>As for me — I’m no expert at using Slack, but I had no qualms using a platform that so many people were familiar with.</p><p>So why are we using Slack, and what works well?</p><h4><strong>(1)</strong> <strong>There’s no hierarchy</strong></h4><p>Love or hate twitter, it’s all about the followers: who is a perceived leader, or bigger and better person, because they have more followers? Who’s achieved enough notoriety that they have an infamous blue tick of verification? Who’s on the latest list of 50 biggest influencers in data viz?</p><p>In Slack, there’s none of that. Everyone enters as just a person. All channels are open to everyone, and all users have the same privileges. You may see a reply on a post from a user named “Alberto” who turns out to be Alberto Cairo, but it’s a voice that is no more amplified than anyone else. It’s a refreshing reboot, and it’s a great feature.</p><h4><strong>(2)</strong> <strong>There are so many different channels</strong></h4><p>The different number of channels allows you to pick and choose, with every individual channel giving more focus to different themes. Maybe you’re just interested in what’s coming up in New York City, or Europe? Join <strong>#location-nyc </strong>or <strong>#location-europe</strong>. Particularly interested in historical data visualisation, or looking for advice on accessibility? Join <strong>#topic-historical-viz </strong>or <strong>#topic-accessibility</strong>. You get the idea.</p><p>But the great thing about so many subdivisions is that after deciding where you want to join, you may find some you wouldn’t have thought about before. I wouldn’t initially have thought of joining <strong>#topic-historical-viz </strong>myself, but have found some fascinating work of pioneers through the ages that I wouldn’t have otherwise known about. This example from Otto Neurath isn’t to everyone’s taste but I love it, and would not have found it had I not stumbled across a conversation that piqued my interest in the aforementioned channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*cCZ5mJVT7ns3h3vG" /><figcaption>Bold, geographic, clear explanation and full of iconography of the time — a striking pre-war visualisation by <a href="https://en.wikipedia.org/wiki/Otto_Neurath">Otto Neurath</a></figcaption></figure><p>The full list of Slack channels is <a href="https://github.com/data-visualization-society/Welcome/blob/master/slackChannels.md">right here</a> — there are no limits to the number you can sign up to. Pick some favourites, then pick something new, you don’t know what you might find!</p><h4><strong>(3)</strong> <strong>It’s tool-agnostic</strong></h4><p>OK, this isn’t a feature of Slack as such, but it is a feature of how we have decided to set up the platform. In setting up so many individual channels, it’s clear that there aren’t any channels for individual tools. This is one thing I love about DVS. Now I’m a Tableau person through and through but I already know where to turn for all things Tableau — that’s not what I look for within DVS. Being non-tool-specific allows the focus to move away from the “how” and into the process, practice or output. I like that, and it also feels like it makes everything more accessible</p><h4><strong>(4)</strong> <strong>It’s friendly</strong></h4><p>Slack strikes me as none too serious. A friend and fellow user told me that I better know my emojis and it’s not hard to see why! This particular middle-aged Brit has only just figured out how to do a smiley face with punctuation marks. :-) But although it’s not all about that, the overall tone of the interface and interactions gives the impression of a friendly space.</p><h4><strong>(5)</strong> <strong>It’s full of surprises</strong></h4><p>We’ve found that due to the large user base it’s been important to maintain the slack channels to keep conversations in threads. This is a nice idea which has allowed for areas to be uncluttered despite the conversations going on. But it’s not always easy to spot an innocent post/question which has 57 replies that can lead you into a long chain of discussion, example, (friendly) argument and counter-example. Some of the best advice and visualization examples I’ve witnessed so far have been in such threads.</p><p>Now we know that Slack isn’t everyone’s preferred tool. And even if you don’t have major objections to it, you might think that it’s somewhat overwhelming and yet another thing to have to feel you want to keep on top of: why should you bother?</p><p>In reality though, the Data Visualisation Society is not all about its Slack channels, which just so happens to be its first and most visible tangible output. It’s a resource that might not be perfect but it’s proving to be valuable for more and more members. For everything else the DVS is doing and has planned, check out <a href="http://datavisualisationsociety.com/">datavisualisationsociety.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd9fea795214" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nightingale/why-were-all-slackers-in-data-visualization-society-bd9fea795214">Why we’re all Slackers in Data Visualization Society</a> was originally published in <a href="https://medium.com/nightingale">Nightingale</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>