What do you foresee as necessary boundaries to integration in our pursuit of operational excellence as a program team?

Team integration is most effective when individuals understand each other's roles and responsibilities and demonstrate respect and flexibility in their daily activities; knowing this helps guide everyone along the same path. Boundaries are important to avoid duplication of work, ensure that the right people are performing the right tasks and that meetings and other gatherings have the right people (including the right number of people to make their work effective). Boundaries begin with observing IPO etiquette-ensuring you are treating your neighbours with respect. More formal boundaries include lanes for design, constructability, procurement, reporting and monitoring. These lanes are expanded or crossed as we come together for integration but it is important that the right people are performing the right roles. We all need to remember that integration and collaboration mean working to get the best ideas for delivery-collaboration does not mean surrendering your role on the project in the interests of "harmony."

We are in the process of delivering organization charts and responsibilities matrices that define roles and responsibilities on the project and put names and faces to the roles.