Friday, July 12, 2013

Preventing Crashes

I was sitting at a stop light the other day. I was making the best of my honey do list running errands by motorcycle on a beautiful day. The light changed for traffic crossing my path and the cars took off. The first car pulled out at a reasonable speed, the second seemed to be tailgating a bit, and the third was apparently in a hurry or marching to another drummer. It accelerated rapidly and plowed into the second car, which in turn ran into the first. Sometimes, the building process can be like this. No, I’m not saying it’s a car wreck, but there are a lot of parties involved in the process. Not unlike many processes, each party observes the same information, but does not always interpret it the same way.

The process of Architecture is an effort to define and communicate an intended result essentially from drawings and written directions. The construction process is the effort to create this drawn item. It is necessary to provide the proper information and direction to prevent any crashes. The greater the communication and understanding between parties, the better they see and perceive the same information, the less likely there are any nicks, dings, or crashes. An integrated Design/Build process fosters that communication resulting in a smoother process and mitigates the likelihood of mistakes.

Oh yeah, the second two cars stopped, but the first drove off with its bumper dragging. I'm not sure it ever stopped.

No comments:

Post a Comment