Thu, Mar 29, 2007
Where does IA fit in the design process? (IA Summit 2007)
This was one of the presentations I really enjoyed.
This was one of the presentations I really enjoyed. Not so much for exposing me to something new, as much for exposing me to new ways of saying old things. (Sounds unsexy, but the good libertine always needs new pickup lines.)
The most important thing about a defined design process is that it helps communicate what we do to non-designers or non-IAs. Day-to-day work may never really map against a defined process, but our collections of tools, methods, and deliverables help us frame and communicate problems and solutions.
Everyone pretty much agreed their process was really more of a toolbox: you pull out the tools you need for a given project.
This echoes an interesting chameleon theme that emerged at the Summit. We change who we are and how we work based on the cultural and project context. I think most of us share the same sense of perspective, and this might explain why the IAs really are a tight-knit, community-oriented group of people. We share a culture; not just a discipline or field.
(From a cultural perspective, I think it’s interesting how SXSW, UPA, and the Summit all feel very different.)
Talk About "Where does IA fit in the design process? (IA Summit 2007)"