So far, published books about information visualization focused on the design results and gavefew or none insight about how visualizations are actually being used. This is bad because we don’t have the full story, we miss what is probably the most important information we need to know which visualization techniques and strategies are the good ones, and which the bad ones: the user feedback. Think on UX, product development and the lean methodology: we now understand that only researching on how a project is actually being used (in actual contexts, by actual users) we can know when there is real value on it. But in the infovis field we don’t have that culture… maybe some have, there are exceptions for sure, but it’s not yet represented in blogs or books.
The formal way visualization methods are assessed is in experiments with control groups, that is: out of any possible real context. These tests mainly focus on perception and memory. But information visualization is a complex media, a communication channel, a new writing, a one that goes way beyond techniques to convey specific numeric values and help memorize them. Those approaches are equivalent to assess a book by the reading quality of its font. Yes, with a very bad font the book can be ruined and a reader won’t understand, enjoy or memorize a thing; but you don’t asses a book solely by the font it uses. Another metaphor: imagine evaluating a tennis player solely by her mental and physical conditions, but not taking into account her performance on the court!.
As a visualization professional, I was long expecting lecture material about the real life of visualization: how it’s being used within organizations, which are the success and the failures cases, how complex a visualization should be in order to be innovative and compelling without generating fears, etc… I need that guide to help me delivering the best possible results to my clients.
Phil Simon did the job: he knocked doors at several companies (not all opened) and made the right questions. The Visual Organization is a book that reveals at least two important facts: 1. companies, regardless of their size, need to incorporate data to survive, and visual tools could be of great help, if not required, 2. this is not an easy step: the market of data science and visualization tools is a mess, and a company needs to research a lot and probably try different solutions. The book is definitively of great help for a company that wants to become a visual organization: Phil describes four levels that serve as a map to make consistent steps towards that goal.
I missed in the book more specific information. Except for a few remarkable cases, I was eager to know more about the specific visualization methods, how they work, how they were used, when they failed and succeeded and why. A book with such a degree of detail would be 1800 pages long, and, on another hand, the book provides you the necessary information to further investigation. I expect Phil will continue filling the hole in the water, and that others will follow his lead. Meanwhile, The Visual Organization is a must for visualization professionals that are concerned about how their projects perform in real life, and for companies that want to become more data(visual)-driven.