What do cognitive psychology and information architecture have in common? Actually there is a good deal of common ground between the two disciplines. Certainly, having a background in cognitive psychology supports the practice of information architecture, and it is precisely those interconnections and support that will be explored.
In my experience, I have found that creating and documenting process has been a good exercise to help institutionalize ways of working, to help educate new team members as well as to unveil the mysteries of what we do for executives, product folks, and development teams.
As the field of information architecture matures, we are beginning to understand the new challenges it raises for wireless media. This article suggests that some of these challenges can be best addressed through an approach called “psychology-driven information architecture,” which bases design decisions and solutions on the psychological profile of the end user.
To date this column has focused on how to make deliverables more effective, either through their content or through the tools to create them. For this issue, I would like to explore the relationship between deliverables and methodology. Unfortunately, this calls for a definition of IA methodology, which may challenge the definition of IA as the hardest question in our field.
Once upon a time, we were curious and everything we encountered was new. We were excited about discovering new things and the world offered unlimited possibilities. Then we went to school and were taught to color inside the lines, that everything had its place and the world was ordered.
“What I need are highly condensed overviews,” I thought, “like those comic books that convert great literary works into a few illustrated pages. They condense Moby Dick down to 12 pages and provide a version of Great Expectations that can be read in 15 minutes.”
We hear and talk a lot about card sorting in various forms, and how it can be used as input on a hierarchy or classification system (or a taxonomy, if you like more technical words). We hear that we should test our hierarchies, but we don’t talk about how.
Jesse James Garrett’s “The Elements of User Experience” diagram has become rightly famous as a clear and simple model for the sorts of things that user experience professionals do. But as a model of user experience it presents an incomplete picture with some serious omissions—omissions I’ll try address with a more holistic model.
As a precursor to cardsorting or as an independent method, free-listing is a technique that can help you determine the scope of a content domain while providing some insight into how the domain is structured.