What is Behance
 
Advanced Search
Tip Exchange Creative-To-Creative Open Knowledge Exchange
Communicating with Clients
Appreciations  9
Posted on July 18, 2009 by Tendouji Chan
I would like to share some of my experience as well as seeking opinion on this issue. Lately, I have been encountering some very fussy clients. Situation goes like this.

When I meet up with client, for a web project, clients will list down features that they want for a site. Due clients' lack of knowledge in how a website works (which is why they seek for my services anyway), obviously they will only describe the sections that they need, contents, and so on. I will on the other hand, let them know on the features I can provide and what is not.

As things goes on, throughout the development, clients will start to notice that the actual features that they requested are actually not to their satisfaction, they will then ask to have these features changed. I always allow them to have a max of 5 changes for free as I too believe it is hard for both side to catch immediately on the final flow of the websites in the beginning. But as things keep on, clients, at times, may request small changes and they does not know the impact on modification of the codes.

This is the time when I will acknowledge them on the difficulties but since the explanation is at times too technical, they tend to brush off my explanation and insist on wanting it change. Sometimes, I feel that clients disbelieve my words and think that I am making up excuses and taking advantage on this situation. Certain changes may look minor to do, but on the back-end programming, it might have a huge impact on the rest of the codes.

Thing gets worse when I decide to make these changes and it affects on the project time line. Although, I have informed them on the deadlines extension, they begin to think I am providing a slow service.

I do however let them know as well that there are certain features that I will not include in the project due to time and money constraint.

I always tries to understand both side of the situation but apparently not all clients think the same.

Any comments anyone?
Created July 18, 2009
Appreciate It!
 
clients usually suck because they think they know their own trade (business, trade, etc.) but they also think they know every thing about design because they have eyes. There is a pretty good book on this. http://www.youworkforthem.com...?sku=P0551

good luck in the fight!
Posted on July 22, 2009 by THE ILL ONE
Hi Laura, that is one good link you posted! Thanks. =D I am sure it will be helpful to other fellow designers.
Posted on July 20, 2009 by Tendouji Chan
Dealing with clients truly is an art of its own, I found this article this past week when I was going through a similar ordeal. Read this blog post and found out some good tips and made me think about my methodology for dealing with clients. check it out http://carsonified.com/blog/b...o-say-yes/
Posted on July 20, 2009 by Laura Galindo
I too appreciate the link, Paul Boag is one great man. Making it clear to the client the 'roles' of your relationship will allow them to see that if you work together, it maximizes productivity. Stay positive and explain every step to them in detail so they can understand your design choices. Besides, you are the expert. I realized that there's a point where clients will test what they can or cannot do to the freelancer, and it's important to make it clear that no, they can't have the red background with yellow text or have 15 revisions. If they do keep asking for more changes, kindly indicate that there will be an additional charge associated with it.

It can be difficult being stuck in the revision stage, I wish you the best
Posted on July 21, 2009 by Robin Bastien
I've always found talking with clients that if you lower their expectations or simplify, what is produced and the methods you produce them in, you will always come across as super pro. Your situation where you tweak something which effects the whole architecture of the site can be handled through drawing a visual analogy. Initially if you explain web architecture is like a house of cards, that, buy altering something at the base you weaken and perhaps make the house fall, the client can understand simply what its like. That way you give them the idea that they must seriously think about the bits n pieces they require from your build and if mods are needed then they must be performed with diligence. You should never think of the client as dumb (big mistake) but just not educated in your speciality, hence they are justified in spending the dollars in a specialist (you) This is a great situation as it justifies their expenditure to themselves and also allows gives you the perspective to honestly say " This tweak will set us back 2 months!' without fear of having that position of 'specialist' undermined as being profiteering. Honest communication... think about talking to a mechanic about your car. Your ok to pay for a repair if its done well and the broken parts are there in a box for you to see! :) Michael
Posted on July 23, 2009 by Michael Chambers
You must be logged in to Add Knowledge
Email this Tip to a friend  |  Share This Tip
Appreciate It!  |  Appreciate It!
Save to Favorites  |  Save to Favorites
Flag as Spam  |  Flag as Spam
 
 
 
 
 
Advertisement
 
Advertisement
 
Advertisement
 
Follow Behance on Twitter
 
JobList Highlights
Cru Digital
Brisbane, Australia
ODA (A WeissComm Group Company)
San Francisco, CA
iconmobile
Santa Monica, Ca - Freelance
 
We Want Feedback