Clients expect their design team needs to be responsive to the changes, requirements and issues that arise throughout their development project. This is vital to the success of small projects and even more so for large projects. Similarly, design teams need clients to be just as responsive.

A strong team leader is key to a successful development project. Among his or her many functions is to educate clients and the design team as to the proper expectations for the project: processes related to the design, communication, management, invoicing schedules, deliverables, and the final result. If a leader says a project will be done in 4 months, what will actually be done needs to be defined. If, for instance only two-thirds of a large building’s construction can be built in a particular time frame, our client needs to know that. Effective team leaders do not try to sell clients on non-accomplishable goals. We can tell you what we want to do but there will never be a perfect project. Getting as close to perfect as we can is our goal.

In discussing historic preservation with a friend recently, I was reminded of my trip to New Orleans’ French Quarter last year. As the oldest still-intact neighborhood in the U.S., its character and city planning is largely identical to what it was 300 years ago. Sure, buildings have been upgraded and advanced construction standards and materials have been applied, but the area’s scale and courtyard theme is the same, and determined consideration for historic preservation has been incorporated into each design issue.

In this new world of fast paced multi modes of communication all parties involved in the design process need to define their primary means of communication. The phone, fax, and mail used to be the standard go to that was understood by all. Now with cell phones, messaging, the internet, social media, many differing hard and software modes of communication each team involved in a development project needs to know what the rules of engagement are. To keep efficiency standards high, everyone needs to be on the same page. Does all the hardware and software communicate together without much heartache? Text vs email vs phone calls need to be defined from the start. Know the capacity of file sharing. Filing systems for easy access and redundancy are always an asset to a project. Security and back up protocol need to be defined. Language and its varying interpretations need to be understood. Within our society people come from everywhere and the diverseness enriches us but also can affect communications. Ask if you are not sure. Be active in making sure all parties are on the same point of reference. Follow up to see that the email was received. Verify each question asked is answered. We notice only the first question gets answered 50% of the time. Each person is responsible to make sure their thoughts are understood by the parties they work with.