The Holy Grail of Information Architecture
Christopher Fahey writes about our tendencies to box our design deliverables -- try to get at a procedure or a master process document, the holy grail as he calls it. He suggests that we have an open mind and try out different ideas when communicating design:
Every client/project is unique. We simply cannot assume that any deliverable template will work for every job. Templates are great for “normal” design tasks, but more and more interaction design tasks simply aren’t normal.
This is the first reason why the Holy Grail will never be found.
Page 1 of 2 pages