24 March 2009
You should have the most impact on your design. The designer shouldn't give a pale pink background when you asked for purple. You need to work together with your preferred colours, fonts, etc. If you don't like something say so, your the boss.

25 March 2009
Hi Steve

Ideally it should be a balance, between you and the designer. But ultimately it's your site, and you're paying for it - so you should get the final say. But bear in mind your ideas (or clients' ideas in general) may be wrong - so it's on your head if it fails!

If you've chosen a good designer, and they know what they're talking about, then it is worth listening to their opinion. As you say it is their job. Do you like the other work they've done, and can they explain their design choices to you - i.e. the reasons their option will work better than yours?

I would usually design something first in the way it would work best (in my professional opinion). Some clients do then ask for changes, and if I disagreed I would explain my reasons for doing what I did. Some then accept that, others still insist on change, at which point I would do what they want.

All design is subjective, and without seeing yours obviously I can't comment who is 'right' or 'wrong'. But not everyone will agree on everything, and your customers might have another different view altogether. The best thing would be to show it to a cross section of people (typical target market if possible) and then make changes based on their feedback. And if you can get the designer to release both versions so people can compare, that would be even better.

Kind regards

Emma
Clarified Web Design

25 March 2009
Steve,

I agree with some of the things that have been mentioned in the previous posts, and others I don't... I think it may simply be semantics, but here is my take on things.

As stated before, web design, well, all design, is subjective and while some things work and others don't the end result should be that you are happy with what you are paying for.

You may have a better idea of what works for a specific demographic in your area than what works for the same demographic in a different area. So the design you are looking for is something that you should have. If a designer gives you feedback, and you listen and still would like changes, it should not be considered, "insisting on changes".

There is a whole study on colors, and imagery, etc, etc, that affect the human psyche, but I would venture to guess that the percentage of web developers that are even aware of their full scope... myself included, is rather now... like, well, none. But I do know without a doubt that anyone who designs graphics gets offended on some level when someone critics their work. The whole, "client wants client gets" attitude gets thrown out the window when developers consider that anything they do should be the next, "Masterpiece" of their portfolio.

Now, all that having been said, you are hiring a web developer for a reason. You should expect, and should consider advice given from someone who makes a living doing the very thing you have hired them to do. BUT, while you receive advice, remember that the same advice from another developer may differ... don't be afraid to get feedback from another designer, friends, and friends of friends. The more diverse group of people you can get opinions from, the better picture you will get for what is going to work well for your completed design.

While designers get married to their designs, clients too are prone to getting married to their own design ideas as well. Don't be in a hurry, your designer should quote you on a price by the job you want, not by the hour. It's an important decision you have made to have a website developed and you should not be rushed through the process and end up with something that you are not happy with. If your designer is offended by you getting feedback from others, then maybe you need to reconsider your option of designer... It is important to keep things moving in a forward direction however, small changes and adjustments toward a final design should be expected; completely changing direction should be billed accordingly!

So, what does all that mean? Build a relationship with your designer/developer, but remember that you are in a business transaction. If you are buying a car and want it blue, but your car dealer says, "No, I think green would be better", I would hope that you would find a different sales person, or a different car dealer. Same thing, only different!

Cheers

30 March 2009
You need to buy 2 books without your designer knowing:

- Don't tell me to think
- Design of sites


The first is pretty small and you could probably get through it on the way to work (if you go by train). By the end of it you will have a relly good idea of what works and what doesn't.
The second is a monster of a book, it is not desinged to be read front to back, but is split into sections so you can pick and choose the good practives you need depending on the type of site you are building. It also goes over all of the design basics, color vs layout vs acesibility etc.
To start with just read the intro sections and then the section pertaining to for your project.

Once you have done this, go over the new design and look through it again, you will have changed your mind on some things, but you may agree with the designer on some as well.

I am not a designer - I build things to work, not look good -, my desinger and I have a copy each of these books and use them as reference points for every project we work on.


But remember also to get other people outside you environment to look over the deisngs and give you and you designer feedback, many eyes make lite work?


goodluck and I hope that helps,
craig

30 March 2009
....is its your money & its you & your company which will look at the site everyday! A good designer can suggest the latest trends in design & technologies, but doesnt necessarily know your market - dont be afraid to say "I hear you - but I dont like it". A good designer will listen.

Good luck with it!
scotia ;)

30 March 2009
Well ultimately as others have pointed out your paying so if push comes to shove the final say is really yours.

