Though it opened in 1911, the Chateau Lake Louise hotel has likely never been as popular as it is now. Room prices are exorbitant, and unless staying there you aren’t even allowed to visit most areas of the hotel. The fact that many of the hotels built by the Canadian Pacific Railway (CPR) and Canadian National Railway (CNR) more than a century ago (and some that are soon to be centenarians) are still considered to the utmost in luxury and style is a testament to the vision and talents of the architects that designed them.
These grand buildings showcase both Canadian architectural prominence and the grit of the builders in those days.
As any architect knows, although it is vitally important, contract administration (CA) is rarely the fun part of any project and is often greeted with similar levels of enthusiasm as when one is called up for jury duty. In our experience, there are two reasons why architects dread the many chores associated with CA. First off, no architect goes into the profession because they love paperwork – the thrills are in the creative design process, and that’s why most architects went into the profession in the first place. Secondly, problems in CA, no matter how trivial, can lead to conflict with contractors and project owners, possibly even resulting in lengthy and time consuming litigation.
Experienced architects also know that managing contract administration well is what keeps projects on track, and what supports the continuity, quality, and intent of their original design. When the architect serves as contract administrator, they can also better manage and limit risks by facilitating communications and maintaining clear project records. The architect is also in the best position to identify and correct problems in construction as they occur, and can quickly deal with them to minimize any negative impact on the construction.
As you evolve any business, finding brilliant new tech solutions to help manage workflow is going to be a big part of how you grow. However, no matter how much you know it is going to revolutionize how your team works, it is absolutely normal that you are going to face resistance when it comes to buy-in from your team. And, if you’re looking to onboard external project stakeholders to that particular tech, you may face further resistance there too. In this blog, I’ll outline ways to smooth the buy-in process in order to help transitions to new solutions, and ensure better outcomes.
Recognize the opposition
There are plenty of reasons why people resist new tech solutions. Not everyone feels that confident with computers, and no doubt there will be some people in the office who are perfectly fine doing things the old way. Often fear of change is based on anxiety about being able to keep up with changes, and it doesn’t take much to reduce that level of fear. A simple acknowledgement that this will require effort in the short term, and that you’re going to ensure that everyone has the support they need to learn it at their own pace, will do the job.
This is a short post to let you know that we will be at the RAIC Festival of Architecture in Saint John. Drop by our booth on Friday at the Trade show to say hello. If you’re an existing user, we would love to answer any questions you might have. If your thinking about using RForm, we would be happy to provide a quick demonstration. If you would just like to pick up one of our pencils and a sticky pad, we would be happy to see you!