To put it simply (and a bit overly simplified), if a user clicks on the browsers back button I think the website navigation has suffered a catastrophic failure (in most cases). Why? Apart from user preference/habit (most cases) the user was forced to end their engagement with the website and engage the browser. Is the browsers back button our report card showing an F (most cases)?
I started in information architecture in 2007, I got out of it and now I am trying to get back into IA/UX. I consequently do not have the 5+ years of experience or the mandatory "senior titles", but I do have the education! I came across this in a recent job posting: "5+ years of agency experience working on site builds. Someone who really understands the user experience." I was initially hired because I was a user experience professional.
For a brief break during the workday, I once posted some humor and satire about the field that was well received. Then the site ended and for awhile the humorous stuff was unavailable. I apologize for this outage. In response to ongoing requests by visitors, the humor has been restored and moved to http://www.filippsapienza.com/blog1/2010/02/02/humorous-writing/
In my line of work I am more accustom to creating visual comps or high level screen designs. I am trying to create more low level wire frames with annotations. I was wondering if anyone had any wire frame templates available for MS Visio?
Also, I am seeking input as to when to add these annotations.
I know it is a common practice for B2B sites to structure the navigation by audience; however, I think structuring the navigation based on tasks rather than audience type could be a better solution. Would analyzing the tasks for each audience type naturally present a common IA that all audience types could understand? For example, each audience type needs to know the benefits of a product (of course, the benefits for the product differs for each audience type).