I’ve just been handed a really great summary of what it is like to work for a client who, “just doesn’t get it.”
“Get what,” you ask? Well, a designer or developer of any kind has so many hats to wear I think most people just don’t realize it.
When we look at a project we see it from the perspective of a customer, a salesperson, a psychologist, a designer and finally as a member of the client’s business itself. We have to get our heads around what our client does and what their clients will actually appreciate. Then we have to make sense of it all and produce something meaningful. (Or so one would hope…)
Often these jobs are made harder when the client just doesn’t know what they want at all, or when they don’t understand that changes in the middle of the process can have devastating effects on the delivery date, or the price of the project.
Some clients seem to think that design work is a factory that churns out cookie-cutter solutions to vastly differing problems.
As anyone in the industry knows, this is simply not the case. Enjoy the article. 
[ If Architects Had To Work Like Web Designers - Shae Allen - Biznik ]
