Off the Top: User-Centered Design Entries
Showing posts: 196-210 of 232 total posts
Interview with John Weir, designer of International Herald Tribune online on James' Ordinary Life. [hat tip Michael at ia/]
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.
USC Annenberg School offers a light personal review of the WSJ redesign. Those of us that use the online version of the Journal on a daily basis have noticed a great jump since the redesign began implementation over a month ago. The site is much quicker and the interface is cleaner. The queries now are very quick again and there is a deep pile of data/information to search through.
Snippets: I have noted the redesign more than once... Nihal ElRayess has shared part of the IA perspective on the main WSJ redesign and the WSJ Company Research redesign parts of the project... The Guardian provided its insight in February (a good piece of researched journalism)... It looks like the WSJ redesign began in at least March 2000... The $28 million spent on the Web reworking (hardware, software, visual, and information architecture) is much less than the $232 million spent on a new printer for the WSJ print version or the $21 million for an advertising campaign to tout the new WSJ... The previous version of the WSJ site was a hand rolled CMS and now have been moved into Vignette... Those interested in the overal WSJ plan will like what is inside the presentation of Richard Zannino, Executive Vice President and CFO of Dow Jones & Company.
The Beeb notes websites watch and learn using the browser to learn how the site's users interact with the site.
A few minor changes here at vanderwal.net. The comments link has been put on all dynamic pages of the Off the Top section. The only page that had the comment option was the main page (/random/index.php).
The CSS has also been modified to unbold and underline for the underblog links to categories, perma link, and the comments. I have found many users come straight into the categories with out a referring page (meaning they have it book marked). Google dumps users directly into categories, but that is understandable, based on their algorythyms. I had also been hearing from some users that they did not know they could click on the categories. Sorry about the confusion. You can go directly to view the categories used here.
UCD is an Art
ViewPointz' Carol Righi examines Art, Science, and Magic: What really happens during User-Centered Design? This somewhat sounds like Jesse's ia/recon repurposed for UCD. The article draws on the concept that there is art (hunches) at the core of good UCD. Much of what any profession does is educated guesswork, which largely is based on pattern recognition (understanding symptoms to doctors). Those that are very good at their craft have internalized which points to watch (where the pulse can be found) that indicate success or troubles.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.
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.
Over at CommArts, Mary Brodie outlines the requirements for developing successful navigations and user experiences. One of the things Mary brings up is UMLi (The Unified Modeling Language for Interactive Applications). I know that Jesse is not a fan of UML, but I have found many of the concepts and models quite helpful to frame interactive interface issues.
Jesse offers part 3 of the ia/recon discussing the over reliance on user testing for everything. This may be my favorite of the three components Jesse has posted so far. User testing offers a great step up and helps to understand the users better. Understanding graphic design, application development, and information architecture will help to construct solutions to information structure and interface and interaction design problems that user testing offers little insight. User testing in these areas can help let us know we are on the right track, but it will not point us in the right direction as we have not offered the user these choices if we don't have the experience.
New item causing muscle memory issues. I had to get a new keyboard for my PC as many keys went out for good last night (a, s, d, e, f, g, h, j, left ctrl, delete and down page). This made for creative alternatives this morning. The keyboard started developing a personality a couple months ago, but always came back to life in 15 minutes or so. I got a MS Natural keyboard, which had really nice key movement. I am quite impressed. Being a touch typist (is it okay to say that?) I really like the feel of the humped center, as it really eases typing. I am not sure I like the directional arrow layout, but I will learn. I did give up a volume knob and a mute button (along with 20 other buttons I did not use), but oh well.
CommArts features the Herman Miller Red site design, which includes User Experience and Information Architecture work of Nathan Shedroff (on of the Vivid Studio founders). I went to a session at last year's SXSW where Nathan presented an over view that is essentially the same as this, I am glad this is now on line as I can share it. This article provides a solid insight into decision making, workflow, and the purpose of wireframes.
An intriguing piece in the Mactopia section of the Microsoft site about Presentation tips from Dale Carnegie Training. The "plan" section reads:
This sounds like it is straight out of a user centered design or user experience design article. This would even be at home in an advertising or public relations primer. Heck, it is just smart communication technique and one of the very basics, we must understand the user/audience.
- Describe your audience as it relates to the topic รณ their knowledge and experience, their needs, wants, and goals. Ask yourself, "What does my audience know about this topic?"
- Define the purpose of your presentation as it relates to the outcome you seek. Is your intention to inform? Persuade? Motivate? Teach? When you clarify your purpose, you will more easily hit your target.
- Plan the content of your presentation around your purpose and your audience's interest and level of understanding. Use words and phrases common to your audience, and focus on your purpose.