From wireframe to design
I found this video on Twitter today and it’s fascinating to watch how much specification and wireframing was done. In the end I believe the title for this video The right way to wireframe due to the finished product.
A very important aspect when you wireframe is that the designer should feel comfortable and understand the idea you want to pass to him and not get stuck to the display of the wireframe. Meaning that a square doesn't need to be a square, the designer should be creative.
The video was create by Michael Leis and as he describes on the youtube video page wireframing is defining a communication strategy and I have seen many wireframes that although with interesting concepts, best practices, good architecture and so on many times lacks on communication.
Buzz thisIncreasingly, as designers of interactive systems (spaces, processes and products for people), we find ourselves stretching the limits of communication tools to explore and document what it will be like to interact with the things we design.
We describe wireframing as a form of design communication that enables stakeholders, team members, users and clients to gain first-hand appreciation of existing or future problem spaces and solutions.
We create wireframes to inform both design process and design decisions. Wireframes range from sketches and different kind of models at various levels of fidelity looks like, behaves like, works like to explore and communicate propositions about the design and its context.
We think that the wireframing strategies user experience designers use are often constrained by the tools they feel most comfortable with: problem space, domain, expertise, theme, context of problem, bias towards types of design tools and documents, timeliness of artifacts created. For this reason, a session that attacks one business problem from the perspective of four different designers will provide attendees with a unique understanding and set of strategies and tactics to improve their own practice.

