Friday May 22, 2009
Last week, Matt Donovan twittered (tweeted?) “Wireframes don’t help web design. I need to start using this process more: 1. Sketch 2. Prototype (when necessary) 3. Implement”.
I echo that sentiment in many cases. But besides just reducing document debt, sketching/prototyping is a positive way to build teams. Creating requirements specs and other such documents are essentially contracts, which are (potentially) divisive means of defining relationships.
The collaboration required to develop prototypes also develops relationships that are more capable to work through differences later in the project.