Map incompleteness

Map incompleteness is something that I am very intrigued about. As shown in the example above taken in Paris, the city itself is well represented but as soon as you leave the “périphérique” (the highway-like infrastructure that surrounds the french capital), it’s a blank grey void as if no one leaves beyond this limit. It’s a phenomenon you also encounter with weather maps as you can see below: weather forecast generally stops at the border (clouds don’t go through the customs, do they?). You can see the swiss map as if it was a stand-alone territory (lots of countries do it anyway).

Why do I blog this?

Some very useful issues to be thinking about and when and where to use for my own work, if appropriate? Taken from Pasta & Vinegar

"Map incompleteness is understandable in terms of information design: the use of “white space” can be relevant to “balance composition and induction properly”. Designing maps and signage is a matter of simplification so that people could easily grasp the situation at hand. However, in both situations above I am often bothered by the simplification; not that I need to go across the border and would be happy to know the temperature, rather because it discretized phenomena that should be represented as continuous."

Chipchase photo Fare Maps

Fare Maps

Thoughts on Data, design…and soul

Some key thoughts from the blog post ghostinthepixel.com,
it is useful to think of where a model would position itself in relation to this discussion -
Does the model have to be data driven? I would hope not... As pointed out “It is more from engaging with users, watching what they do, understanding their pain points, that you get big leaps in design.” This again is pointing to how a model may lead to such discussions - with the value of data and value of data taken from the context ?
The full discussion is below:

Data, design…and soul

Following up on the initial posting on Google’s “data-driven” ethos by web designer extraordinaire Doug Bowman, and the subsequent heated debate on data vs. design (on ixda, etc.), another web design guru, Luke Wroblewski has published a beautifully compact articulation pointing out the falsity of the debate (which the NYTimes even used in their article title over the weekend–hmm!). Indeed it’s not a conflict, but a parallel dialogue of approaches and viewpoints, working together.

As Luke says:

1. Data informs design
2. A handle on design builds credibility
3. Data is not the only way to make decisions

Nice!

On the same topic, Luke Stevens published this lengthy read teasing apart the issues of “data vs. design”, largely defending data-driven design with thoughtful explanation, but avoiding the typical holy war of righteous indignation.

Ok, that’s fine. However, my issue isn’t really that data drives design or not, but the following:

1. What is meant by data? Seriously. This may sound like a naive question but certainly in light of ethnography, affective studies, personal storytelling, etc (and more from Jane Fulton Suri, Liz Sanders, Brenda Laurel, among others). I’d say the parameters of what constitutes “data” are broadening. I fear there is such rigid attachment by researchers, marketers, engineers to just numerical studies that there is a blind spot to other kinds of data…

In addition to the conventions of web analytics and statistically quantifiable numeric studies/surveys/measurements, there must be room for the data of past professional experience, evolved and applied patterns/principles/guidelines, and yes personal intuition via judgement and thoughtful insight (developed over time with exposure to projects, clients, etc.)

I suspect that a rigid adherence to only numerical data is actually just a snub of contemptuous disrespect for trusting a learned and experienced designer’s judgement, which is multidimensional and dynamic…and evolving.

2. What about the soul of a design? How does extensive numerical data studies enable the aesthetic character, the humanizing quality, the elusive wonderment that makes a design resonate with one’s dreams and desires? “To light a fire in the mind and breathe life into the heart”, as former Sony head of design once described some compelling design concepts, is not something numbers can do. It takes a genuinely inspired and talented human being to elicit forth such qualities in pixels and matter, through a complex messy amalgam of culture, expression, arts, language, style, and so forth. There is an ineffable quality that transcends mere numbers, suggesting a poetic graceful elegance…a kind of equipoise if you will. Hundreds of numerical studies will not provide this no matter how rigorous or detailed. Some of it may be of value, but as Doug Bowman says, “But we take all that with a grain of salt.” And remember… as Jared Spool said once, “any piece of data can be whipped to confess to anything.” It takes the judgement, inspiration, experience, and temperament of the designer(s) to resolve a cohesive blend of the rational and the imaginative into something that people will emotionally connect with and effectively use.

Marissa Mayer may unapologetically say “We let the math and the data govern how things look and feel,” but doing so only confesses the lack of humanity and soul in Google’s products, only a raw Terminator-esque ruthless efficiency embraced by triumphant engineering-centric glee. (Google Analytics–ironically–may be an exception, as is Google Chrome. IMHO per the recent bayCHI talk)

And finally, since when did a numerical quant study alone lead to some of the grand paradigm-shifting, breakthrough products of our time: the iPod, the Dyson, Tivo, Prius, twitter, youTube, blogs and of course the iPhone. Those dramatic jumps of insight more often involve multiple kinds of “data” mentioned above, and the recently recognized skills of abductive thinking (as Frog’s Jon Kolko described at Interaction’09)…with some curiosity and inventiveness and a good measure of perspiration, to hint at Thomas Edison’s old saying. Indeed, from the NYTimes article: “It is more from engaging with users, watching what they do, understanding their pain points, that you get big leaps in design.”