Unreasonable client demands needn't ruin the integrity of your work, says web designer Paul Randall. Follow his advice on how to ensure a meeting of minds...
Slavishly implementing client changes won't do either of you any favours, argues Paul Randall
So you've sent the email or given the presentation. You wait for feedback and hear the dreaded word: 'changes'. Talk to any designer and same sinking feeling occurs. What are they going to ruin?
Client feedback is always going to happen, and they may suggest specific design changes; but here's the secret - DON'T TAKE THESE LITERALLY.
It might sound counterintuitive, but the worst thing that you could possibly do at this stage is arbitrarily make the changes they ask for. Simply fulfilling this request isn't what the client is paying you for.
Break down the brief
Try to set a brief for the site. This can be broken down page by page, such as: 'highlight our five-year guarantee to new users'. This allows you to refer to the brief and demonstrate how the design meets the brief. More appropriate client feedback would be 'can we give more importance to the guarantee. It needs to be more important', not 'can we make this bigger and bolder... and perhaps red?'.
This request can be interpreted in a design matter, and don't feel pressured to do it on the spot. Let this request mull over. You can present the changes (and the working out you did to get to the conclusion) in the next session. Always revert back to the brief. Has the design brief met the business request?
Subconscious decisions
Showing them your working out is the key. It sets you (the designer) apart from the client. Believe it or not, we make a lot of subconscious decisions when designing. There's a good reason for this. It gives you the opportunity to demonstrate how you solved the problem. You would be marked on the working out, and not just the final answer.
It's the same with design work, if you can't describe how (and more importantly why) things are done a particular way, then the client should (quite rightly) think of it as just a guess.
Being able to successfully interpret client requests and communicate them into design decisions is probably the most important skill to learn in client services. Without this, you risk a client reject or dismiss good ideas, simply because they can't see how you worked out the answer.
Communicate your craft
Follow the example of IA, who pushed back on client changes to get to the root issue
We need to communicate our craft more. We are graphic communicators. Save the design with no explanation to the artists. In a recent blog post, Information Architects reasoned why they didn't simply add a text size property in their iAWriter app.
Their reason was they wanted to get to the root issue, and not just implement the design solution the client (users) suggested. Their response back? The first responsive app to hit the App Store. This hit the 'business brief' with their design solution, and made a better project because of it.
