Just to supplement Adrian and Danny's comments. I use this approach in my own projects. The documentation, in form of electronic files, should be minimum: It takes time to write and is often a bore to read. It is really inefficient to communicate this way.
It is an important element in Agile development. User Stories, a specification method, actually has a principle that a feature should be specified so vaguely that interaction with a designer, user, or other stakeholder can't be avoided. Additional notes are used for a few very illustrative points, or things that are unusual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=39000 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
