Information Pollution, Poisoning, and Hygiene, by @uxdesigncc:

https://archive.fo/NqYZ5

The Hidden Cost of Poor Navigation: How Information Architecture Directly Impacts Business Metrics, by @uxmatters.bsky.social:

https://www.uxmatters.com/mt/archives/2025/07/the-hidden-cost-of-poor-navigation-how-information-architecture-directly-impacts-business-metrics.php

Designing Information Architecture: Design Principles, by @pabini.bsky.social (@uxmatters.bsky.social):

https://www.uxmatters.com/mt/archives/2025/07/sample-chapter-designing-information-architecture-design-principles.php

The ugly ducking theorem has relevance for all efforts at organization.

https://en.wikipedia.org/wiki/Ugly_duckling_theorem

Put simply, it states that all categorization systems are fundamentally arbitrary, once all possible attributes are considered.

It's basically "proof" that common sense is contextual. For me it shows that you need to deeply engage with the people who need to find (and return) the stuff, and always include "uncategorized" for the stuff that slips between the perfect system.

"The following are my suggestions regarding what else to consider for each of Daryl White’s excellent questions about choosing a toolset for documenting a software product or project.

I have appended a brief guide to the main/broad categories of documentation toolsets and some of the platforms/components that are popular in each.

Finally, this resource ends with a table of possible solutions for various scenarios you might find yourself in.

Before we start with the existing list of questions, I want to highlight one that I think is most important of all, but which is often assumed by people who create these kinds of guides, as they tend to come from one or another world already.

What are you documenting?

When it comes to software technical writing, the more appropriate way to ask this might be: For what user roles is your documentation intended?

For graphical end-user interfaces (GUIs), the largest range of docs tooling is available, but here some of the more commercial turnkey tools have most of their advantages.

For administrator interfaces (installation, configuration, etc), again any tooling will work, but we start seeing real advantages for lightweight markup, codebase integration, and version control.

For developer interfaces, docs-as-code offers significant advantages. Developers can better contribute directly, and it’s generally friendlier for coded samples. APIs (native and remote), SDKs, and CLIs are almost certainly best documented in a docs-as-code environment, even if you integrate it with a more conventional platform for end-user docs."

https://gist.github.com/briandominick/d4cbe11228de0ebe31cda630976af4ef

As I wasn’t able to register a #c3ux assembly for #38c3 („you are not a group“), and I still hear about suboptimal #InteractionDesign and confusing #InformationArchitecture in the very materials that are supposed to lower barriers to newcomers, I will now at least wander the halls with my sparkling new LED badge occasionally displaying the hashtag.

Let’s see what comes out of it

Today it struck me that #systemsDesign and #informationArchitecture planning are 95% emotional labor 5% technical understanding. People who write great code may set up healthy structures but they only do so when a shared model has been agreed upon by the stakeholders. This sets consensus building as the first essential skill set needed to get the job done. You want a great systems architect? How are their hostage negotiation skills?

Ever wonder how U.S. highways are numbered? It’s not random; there’s a system.

I know—nerdy. But cool if you like this kind of thing.

Source:
instagram.com/reel/C85hISIotnr

I miss websites with search. Perhaps it's a case of more sites being delivered as static sites? MovableType solved static sites with search... Perhaps organizations have just given up? I don't want to build CMSes (alert: lie detected) but I miss when websites were expected to have a CMS behind them, and things like categories, tags, and search were expected. #cms #informationarchitecture

/cc relevant to @eaton 's interests

For whatever reason, my 3-year-old piece about the etymology of “godspeed” is suddenly getting some new traction. So I thought y’all might be interested, too.

https://markwyner.medium.com/information-architecture-and-the-etymology-of-godspeed-and-goodbye-5417671da6df

Are you interested in learning more about Information Architecture? Look no further than Richmond World IA Day! This global event will take place on March 2nd, 2024 in nearly 30 locations worldwide. Attendees will have the opportunity to participate in informative presentations, workshops, and discussions focused on information architecture.

Sign up now → https://buff.ly/3P11XeR

I talk with host Jorge Arango (@jarango) about layoffs and what it’s like to be laid off on his podcast, The Informed Life. This episode is a departure from his usual topic — information architecture (IA) — because the trend of layoffs has spread to all areas of the technology industry, including IA.

#layoff #layoffs #laidoff #podcast #IA #InformationArchitecture #job #jobs #employment

https://theinformed.life/2024/02/25/episode-134-joey-devilla/

What kind of dip goes with people? Should we ask the cannibals?

This is why you need a good IA/UX person on your team.

I'm thrilled my infographic "101 Derivatives of French Mother Sauces" made the longlist for the category "Arts, Entertainment & Culture" in the 2023 Information Is Beautiful Awards! I don't think it will make the shortlist as it's pretty competitive, we're competing against individuals, teams, studios and even agencies from orgs like Reuters, USA Today, MIT, and Harvard Engineering.

https://lnkd.in/exZpzXH6

Here we go! Prints will go on sale after the competition wraps up, in case they're of interest.

The best part of doing this is now I want to try making every sauce at some point

The Teacher's Guide to How to Make Sense of Any Mess: https://www.thesensemakersclub.com/teach-ia
A must-have book, that comes with slides and suggested assignments you can re-use, to teach information architecture. Worth every dollar! By Abby Covert
#InformationArchitecture #TeacherResources

Infographic WIP: 101 Derivatives of French Mother Sauces.

There are 101 "elements" now. I just have to input the last of the ingredient revisions (some sauces have ingredients but they are placeholders), proof it, then it's done.

Having a hard time tonight so I'll finish the ingredient revisions tomorrow. I think I will cut it off at 77, adding more at this point will sacrifice the readability.

Infographic WIP: 77 Derivatives of French Mother Sauces

How to Create a Content Model: https://www.sanity.io/content-modeling/how-to-create-a-content-model
A great step by step guide to help you build content models for your systems
#InformationArchitecture #ContentModel

How to Write Good Labels: https://jarango.com/2023/07/10/how-to-write-good-labels/
Labels are important for information architecture, but also for accessibility, localization, etc. @jarango walks you through the basics on good labels.
#Label #InformationArchitecture