- Maintaining Integrity of Design Objectives

Hi, my name is Lindsay Woods and I'm a junior project manager at Hamilton Anderson in Detroit, Michigan. Today we're gonna talk about technical and quality reviews based from the project manager's perspectives on a variety of projects ranging in scale from one consultant and one architect to large project teams of almost 10 people, which is what I consider a large project team, in the hospitality sector. 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 is 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 little changes but still meets the needs of the client.

So that's one thing that I really like that we do 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 a project, like SDDD. 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 our COO officer, the project manager, the lead architect, and usually an intern and then maybe our director of design. Whoever's going to be doing the technical review will also be at that meeting. 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 on different hospitality teams and so since they are similar project types but they're not on 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 project since they are familiar with it but just enough to not let their knowledge of the project interfere.

Depending on the project size, it can take anywhere from 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