Modeling Insights

Taxonomy Boot Camp 2024 Themes & Takeaways

Image of the DC metro map, centered on Federal Triangle and the National Mall

Two weeks ago it was again my pleasure and privilege to attend Taxonomy Boot Camp (TBC) in Washington, DC. This was TBC's 20th year, and, in the four times I've attended since 2016, was the strongest argument yet for the enduring importance of well-designed and integrated taxonomies. In addition to tracks for "taxonomy fundamentals," this year's event featured tracks for "taxonomy applications," "taxonomy operations," and "advanced data and semantic layers." This is my roundup of the themes and insights that stood out to me most.

Structured Content and the Headless CMS

A Garmin smart-watch, sitting on a wooden bench.

Are you still trying to wrap your head around what structured content is, how to use it, and what the benefit is to the folks who use your content? One way to think of it is that structured content treats information as a set of ideas, concepts, and facts to communicate, each described in a way that conveys its meaning in a machine readable way. Here's a brief illustration to demonstrate what that looks like.

Domain Modeling for Structured Content

undefined

Domain modeling helps organizations discover the information structures and meaning that allow structured content to reach further and last longer. By uncovering the assumptions and tacit rules that plague your content ecosystem, domain modeling can help you facilitate the shared vision necessary to create resilient, scalable systems for communication across channels.

Structured Content Design Workflow 2022

undefined

Structured content design focuses on communicating effectively to an organization’s patrons, constituents, and customers, wherever they are and however they choose to access content. While it is the cornerstone of effective, scalable content design for the web, it’s also much more than just a “web” technique: it is a way to prioritize effective communication across contexts.

Delivering Information Architecture

A creative photograph of a cityscape focused within the lens of a camera held by a hand, with the blurry background of the sunset sky and city buildings outside the lens.

One of the greatest challenges in digital design is identifying and maintaining focus on the right problem. For information architecture, one of our most common deliverables, the visual sitemap, can actually make focusing on the right problems harder, if not impossible. In this article we’ll examine why this happens, explore what practitioners and teams can do to avoid this trap of misplaced focus, and learn how to rehabilitate our wayward sitemaps and reinstate them as the effective design artifacts they can be.

Stop Publishing Pages! – Content Strategy MeetUp Talk Highlights

undefined

The way that we consume information on the web is changing. Voice and IA technology are driving this change in a way that affects anyone publishing online. And yet: we continue to hold on to the metaphor of the content we publish as “pages,” destined to be found and read as delivered by patient, attentive online readers. I recently had the opportunity to talk with the Seattle Content Strategy MeetUp group about this alarming state of affairs—and about what we can do to fix it.

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.

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.