vanderwal.net

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.

Home usability problems

Katie Hafner writes in the New York Times about comforts of home yield to tyranny of digital gizmos. At times it seems like there needs to be a human upgrade to keep up with the applications that allow you to "easily" have control over your applicances.

New edesign mag

Last night I stumbled across edesign magazine at the local Barnes and Noble. I have been bemoaning the loss of Web Techniques and other electronic medium magazines. The preview copy that I picked up was a rather solid issue that covered a broad swath topics. The magazine did not hit the cutting edge, but it was the first time I have seen some topics covered in hard print. The magazine pointed to MeFi (including some specific threads in MeFi) and talked with Zeldman and other developers who are in the digital medium for more than just fast cash. This issue touched on the folks that have been and are still passionate about the digital medium and electronic design. It was nice to see Carl Steadman's name in hard print again. I hope these folks can stick around. Now I am waiting for a May/June issue.

Peterme has exposes Using Conceptual Models in Interaction Design. Putting this forth was a discussion about using metaphors for interaction (interface) design, such as a desktop as an interface. Peter's post is wonderful, go enjoy.

CompUSA no sale

Need to have an example of not thinking through all the steps when building a Web application? Macwhiz tries to buy a monitor with good money, but bad application does not allow it. Having the credit from CompUSA on a CompUSA card and using to buy from CompUSA does not mean a thing. The buyer wanted it delivered to his office (always a logical option), but had his home address listed on the credit card (another logical option). CompUSA needed him to add his office address to the card (another logical option), but does not offer any mechanism to doing so (somebody will get fired).

When building applications there needs to be processes put into place to handle the needed options. Many times this requires a phone call to people trained in customer service. Not understanding processes before building an application or have ALL parties talking while developing an application will save embarrassment.

You should never start building before drawing a blueprint that takes into account all the options and needs. There is too much experience around to really have this happen with out a conscious decision being made (usually up the food chain) that stopped the options from being developed (if this is not the case they have the wrong developers or not enough time to have the processes worked out). These reasons are very close to why I will never buy from Barnes and Noble on line again. Ever.

Opening an application to the Internet opens the application to real people and real people provide a wide variety of aberrations to the planned uses for any application. Not having the time, resources, or approval to build in processes for easily handling these aberrations or spending time developing the application using user centered design/development skills will sink even the best funded applications. The user is always right and the real users must be a part of the development.

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.

The Visual Display of Quantitative XML on O'Reilly Net really rocks for me. I am really impressed with the presentation, but not nearly as impressed as I was with the ease of downloading and running the SVG plug-in in IE 6 on Windows and IE 5.1 on Mac OS X. Overal this is a great article as it not only walks through the how-to portion, but also offers insights into things that will make similar development go more easily.

Kevin Fox adds New to You functionality to his site. This is the best idea I have run across in a while. It is a great idea that beats the problems I find on sites I frequent often. It also seems to cover the territory between visited links and not providing them. [hat tip Dinah]

Seach Not and Find the Answer

Peter Morville explains why search doesn't suck, but is just not great. I completely agree. Search by itself misses much of the information, unless the site is well written (which provides a cohesive use of terms) or is augmented with metadata.

Let me explain, as Doug Kaye uses in his quest to find what is wrong with searching, a person six months or more ago could have been writing about IT as the possible wave of the future. More recently the same person could have been writing about Ginger. This past week the writer would have started writing about Segway. All were the Dean Kamen invention, but a user searching for a the breadth of our writing on Segway could easily miss our mention of IT or Ginger. The user would have to know to search on these other terms, if they did not they may not find our work. We loose.

This is where metadata helps out. If the information is tagged with a term that classifies this information or could have synonymous relationships established from that metadata item (personal powered transportation = IT, Ginger, Segway...) would greatly help the search. Most of us have been worked on projects that have had searches yet we constantly had users asking us were our information on "xyz" could be found, as they did not find it in the search and they know they read it on our site. That is a large persistent problem. Searching is not a solution only a patch that leaks.

By the way taxonomies can be fluid, they have to be as usage changes.

A New York Times article on the skill of interface design is a solid insight into how to make applications and devices more usable.

The BBC reports that Intel is running field studies on mobile device use in London. The research is an ethnogrphic study of interactive use. The article states, "'One of the things that makes a successful technology is a technology that supports experiences that people want to have,' explained Ms Genevieve Bell, senior researcher and design ethnographer at Intel." This is nice news, but slightly more impressive is the general media's explainations of the study, (you go Beeb!!).

Joe Gillespie's Interface Design Primer offers a wonderful background of the computer interface. There are wonderful nuggets that we designers and devleopers need to keep in mind. Knowing how, why, history, and reasoning behind elements of interface understanding are some of the best tools we carry in our tool belts. We also need to keep testing what we know to ensure there are not new shades that will help get all of us around a corner to a much better method of providing the user an intuitive interactive interface. [hat tip Jeffery]

The Sacramento Bee has modified their look and added some great usability tools. Their new look is very clean and easy to read. Each page provides access to the top level pages with in each section from the top of the pages as well as the bottom of the pages. The pages are built with extensive use of cascading style sheets, which allows them use of a tool that lets the user select the font used and increase or decrease the font size. [hat tip Matt]

I am continually running in to graphic display problems with Quicktime on Windows XP and with an ATI 7200 Radon graphics card. I lose the picture in movies and the skin on the player. If I go back and reload the drivers and the Direct X drivers it all works wonderfully. XP has been solid but there are a lot of little annoying bugs running all throughout. There are loads of interface and interaction anomalies also. In all I am happier with it than I was prior, but they still don't get things right.

Web Designers should stop relying on search to cover for poor IA and design, to paraphrase PC World's presentation of User Interface Engineering's (UIE) latest research. This states 77 percent of the users do not find what they are looking for through search. The article does list some pitfalls that the user can fall into (poor spelling on the site, etc.), but with great depth of information and users often looking for specific information search could be a solid option, but this takes some work.

One navigation method that I find less and less is offering similar links based on what the user has clicked to. Often I would like to read the archives of a regular columnist in a magazine. I should not have to search to find the archives as that method often provide chaff with the goal of my search. Storage and metadata can greatly assist the navigation approach.

I personally find navigation and search combinations on a site create a higher probability that I will find the information that I am searching for.