Insights

Perspectives, methods, case studies, and interviews about information architecture and structured content design for the modern web.

What Is Information Architecture?

undefined

Information Architecture is the process and the product of designing shared information environments. In the same way that building architects collaborate in the creation of physical environments for shared human use, information architects collaborate in the creation of information environments for shared human use. The architect may not know in detail how each wall or widget gets built, but they know enough about how all the pieces fit together as a whole to ensure that the final result effectively meets the human needs.

Conversations with Robots: Voice, Smart Agents & the Case for Structured Content

undefined

Voice user interfaces, smart software agents, and AI-powered search are changing the way users—and computers—interact with content. Whether or not you’re building services for these emerging technologies, structured content is now necessary to ensure the accuracy and integrity of your content across the evolving digital landscape.

Structured Content Design Workflow

undefined

Over the last several years I’ve become an ardent advocate of “structured content design.” This is the process of designing digital resources (like websites and apps) from the content out, as opposed to creating interaction and visual design first, then shoehorning the content into it right before (or right after) launch. A structured content approach to digital work has a number of advantages over typical “interface first” processes.

Site Maps & Connected Content

undefined

As the systems of information for which we design get more complex and more fluid (hospitals, government, and higher education are all good examples), it is increasingly important that we explicitly express the rules that underly the visible structures we deliver. So where does this leave us with site maps? They’re still effective communication tools (and clients do love them), but I think we’ve moved beyond the point where they’re a foundation of information architecture.

A Cognitive Sciences Reading List for Designers

Close up of book spines on a shelf

If you’ve ever done any contextual inquiry or usability testing, you’ve probably observed first hand the difference between what people say they will do and what they actually end up doing. Overlooked calls to action, bizarre navigation paths, mind-bogglingly irrational decisions — even the most sensible seeming users occasionally (or often) do things that “rationally” make little sense. Which is to say that we all, on occasion (or often) do things that seem to make little rational sense.

Language + Meaning + User Experience Architecture

Schematic images of three different kitchen layouts from above, showing the consistency of the kitchen triangle in each.

In order to effectively communicate across contexts in digital information spaces, we need to understand the way we make meaning as thinking animals. We also need to dig in to the details of the language and models we use to make them intelligible, both so that we can use them more effectively and so that we can leave them behind when they are hindering communication. In the same way that we construct our built environments in response to the physical mechanics of our bodies, we can construct our information environments in response to the conceptual mechanics of our minds.

Designing with Code

A stack of notebooks next to a laptop computer

With the growing need of responsive web solutions and adaptive, flexible content, there are new reasons for designers to roll up their sleeves and get into “code.” Since HTML is, at its core, a layer of description wrapped around content, working at this level helps designers think more critically about their content and about the architectural implications of that content. While considering markup won’t replace our content audit, user research, or taxonomy work any time soon, it can increasingly function as an important part of the design process.

The Trouble with Systems

A hand holding a clear spherical lens up to a computer screen of data

Much virtual ink has been spilled in the last year or two over the importance of thinking about information design in terms of systems as opposed to thinking of it as a set of carefully laid out maps. As an initial stab at defining an approach to systems informed by the way we think, I submit that information architecture is in a unique position to act as a shim between systems and sentience. IA is where we create information from data and structure that information with narrative. We use IA to wend a deliberate path through the wilds of content at large.