Measure the Internet, Map the Internet
By Ken Hilburn
January 28, 2008
Find more about:
infographics
infovis
interface
map
visualization
One area we’ve been paying particular attention to recently has been the internet traffic for different web site categories. Our friends over at comScore Inc. collect a wealth of information for “measurement of the myriad ways in which the Internet is used and the wide variety of activities that are occurring online.” Nice alliteration, guys.
Using some of the data they’ve allowed us to share with you, we had the bright idea to stuff it into our most favoritest charting type, the treemap. And what’s better than a chart? Answer: an interactive chart with a toggle button.
You’ll need to know a few things to really Juice the data:
- The map is based on unique visitors by site for August 2007 and November 2007.
- Red means a decrease in unique visitors over that three month time period and green means an increase. Black means there is no change.
- You can click on the category headers to zoom into each category. Click on the category header again to zoom back out.
- We provide two views of the data: the default shows just the top ten sites in each category. However, for nearly all categories, sites outside the top 10 account for over 50% of the visitation in the category (the exceptions were Search, Portals, and Auctions where the top players dominate traffic). A checkbox adds “All Others” and gives you a better sense of the size of each category. You can toggle these two views using the checkbox just below the map.
- Due to some confidentiality restrictions that we’re under regarding the raw data, we couldn’t show other metrics that would really make this visualization sing—but I bet if you contacted comScore, they’d be glad to discuss with you.
- A few tech notes. The treemap is adapted from Josh Tynjala’s capable open-source Flex Treemap component. Site images are provided by Amazon.com’s Alexa site thumbnail service.
So, without further ado, take a gander at our latest liberated data:
There’s so much information here, you won’t have any trouble drawing your own conclusions, but here are a few conversation starters:
- Notice that there was a distinct increase in retail web visitors leading up to the holiday seasons.
- Surprise! eBay owns auctions
- Not too good of a showing for those online gambling sites; travel either.
- Sports traffic is up… but not for the MLB.com site. Oh yeah, baseball season is over.
Enjoy.
Disclosure: comScore is a client of Juice Inc.
New Year’s Resolution: Tufte and the iPhone
By Chris Gemignani
January 24, 2008
Find more about:
interface
sparklines
tufte
visualization
Edward Tufte has produced a illuminating video tour of the user interface of the iPhone. The video illustrates Tufte’s struggles to come to grips with the difference between dynamic screen resolution and the resolution of printed paper. Tufte is prone to grandiose pronouncements, like this one:
All history of improvements in human communication is written in terms of improvements in resolution: to produce, for viewers of evidence, more bits per unit time, and more bits per unit area. Slideware is contrary to that history. Trading in reductions in resolution for user convenience or for pitching may be useful in mass market products or in commercial art, but not for technical communications. The solution is not to rescue slideware design; the solution is to use a different, better, and content-driven presentation method. On this solution, see our thread PowerPoint Does Rocket Science—and Better Techniques for Technical Reports — Tufte Nov 10 2006
Somehow, I don’t think the importance of the Gutenberg Bible related to it showing “more bits per unit area.” Quick, count the “bits per unit area.”


