Close and Go BackBack to Viget

Properly Focusing Clients on “The Look” of Their Site

Peyton Crump
Peyton Crump, ON THE TOPIC OF Favorites and Tips and Tricks
Mar11 5

Viget works with a wide variety of clients with varying depths of web knowledge. Some simply have a business plan based on a strong idea, while others have designed, built, or maintained sites themselves. Regardless of this level of understanding, there’s one thing we all “opinionate” and iterate on — the look of the site. Aesthetic is typically unique in that all of the stakeholders in the project can and want to have input. After all, if we can see, we tend to have preferences for colors, layout, photo selection, font styles, etc. So the visual design of sites is typically an iterative dance between the subjective opinions of those involved, the established goals of the site, and the more objective “rules” of good web design.

Hopefully, the client is involved in or aware of all of the planning (sitemapping, wireframing, defining of audiences and actions) before the look is ever approached. Occasionally, even when they are involved in the planning, clients lean toward an unproductive and over-iterative focus on aesthetic. Many times, this is simply because we as designers allow the client to see visual decisions as a separate “phase” of the project, and they unconsciously become detached from the rest of the site goals for a short time.

So, a simple suggestion to keep a healthy, balanced perspective toward aesthetic — at the beginning of any visual evaluation (competitor site reviews, mood boards, comps), simply take two minutes to clarify with the client that visual design is much more than preferences/decisions on color, photos, and layout. Remind her that visual direction must always be evaluated in the light of:

Users/Actions

How will intended users perceive this design? Are the actions they’re meant to take apparent?

Aesthetic

How does it look? What feeling does it evoke? Are colors/fonts used appropriately? How is the brand being used/reflected?

Content/Data

What information are we offering through this design? What are we collecting? Are the content areas being given proper design attention and priority?

Functionality

Is the content/data/technology that we have available being leveraged to create appropriate and interesting features?

Usability

How easy or hard is it to use the page/site? Is the content visually prioritized, is it easy to find, and is the user effortlessly able to take intended actions? Is usability suffering because of other poor decisions?

These simple ground rules for evaluating the look of a site tend to get everyone more healthily engaged in making design decisions. Decrease subjectivity and iterations, increase objectivity and communication, and maintain focus on the larger site goals.

Rob Soule said on 03/11 at 07:56 AM

Great writeup Crump, thanks!

Harry Roberts said on 03/13 at 12:14 AM

Very good article. It’s something that clients really need to be made aware of from the outset.

Harry

Ty (tzmedia) said on 03/13 at 09:03 AM

Nice politically correct (PC) write-up P.C. :)
This scientific run down should distract clients who as you say see visual design decisions as a separate phase of the project. We’ve all seen that.

How about the client who wants to finesse the text layout, which is really structural html decisions now days, only to send in a whole new rewrite of the content anyways. Any suggestions there ...prompting for final content?

Peyton Crump said on 03/17 at 05:07 AM

@Ty - Yes, in general, it seems like the earlier final content can be nailed down, the better. In an ideal world and as a designer, I’d love to have final content before the visual design even begins. Also, making sure that hours are budgeted specifically for content design and clearly defining at what point content changes/styling will need to become a part of a follow-up task order are helpful. Again, when clients truly get that content is as much a part of the design as aesthetic, they’ll generally understand the benefits of getting final content into the mix earlier.

Not sure what type of projects you work on, but content creation and delivery especially seem to be a problem on some of the smaller marketing type sites (web apps, on the other hand, generally require that content be considered as a part of the design). Unfortunately, the approach toward marketing-type sites for years has been to get a general idea of the content, design a home page and secondary page template, and then throw the content in at the end. The general excuse was that smaller budgets simply didn’t support “content” design. This type of process/mentality really downplays the importance of content and its design and typically allows clients to drag their feet on and change their minds about content.

Great topic in itself.

Matt Crest said on 04/11 at 01:51 PM

@Peyton - Great write-up, and even better insight in the follow up to Ty’s question. I definitely agree with that.

Here’s another question: say you do get “final” content prior to the design and layout phase and the design compliments the content perfectly. Do you have any insight into applying this mentality to a CMS integrated site - where the content is changing and the client is managing things? I’ve seen some people create content/copywriting guides - any other suggestions?

Name:

Email:

URL:

Not a robot? Prove it by entering the word below.


Remember my personal information

Notify me of follow-up comments?

We're The Designers

at Viget Labs. We write about design news, trends, techniques, buildout, inspiration, CSS, and our projects.

So Can You:

Viget's hiring a Senior Designer, a Front-End Developer, and Web Designers. Find out more »

Recent Comments

JQuery is cool. I recently combo’d it with shadowbox.js to make a gallery of recent projects. The cycle.js plug-in is also worth looking at for lots of ‘Flash-like’ transitions and animations.

Subscribe to Comments RSS RSS