vanderwal.net

Story of information

Information wants to be found. Somebody created the information to be used (including the coding of an application to extract data to form information). Information (both good and bad) has inherent value. Information that can not be found or used is wasted money and wasted time. Information requires a structure around it to increase its findability. Attempting to make information available with out a usable structure around it is a recipe for failure. Information without a usable structure surrounding it wastes the time of the person (or worse, persons) who created the information, prepared the info for dissemination, and the person/persons/application looking for that information. The waste of time and money by not having a usable information structure or not having any information structure is problematic and, in this day and age, inexcusable waste of vast money, time, and other resources.

The solution lies in working with people who understand information structure. Often these folk are called "information architects". Technology should not be the first step to solving information capturing, storing, structuring, and presentation needs. Human minds are the best first step. Human minds that have training and experience in solving these problems is the best bet. These humans are often called information architects, which:

• Understand that most often the users of information are not the person in the cube or office next door
• Know the users of the information often do not know the creator of the information
• Know the users of the information may not understand the structure of the organization that created the information
• Know the user wants to find the information
• Know the user wants read and use the information in a format they can access
• Know the user will want to consume the information and repurpose that information
• Know that if the user finds what they are looking for and you are providing it the user will often be interested in finding other related or similar information
• Know how to work with designers and technical developers to ensure the needs of your information and the user are joined together
• Know there are many methods of finding information (search, navigation, etc.) and none of these are perfect on their own, but know how to best augment the technologies to provide the best result
• Know that at the heart of this information transaction is the information and the user, which is where the focus belongs
• Know how to increase findability and make the attraction between the user and the information stronger
• Know in the long run their work saves money and time because their experience has proven what they know works

Functional and design documentation

Functional vs. design in documentation explained in one article. This article explains why these two thoughts should be in two different documents. The article also explains what should be in each of the documents. Do discuss, or I suppose folks are somewhere...

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).

Finally a move to centralize organization's Websites is the norm

Peter Merholz wrote The Pendulum Returns: Unifying the Online Presence of Decentralized Organizations for Adaptive Path. Peter points out the needs for organizations to centralize their Web content and visual interface. Consistency helps the users greatly, I have been finding this for years. The "let every flower bloom" is has always been horrible means for organizations Internet and Intranet sites. This is does not provide for central branding and ruins a user's experience when dealing with a the organization. Research, for years, has shown a homogenized brand and information structure will greatly benefit the organization and the users. There are great cost efficiencies to be had as well. For now go read Peter's work.

Adaptive Path talks with Marc Rettig

Adaptive Path interview with Marc Rettig. Marc is one of my favorite people, who continually blows my mind with his approach to problem solving (Peter and Lane are no slouches either). [hat tip Brad]

Business gets serious with Web writes the Beeb. The prediction is that Web services will take off an become part of the norm. The article states the current next step is defining the grammar and vocabulary, which sounds like a job for Super IAs.

InfoBank does IA

InfoBank offers a quick understanding of IA. Rob Manson is behind this wonderful work. The site provides a nice Flash interface.

Information Architecture of Everyday Things

Jesse now has his The Information Architecture of Everyday Things (presentation from the IA Summit) available. I did not make it to this session, as I was taking in the Scent of Information session. I wished I could have made both. Jesse has a great way of digesting information into their primary elements and showcasing these understandings in easily digestible parcels.

Over at IAWiki in the Memetic Engineer page I ran across Darwinian Processes and Memes in Architecture. Very cool stuff.

I have updated Eric Scheid's initial entry of the Metaphor of Attraction at IAWiki. I will try to keep that up to date as well as the MoA information here. I am preparing an update to the information, but as there is an out of town wedding this weekend and other diversions this next week it may be a short time longer.

I not only found the Edison and the Big Thing, but the New York Times now offers signing up for narrowed news trackers. These e-mail alerts are set to keywords that have a corrolation to the article. This seems to be a nice easy step for user to set the alerts via e-mail. It would be interesting to know how well this service is used and received.

Over at CMS Watch there is a wonderful feature about the long pain of implementing a CMS and the steps in the process to make it easier. These steps are very important to keeping the project on track and successful. Not only are these element important for CMS, but they are quite essential for any information application development.

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.

Extranet overview

John Rhodes provides an overview of extranets and hits some great points.

...most people like self-service. An extranet facilitates this activity, if you design it correctly.