Developing on an Occupied Campus Is an Operations Problem First and a Construction Problem Second.

This project wasn’t just about delivering a new building. It was about delivering it next to an occupied campus we already owned and operated. On paper, that proximity looked like an advantage. We knew the site, the market, and the tenant profile intimately. In practice, it introduced a layer of complexity that touched almost every aspect of the business, from construction logistics to leasing performance to internal team dynamics.

Building adjacent to an occupied campus means every construction activity has a downstream impact on people who are already living there. Traffic patterns change weekly. Access points shift. Noise and dust are no longer abstract nuisances; they are daily experiences for paying tenants. To keep those tenants in place, the operations and leasing teams were forced to offer larger concessions than originally underwritten, absorbing real financial impact to preserve occupancy and reputation. Leasing velocity slowed, and as it often does, frustration followed.

This is where a familiar tension in the industry surfaced. When leasing slows, development and construction become convenient culprits. From the operations side, the story is simple: construction is disrupting the product they are responsible for selling. From the development side, the instinct is to point to schedules, contracts, and inevitabilities. Both perspectives are valid. Both teams are under pressure. And if the developer doesn’t actively manage that relationship, resentment quietly fills the gap.

The deeper lesson is about mindset. The operations team is the customer of development, and their customer is the tenant. They are the front line, tasked with selling, operating, and protecting the physical asset that development brings into existence. When you’re working on an occupied campus, coordination cannot be delegated entirely to the general contractor. It requires daily alignment, empathy, and proactive communication from the development team itself. Expect added costs, longer schedules, and operational friction. More importantly, recognize that managing the development–operations relationship is not soft skill work. It is core risk management.