UXmatters has published 25 editions of the column Finding Our Way.
“The practice of information architecture is the effort of organizing and relating information in a way that simplifies how people navigate and use information on the Web.”—DSIA Research Initiative
Over the past two decades, the volatile evolution of Web applications and services has resulted in organizational uncertainty that has kept our understanding and framing of the information architect in constant flux. In the meantime, the reality of getting things done has resulted in a professional environment where the information architect is less important than the practitioner of information architecture (IA). Read More
The title of this column could have been “Getting Your Information Architecture Right.” But, to be honest, my guess is that the majority of people still don’t understand information architecture and the value that it brings to Web sites and other information-technology experiences. Uttering the term information architecture when speaking to a sophisticated business person or even an intelligent lay person typically leads to raised eyebrows and a tilted head—that is, an expression of perplexity—or perhaps curiosity.
While information architecture, as a term, sounds impressive, it consists of two concepts that can be difficult to grasp—even for IA practitioners and academics.
Even though the average person deals with many forms of information every day, people’s popular view of information is as an abstract idea that applies to just about anything. Anything can be information. As for the term architecture, it’s equally troublesome. 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