I think it is worth emphasizing what Todd said. Wireframes will be around until the sophistication of the buyer gets to the point where they are not needed.
When doing consulting in large corporations or government, when you developing new tools for complex processes, wireframes allow you to focus the attention of the buyer onto the functionality within the screen. The norm in these situations is using the wireframes to flesh out the requirements. You could have done some great research, and inspired requirements documentation but odds are that most people in the room still do not get what you are trying to build. Wireframes allow you to quickly show them what it is and iterate it many more times then you ever could in a prototype or a fully design comp. Reason two has to do with detailed screen specifications. When you are designing an application to aid highly trained experts, the business rules within the system need to be documented and illustrated in a comprehensive manner. Prototypes will not cut it. Notes on comps will not cut it. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=39897 ________________________________________________________________ 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
