Every World Cup before this one had a single host, and with it a single set of rules. One government to deal with. One currency, one legal system, one customs regime, one set of labour laws, one national authority whose yes actually meant yes. The 2026 tournament threw that away. For the first time, the World Cup is being staged across three countries at once — the United States, Canada and Mexico, sixteen cities between them — and the moment you look at it as a piece of work to be delivered rather than a sporting event to be watched, that single fact reorganises everything.
I find this the most instructive thing about the whole tournament, because most people running large projects will never face three host countries, but almost all of them will face some version of the underlying problem: delivering one outcome across boundaries that do not share rules.
One tournament, three rulebooks
Start with the thing that sounds trivial and isn’t. Three countries means three of nearly everything.
Three governments, each with its own priorities and its own election cycle. Three legal systems. Three tax and customs regimes, so that equipment, broadcast gear and merchandise crossing from the US into Canada or Mexico is not an internal transfer but an international one, with paperwork and delay attached. Four time zones across the footprint. Different labour laws governing the tens of thousands of workers. Even the distances are continental: the venues stretch from Vancouver in the north-west to Mexico City in the south to Miami on the eastern edge.
A single-country tournament can assume a shared baseline. Everyone inside it operates under the same rules, so coordination is mostly about sequencing. A three-country tournament can assume almost nothing. Every cross-border movement is a small project of its own. The coordinating layer is not managing one environment; it is reconciling three that were never designed to work as one.
The work is not equal, and pretending otherwise breaks it
Here is where the project lens gets sharp. “Three host countries” sounds like a partnership of equals. The delivery reality is nothing of the sort.
The United States carries seventy-eight of the hundred and four matches. Canada and Mexico host thirteen each. The overwhelming majority of the high-stakes knockout fixtures, and the final itself, sit on the US side. So the effort, the infrastructure load, the security burden and the operational risk are distributed wildly unevenly across three partners who are, politically, supposed to be co-equal hosts.
That gap between the symbolism and the workload is one of the hardest things to manage on any joint venture, and it is worth naming honestly because it shows up everywhere, far from any stadium. Two departments “jointly own” a project, but one does eighty percent of the work. Three organisations partner on a bid, but the obligations are nowhere near evenly split. The failure is always the same: the governance treats the partners as equal because that is the polite fiction everyone agreed to, while the actual work concentrates somewhere the governance refuses to acknowledge. The resentment and the bottlenecks both build in the gap.
A three-country World Cup cannot afford that fiction. The structure has to reflect where the work actually sits, even while the ceremony treats everyone as equal partners. Holding both of those truths at once — equal in standing, unequal in load — is the real coordination challenge.
Whose authority actually counts?
In a single-host tournament, there is ultimately one national authority you can appeal to when something has to be forced through. In a three-host tournament, that backstop disappears. No single government has jurisdiction over the whole thing. FIFA sits above all three, but FIFA cannot overrule a national customs service or a city’s policing decision. Authority is genuinely distributed, and distributed authority is the hardest kind to work with, because there is no one who can simply end an argument.
This is the part that separates program governance from project management most clearly. On a project, you can usually find the person who decides. On something like this, for many of the hardest questions, there is no such person — there is only a negotiation between authorities who each control one piece and none of whom controls the whole. The coordinating body’s power is not the power to command. It is the power to convene, to align incentives, and to make it easier for three sovereign parties to choose the same thing than to choose differently.
If that sounds familiar to anyone who has run a cross-organisational program, it should. It is the same problem, scaled up to nations.
What this teaches anyone delivering across boundaries
You do not need three countries to learn from this. You need only to have delivered something that crossed a line your authority did not — another department, another company, another jurisdiction, another culture.
A few things the three-host World Cup makes unavoidable, which are easy to dodge on smaller work until they bite:
Map the boundaries before you plan the work. The 2026 organisers could not treat the three countries as one space; the borders, rules and time zones had to be designed into the plan from the start, not discovered later. On any cross-boundary work, the seams between the parties are where delivery actually breaks, so they deserve attention first, not last.
Build the structure around the real distribution of effort, not the diplomatic one. Let the ceremony call everyone equal partners. Let the governance reflect where the work and the risk genuinely sit, or the overloaded side becomes a bottleneck nobody is allowed to mention.
Accept that you may not have a final decision-maker, and build for it. Where authority is distributed, influence and alignment replace command. The job becomes making the right choice the easy choice for parties you cannot instruct.
The first of its kind
The 2026 tournament is a genuine experiment — the first World Cup nobody has run before, in a shape nobody has tested at this scale. Whether it is judged a triumph or a cautionary tale, it is already the clearest live demonstration I can think of for a problem that turns up, smaller and quieter, on a huge number of ordinary projects: how do you deliver one coherent outcome when the thing is split across parties who do not share rules, do not share a boss, and do not share the load equally?
Most of us face a version of that. Very few of us face it across three nations and sixteen cities at once. Which is exactly why it is worth watching the people who do.
This piece sits alongside Why the FIFA World Cup Is Really a Program, Not a Project and The Governance Behind the FIFA World Cup.
Ben Webb is a Sydney-based project leader and former Australian Project Manager of the Year, sharing practical lessons from major projects, events and complex stakeholder environments.
Leave a Reply