Just when you thought you fully understood the three circles of information architecture, your assumptions are being challenged again. Withrow comes around with an argument for looking at the context circle differently.
User State-Trace Analysis
Interaction modeling makes design decisions explicit. In principle it’s simple: record what users “should” do, what they actually do, and then explain the differences between the two. Of course there’s more to it than that, and Matt Queen gives us all the details in this story.
Adapting an Existing UI for a New Purpose
Not every upgrade comes with a big budget, so you have to work with what you’ve got. Here are a couple of ways you can work with an existing UI to give it a new look and a new function.
The recent rise in more powerful technologies that provide richer user experiences online has presented us with a challenge. As designers, we are moving from from designing for “PIAs” to designing for “RIAs.” Does our documentation style change with the technology? Will our standard ways do the job?
User journeys are a method for conceptualising and structuring a website’s content and functionality. These journeys allow us to shift away from thinking about structure in terms of hierarchies or a technical build; instead you create a narrative around your user’s needs.
Personas and scenarios tell honest stories that are sculpted from diverse and comprehensive sets of data. Parrish Hanna and his Experience Planners demonstrate how to keep it honest throughout the organization.
Collaboration Sessions encourage multidisciplinary collaboration while creating a unified design vision–all within a compressed time frame.
Network audio devices provide a convenient way to play digital audio through your home stereo. How do they provide remote access to your music library, given the UI limitations of the first generation of devices? This looks like a job for an information architect.
The Yahoo! platform design team shares their process for defining and designing a pattern and standards library, the process for defining the requirements of the repository and the process for defining the lifecycle of a pattern.
Assume that you are in charge of a development project and you have about $10,000 to spend on usability. What is the best way to use the money? What is the right thing to do for the organization? What will be best for customers?