Peter, thanks for the post. This overview describes what I do pretty closely. IA oversees the center point where information/data, applications or computational calculations, and usable interfaces for these meet. The IA can more than one, if not all the analytical/development/design roles and knows (or can work to) the structures that will efficiently make these applications, products, or projects function efficiently. The IA removes themselves from the focus to put the user at the center of the focus.

Most every digital endeavor begins with a problem to be solved and information. The IA understands that the data/information must be structured and stored in retrievable manner. The IA understands that programming an application that is fast and efficient is lost if the interface is designed and developed poorly. The IA knows a stellar interface is useless with out a properly built application or the data is in poor condition (not properly stored, filled with errors, missing values, not understood, and/or is with out context). This overview describes what I do pretty closely. IA oversees the center point where information/data, applications or computational calculations, and usable interfaces for these meet. The IA can more than one, if not all the analytical/development/design roles and knows (or can work to) the structures that will efficiently make these applications, products, or projects function efficiently. The IA removes themselves from the focus to put the user at the center of the focus.

Most every digital endeavor begins with a problem to be solved and information. The IA understands that the data/information must be structured and stored in retrievable manner. The IA understands that programming an application that is fast and efficient is lost if the interface is designed and developed poorly. The IA knows a stellar interface is useless with out a properly built application or the data is in poor condition (not properly stored, filled with errors, missing values, not understood, and/or is with out context). Many of those developing focus on their particular roles or skill sets, but the IA forms putty that holds the separate pieces together.

Each person on a team should have some role and focus on IA, this is rarely anyone persons role. Most on a team can cover some other role to some degree, with programmers knowing some graphic design or data modeling skills. The project manager often fills this center point, but also rarely comes to the table with enough of an understanding of IA. As most teams have a great designer, a great programmer, database designer, and systems person the role of IA is the central piece to ensure everything is tied together and usable. The IA is often the person that knows who on the team needs to talk with whom to sort out difficulties that may be problematic.

The part of your article that resonates with me is the importance for everyone on a project to think about the user, not just an IA. Problem becomes then that everyone thinks they are an IA because they contribute to IA. Better than the alternate, I guess, with people not valuing the contribution of IA to a project's success.

you are not full of shit peter ;)

So. Am I full of shit? Did I spur any of your own thoughts? Put 'em here!