A List Apart
Brightly Colored Food
City of Sound
Croc o' Lyle
Digital Web Magazine
Dive Into Mark
Guide to ease
Joel on Software
Noise Between Stations
Off the top
Signal vs. Noise
Leisa Reichelt of Disambiguity.com posted earlier this month against content inventories, positing that they immerse you in the status quo of the content types and approaches.
Her position is interesting, but we'd like to hear from you about how you react to this post. How have content inventories affected your process and creativity on projects? Is completing a content inventory as one of your first major IA tasks good or bad?
The responses to this question gave a nice blend of ideas, mainly that the initial runthrough of the content at the start of a project can be thorough, but likely should not be the final, detailed audit.
Also, there is a desire to clarify the terms at work here. One person’s “content survey” is another’s “content inventory.” Or, one person’s “content inventory” is another’s “content audit.”
The responses to this question suggest the following continuum for the level of detail:
(Least detail) Content survey > content inventory > content audit (More detail)
They key to avoiding content myopia is to look at content produced not only for the website, but also via traditional means, feeds, competitive research, and adding in the desired additional functionality.
Look for ways to take content, add effective markup, and allow people the ability to build upon it – very Web 2.0.
The existing content provides lots of insight into what has come before, informs your ideation for the project, and indicates where issues may arise.
An IA that becomes “indoctrinated” by existing content is not doing a good job. One way to learn about your client company (not the users) is to examine what content is on the site. Time and budget are factors here.
The interesting thing here is the discussion around the differences, if any, between a content “survey” and content “inventory.” This shows that the practices is still in the formative stages and that there should be an agreement at some point in the future.
In the end, which you do is determined by the project and the client (whether internal or external – ed).
Content inventories should be considered roadmaps, and it will become apparent when old content is not needed.
Sketch earlier to create artifacts and shared context. Many artifacts are much simpler to create and digest than content inventories - prototypes, comics, sketches, participatory design, games, etc. Numerous UX professionals are now doing so with much success, and the idea was promoted about 50 years ago - see Henry Dreyfuss’ 1956 classic "Designing For People."
Hello, Information Architecture fans.
To share the insights gleaned from years of deep dives into Information Architecture and the various User Experience areas of practice, every two weeks we will pose a question to the Information Architecture Institute's member mailing list, collect the responses, then summarize the key discussion points right here on iaslash.org.
Look for the first summary in the next couple days.