How to approve the site design?

Question

User interface

Hi all!
Tell me, please, what are the best ways to approve the design of the site with the client?
There are always controversial moments when a client wants to fix something, redo it, replace it - all this is time, money, and possible damaged relationships. Let's take a situation where the client is really wrong and is trying to turn the site into something terrible, based on their unprofessional opinion.
How to persuade not to make terrible adjustments, how to justify the literacy and relevance of the design?

Answer 1

Let's take a situation where the client is really wrong and is trying to turn the site into something terrible, based on their unprofessional opinion.

See what a thing. You will discuss here rather one-sidedly, because basically you are standing on one side of the barricades.
On the one hand, you need to get used to the fact that you are just service personnel who are paid loot for the release of ideas and ideas of the client. On the other hand, the client diligently tries to realize his wonderful ideas in some perverted form.
What can be advised here. Negotiate, discuss, convince.
The most correct argument is: "You don't talk like a lawyer to defend you in court."
But as before, I propose to remember that you are paid loot for the implementation of the ideas of the customer, and not for worshiping your religion.

Answer 2

First, the contract. You can write whatever you like there.
Secondly, you need to read the relevant literature. There was an example: The client wants a poisonous green button (green color design) and that it should be half the screen. At this point, you should say: "This is not correct. But I understand you. You want to highlight this button so that the visitor comes and immediately pays attention to it." There are so many nuances that you can't list them all.

Answer 3

Just do not go on about the "Wishlist". If you have been chosen as a designer, it means that you are trusted in this area from the very beginning. Edits that do not carry a semantic load and do not solve any problems of the site - to hell. All subjective assessment - to hell.
Highlighting the payment button so that it immediately catches the eye is a correct remark, backed up by the client's fears.
In general, you can conduct a-b testing with Yandex.metrics and see which design solves problems better (with or without client edits).

Answer 4

In the case when the client starts to be overly capricious, I close the project and return the prepayment (if I took it). You can only protect a design with numbers that appear after the design is launched into the production environment. It is better to convince that a green button is needed here, and not a red one, arguing with statistics that are easy to get by studying competitors. If the client relies on the taste preferences of his half-brother (especially in e-commerce) and ignores statistics, Google analytics, etc., then he is a fool who is afraid of losing his 2364 rubles on design without personal intervention. Believe me, there are a lot of adequate clients, do not be afraid to change them more often. But you need to be able to convince

Answer 5

look, listen to the customer, say that drawing, for example, 5 design options costs 4k. and subsequent edits and changes cost, for example, 3k. for redrawing, draw layout options, then show the customer chooses the layout he likes the most, if not, and starts saying here I want a button and here is a photo of a naked woman Dusya, trying to explain, recalling the surcharge for edits, that Baba Dusya is not a beauty and a concept the design does not fit in, if it doesn’t work, then either refuse to work or raise the bar for revision so that the customer regrets his babos

Answer 6

As a rule, no matter how much you explain, don't care - "I want that and that's it." IMHO, it's better not to argue much. If it is clear that the client is impatient, then you need to do as asked, trying to fit what is required into the design as much as possible. Additionally, it is necessary to stipulate in advance how much "free" time is attached to the ready-made options (ie we put the cost of this time into the cost of the options) and for everything that comes from above, an additional hourly payment. Well, not all the designs made will be in the portfolio, so now.
It’s worse when the customer doesn’t know what he wants, he can’t decide, and it even happens that, having frayed his nerves, he dumps without paying, they say, what kind of money, there is no ready-made design? And that there are only requirements in the technical specification, he shows the opposite references, and he asks for third changes to be made - in the end, he is not satisfied with anything ... it’s better to spend a little time at the very beginning to find out the adequacy of the client and send such “nina-cho-want” away - time and nerves are more expensive.
It also occasionally works (only if the discussion is personal or by voice on Skype, but not in writing) thrown as if in between times something like "this button, of course, attracts attention, but I won’t put it in my portfolio - and clients I'll scare you, and your colleagues will laugh"