[Sigia-l] you're invited- ART OF THE PROPOSAL- NYC

[Jody A. Hankinson]

I'm not so sure I agree with your assertion. There's a difference between
*rapid* and not-so-rapid prototypes. I've used *rapid* prototypes for a type
of hands-on brainstorming. Wireframes would not be helpful in that
situation. And certainly not if the prototype is being used as part of a
pitch. There may be a need for wireframes later in the process, but not if
prototype can be amended to communicate the information I would put in the
wireframe.

I think my contention is with your language - it sounds absolutist. In my
practice I've found flexibility is the key. I can't imagine being in a
situation where I would included an activity that isn't essential.

Out of curiosity, did you read the event announcement or are you only
responding to Ziya?

Jody A. Hankinson  
   Information Architect ......| Interpreting strategy and processes
e: hank99 at bway.net             | into Internet applications.
t: 917.749.0910  
w: www.bway.net/~hank99



On 10/30/02 6:36 PM, "Christina Wodtke" <cwodtke at eleganthack.com> wrote:
 
> 
> rapid prototyping should be done *with* wireframes. "and" not "or"
> 
> or perhaps "then"