Laura S. Quinn explores the concept of a vision prototype in her Boxes and Arrows article: Defining Feature Sets Through Prototyping.
One of the main reasons to create a Vision Prototype is to allow the rest of the project team and the client to understand, review, and provide feedback on the vision. Because the prototype makes the ideas under discussion visible and concrete, it's common for new needs or concerns to come up at this point--even in areas that might have been completely covered in previous conversations. It's simply hard for many people to think abstractly about the same things that are made obvious by the prototype.
This looks like an interesting tool for the early stages of any development project.
Posted by Karl
November 25, 2002 01:07 PM