Showing posts with label Fun. Show all posts
Showing posts with label Fun. Show all posts

Thursday, May 7, 2015

storytelling with data...scribed!

I was in Dallas earlier this week and had the opportunity to talk about storytelling with data with a few different groups. One of those was the DFW Data Visualization and Infographics Meetup. This afforded me the pleasure of meeting Randy Krum, president and founder of InfoNewt, and John Colaruotolo from Collective Next, who (as far as I'm concerned) is able to create magic with pens and a whiteboard. Here is the latter's creation, which he completed during my talk:
Download full-sized here.

My experience with meetups is that people tend to flee pretty quickly after the presentation and Q&A. This isn't surprising - in most cases, people have shown up after a full day of work and are understandably anxious to point themselves towards home when the 9PM hour strikes. 

But this meetup was different. After my talk, people congregated around John's whiteboard creation in awe. Taking it in was like reliving parts of the presentation they'd just experienced, but with a slightly different twist. For me, it was fascinating to see a visual replay of what I'd just said: seen and heard through someone else's eyes and ears.

I overheard one person describing this as a superpower. As in, "yes, John has a super power that many of us do not have." I thought this was an interesting perspective. And very cool - when you consider that probably most people you encounter have some sort of superpower that you do not personally possess. John's superpower was palpable. Or at least, I stood in awe. He was...

listening...

intepreting...

drawing...

ALL AT THE SAME TIME. 

Crazy. Brilliant. Beautiful.

That's all I have to say.

Well - not quite all. Big thanks to Randy (@rtkrum) for hosting a great event and to John (@johncolaruotolo, www.collectivenext.com) for capturing it on a (beautiful) whiteboard!

Friday, October 31, 2014

annotated line graph from Uber

With the email that hit my inbox earlier this afternoon, Uber has impressed me twice in the past week. The first time was in response to a simple comment that accompanied my '3' numerical rating (the lowest I've ever given): "With the world series game today, should have avoided stadium area." I had an email in my inbox from Uber's customer service within the hour agreeing that was a silly route given the Giants' game and reducing the price to what it would have been without the crazy traffic. Amazing.

And now they've done it again, this time via effective data viz. The annotated line graph below shows expected Uber demand over the course of the evening and into the wee hours of morning. This is one of those rare cases where they can get away without showing the y-axis values at all, since the relative peaks and valleys are more interesting (and meaningful) than the absolute numbers.


Nice job Uber. Though I must say this makes me happy to report that kiddie Halloween in my neighborhood is on foot, so no need to even think about surge-pricing here!

Speaking of which, I find it impossible to publish a post on Halloween without couple pics of my superhero family.


Happy Halloween!

Thursday, May 8, 2014

calling all Bay Area data viz gurus

Facebook recently announced their 2nd bi-annual Viz Cup, bringing together the finest Bay Area vizzers for a night of competition and fun! I'm excited and honored to be one of the judges at the event, which will take place the evening of May 20th at Facebook headquarters in Palo Alto, CA.

Click here for additional info and to RSVP.

If you're interested in what I'll be looking for when it comes to effective data viz, check out this post, recapping the last event. I hope to see you there!

Tuesday, January 14, 2014

things change when you have children

I just watched a video of a short chat between Nancy Duarte and Garr Reynolds about creativity and story. In it, Garr talks briefly about how having children has influenced his view and approach: "Things change when you have children."



Yes, they do.

And will continue to for me, as my husband and I are excitedly expecting baby #2 this summer!

(When you've got one who is this cute, how can you help but do it again?!?)


Wednesday, August 22, 2012

how long it takes to get pregnant

I love when data viz and life intersect. This happened for me recently, when I came across the following visualization - it's from a post a couple of months ago on flowing data.

How Long it Takes to Get Pregnant
Slightly modified from this post
The graph shows the odds of getting pregnant (y-axis) by the number of months one (or two as would typically be the case here) tries to get pregnant. The different colored markers denote the age (I assume of the female) trying to conceive. This shows that 25 year olds will nearly always get pregnant within a year of trying to conceive, and that this probability decreases the older you are.

How does this intersect life, you may ask? I had one empirical data point to add to the graph, denoted by the * at the (x, y) coordinate (5 months, 100%). Colored correctly, it would be somewhere between yellow and green.

For anyone who is still scratching their head to figure out what I'm talking about... 
I'm due in February!

Wednesday, June 6, 2012

visualizing everyday life

The data visualization in my life is primarily in the business-world. At my day job: how do we ensure that people decisions at Google are data-driven? In my presentations and workshops: who is our audience, what do they need to know, and how do we craft a visual and story to do that?

But many take data visualization into the personal sphere as well: using visualization to better understand aspects of their world or their life. I encountered one such example recently, when a data viz course participant at Google shared an example he created:

"Hi all,  Here is silly little thing I cooked up over the weekend. My wife likes fresh tomatoes, of what are called heirloom varieties (not the big commercial ones) - 16 different ones each year in our garden. We used to have trouble selecting which ones to grow each time, for the last 4 years have kept pretty good records of them, so I wanted to see if there were any patterns.

This is my first such chart after taking the basic data viz class, where I had a chance to sit and think about how to make it look. I did violate the color palate guidelines a bit, to color code each tomato by type. But this makes the type of tomato stand out, as well as the pattern."

Neil goes on to say, "Interestingly enough, until I graphed it, I didn't know that we rarely have a yellow tomato invited back a second year. Our by year lists (stored on a wiki at home) tended to mask that information." I love the use of data viz for this sort of problem solving: what type of tomatoes should I plant this year? I think Neil's next challenge will be to identify and start recording and visualizing some success measures (e.g. plant yield, flavor) to really hone his future garden crops.

This reminded me of another food-related data viz I saw some time ago, where a woman had tracked everything she ate for a year, then created a number of visualizations based on the data. You can read about that and see the visuals in this Flowing Data post.

Food for thought (no pun intended!): what do you (or could you) visualize in your life?

Tuesday, May 1, 2012

I like camembert, but I don't like pie charts

Earlier today, while reading a brief NYT article on William Playfair and the genesis of pie charts (link), I learned a fun new fact: in France, pie charts are referred to as le camembert.

I suppose it's not so strange that the hard-to-read visual we named after a sweet circle dessert in English is described by a savory dessert in France. But I still find this wildly amusing (yes, I am a dork; I take no shame in that). So much so, in fact, that I almost didn't believe it at first. But a quick minute in Google Translate confirmed it for me:


Alas, if only pie charts were as effective of a visual as pies or cheese are as tasty desserts. (personal diatribe)

Thursday, April 26, 2012

the color forecast

OK, so far I've been more impressed by this than anyone I've told about it, but I am not going to let that stop me from blogging about it: the color forecast.

What is the color forecast, you might ask? The Pimkie clothing company has installed cameras in Paris, Milan, and Antwerp that record each passersby's clothing, magically extracting the colors and posting them to their website. Not only that, but they provide visualizations that you can use to explore the colors of the day, week, and month. So perhaps forecast is a bit of a misnomer, since we're mostly looking backwards, but let's look past that and explore some of the data.

Here's what clothing colors have looked like recently in Milan:




Normally, I would be offended at a chart that combined as many colors as the ones above (or even a fraction of them). But that doesn't apply when what is being visualized is the color mix itself. Apparently, periwinkle is in right now in Milan. Who knew? Answer: Pimkie, and they are going to use this knowledge to try to get you to buy periwinkle colored clothing:


I still love it.

Wednesday, March 7, 2012

birthday data viz

I celebrated my birthday last weekend. Those who know me are familiar with a few of my passions: good wine, good food, and good data viz. The first two were enjoyed during a wonderfully relaxing weekend trip to Calistoga. It turns out that my team at work had the latter covered. Today at our team meeting, they presented me with the following:

The birthday card: note the effective use of preattentive attributes.
A laminated poster: they know me well. :-)
A big thanks to my amazing team for the creative birthday wishes!

3/12 update: turns out my current team doesn't have a monopoly on the data viz card business. I received the following card from a friend - as he points out, amusing due to my "love" of pie charts.

Friday, December 16, 2011

the cost of christmas

Each year around this time, the US financial institution PNC produces the "Christmas Price Index," in which they calculate the cost of Christmas based on the items in the 12 Days of Christmas carol. I guess it's a sort of merrier (at least in theme) version of the Consumer Price Index and is meant to provide some economic insight into how the price of goods changes from year to year.

This year, they've layered on an interactive layer of glitz: the Christmas Price Index Express. Fast Company describes it as "A game-enhanced site with a handmade feel, the Index Express appears as a magical train that carries visitors through an alpine world to collect each of the 12 gifts. But it's essentially an elaborate interactive infographic, where the data points come to life with animation and sound." (Fast Company article) Whatever it is, it takes forever to load and I wasn't patient enough to spend time on the Index Express (where there are literally bells and whistles), rather, I clicked through the site long enough to find what I really wanted to get my hands on: the underlying data.

PNC certainly didn't make the data easy to extract. After painstakingly copying and pasting data from each of the 13 pages (total cost of Christmas plus one page for each day of Christmas) and reformatting to get a dataset I could do something with, I had myself an Excel spreadsheet with 28 years of 12 days of Christmas cost. Next challenge: visualize it and see what gems of wisdom we can acquire.

Often, there is much to be learned by looking at how not to visualize data. So before we get to how I'd visualize the cost of Christmas, let's look at a few less-than-optimal visualizations of this data and discuss their limitations.

First, the stacked bar chart. I often see data like this (multiple series over time) displayed this way. Unfortunately, this usually isn't a great approach. Stacked bar charts are tricky, because once you get past the first series, there is no longer a consistent baseline to compare the other series. Here's what it looks like with this data:

In the above, we can see how the total price of Christmas has changed over time and also see what the major contributors to the total price are. But if I want to understand how the different components have changed over time, that's tough with this visual. Are all goods changing in the same way, or are some getting more expensive while others have become cheaper? It's really difficult to tell with this graph.

So what if we unstack the bars so that we do have a consistent baseline for each series. Here's what we get:



This clearly doesn't work here - there's way too much going on. But even with fewer series (picture just the first 5, for example), this format is hard to read. It puts a lot of onus on the audience to spend time staring at it and looking for interesting things to pull out. That's too much work, when we can make the interesting things more obvious so our audience doesn't have to search for them.

Let's see what this data looks like in a line chart:



This is getting better, but still may not be optimal. There are a lot of overlapping lines, especially at the bottom where a number of series have similar values. But the biggest drawback is that we don't get a good sense of how the total cost of Christmas has changed over time with this graph, which is kind of the meta point of the data and is probably interesting.

While we're on the topic of non-ideal graphs for this data, I can also picture some sort of horrible visualization with pie charts: one for each year showing the breakdown of Christmas items, perhaps even with the size of the pie scaled by the total cost of Christmas. This would take some time to build, so I'm not going to go through the effort, particularly given that pie charts are my enemy. Rather, I'll simply say: don't do this! Why? Check out this blog post for some background.

We've looked at some less than stellar graphical representations of this data; now let's turn our attention to something that I think might work a little better.

In any visualization exercise, one of the first things to do is determine what question(s) you want to answer. This will drive how you show the data: the goal is to show it in a way that makes it clear what questions you set out to answer and answers them in a straightforward manner. The problem is that this step is often skipped, resulting in graphs like the ones above. When you don't isolate what question(s) you want to answer and try to create a visual that will answer any question, you run the risk of not answering any single question very well.

With this data, I'm going to choose to answer a couple of questions: how has the price of Christmas changed over time? (both in aggregate and for the various items) and what proportion does each day contribute to the total cost of Christmas? The trick I'll employ to do this in a way that isn't overwhelming is to create a visual with multiple graphs (and words!) so we can answer these questions one at a time. Said in another way, I'm going to use my visual to tell a story with this data. Here's what it looks like:


The top left graph shows how the cost of Christmas has changed over time. The top right graph shows the 2011 cost breakdown per item so we can understand the contributors to the total cost. Finally, the mini-graphs at the bottom help us understand the drivers behind the total changes we see in the top left graph. I've put on my analyst hat and added some words to describe what I believe are the main takeaways that my audience shouldn't miss.

The bottom line: Christmas is getting more expensive. If you have a tight budget for your holiday party, for entertainment you may consider replacing your leaping lords and dancing ladies with milk maids and for decor swap your swans for hens to save a considerable amount of money!

In case you're interested, my full Excel spreadsheet with data and graphs can be found here.

Friday, July 29, 2011

porn & cake

Get your attention?

The following data cake pic was posted over at Chart Porn a couple of weeks ago (originally from Epic. graphic). I couldn't help but share.


While all are important, one might guess that my favorite step is presentation (yes, I like to make things pretty, cakes included). But that's not the case. My favorite is the final step to knowledge: information is worthless if we don't learn something and act on (eat!) it.

Friday, July 22, 2011

vacation stress: visualized

Love this. Reminds me of the clever Facebook breakup visualization that David McCandless did last year. Though my personal sample size (1) is small, this is an accurate reflection based on my empirical evidence...

Sunday, March 6, 2011

think brilliant infographic

Infographics are increasingly prevalent in the media and elsewhere. At a high level, the goal of the information-graphic is to show information across various dimensions of a single topic or related topics in a way that is easier to digest than words alone would be.

The combination of art and data often yields an attention-grabbing visual. While almost always visually appealing, one point of struggle is that they are not always as easy to read as one might hope. Sexiness in many cases is valued over clarity of information.

A recent post on thinkbrilliant.com uses the infographic itself to highlight some of these issues:

View original image.

The descriptions get increasingly amusing as you move down the page. My favorite snippet is the text that accompanies the pie chart: this is the same graph only in pie shape form. this was done to overemphasize a very simple point but now you think it's really important.

When it comes to the visualizations shown on this satire - two words of advice: avoid them!

Tuesday, December 14, 2010

label your axes

The following comic from xfcd has been making its way around the data visualization blogs and I couldn't help but repost it here.


The lesson is a good one: every axis should have a label - no exceptions! (Ok, one exception: if the values are January, February, March, ..., you probably don't need to label the axis "months", but anything less explicit than that simply must be labeled!)

The lack of a label, even if you think it's obvious from context, leaves space for your audience to question what they are looking at. If you state it explicitly with an axis label, rather than spend their brainpower trying to figure out what the axis represents, your audience can spend that power on actually understanding the information that is being presented in the graph. Wouldn't you rather that be the case?