As often as not, when I’m confronted with a redesign project, the reason behind it is “I’m tired of this look” or “this just doesn’t look modern.” Well, that’s fine. After all, if you redesign your website, the reason for it IS certainly closely tied to the way it looks. However, in my mind, just changing the appearance of a site is not sufficient reason to do that kind of work.

A website redesign is about creating a better website.

One of the services I’ve done for people for quite a while is WordPress installations. These are people who already have websites and want to add a blog — I simply install WordPress for them and create a theme which clones the look and feel of their existing site. It’s not an incredibly challenging job, so I can offer it quickly at a pretty reasonable price point. (These projects have little to do with website usability or accessibility, and a lot to do with paying the mortgage, by the way. Don’t look for these sites. They’re not up to my standards in most other respects.) As a result, I’ve now been doing this long enough that I’m getting the occasional blog redesign. Businesses have had their main website redesigned, and they’re coming back to me to have the blog matched to the design.

Sometimes, this can be a very depressing task. It’s not necessarily that the old site was fantastic — but my central principal behind ANY redesign project is to improve the site. It should have higher quality code, better accessibility, better search engine optimization, better marketability and a better design.

And sometimes, these redesigned sites just don’t have ANY of these qualities. Why was the site redesigned? What drove this change? I know the answer, to some degree — a new marketing director may have been hired and felt that they needed to put their stamp on the site, for example. But it’s frustrating enough to implement WordPress patched into somebody’s sloppily coded, transitional, hack-filled CSS site — converting the same site over to a table-based site with nominal use of CSS and no Doctype at all 6 months later is just maddening.

This is why, when I’m hired to redesign a website, I always start the process by talking with the client about what we should improve. I want to make certain that we’re both clearly aware of all the diverse changes which will be made besides the most apparent shift in visual appearance. If a site hasn’t had a functional improvement as well as a visual improvement when I’m finished with it, I feel disappointed in the project. I’d like the site owner to understand the degree to which their site has been changed.

I don’t feel the need to go into a highly technical conversation on every semantic decision, of course. However, conveying a basic sense of the importance of accessibility, standards, usability and search visibility to the client (as well as any other -ilities that come to mind,) is something which I consider to be well worth the time.