Semiotics teaches us as designers that our work has no meaning outside the complex set of factors that define it. The deeper our understanding and awareness of these factors, the better our control over the success of the work products we create.
As a specialist in the user, you gain knowledge through observation and direct questioning of individual users. Now, you can add to that insights gained from data pulled during their actions on the site. By looking at this information, you will get a fuller picture of user behavior, not in a lab, but in the true user environment.
There is not consensus on exactly what information design is. Definitions of the discipline from stakeholders who associate themselves with the field are consistent only in that they are typically high level, not very concrete and do not offer much in the way of direct practical application.
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.
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.
Both programming and IA are oriented towards abstraction. They both want to find patterns and rules that describe and predict. They both are concerned with handling structured content and metadata. But more often than not, IAs don’t know what’s going on with code. In this article, Andrew Otwell introduces IAs to the basic building blocks of programming.
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.
We need a way to document and express mental models that is as simple and robust as personas for user profiles and scenarios for tasks. By laying out users’ current mental models and a target mental model, we can clarify our thinking and communication about the user interface’s objects, metaphors, and interaction.
Design organizations inevitably run across the debate of Visio versus HTML wireframes. The decision for one over the other is never a clear-cut one since, as with all things IA-related, it depends. This article seeks to sort out the issues by describing the pros and cons of each and identifying situations where one may be more effective than the other.