… or whatever we want to call it.
Yin Shanyang writes on twitter in response to my last post on vis as bidirectional channel:
This comment really hits a nerve on me as I have been thinking about this issue quite a lot lately. I must confess I am no longer satisfied with the word “visualization”. And I am even less satisfied by all the other paraphernalia people like to use: data visualization, interactive visualization, information visualization, visual analytics, infographics, etc.
The reason is that I think all these words do not describe well the work I and many other people do. While visualization seems to be appropriate when the main purpose is data presentation, I don’t think it captures the value of visualization when it is used as a data sensemaking tool.
When used for this purpose interaction is crucial. Analysis looks more like a continuous loop between these steps:
- specify to the computer what you want to see and how (the specific visual representation)
- detect patterns, interpret the results and generate questions
- ask the computer to change the data and/or the visualization to accommodate the new question(s)
- assess the results … repeat …
Analytical discourse is a term I saw used in the visual analytics agenda a few years back and I think it captures very well this concept. This all interplay and discourse between the machine and the human. This is what many of us are after and I am not sure the term visualization is able to express this concept in its entirety. The value of these tools is not exclusively in the visual representation; interaction plays a major role.
This became even more apparent to me while teaching my InfoVis course this semester. I teach a lot of things about visual representation but when students come down to building software for their projects, what they are really working on is a fully-fledged user interface. They have multiple linked views, search boxes, dynamic query sliders and all the rest. It’s interactive user interface design they end up doing, not visualization. And user interface design carries a lot of additional challenges that go beyond visual representation. Sure, designing the appropriate representation is still very important but many other choices impact the final results.
For instance all my students’ projects have multiple interactive views, maybe sometime just a main visualization, a list of terms and a couple of query sliders for dynamic filtering, but how do you call that? I call that visualization but in practice it’s a complex user interface. Or a “data interface” as suggested by Yin.
One last note. While thinking about this whole idea I recalled that Jeff Heer‘s lab at UW is called Interactive Data Lab and I think he’s got it right. Interaction with the data is the main thing, visualization is the medium we use to create part of this interaction.
What do you think? Too heretic? To much of a hassle?