What are the Design roles you use to make the client can't refuse your product or get the minimum choice to be refused ?

Try to Under stand Proper view of your clent and creat minimum3 designs and in two of them should be more accurate as same as clients view and one exactly opposite and he will offcourse reject the last one and99% chance for accepting1/2

hope you have the answer

This is more of a marketing question rather than a project question. When i create a project i try to find a logical reason behind everything. I would use the three key elements for convincing : ETHOS, LOGOS and PATHOS

• LOGOS : Logos refers to logic. Explain why you made XYZ decisions and how it affects the overall look. Make it simple and concize. Do not force it down his throat, just make simple statements which will give the next step of our convincing procedure
• ETHOS : ETHOS refers to credibility. Credibility can be established through logos (logic) or by refering previous famous work. "oh my website is too simple" which you can reply by "yes, but twitter is simple too, and this is why it remains efficient. Websites like XYZ were complicated and ended up failing"
• Finally "PATHOS", Pathos is an emotional attack to the individual (not litterally). It is a way to make him feel and be emotionally attacked to what you made. Time, effort, children to feed, his mother's birthday, anything will work if it can make him overlook the things he more of less likes.

But remember, even after following those tiring steps, the customer's decision and opinion is still what will seal the deal. So don't be pushy and when things get hard, try to use some of that Pathos on them :)

Best of luck !

From my experience user always looks for things make his life easy:

so to minimize any change you have to do some steps:

Do a prototype at the beginning of the project.

Involve the user in the interface development.

Don’t try to add many things that will confuse and make it difficult to understand.

More simple and easy to use ... plus involving the user in your development face will end up your project with best use satisfaction. Please ... don’t try to be so smart and give the user more than what he want or give him choices.. let the user decide what he want and just analyze the requirements and modify them based on the application need and inform the user and take his agreement on interface prototype design before implement it .By this way you will be in safe side and the risk will be minimize for any coming changes after development or go live.

The client can ALWAYS refuse the product. The client may have to honour payment on any effort expended but they can always refuse a product.

If you want them to make a decision when they HAVE to make a decision give them3 choices . The one you want them to choose.2 One that's a bells and whistle version that's way too expensive.3. One that's way too risky to select.

Give them more than3 choices and it will go to a committee etc. Give them2 and they don't feel like they are deciding anything.3 choices is the Goldilocks number.