[Sigia-l] your'e invited- ART OF THE PROPOSAL- NYC

[Thomas Vander Wal]

I am with you Christina.  I came out of rapid prototyping environments 
where the elements have not been well defined, but layers are placed on 
on top of poorly thought through elements that have dependencies. 
Unhooking layout and interaction elements to divert a train wreck in a 
rapid prototyping environment is very costly.  I went back to my Comm 
roots and started including wireframes early on in the development 
stages a few years ago (before I know of an IA profession), because that 
is how I learned to craft message pieces for advertising and print layout.

Ensuring the layout and interaction components are set using wireframes 
should, er no, must be in the early stages of rapid prototyping. 
Skipping this step, as I have often seen in rapid prototyping, or tying 
to bring it in too late in the process leads to unhappy developer and 
often irate clients and we have not even talked about the users yet.

Just 2 cents from the school of learning through bruises and broken bones.

All the best,
Thomas

Christina Wodtke wrote:
>>>rapid prototyping often now supercedes wireframes
>>
>>About bloody time.
> 
> 
> 
> rapid prototyping should be done *with* wireframes. "and" not "or"
> 
> or perhaps "then"