> Yeah, clients are always going to want to know what it's going to "look like." However, I've found it extremely helpful to segregate > the wireframing from the design.
> In my experience, most clients put the cart before the horse, concentrating way too much (or too early, or both) on the aesthetics > without giving much thought to how their site/app/whatever needs to work, how information will be delivered, etc. But what they > don't realize is that it is, in fact, the information/content/etc. that should be driving the design, not the other way around. Amen to this! I can't count the number of times I've seen a beautiful design get completely hosed because the client decided at the last minute that half a dozen app functions should suddenly get Top Nav treatment. Nailing down the functional requirements first can be really helpful in determining what needs to be included in the design and how it needs to be treated (what's important, what's 2nd level, etc). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:340981 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
