When Coordination Becomes the System

Last year, on a project, we had a moment everyone in construction knows.

The schedule “worked” on paper.
Costs were technically under control.
Reporting was on time.

But the structure was already fragile.

The owner chose to split the works into too many packages.
We warned early that this would increase coordination risk and compress the room to maneuver.
The expectation was that tighter packaging would reduce cost.

What followed was predictable in direction, but impossible to compute in detail.

Awards came late.
Parties joined the project at different times.
Interfaces multiplied.
Too many moving parts, arriving out of sequence.

Tension rose.
Meetings multiplied.
Urgency increased.
Nothing actually improved.

After the fact, it was obvious what mattered.
There hadn’t been enough space for things to move.
Interfaces had become the system.

In the moment, you could feel it.
You just couldn’t calculate it cleanly.

This is why I keep coming back to the P ≠ NP question.
Not as computer science, but as a leadership lens.

Some problems are easy to evaluate once you see the outcome.
Very few are fully computable in advance.

Construction is full of these:
sequencing, coordination, stakeholder alignment, risk that only reveals itself under pressure.

Most project stress comes from pretending otherwise.
From treating complex systems as if they were solvable by more speed, more meetings, more reporting.

Good project leadership doesn’t “solve” the problem.
It reshapes the terrain so the problem stops exploding.

Clear ownership.
Short feedback loops.
Reversible decisions.
Visibility instead of approval.
Calm instead of speed.

That’s how intractable problems become manageable.
Not because they’re solved.
Because they’re no longer fought in their worst form.

This is the work I care about most.

Not perfect plans.
Not more reporting.

Structures where coordination is real, feedback is short, and decisions stay reversible.
Where good outcomes become easier than bad ones.