At the IA Summit earlier this year I had the pleasure of chatting with the brilliant and affable Carrie Hane over lunch about structured content, prototyping, and connected data approaches to IA. One of the things that had us both in a bit of a quandary was what to do about “the site map.” Being an “organizer,” that neat hierarchy of tidy boxes and connections has a lot of appeal. And clients love them: they get to see where all their stuff goes! But when designing large scale digital content organization systems (you know, “websites”) for dynamic, evolving collections of content, creating that map of “where everything goes” seems to have become, in equal measures, increasingly laborious, and increasingly short lived. ... continue reading
Here is a video and complete transcript of my 2018 Information Architecture Summit talk on prototyping information architecture with dynamic content, “Prototyping Information Architecture,” delivered in March 2018 in Chicago. ... continue reading
Just when it seems we’re starting to get our heads around the mobile revolution, another design challenge has risen up fiercer and larger right behind it: the Internet of Things. The rise in popularity of “wearables” and the growing activity around NFC and Bluetooth LE technologies are pushing the Internet of Things increasingly closer to the mainstream consumer market. Just as some challenges of mobile computing were pointedly addressed by responsive web design and adaptive content, we must carefully evaluate our approach to integration, implementation, and interface in this emerging context if we hope to see it become an enriching part people’s daily lives (and not just another source of anger and frustration).
It is with this goal in mind that I would like to offer a series of posts as one starting point for a conversation about user interface design, user experience design, and information architecture for connected environments. I’ll begin by discussing the functional relationship between user interface design and information architecture, and by drawing out some implications of this relationship for user experience as a whole. ... continue reading
To code or not to code? For designers, that’s a very contentious question. Clients like designers who code because (among other reasons) that’s one less body on payroll. Design advocates, on the other hand, often see code as a technical limitation that stifles creativity. To make matters worse, the information ecologies we all work in refuse to stand still. By looking carefully at some of our favorite arguments, however – and by taking them within the context of our ever-evolving digital landscape – we can begin to make a case for when working in code makes sense. ... continue reading