It didn’t take bits per unit area to revolutionize communication in the past and it won’t in the future either. The iPhone is a tremendously engaging information device and points the way forward for information displays. Here’s what the iPhone does well:
Maximize screen real estate: Controls are only visible when needed, fading away gently when you are concentrating on content. Tufte furiously neologizes, calling this “computer information debris.” Control junk is more apt, more terse, more Tuftian.
Direct manipulation: As Tufte says: information is the interface. Filtering and choosing should take place in the context of direct manipulation. A good essay on the possibilities of direct manipulation can be found here.
Fun: Above all, information can be fun and engaging to navigate. Tufte condemns Apple’s stock ticker for having “cartoony” and PowerPoint-like displays and offers an improved version (with 5 digits of precision). Apple’s cheery display offers a more entertaining, usable interface for day-to-day usage.
With our empathy for the day-to-day troubles of the business person seeking insight in data, it’s frustrating listening to Tufte. He is clearly an academic, with academic interests and academic timeframes. As much as his work is respected and inspirational within business circles, he makes little effort to enable his message to be implemented.
Good Tufte: Clutter and overload are not an attribute of information, they are failures of design. If the information is in chaos, don’t start throwing out information, instead fix the design.
Bad Tufte: “…the conclusion of sparkline analysis in Beautiful Evidence, where the idea is to make our data graphics at least operate at the resolution of good typography (say 2400 dpi).” http://www.edwardtufte.com/bboard/q-and-a-fetch-msg?msgid=0002NC&topicid=1 *Ed: At least 2400 dpi? Orly?
Mostly right Tufte: “Thus the iPhone got it mostly right.”
Mostly wrong Tufte: “Adobe Illustrator is a big serious program that can do almost anything on the visual field (other than Photoshop an image). Most of my sparkline work was done in Illustrator. Fortunately all graphic designers and graphic design students have the program and know how to use it, so find a colleague who knows about graphic design.” http://www.edwardtufte.com/bboard/q-and-a-fetch-msg?msgid=0000Jr&topicid=1&topic=Ask%20E%2eT%2e
It is heartening to see Tufte engage and connect his mental frameworks to our modern, screen-oriented, graphics-accelerated, not graphics-designed world. But the future of information design and interaction belongs to the iPhone, not the printed page.
3 comments
ross said:
Nice post, thanks for making it, I found in interesting and I think it's good that people are prepared to quest Tufte, who seems to have rightly or wrongly some God like stature.
For my part, I have used TyTN's series since mark 1 and these, running windows mobile, have had all of the features (more or less) of the iPhone for some time. Compromise in the key with small devices. - Untill we get screen that can project into air! :-)
Cheers
Ross
mahalie said:
It's always folly to never question anything someone says just because you have a lot of respect for their ideas generally. Yet I see many bloggers flame well-respected experts...probably as traffic bait. So great to hear a voice of reason. Thanks!
darrell said:
"To clarify add Detail" - as an example, Tufte adds a satellite weather pattern to augment a weather forecast of X degrees and Partly Cloudy. How does that clarify? You need expertise to interpret it, and it didn't offer analysis / interpretation just raw data (satellite view).
I understand his point if you're presenting to a panel of experts. But the iPhone is sold to consumers, not weather forecasters.
Few of us are weather forecasting expertise (beyond idle speculation). Using the satellite video, a non-expert could probably guess, the degree of cloudy, and perhaps the direction of the wind. Other useful info like wind speeds, wind chill factor, probability of precipitation and temperature are not aided by the satellite visual.
Eye candy; yes. Useful; only to a limited expert audience, and only with additional information not displayed.
"To Clarify; first consider the audience, then add relevant detail."
Add a comment
Beauty in the Details
By Zach Gemignani
June 18, 2007
Find more about:
infovis
interface
The design process is about whittling away distractions, making the obscure feel obvious, making the obvious feel implicit, and doing it without anyone noticing. To the untrained eye, your best work looks like you’ve done no work at all. If you’ve done a stellar job, then your design will feel utterly obvious. —Neil Mix from Paradox of Elegance blog post.
Neil goes on to say that "it’s easier to see the flaws than it is to see the elegance." That may be true, but a careful look at the best interfaces reveals the little and beautiful elements that make all the difference. These small features might not determine whether someone uses a piece of software, but they will determine if the user enjoys their stay:
Designer Bret Victor, who we first wrote about here, has developed a desktop widget for the SF-area train schedules. He allows users to change their query right in the description of an object—notice the red text.

While we are fawning over Bret's handiwork, here's another cool feature he built into his Click-Shirt site for customized design of t-shirts. This bar at the bottom of the screen tracks the history of changes as the user designs a shirt. Each time I make an edit, I get a visual breadcrumb trail to easily see my history and backtrack.

Google Finance stock charts have a nifty little device that lets you change the time range you are looking at. You can change both the size and the start of the time window using one adjustable object. Not to mention the embedded alert markers.

Some elegant touches are more subtle. Check out the search toolbar in Firefox. When I start typing, it fills out search terms both from my history (above the line) and from common searches (below the line).

The Safari browser for Windows offers a new approach for finding words in a web page. The browser greys the screen and highlights the target word. And you can to tab through the various instances of the word with the orange highlighting.

And while we are on the subject of Apple: sometimes the difference between clunky and good is simply about the quality of the images. A while back I wrote a break-up letter to PowerPoint—one reason was that the Mac-alternative called Keynote does a much job with the look of default charts. The chart on the right feels more professional, in part due to the anti-aliasing of the image. (Joel on Software has an interesting post about anti-aliased fonts here.)

Finally an infographic from the New York Times called the Sector Snapshot. The beauty of this presentation of information is in the careful use of contrast and skill at keeping the focus on the numbers.

