Organization of the Artist - A simple management concept that works

Here is a concept that I tend to live by when it comes to running web dev projects for my clients.  It was never very popular with them since it didn't give them the opportunity to voice their opinions during the development stage but it allowed me to concentrate on delivering a good product and within their budget.

Gehry initially developed the concept of the organization of the artist as a reaction against what he calls the "marginalization of the architect/artist." Gehry explains:

There's a tendency to marginalize and treat the creative people like women are treated, 'sweetie, us big business guys know how to do this, just give us the design and we'll take it from there.' That is the worst thing that can happen. It requires the organization of the artist to prevail so that the end product is as close as possible to the object of desire [the design] that both the client and architect have come to agree on.

While architecture isn't exactly the same as web development the concepts are almost identical, and you wouldn't believe how quickly projects can go sideways when your clients start asking for chances from the initial design.  Yes, sometimes these changes are a good thing, and should be celebrated but that is not always the case.  In those instances I have to ask, "if you are such an expert why did you hire me?"

Related Web URL: http://en.wikipedia.org/wiki/Organization_of_the_a...