This is the P2PU Archive. If you want the current site, go to www.p2pu.org!
The revisions let you track differences between multiple versions of a post.
User Behavior
There are quite a few short articles at Usability.gov on user behavior and how it should guide designers. It's a very good resource, written fairly accessibly, without ads, not focused on SEO, and not requiring a fee for content. I'm also including a number of links to short "alertbox" articles by Jakob Neilsen. Some of the former reference the latter. You'll notice a lot of repetition in how average user behavior is described. That's because there is a lot of predictability in typical user behavior. it's a good thing, because predictable behavior is easier to design for.
Designing to user behavior can improve the performance of any website6,even nonprofits and government sites. It can also increase your credibility5 in the eyes of the user, which will keep them on your site instead of going elsewhere for the same type of content.
Eyetracking - what is it? How does it apply to an "average" user? Eyetracking is a type of user behavior analysis that uses various methods for following where the user looks, and how long, on a given site. Typically, the user's eye tracks in an "F" pattern, or a "Z" pattern, depending on the content looked at, or what the user is looking for. The F Pattern actually applies to blocks of text content, not the overall layout, and this should be considered. See reading section 3 "Understanding Eye Tracking"
Assignment 1: read resource 1 (Designing for the Average User) and think of someone you may know, who might fit that general description, who you often help with computer or technology tasks. This person is your equivalent to an average user. What is their typical behavior when interacting with a website or UI? How would you build a site so that they did not need your help to navigate it? Discuss.
Assignment 2: go to http://www.yahoo.com/ and use markup http://markup.io/ to show what parts of the page caught your attention, show how you think you scanned the page, and shwo what you ignored. Example: http://markup.io/v/pqph6b7kv19e Post a link to your markup in the google group.
Resources:
Information Presentation
Now that we have looked at typical user behaviors, we need to apply that knowledege to how we present information. What we need to consider is how that behavior should guide our designs.
Assignment 3: Read the linked articles, and discuss:
Resources:
Sure thing!
Sure thing!
Can you post this to the
Can you post this to the google group as well? The threaded discussion isn't really user-friendly here. Thanks!
My average user indeed comes
My average user indeed comes to me for help in various computer tasks such as navigating sites or retrieving pictures taken and stored in a digital camera. A new anything can be daunting and I, too, was once new to this, so I don't mind. Though my average user knows how to operate a digital camera, they always succomb to Walgreens or Wal-Mart to retrieve the photos. One reason I know they do this is because it's easier than having to learn how to fully operate something they already have growing doubts and opinions about. This is expected and, in regards to User Advocacy, should be acknowledged. However, their experiences are a bit different when it comes to interacting with a website - they are not intimidated, but rather excited. I remember the first time I attempted my best at explaining how to search for a vehicle on Craigslist. Though my average user had trouble reading the smaller fonts, they performed searches in steps and stuck with it until it became something familiar. Ultimately what I think helped them in getting adjusted was memory of where each link was, no matter what city or state, and the colors associated with them. If I were to build them a site, I think I would incorporate something of the same sort, (links and accompanying colors) but also, perhaps a constant reference/ help menu when they hovered over a new area with their mouse, and a translator, in case their browser didn't have that support.