Major projects have always been distributed. An international programme can involve partners on several continents; an energy project might have engineering in one country, fabrication in another and construction on site a flight away. Remote and hybrid working simply extended a reality that capital projects already lived with. The lesson from those programmes is clear: distance is manageable, but only if you replace with discipline what proximity used to provide for free.
What actually breaks when a team is distributed
The problem is rarely the technology. It is the quiet loss of the things a shared location gave you without anyone noticing:
- Informal information flow. The corridor conversation and the overheard problem — where much of a project's real coordination happens — simply stop. Nothing replaces them unless you design something to.
- Silent drift. When you can't see the work, small divergences between what people think was agreed go unnoticed until they surface as rework.
- Diffuse accountability. Across organisations and sites, it becomes easy for an action to belong to everyone and therefore to no one.
- Slower decisions. Time zones and email turn a five-minute decision into a three-day thread if there is no faster path built for it.
What you have to put in its place
A single source of truth
One authoritative programme, one risk register, one place where status lives — visible to everyone, updated on a known cadence. When the team is distributed, ambiguity about "which version is current" is fatal. The controls function becomes the backbone that holds a scattered team together.
A fixed cadence
Distributed teams need rhythm more than co-located ones do. A predictable pattern of short, purposeful check-ins — with a clear agenda and decisions captured — replaces the informal contact that distance removed. The cadence matters more than the meeting length.
Decisions in writing
Verbal agreement doesn't travel across sites and time zones. Decisions, actions and owners have to be written down, visible and traceable — which, usefully, is also exactly the record you need if the project is ever scrutinised.
Controls discipline
Everything covered in project controls — a defensible baseline, honest progress measurement, critical-path focus — matters more, not less, when you can't walk the floor to sense how things are really going.
Co-location hides weak process. Distance exposes it. The fix is better process, not more meetings.
Tools don't create discipline
Collaboration software helps, but it is not a substitute for the disciplines above. A distributed team with clear ownership, a fixed cadence and one source of truth will outperform a better-tooled team without them every time. The tools amplify whatever discipline already exists — including the absence of it.
Time zones, culture and trust
Genuinely international teams add two more variables. Time-zone spread rewards asynchronous working — clear written hand-offs that let work continue around the clock rather than stall waiting for an overlap. And cultural differences in how directly people raise problems mean a manager has to create explicit permission to flag bad news early, rather than assume it will surface on its own.
When co-location still wins
Distributed delivery is the default, but not for everything. Kick-off, the early shaping of a complex programme, and recovery of a project in trouble are still far better done with the key people in one room for a few intense days. The judgement is knowing which moments justify the travel — and running everything else with the discipline that lets distance stop being a disadvantage.