Wright practiced what is known as organic architecture, an architecture that evolves naturally out of the context, most importantly for him the relationship between the site and the building and the needs of the client. (from Wikipedia: http://en.wikipedia.org/wiki/Frank_Lloyd_Wright)
Wow - import thing being the relationship between the site, the building and the needs of the client...or in IT terms - the technology, the application and the client. Sounds like a back to basics approach to me. We (meaning me) often enter a project with preconceived notions, a technology prejudice, a thought that we know more then the client, a miss-construed notion that we know their business as good or better then they do, a feeling that a prior approach will be the right approach because it worked then, etc.......what we are doing is adding risk and reducing value from the start. We need to enter every new project/relation with a fresh open mind, understand the overall landscape and truly appreciate the needs of our clients prior any initial problem solving thought (a very tough thing to do). IT'ers are problem solvers...we need to resist the urge to solve (like resisting the urge to code) until we understand and appreciate what it is that we are being tasked to do.....
No comments:
Post a Comment