Forum Moderators: not2easy
So, we build a new Web 2.0 Template, nice and clean, validates, 100% fluid, a real work of art I think, and so did many others during the redesign. The initial responses from the client were not what we expected...
"Wow, everything is so big now, can we have it small again?"
"It fills my entire screen, I want it centered in the middle."
"Can you make the fonts smaller again?"
"Why the Expand/Collapse options? Can we have the long scrolling pages again?"
You'd really be surprised at some of the responses from the client.
So, I got to thinking, why was this such a "big change" for him? I think its because we've been stuck in the 800x600 mentality way too long. And, with 12px fixed font sizes, fixed widths, everything was all scrunched into the middle of the screen.
The new layout is "pure". We're going to make modifications to compromise but I think after he's used it for a while we'll get the okay to proceed. It really is a work of art. The fluidness has added a usability factor that we not had before. And, with the growth of the backend applications, the amount of data we are displaying just would not work in a fixed width non-fluid environment.
So, what's your take on it? How often should we redesign and/or upgrade our websites look and feel, functionality, usability, etc? I know, its an ongoing daily grind for many of us but in this instance, is four years a bit too long? We missed a couple of screen size jumps during that time so what we had finally became this little portrait size website in the center of a large landscape universe. :)
I think you need to make the change and convince him of it, otherwise the site will become stagnant.
We modify our travel site about every 2 years. Some changes have been drastic (static to CMS) while others were simple rearrangements or color/icon changes.
We never once heard any complaints and business grew steadily. We'll be making another major change next month... I'm looking forward to it.
As a designer you always want to make things better. Me, I only re-design if the client specifically asks me too. It can cause too many headaches for both parties otherwise.
dc
Four years is really too long, but you do have to strike a balance between too much change and too little, because it costs a lot of money/time to be always redesigning. If your design is pure CSS, however, you can always give people the option of going back to the old design if they preferred it for some reason.
Some of the online electronics stores I use have designs that have been around for many years. And it still works fine. If they 'updated' the design that'd be bad for us customers.
I haven't updated the design on some of my sites for many, many years. They're clean, simple layouts with a bit of CSS. Almost not 'designs' at all. They rank just fine and I still occassionally get compliments from visitors.
and to the answer of you rquestion.. i think a site design should not be changed unless necessary BUT there should be constant changes and improvements. for ex. when we create a funky feature or a nicer photo album we might as well add it to a couple of customers. users and clients like to see improvments, over 4 years the site will be different and users would get pissed at you for changing everything.
I remember - a while back - a company I consulted for moved 2 websites of a client from older design and php platform to Windows...I didn't have much saying 'cause they had "know it all" boss and tech lead. We missed deadline by a large margin, and eventually got fired. Too much change, too many things got broken, including 404's, 301's, SEO and such...that client is now on iteration 3 with .NET, completely different webdev company.
Rule #2: Small incremental changes are better than full-blown over hauls.
On my sites, we have been slowly incrementing the width of the pages to fit the more popular 1024x768 screen sizes... By doing it slowly over a few months, no one has even noticed, or commented... ;-)
I imagine I'd feel the same way about about a website that changed too radically too often. In fact, I can think of one that does - and I don't use it anymore at all.
100% is nowadays not the best option
why: reading a page 100% width on a large monitor is a pain for the eyes, to the point that 1,2,3 you loose interest and click away...
a nice fluid design is built around a mini/maxi
so it looks good from X width to X width
Quite true, but there are (sometimes) ways around it. I have yet to find a perfect solution, but often just keeping the main "reading area" down to a reasonable size works.
It has gotten harder recently with the wide range of devices that access the internet, so we are looking at changing to a semi-fluid design, where it looks good from 600 to 1300, and is at least not broken at others.
Depends on the industry of course, but if your site is more B2C then you will face a potential backlash for awhile. Assuming your new version is really easy to use you will be fine in the long run. But it will likely be a bit painful in the short term.
Updates aren't looked upon with much favour, both on the client and admin side.
Humans don't care much for change. Change puts them out of their comfort zone at times.
As far as redesign and how often? Well, that would depend on the client, but we suggest no less than every 18 months and no more than every 24 months.
However, I have noticed that established Web1.0 sites don't turn into Web2.0 sites. It is not worth it. It doesn't work. Being Web1.0 exudes history, tradition, quality - a sense that the site has been around since the start of the internet, and will therefore stick around forever. Why throw that away?
So, what's your take on it? How often should we redesign and/or upgrade our websites look and feel, functionality, usability, etc?
The answer to that is simple. When something isn't working, you change it. When you think you can make something work better, you change it. When you're not sure, you test it. The reality is, clearly, far removed from this ideal, but that's the real answer.
"Wow, everything is so big now, can we have it small again?"
"Can you make the fonts smaller again?"
"It fills my entire screen, I want it centered in the middle."
"Why the Expand/Collapse options? Can we have the long scrolling pages again?"
I always tend to err to actual sales over what the business owner thinks they want. If thats too much for them then test to prove who's right and be prepared to be proved wrong sometimes, its harder to take than you think...
Also, multi-variate is great because it allows people to really see the conversion difference, it's a great selling point.
Now, if a site doesn't monetize and is just "there because everyone has to have a website" then dangle the carrot of real measurable bottom-line change, and if they still aren't on board, just do exactly as they want and let them sink themselves.
Also, I read somewhere in WebmasterWorld that it is estimated that a design change to an e-commerce site will only increase traffic less than 3%. Does anyone recall that post?
In the end, my sentiment is - If it ain't broke, don't fix it!
Marshall
That is why I decided to take my expertise, and work to make some sites for myself and put all my energy into running those sites. I am now much happier, work less harder, have SO much less stress, and am making consistent wages at a comfortable level.
I have only two clients left, one has been a client for many years, and has become a friend. This is only because he listens to me and his business growth consistently every year.
The other was an associate who needed help after I quit design, and he is a pain in my neck alot of the time. Rarely does he listen to me, and forces me to do things I know is wrong. He is largely a charity case, a not-for-profit. It is the only reason I accepted him. I have watched as his website traffic has decline to less than 100 hits a day. All because he made ONE major mistake in a critical decision and has refused to listen to reason. He wants to know why his site traffic has declined, I tell him, and remind him I advised against that mistake. He becomes quiet, and goes away until we revisit the problem AGAIN a few months down the road. It is like groundhog day.
You can lead a horse to water, but you can't make them drink. Deal with it, or get out, as I did.