The Coordination Black Hole

The coordination black hole doesn’t have to be inevitable. You just need to stop feeding it and start building a system that scales with you.

There’s a moment in every project where the VDC Director recognizes: the schedule slips, communication breaks down, and the instinct kicks in: we need more meetings.

It’s rational. Logical, even. If coordination is failing, add checkpoints. Get everyone in the room. Create visibility and action.

So, you do. You add the Tuesday sync-up. The Thursday deep-dive. The Friday lookahead. And something strange happens.

The problem gets worse.

The Vicious Cycle

Here’s what actually unfolds:

More meetings generate more RFIs. More change orders. More action items. The issue log balloons from 200 entries to 2,000. You’re surfacing problems faster than ever, but not actually solving them.

What’s happening underneath:

• More meetings = more documentation burden
• More tracking = more things waiting on responses
• More people involved = slower decision-making
• The system becomes the bottleneck

The coordination overhead compounds the original delay. You thought you were fixing the problem. Instead, you fed it.

The More Meetings Trap

The coordination problem doesn’t stay contained, it metastasizes across your portfolio.

Every project invents its own coordination rhythm. One uses Monday check-ins, another does Thursday deep dives, a third runs daily standups. Each rhythm is rational in isolation. But multiply it across 15-20 active projects and your senior VDC leaders are spending 60% of their week in tactical prep meetings—reviewing models, validating clash reports, and triaging RFIs—instead of leading.

The meetings themselves become performative. Teams show up, share updates, surface issues, but decisions get deferred. “Let’s take that offline.” “We’ll circle back next week.” The noise-to-signal ratio inverts.

Meanwhile, reporting quality degrades. Project teams are drowning too, so their weekly dashboards become copy-paste exercises. Metrics lose meaning. By the time something escalates to portfolio leadership, you’re looking at lagging indicators from two weeks ago.

And here’s the cruelest part: the better your team is, the more painful this becomes—because your best people end up compensating for system gaps. Your top coordinators become human duct tape, manually stitching together what should be systematic. They’re working weekends to keep projects from derailing, and you’re rewarding the behavior because it works—until they burn out or leave.

The result: You’ve lost portfolio-level visibility. You can’t answer basic questions like “Which projects are actually on track?” or “Where should we focus support this month?” without launching an investigation.

This isn’t a people problem. It’s a system that scales linearly while complexity compounds exponentially.

What This Actually Feels Like

What This Actually Feels Like

You are accountable for coordination outcomes you don’t fully control.

You constantly switch between different project rhythms, tools, and team dynamics.

You personally make sure meetings matter. If you skip the prep, facilitation, and follow up, those meetings drift into just status updates.

Most VDC Directors tell us the actual work isn’t the stressful part. The stress comes from not knowing if things are running well when you leave the room.

You shouldn’t have to be everywhere to trust that coordination is working.

A Different Model

On a recent data center conversion project, a former warehouse being repurposed into a high-density network hub, the coordination load was significant from day one. Incomplete model submissions, erroneous geometry from trades not adhering to BIM standards, and a design that was still evolving mid-coordination meant the clash environment was noisy and hard to navigate.

Rather than letting that noise flood every coordination meeting, VIATechnik’s BIM coordinator, ran a pre-meeting the day before each session with the full project team. He’d already worked through the model, filtering out irrelevant geometry, identifying the clashes that actually mattered, and flagging anything that needed a decision before it hit the field. By the time the actual coordination meeting ran, the team wasn’t sorting through raw data. They were reviewing prioritized issues, tracking RFI responses, and making calls.

The General Contractors’ lead coordinator, stayed out of the clash minutiae. That was handled. Instead, he focused on what only he could do: managing trade relationships, pushing on design changes affecting lead times, and steering the coordination toward the areas with the most field impact. When VIATechnik caught something unusual, a base plate condition on a column cluster that would have conflicted with prefabricated equipment,  he brought it to the lead coordinator in the pre-meeting. It got resolved before it ever surfaced as a field problem.

That’s the model. Not more meetings. Not more bodies. A system where the tactical work is handled upstream, so the people who need to lead can actually lead.