Published on 2006-05-17 17:28:54

Usually when I'm confronted with a code not well written or a concept not well explained it's very easy to explain it and say why it is not good and how it should be, there is many logics that we used to work with and accordingly you can convince your coworkers. When it's about design and usability the process become a little more complicated. What is bad for designers is to receive recommandation for a "bad design" to do, and I remember this happening with my very first customers : the result was so horrible, the customer is satisfied, but I'm ashamed to add that work in my portfolio.

about-design.jpg


After it I started to follow different strategies to deal with such customers, and I learned how to say "No" for some recommandation. Anyway this is for the benefit of both of us, so why not ? With my new customers I'm happy that this don't happen anymore, they always ask me if it's possible to do something in this way ? depending if this idea will add a positive value to their product or no, I suggest them the proper solution. But what to say if your customer say "I want menus in this way, colors in that way, make the fonts that way ... etc. " ?

Read More


Related Entries

Member of the PHP Magazine Network, Copyright (C) 2005-2008 phpmagazine.net All Rights Reserved