Maintaining Integrity of Design Objectives

2m 20s

Lindsay Woods of Hamilton Anderson Architects discusses the various aspects of project management.  She explains the process involved in assembling a team, allocating resources, and reviewing contracts.  She also shows examples of work plans, construction budgets, and a project schedule.

One thing here at Hamilton Anderson that we do take part in is, we'll do collaborative reviews. Which is where the main team who's working on a project, actually assembles a presentation. And we invite other members or team members from our office, who don't have any direct connection with the project. And they actually sit in one big room and go over all the drawings and the design process. And everyone, you know, from a designer's perspective, comments on the project that's going on. So, then, the team that is working directly on it, gets this outside perspective and makes some, like, little changes, but still meets the needs of the client.

So, that's one thing that I really like that we so early on, to facilitate the design of a project. It's also a good check for everyone. Everyone in the office gets to come by and see it and make sure that it's in our line of thinking, for our design vision here. But that's usually in the early phases of the project, like, S-D-D-D. The next thing we do is, after that's kind of been established.

You know, everyone moves into construction documentation. We set up meetings to actually kick off technical reviews on documentation. There's usually around five people included in a meeting like that. And one of them being, like our C-O-O officer, the project manager, the lead architect and usually an intern. And then, maybe our director of design. Whoever is going to be doing the technical review, will also be at that meeting. And it's usually someone who is familiar with the project type, but is not directly working on the project.

So, we have two large studios that work of different hospitality teams. And so, since they're similar project types but they're not the same project, we might choose one of the leads from one of the teams, to do the quality review and technical review of the other projects. Since they're familiar with it, but just (mumbles) to not let their knowledge of the project interfere. Depending on the project size, it can take anywhere from a half a day to a whole week, week and a half, to review a project set.

Again, it depends on the size of the project. We do that, they make comments, our team has about a week to pick up red lines and comments. And then, simultaneously, we're still collecting everything from consultants, working towards that final deliverable to the client.

Log in to access files