However if you have chosen a *good* designer and note there is a difference between a 'designer' and a 'developer' - then they will be able to talk you through their rationale and the processes behind the design. And if you like their previous work - listen to the reasons.

They be willing to provide alternative designs and help you through the process - if your stuck at an impasse they should be professional enough to work through and resolve the situation.

I've had clients in the past literally cut up my designs and stick them back together via Photoshop in a fun "The board and CEO" came up with this as the 'final' design type game! Well as the professional its up to me to ask why they made the changes, what they were trying to achieve and then apply their thoughts to the design - and make it work.

95% of the time in this scenario when I present MY revised versions with explanations and examples of why my design works and theirs doesn't (Without upsetting them!) they can see why and more importantly understand why I've made the decisions that I have .

5% of the time they go with what they want - and that's fine - all I can do is try my best..

99% however we provide a fantastic design that works both for the market AND for the client.

31 March 2009
I think the design process should be a collaborative effort. Both the client and the design team bring something to the table. While we do some preliminary research of our client's industry prior to accepting him/her as a client, we do understand that the client knows his business, his industry and his competitors better than we do.

It's important to communicate your wishes to your web designer. While I understand your frustration and the comments of some others (It's your design, you're paying for it, you should be happy), it's also true that there are nuances of web design that the client simply cannot possibly be aware of. That's why they hire the professional. You don't tell your doctor how to remove your spleen now, do you?

So the goal is to meet somewhere in the middle, where the client's design desires are met while delivering a site that will drive customers to it, not away from it. :)

31 March 2009
Hi Steve

While it's your money and your website, the designer is trying to provide a solution to your problem and you should bear with him. Hopefully he'll be able to explain why he's made the design decisions he has, you're paying for his design skills remember and hopefully his design is aimed at what the customer/client likes not what you like.

If he has a portfolio of professional looking designs which fit nicely with their respective businesses, then he probably knows what he's doing.

Have you tried showing his design to anyone else to get their feedback? Customers would be ideal, but perhaps you should see what other people think. You're not the target audience after all, your customers are.

Hope that helps
david@achroma.co.uk

31 March 2009
Hi Steve,

Sounds like you may have teamed up with the wrong web developer and you are not gelling at all well.

I would advise you to attempt to find a different more approachable web developer and establish some good ground rules before you embark on the project with them to ensure that this situation doesn't arise again going forward.

Regards,

Tony Green
Webography

4 April 2009
design your homepage with relative activties of your business, if you are not into creative services, you dont need a million dollar web design, just make sure visitors find your website easy to navigate, they are able to find / locate what products or services you are offering.

8 April 2009
Steve

Certainly this is a problem that comes up in the design process from time to time. But it is exactly that; a process, nothing is written in stone.

To be honest I personally have produced 10+ websites for clients that I will never add to our profile, basically because whatever advice we provide the customer is always right.

So the simple answer is listen to what your designer is suggesting certainly but use your own common sense, look at the competition (as the designer should have done), get the oppinion of colleagues and friends even then make your judgement.

You are paying after all and should get what you want !!

Please contact me if you have any questions or require advice.

Regards

Ashley Smith

Acknowledged Web Solutions

ashley.smith@acknowledgedsolutions.co.uk

14 April 2009
The client is always important! However we find that some clients are guilty of being self indulgent about their business, pleasing themselves and not their customers.

Take care before dismisisng your designer as he / she will most likely have a more balanced approach that;s not just self satisfying.

Peter Farrell
http://www.doodleit.co.uk

17 April 2009
You are the client and there should get exactly what you want.

The designer should the be able to incorporate your ideas into a design that is both exactly what you want and that also achieves the results you want.

We work with the client in order to create a single page, test design, that we get right and agree before the rest of the site is completed. This way both parties know where they stand.

18 April 2009
I have this issue with clients but only Ocassionally, I would only ever tell a client "no" to a particular design or element if I felt it would hurt their business in any way.

My normal MO is to get a blank sheet of paper and basically draw the site out in rough and then I translate that into a design. Now and again I will get a client that insists on using a particular layout or keywords or domain and it's at that point that I usually layout my reasons for why I am designing a project a particular way, then they still have the option to do what they want.

I hope that's of some use to you.

8 May 2009
Customer is the king
We offer our customers qualified support and are proud to say that we have maintained a 100% customer satisfaction!
We want to delight our customers from our initial contact to the continuance of future program execution.