This weeks design rule has to do with client/dev team relationships, and dealing with questions and revision requests…

Challenge changes you don’t agree with, doing so pragmatically , and objectively

This is not a call to arms, nor am I in any way endorsing snooty, arrogant, designer attitudeness (yes attitudeness is a word cause I just made it up). Instead as designers/developers when we come to these situations where “changes” are occurring that we don’t agree with, or just flat know are not adding to the quality of the design for the product/project, the best thing to do is ask questions.

Ask leading questions such as “What problem are we solving with that change?” or “how do you see this change befitting the project”, the sooner we start asking questions the sooner we can get to the real needs of the client/company project. more times than not Large Red Glossy Buttons, terms like “Make it POP” come from clients and marketing/project managers not being able to communicate what their real needs are.

So if we ask leading questions, and then follow those questions up by educating our clients on a level they understand (usually ROI) then not only are we setting up better communication we are showing our knowledge and ability at the same time, and improving the value of what we offer.

Lastly provide valid references show them what you read, watched, or experienced that backs up your claims, and be open to being wrong, or the other party having a good point… no one likes a know it all. These types of situations don’t all have to be bad… more times than not they can be learning opportunities.

So yes challenge, but challenge with intent. The intent to educate and improve communication, and the needs of the project. This will lead to better design, more successful projects, and happier clients.

have an experience that relates? how dod you challenge a client question/revision request in a way that benefited the client, and the project.

~ Aaron I