vanderwal.net

Inner Navigation and Information Cascade

A couple of weeks ago I picked up Inner Navigation: Why we Get Lost in the World and How we Find Our Way by Erik Jonsson. I was interested in the title and a quick read of the cover and forward brought me to buy it. The book offers very short snippets about how folks lose their way in environments. The use of visual cues or the ignoring the visual cues and how they prompt us to make decisions or mis-decisions has had me interested. I have been reading one of the short stories most nights and pondering.

One of the other interesting elements is the disconnect between known right and wrong. There is a story or two about folks thinking they were heading one direction so to reach a destination, but were actually travelling in the opposite, or nearly opposite direction. The folks knew the destination was a block or two away, but yet kept travelling for many more blocks beyond what they figured was even possible. The brain gets filled with doubt and at the same time conviction that it has made the correct decision.

This has dovetailed with some readings from the past few months on Information Cascade, which Lisa Anderson and Charles Holt coined to explain individual choice that follows the trends of others, even though they know the trend is not in their best interest or will provide them a positive outcome. This echoes of the late '90s stock market, but also those following "guru's" statements because others have but value in them. Some of this can explain reliance on poor information vehicles, like the mis-use or improper use of PDF's to store and present information. PDF's provide a wonderful information vehicle to store information that is intended for exact visual representation of the information. PDF's now have poor methods of information extraction and searching (when compared to other information storage like a database that would output perfectly validating HTML as its presentation layer), but this all depends on the use and purpose of the end user for that information. PDF's gained prominence because others were using them to distribute information, even though there were issues with the intended purpose meshing with the information vehicle, the use by others developed a "herding" decision based on use by others.

There are many possible illustrations for these issues and the Inner Navigation book offers some great triggers to better personal examination to the world around us. These are some of my favorite books, the one that cause me to have introspection and outward observations in a new light and can tie other readings and knowledge together in new ways. Grow ye synaptic connections.

Site architecture of Slate

Jesse provides yet another wonderful backward engineering of the information architecture of a site, the new addition is a Slate site analysis found published in Boxes and Arrows. Jesse uses his own visual vocabulary for the graphic.

Findability explained

Peter Morville finally puts his findability explanation in writing for all to see (in the wonderful site called Boxes and Arrows). The idea of the term and meaning of findability is growing on me. Findability is a solid lead into the problems of information structure. The explanation of how to start fixing the problems and actions needed to help eradicate the problem can reside in the method/model of attraction (an update to the MOA should be available in two or three weeks, extenuating circumstances have slowed the updates and progress).

Internet Archive a information mess

The Chron focusses on the lack of organization of the Internet Archive. This would be a dream to organize for some folks I know (or at least I think it would be). The problems at hand for this project rule out library science approach (too much human touch needed) and search engines as their design is not conducive. A great read to get the wheels turning.

Metaphor of Attraction

Beginning with a discussion with Stewart on Peterme and the encouragement of Lane in another discussion to look for a metaphor other than navigation that could better explain what we do on the Web. Seeing Stewart walk by at SXSW after I had seen some of Josh Davis visual plays I combined the discussion with Stewart with the magnetic attraction Josh showed, which began my thinking about a metaphor of attraction. Magnetism seems like what happens when we put a search term in Google, it attracts information that is draw to the term on to your screen.

Come see where else this metaphor can go in this poorly written for draft of the metaphor of attraction. This is posted to begin a collaboration to dig back and move forward, if that is where this is to go. The writing will improve and the ideas will jell into a better presentation over the next few weeks.

Based on descussions begun with Stewart, Peter, Lane, and others in, beginning in discussions about navigation as a poor metaphor for the interaction of humans and information on the Web (which really breaks down further when looking at other types of Internet information interaction), I am working on another metaphor that struck me while in Austin. Lane asked in another conversation for alternatives to the navigation metaphor. I will be posting a series on this site that will open the idea for discussion and help finding holes or coming to the conclusion the idea sucks. The postings will most likely begin next week sometime. I am going to put the idea past a few friends at the IA Summit and see how hard they laugh or like it. For me the concept is working so far and seems to have a decent reach into Web and non-Web Internet interactions with information. No I am not going to state it now, but I will soon.

I think a note of clarification is needed regarding the frames comments from the other day. I am a huge fan of the Content Management Bible and have been perusing it for a couple months (or so) now. The use of frames is not all bad, if used in a proper context.

One reason to use frames is using the browser client as an application interface and there are distinct sections with quasi-interrelated functionality. A mapping application (select any one of these elements on the page to see the use of frames - keep in mind there is a heavy use of JavaScript that requires a version 4.5 browser or higher). The application interface often has command elements that are essentially toolbars and definition selection elements that set the metadata layers of the information to be displayed. These toolbars direct the actions of the other frames or provide tools to be used in other frames (a zoom tool, etc.). The functionality in a toolbar is not an element of the map display and it should not be an incorporated element of the map as it has a much different functionality from the map display. Conversely, our users are familiar with navigation being incorporated into the Webpage and that is now a common and preferred construct. But, we are looking at an application being displayed in a Web browser, which requires a different mind set.

Another use of frames is in a controlled environment that has a plethora of distinct content items that are within a contiguous text, such as an extensive table of contents. Here the Metatorial CM Bible is a good example of when to use frames. There table of contents is a helpful information tool to quickly scan through the information to place the reader at distinct point in a larger body of text. The table of contents is a large (long) element of text that could work as an element is one distinct page, but that would require rebuilding those elements of the page with every snippet of information delivered to the browser.

Frames should be used when the distinct content elements require each other. The table of contents and the page display elements should not work with out the other components (if they can we really have to ask ourselves why we are using frames). If we can enter a page in the CM Bible without the table of contents the functionality of the site is broken. The navigation is not available and the assistive information (navigation and/or metadata elements) is not available.

The last item is to ensure that if a frame can stand alone as its own page, please ensure there are the needed navigational elements on the page. In the example that drove my frames rant (largely because the CM folks understand information and its need to be used, but the site breaks information use constructs we know from experience and research to be proper and needed) the thing that was disconcerting was each of the frame elements needed the other to provide complete information for the user. The user needs context. We need to provide the user a means to get to our front page or to other areas within our sites, because if they like our information we should offer them more. If we build a site using framed elements and these elements can be used on their own (no JavaScript sniffers to ensure the other frames are open as a requirement for displaying the content, or other similar technique) the content must have navigation elements (the footer is an unobtrusive placement) and really should have some branding or other statement of ownership.

We know that users of information have varied purposes and methods of using our information. We need to provide the users the tools to help the user provide this information. We are often proud of our information work, but if a user does not know it is us or we do not want to claim our work is decreases credibility.

We need to embrace functional information architecture to ensure proper information use. This bleeds in to user experience design, but understanding how information is used and the information interface is used must be integrated into the IA. Proper functional IA should keep improper use of frames from occurring. Functional IA would walk through a string of questions using a wireframe of a site and ask how the frame sections would interact. We would ask what information is lost if not all the frames function (a surprisingly common occurrence). We would ask if frames maintain context for the information. We would look at methods of insuring the whole of the frames remains so to provide proper navigation, proper context, and proper metadata to help understand the information provided. Not asking these questions is not being responsible to the information, those that collected the metadata and spent time understanding how the information is to be used, and is not responsible to the consumers of the information.