The Move Nobody Complained About: The power of a simple heads-up

Some of the most impactful project management decisions don’t show up on a Gantt chart. They show up in what doesn’t go wrong.

Early in my career, while working at Savannah College of Art and Design, I was tasked with coordinating a facility move that would consolidate approximately 60 full-time and adjunct faculty members from six separate buildings across campus into one brand-new facility: Arnold Hall, a three-story building on Bull Street in Savannah’s midtown neighborhood.

The logistics alone were complex. But what made this project successful wasn’t just the move itself—it was the decision to think beyond the org chart and consider every stakeholder the project would touch, including the ones who never set foot inside the building.

The Scope: More Than Moving Boxes

Arnold Hall was opening for its inaugural year. The building housed four computer labs on the first floor—two PC, two Mac—along with an auditorium with second-floor seating. The second floor featured additional classrooms, and the third floor was entirely dedicated to faculty workspace. We were expecting 1,600 students to flow through the building once classes began.

I stepped into this role after the previous administrative assistant was promoted. The faculty had already packed and labeled their boxes, so that phase was complete. My responsibility was everything that came next: ensuring that when those boxes arrived, the building was ready to receive them—and that the people inside and outside the building were ready, too.

Internal Coordination: Designing for People, Not Just Floor Plans

The third-floor faculty workspace used shared cubicles, each designed to accommodate three professors. My job was to create the seating layout, which meant more than just filling slots on a diagram. A few faculty members had interpersonal conflicts and could not be seated near each other. Several married couples on staff requested to sit together. And one or two professors had mobility limitations that prevented them from accessing the third floor, so I needed to identify first-floor office space for them—and ensure their class schedules were assigned to first-floor classrooms as well.

Once the seating assignments were finalized, I labeled every desk so the facilities team would know exactly where each person’s boxes belonged. I also shared the layout with the facilities team in advance of the move. When you’re coordinating the delivery of boxes for 60 people, clarity isn’t a nice-to-have—it’s a requirement. That advance communication eliminated confusion on move day and allowed the team to work efficiently without needing me to direct every delivery in person.

After the physical move, we tested every workstation: electricity, phone lines, and individual phone extensions, since each extension was tied to a specific faculty profile. Every connection had to be verified before the first day.

The Decision That Changed Everything

Here’s where this story shifts from standard project management to a lesson in stakeholder awareness.

As a Savannah native, I had watched SCAD expand across the city for years. I’d seen the friction firsthand: students flooding neighborhood streets, parking becoming a daily battle for residents, foot traffic disrupting the rhythm of quiet blocks. Many residents and business owners carried real resentment toward the college’s growth. That frustration was rarely addressed by the institution, and it had built up over time.

Arnold Hall was opening in the heart of a residential midtown neighborhood. We were about to bring 1,600 students, 60 faculty members, and construction activity into a community that had already experienced the disruption of institutional expansion without warning or consideration.

I decided to do something about it. On my own initiative, I created an informational flyer and personally visited every business, home, and public institution within a one-block radius of Arnold Hall—including the public library. The message was simple and respectful: Arnold Hall will be opening for classes on this date. We are expecting approximately 1,600 students. In preparation for the opening, there will be construction activity in the area. We apologize in advance for any inconvenience.

That was it. No promises, no elaborate community relations campaign. Just a heads-up.

The Result: Preparation Instead of Protest

No one from the surrounding community responded to me directly. But something more important happened: they were prepared. The library increased its security presence. Neighboring businesses adjusted their operations for the anticipated increase in foot traffic. And I worked with our campus security department to develop a plan for the neighborhood, particularly for evening classes that would let out after dark in a residential area.

The building opened. Classes started. And the community absorbed the change without the conflict that had characterized previous SCAD expansions in other neighborhoods.

The Takeaway: Stakeholders Aren’t Always on Your Org Chart

Over the course of my 32-year career—progressing from junior administrative assistant to Director of Operations, with 26 of those years in project management—I’ve managed hundreds of projects across healthcare, higher education, e-commerce, and nonprofit sectors. This relatively small facility move at SCAD remains one of the stories I return to most often, because it illustrates a principle that applies to every industry and every project size:

Your stakeholder map is only as good as your willingness to look beyond the obvious.

The faculty, the students, and the facilities team were the stakeholders anyone would have identified. The neighbors, the library, the small businesses on Bull Street—those were the stakeholders that could have become obstacles if left in the dark. A simple act of proactive communication transformed potential adversaries into a prepared community.

Key Principles from This Project

• Anticipate impact beyond your project boundaries. Every project creates ripple effects. Identifying who will feel those ripples—even indirectly—is part of thorough planning.
• Communicate early and simply. The flyer wasn’t elaborate. It didn’t need to be. People don’t need a presentation—they need a warning and a sign of respect.
• Design logistics around real human needs. Seating assignments that account for interpersonal dynamics and physical accessibility aren’t extras—they’re what separates a move that works from one that creates weeks of complaints.
• Share information with your support teams in advance. Giving the facilities team the layout before move day allowed them to execute independently. That’s the difference between managing a project and micromanaging every task.
• Success is often measured by what doesn’t happen. No complaints from the neighbors. No confusion on move day. No faculty unable to access their workspace. The absence of problems is sometimes the strongest evidence that a project was managed well.

Whether you’re managing a facility move, launching a new initiative, or navigating any organizational change, the stakeholders you overlook today become the obstacles you manage tomorrow. Take the time to look beyond the project plan.

For more real-world case studies and practical business operations strategies, visit the Tools of the Trade blog, or connect with me on LinkedIn.