Information and Technology—Time for a Divorce

Information and technology have been dating since the creation of the printing press. However, they consummated their marriage in the digital age. Now it seems that they are inseparable. As the newlywed bliss has faded and the two live together, they have fallen into an enabling relationship.

Technology is the one who wears the pants in this relationship. Information is a willing subservient, waiting to see what technology will serve up.

All too often when people and organizations have trouble gaining, retrieving, or using information, they blame the technology. "Buy another server," "get more band width," or "upgrade the software." are often the answer. Do you ever hear "Are our information organization schemes optimized?" or "Do our meetings produce and use information that is useful to the Enterprise?"

The field of IA has been co-opted into the co-dependent relationships of technology and information. The practice of information architecture is the answer to structuring information for the presence on a technology platform (a website, intranet or mobile device for example).

Why should Info Architects look only at information on technology platforms? Should not the IA look at Information in any form? They should for both practical and theoretical reasons. Practically because information rarely lives solely in the digital world and theoretically because the more types of information an Info Architect sees, the better he or she better their craft.

IA Summit 09

Just finished the keynote and first session of the IA Summit. I Will post more as time permits (I hope). Added the the Twitter #ias09 feed for the duration of the Summit.

Information Archeology

I just finished a half day seminar on Information Archeology and gained a whole new insight on User Research.

Lorelei Brown and Hallie Wilfert lead the seminar and it was a very good survey of techniques for gaining user data through web analytics and research. It was a fresh and convincing approach to gaining user data for design.

While I knew what the seminar was going to be about before going into it (from the IA Summit website), I have always had a different meaning for archeology as to when it comes to Business Architectures. Namely, archeology was the act of studying, and understanding systems, applications of practices that came before. Usually archeology is performed when what came before was either poorly designed or had no consideration of architecture. In enterprise architecture circles, you often hear:

"An ounce of architecture is better than a pound of archeology."

Normally this phrase is used as a club over the head of a client who wants to
implement something without deliberate though or planning. I don't think that anyone has ever considered formalizing a practice or methodology for this use of archeology. I think I like the use of Brown and Wilfert's practice. It is a more positive application and it may be the next discipline in the IT/IM pantheon.