1 comment
derek said:
You're dead right about anti-aliasing, although with Excel for Windows my beef is not with the fonts themselves, which are fine enough to suit me, but with the graph symbols, which are embarrassingly childish-looking at any serious resolution. I have resorted to using data labels in Wingdings fonts, centred over a data series formatted so that its symbols are invisible, and this is sometimes acceptable. Though sadly not always, due to the tendency of text and drawing objects to drift away from their appointed positions when printed, exported, or resized.
If they could fix that problem, I would strongly suggest a modern graphics program should make use of font technology for its symbol set, with specialist fonts making hundreds of different symbols available to the chart maker instead of the WinExcel traditional circles, squares and diamonds etc.
Add a comment
The Google Analytics relaunch
By Chris Gemignani
May 9, 2007
Find more about:
analytics
bi
innovation
interface
tools
Google Analytics has been rebuilt and the result redefines the frontiers of doing analytics on the web. Avinash Kaushik has the definitive early review.
I had the privilege of attending the launch and playing with the early release. Here are a few things I noticed.
- Speak my language: Google has put a lot of effort into replacing specialized terms with everyday ones. This makes the application usable by a broad base of people and is one way to fight GUI Jock-itis.
- Speed kills: The interface is easily reconfigurable and fast. I've long argued that interface speed is a substitute for configuration options. I'm curious to play with the tool and get a better sense if this is true.
- Flex rules: Much of the componentry for viewing data in Google Analytics is built in Adobe Flex. This is similar to Google Finance, and not at all like GMail or Google Reader, which use the GWT. We believe this has profound implications for analytical tools on the web and will dig into this in later posts.
2 comments
FM said:
Nice and must say timely review, I've been using Analytics.google.com and found it good, some time.
some time it's not an average site owner would like to look at, i mean you may lost your way through it.
Talking about Speed, it's been major sat back, till the day. however if it's improved in relaunch, it's great.
Lynn Cherny said:
I had lunch with a friend recently who told me that the Mindmaps fellow who built the new Google Analytics was just more used to Flex. So it may not be sinister or deep, although I agree with you on the overall benefits of the feel and design :-)
Add a comment
Dashboard Storytelling
By Zach Gemignani
May 7, 2007
Find more about:
dashboard
infovis
interface
reporting
visualization

Everyone wants a dashboard and the promise of a world in which the intricacies of your business are clearly laid out on a single page. Dashboards can make running your business as easy as driving a car, where slight adjustments and careful attention to warnings mean smooth sailing on the road to success.
I'm not so convinced. For someone who is, check out the mysterious Dashboard Spy. He/she has a massive collection of dashboard screenshots and describes these precious morsels as "simple to understand and impressive to look at, these scorecards are becoming 'must-haves' for all enterprises."
If we already live in a dashboard-centric world, we might as well do them right. I see at least three areas where dashboards need improvement: depth, information display, and storytelling.
Depth. Stephen Few makes a worthwhile distinction between dashboards and something he calls "faceted analytical displays" (FADs):
- A dashboard is a visual display of the most important information needed to achieve one or more objectives; consolidated and arranged on a single screen so the information can be monitored at a glance.
- A faceted analytical display is a set of interactive charts (primarily graphs and tables) that simultaneously reside on a single screen, each of which presents a somewhat different view of a common dataset, and is used to analyze that information.
We might consider dashboards a static version of FADs (or we could consider FADs a versatile dashboard). If that's true (and I'm sure Stephen will step in to correct me), then who wants a plain dashboard? Why build something that only raises questions but doesn't give the user any ability to drill down, explore, tweak parameters, or otherwise try to answer those questions?
Information display. Like most reporting, dashboards suffer from poor information design. Here's our list of blogs that preach the right way and highlight the offenders. Here are two particularly misguided design approaches that I've seen recently...
Just because it is called a dashboard doesn't mean you need to take the concept literally (via Dashboard Spy)
Just because you can make it shiny doesn't mean you should. Crystal Xcelsius not only vigorously embraces pie charts, but they add a "reflective kidney bean" to further derail the information display.
Storytelling. Most dashboards are loose affiliations of charts—a hodgepodge of graphics on the same topic intended to offer a full view of a situation. It is the same problem so many people run into in creating PowerPoint presentations.
You want the information to easily slide into the viewer's brain and stick when it gets there. The best dashboards have story-like features such as:
- Set the stage. What is the context? Who are the characters?
- Focus on only the important elements and themes; don't try to be a comprehensive account of everything that happened. Ruthlessly cut extraneous content.
- Offer recognizable characters to spare the reader's precious attention. There is a high cost to asking readers to learn from scratch. For dashboards this means terms, metrics, graphics, and metaphors that are familiar within the organization.
- Create flow and cohesiveness from chapter to chapter. Themes and characters reappear chapter after chapter. A good dashboard isn't a bunch of disjointed charts, but a logical flow from one analytical examination to the next.
- Levels of detail. Some elements of the story span the entire experience; other details provide the insights and seasoning to keep your interest.
Here's a good example of a dashboard (perhaps FAD) from Visual I-O that has many of these storytelling elements.

