The Structure of Complexity With the 2020 events for World IA Day (est. 2012) and the IA Conference (est. as IA Summit in 2000) approaching, the team here at Boxes and Arrows is taking this opportunity to highlight the importance of Information Architecture (IA). We reached out to some pillars of the IA community to … Continue reading Information Architecture Expert Panel – Part One
Imagine if you will information architecture as a pimply-faced, malcontent teenager. IA is eager to express and redefine itself. It wants to be an individual yet accepted by its peers. It is simultaneously aggravated and apathetic about its parents, mentors, and role-models. It is a bit of a mess, but a wonderful, beautiful mess with … Continue reading Information Architecture’s Teenage Dilemma
In this podcast, Jeff Parks talks with Jessica DuVerneay, the Global Director for the first annual World Information Architecture Day, held in February 2012.
Audio content is becoming increasingly prevalent. How do you design it effectively? Jens Jacobsen combines information architecture, journalism, usability engineering, and interface design to resolve some of the issues that arise from introducing audio.
Part 1 Content Management Systems promise so much: content is easier to publish, easier to update, and easier to find and use. Lots of promises, but do CMSs really deliver? Masood Nasser examines why Content Management Systems often fail and shows how Information Architecture can come to the rescue.
People disagree on what happens when IAs grow up, but Tom Reamy knows. He offers a foundation for information architecture as it advances, grappling with problems across the enterprise.
At least several times a year, I try (I really do) to set up folders to sort my email. I am an information architect, after all. Setting up folders is, according to my job description, my area of expertise. Actually, I suck at setting up folders for email.
The efforts to define our field and our role are understandable by-products of our economic times and of forces in our contexts of practice. What are the pressures behind this quest for definition? What are the options (and potential advantages) of refusing to pigeonhole ourselves?
We’ve all seen blueprints–formally known as contract documents–which architects produce and builders use to construct. No one person knows all the details of the design; the end result is entirely a product of teamwork. But there is one axiom: architects do not build.
Long before anyone was looking for “godfathers” of information architecture, our fellow species were wrestling with some of the same problems we face today. The real godfathers of information architecture, as it turns out, emerged a very long time ago with the earliest origins of life on this planet.