Andy Clarke: Time to stop showing clients static design visuals

• Rated 4 stars out of 5.
• 

I totally agree with Andy that it makes a lot of sense to show clients HTML/CSS/JS prototypes rather than static visuals, but I'm not sure how to reconcile this with the needs of our clients, as well as our resources at Blue Flavor. For us, the trouble with interactive prototypes is twofold: 1. Clients tend to want to see constant updates along the way. If we don't show them anything until we've got an interactive prototype, they're not going to be very happy. 2. Getting all the way to an interactive prototype is a lot of work. If we get there, show it to clients, and it turns out they're not happy with the direction, we have to re-do a *ton* of work. This is one of the main reasons we like to show a lot of progress along the way. If at any point the client isn't satisfied, we can't quickly change course without redoing a whole lot of work. In short: I totally agree with Andy, but saying "we should do interactive prototypes instead of static design visuals," is the easy part. Figuring out how to *actually make that work* within your business model is harder. If you can pull it off, awesome.

• Web Address: http://forabeautifulweb.com/blog/about/time_to_stop_showing_clients_static_design_visuals/
• Short Name: doscoye
• Short Link: http://ma.gnolia.com/doscoye
• Tags: andyclarke, webdesign, business
• Saved by Jeff Croft on September 26, 2008.
• Bookmark licensed under Creative Commons Attribution Non-commercial Share Alike 2.5.