 | |  |  | 

Traditionally, information architects and designers (UI, visual, ID) are creatures of process. We generally work in prescribed ways—discover, design, validate, repeat. We sketch first, then create rough flows and then finetuned detailed wireframes and mocks. This usually works well, once accepted, and most companies—whether in-house teams or consultancies—work along similar lines.
In my experience, I have found that creating and documenting process has been a good exercise to help institutionalize ways of working, to help educate new team members as well as to unveil the mysteries of what we do for executives, product folks, and development teams. View all 19 works by Malone, Erin View all 311 works published by Boxes and Arrows |
 The Power of Process, The Perils of Process http://www.boxesandarrows.com/archives/the_power_of_process_the_perils_of_process.php
Malone, Erin Boxes and Arrows 2003
Abstract: Traditionally, information architects and designers (UI, visual, ID) are creatures of process. We generally work in prescribed ways—discover, design, validate, repeat. We sketch first, then create rough flows and then finetuned detailed wireframes and mocks. This usually works well, once accepted, and most companies—whether in-house teams or consultancies—work along similar lines.
In my experience, I have found that creating and documenting process has been a good exercise to help institutionalize ways of working, to help educate new team members as well as to unveil the mysteries of what we do for executives, product folks, and development teams.
|
 |
 |  |