In contrast, the following dashboards (courtesy of Dashboard Spy) don't attempt to explain anything to the reader:


If you've seen a worse dashboard, sent it our way and we'll put together a gallery of the worst of the worst. Please redact any company-specific information.
9 comments | Show all comments only the last 5 are shown
nixnut said:
According to Steve dashboards and FADs serve two distinct purposes. In Steve's words:
The greatest clarification that is needed today is a distinction between dashboards, which are used for monitoring what’s going on, and displays that combine several charts on a screen for the purpose of analysis.
So dashboards are for monitoring and FADs for analysis.
A dashboard displays predefined measures that may come from a multitude of data sets.
A FAD will usually display different views of one dataset.
A dashboard is for displaying answers to existing questions.
A FAD is for discovering new things of interest in a data set. Manipulating a FAD leads to new questions and (hopefully) answers to these questions.
So why would one be satisfied with a mere dashboard? A dashboard can display measures covering a great number of areas of interest using data from a large number of sources. The value of having all the measures that are important for your work available in one display may outweigh the value of being able to directly manipulate the display to slice, dice, drill up/down/left/right etc. I think having a seperate tool for analysis makes more sense then forcing your dashboard to do a job it is not designed for or trying to make your analysis tool be a dashboard as well. Use the right tool for the job.
Also analysis might not be the most effective way to spend your time on or even be your job. I reckon a senior manager is more likely to put an assistant onto finding an answer to a question raised by a dashboard measure than performing the analysis himself. In operational monitoring you may just need to keep track of things and inform the relevant team if the value of a measure reaches a threshold. Finding out why the threshold is reached would not be your job.
Zach said:
Putting aside qualifiers like "it depends on the situation", I don't think I agree with the distinction as you've described it. A couple reasons:
* Senior managers should be willing to spend some time examining data beyond looking for a warning light. That isn't to say they should be running logistic regressions, but it is worth the mental effort to discover which division is causing a deviation or understanding sales variance by day of the week. In my experience, understanding nuance is what separates the good leaders (enter political joke here: _____)
* More generally, I think it is artificial to make a strong distinction between raising questions and answering questions. Granted it may be difficult or impossible in some situations to have a tool that does both. Why not make that the goal? The Visual I-O tool shown above will highlight strong and weak performance, and the ability to cut the data will help answer some of the questions about this performance.
* FADs need not be constrained to a single data source. Getting the full picture of a situation usually requires tapping into multiple systems.
Michael said:
Nice blog post. I think you made a pretty strong point. There is another angle here but I'm not sure how it fits in. The niche that I am personally interested in is the fact that many dashboards as well as FADs are backwards looking. They rely on the individual to extrapolate what they see, into where sales might end up for the month or the direction sales are headed for the year. With the amount of predictive modeling and simulation analysis that is available, I would really like to see dashboards incorporate much more sophisticated analysis. This doesn't mean that the display of information should be less intuitive, but that the underlying drivers that create the information to be displayed, could be so much more useful.
For example: I know that as of May 7 we have closed 20k in sales. I may also know that historically, in May, we have had 30k in sales booked. I also know that our plan says we should have 35k in sales by the 7th. Of course, there is always uncertainty in any forecast and sales could pick up significantly over the next couple of weeks. Maybe a monte carlo simulation could be run in the background and surfaced to the dashboard in such as way that the indicator tells us that based on current data our expected month end results are:
85% chance of hitting 35k
90% chance of hitting 30k
98% chance of hitting 25k
etc.
Kevin Hillstrom said:
Dashboards are fun to implement when you have a company with 60,000 employees and 130 executives who have differing ideas of what is important.
But if you can get past that, you can really teach leaders what is important via a dashboard.
nixnut said:
Hello Zach,
Perhaps my example of senior managers is a wrong example. I was merely trying to point out that there are groups of dashboard users that would use a dashboard for monitoring and not for analysis. I think that the difference between monitoring and analysis is large enough that the principles of perception and cognition would lead to different designs.
Having a tool that is capable of designing visual displays to cover the full range from monitoring KPI's to sophisticated analysis is indeed something to aim for. Alas such tools are not available yet (at least none that I know of).
While such a tool would allow you to build both dashboards and FAds these are still different things imho. The dashboard would still display the KPI's (or their derived metrics) and the FAD would let you look at the numbers behind the values for these metrics, generate and look at different perspectives, possibly do some simulation etc.
I didn't say FADs are restricted to one data source. I said they would usually work with just one dataset. I suppose my wording wasn't too clear. By dataset I mean a set of data about one subject area. In a dashboard it's natural to display metrics from several subject areas that are not related (other than by organisation) or not related in ways that are useful for filtering. Filtering or brushing as you could do in a FAD would update all the facets in the FAD to reflect the selection made. But in a dashboard that would only update the relevant metrics and leave the rest untouched. If you are interested in playing around with a metric (or a set of related metrics) it would make more sense to me to design a FAD for that purpose and use the dashboard as a starting point to drill down to the FAD from the metric on the dashboard. More sense than trying to force every dashboard to be a FAD that is.
I hope this post makes more sense to you than my first :-)
ltweedie said:
Michael
I entirely agree that dashboards/FADs showing predicitive models are a whole area that is very unexplored!
I did something very similar to this in my thesis in 1997 "The Influence Explorer" (a quick websearch will bring up the relevent papers) where we sampled a response surface model (Nelders generalised linear models to be precise) and then visualised it using interactive histograms, scatterplots and various other tools.
My experience in showing it to users was that it was immensely powerful as a tool to communicate a model. Suddenly analysts were able to make their models real. So that these models became real shared problem representations.
You could explore the relationship between inputs and outputs fluidly and easily.
I still haven't really seen this done in many other places and yet it is such a simple idea to put into practice. Has it?
Lisa
ltweedie said:
Zach/nixnut
Surely adding interactivity is about how much complexity you add to a tool.
I would say the important thing is not whether to add interactivity to a dashboard but whether it is justified in the context. So there will be situations in which allowing a user to interactively track back through time or drill down on a piece of data would be central to the dashboard design.
My hunch is that Responsive (dynamic) interaction enables a user to quickly compare many graphs in a way that is just not the same in static view. I guess we need some research to back this up - anyone know of any?
In an analysis situation we want to provide unlimited freedom. In a dashboard situation we want to provide key information quickly and clearly.
Thus I argue that in a dashboard design one should consider what key activities are going on and assess whether interactivity is appropriate. I believe there will be situations when it is very pertinent.
Lisa
Ted Cuzzillo said:
I like the idea of a “faceted analytics display.” I’m sure FADs are important. I just hate to see Stephen Few opt for this term because inept designers have spoiled “dashboard.”
Dashboard is a valuable metaphor and should be defended. I’m afraid FAD will be forgotten.
Isn’t a FAD just a dashboard with extra features? When they added tachometers to auto dashboards, did dashboards become something else? If you add new software or a new peripheral to your computer, isn’t it still a computer?
Perhaps we could think of it as a simulation dashboard--but still a dashboard. Calling it a simulation dashboard is still stronger than calling it a FAD.
Using “simulation” might force a modifier onto dashboards that don’t interact. How about “dumb”? Then we’d call the really bad dashboards just “dumber.”
Zach said:
Ted, I agree completely. FAD isn't likely to stick. Simulation (or perhaps interactive) dashboard is a good modifier.
Add a comment
Earlier writing




9 comments | Show all comments only the last 5 are shown
Hadley said:
How about a version for all the deuteranopes out there?
Chris Gemignani said:
Hadley, You bet. We'll publish a version for your chromatically challenged clan.
Kyle said:
I think you've left the footer from the Chart Chooser page on the bottom of this one.
Chris Gemignani said:
Thanks Kyle
Friedbeef said:
Hi - does the app work in Firefox? Because I'm having problems loading it up with the FF and Flock browser. Works OK on IE7 tho....
derek said:
What's the history of the use of black in treemaps? It seems to run counter to the normal tendency for info visualisation to have white as the background.
Brian Timoney said:
Very interesting use of Flex components; quite sticky indeed.
I guess it's cold comfort to the newly laid off, but I was struck how prevalent Yahoo was across a number of different categories...
Brian
Fubiz said:
Excelent title!
Fin said:
Interesting google doesn't come up in the portal rankings. I use my google homepage about 60 times a day. It is as much a portal as Windows live.
said:
Add a comment