Throughout my career as a user experience designer, I have continually asked myself three questions:
What should my deliverables be?
Will my deliverables provide clarity to me and their audience?
Where do my deliverables and other efforts fit within the spectrum of UX design?
I have found that, if I do not answer these questions prior to creating a deliverable, my churn rate increases and deadlines slip.
When attempting to answer the third question, I use a framework I discovered early in my career: The Five Competencies of User Experience Design.PDF This framework comprises the competencies a UX professional or team requires. The following sections describe these five competencies, outline some questions each competency must answer, and show the groundwork and deliverables for which each competency is responsible. Read More
In my previous columns, I’ve framed my discussions around the practice of information architecture. To recap, the DSIA Research Initiative—of which I am the curator—defines the practice of information architecture as “the effort of organizing and relating information in a way that simplifies how people navigate and use content on the Web.” While the practice of information architecture can surely extend beyond the Web and its content, this IA practice definition eschews theoretical language to resonate with businesses looking for concrete Web solutions and practitioners who want to make a living off something tangible.
In the end, business clients don’t pay practitioners to practice information architecture; they pay professionals to produce IA work products that help them to meet their business objectives. So, of the many professional interests that come together to create a digital experience, what work products make the practice of information architecture unique? Read More
Unfortunately, in the field of user experience, people often confuse terms like information architecture, interaction design, visual design, usability engineering, and UX design. In some cases, people use these terms almost interchangeably. This article provides a lexicon of these terms and more clearly defines the role of the user experience designer.
Information architecture (IA) focuses on the organization of data—that is, how data is structured from a user’s perspective, as opposed to the system, or technical, perspective.
At the level of an entire Web site, or application, information architecture determines what data is on each page and how pages relate to each other. For example, defining a site map is an IA activity. At the level of an individual page layout, information architecture ensures that data is logically grouped and interrelated. Read More