There is a habit, common among people who have run one or two large things, of calling everything a project. It is a comfortable word. It suggests a beginning, a middle, an end, and a single person who can be blamed if it goes wrong. The trouble is that some undertakings are simply too big for the word to hold, and when you force them into it, you manage them badly.
The World Cup is the clearest example I know. People call it a project. It is not. It is a program — a coordinated collection of projects that share a deadline and almost nothing else — and the difference is not academic. Mistake one for the other and you will staff it wrong, govern it wrong, and discover the gap at the worst possible moment.
I want to take the distinction seriously, because it is one of the few pieces of project-management vocabulary that actually earns its keep.
What the word has to carry
Consider what is happening underneath the 2026 tournament, the first to be staged across three countries at once. Sixteen cities. Four time zones. One hundred and four matches across thirty-nine days. The United States alone carries seventy-eight of those matches; Canada and Mexico thirteen each. Each of those is its own operation — its own venue, its own workforce, its own transport plan, its own relationship with a local government that answers to nobody in the tournament’s head office.
No single project plan can hold that. You cannot draw one critical path through sixteen cities in three countries. What you can do is run each venue, each city, each function as a project in its own right, and then coordinate them toward the one thing they genuinely share: the calendar. That coordination layer is the program. It is a different discipline from project management, and pretending otherwise is how large things quietly fail.
A project optimises. A program reconciles.
Here is the distinction I have found most useful, learned the hard way on work far smaller than a World Cup.
A project manager’s job is to optimise a single delivery. Get this venue built, this system live, this event run, on time and on budget. It is a focused, almost selfish discipline, and rightly so. The best project managers are slightly obsessive about their own patch.
A program manager’s job is almost the opposite. It is to reconcile. To sit above a dozen project managers who are each, correctly, fighting for their own outcome, and to make decisions about which of them gives way when they collide. Because they will collide. The transport team and the security team will both be right and want opposite things. Two host cities will want the same scarce resource on the same weekend. Left alone, every project manager optimises locally and the whole drifts out of alignment. The program exists to manage the trade-offs that no individual project can see, let alone resolve.
A World Cup is nothing but those trade-offs, stacked thousands deep.
The deadline is shared. Nothing else is.
What binds a program together is rarely a shared method. It is a shared constraint.
The sixteen cities of the 2026 tournament have little in common. They operate under three national governments, three sets of labour law, three customs regimes, four time zones. A team might play group matches in different countries within days. The only thing every one of those moving parts truly shares is the date the football starts, and the fact that it cannot move.
That single immovable fact is what makes the program a program rather than a loose federation of unrelated events. Everything is reconciled against the calendar. When two projects conflict, the question is never “who is more important” but “which resolution protects the schedule.” A program without a binding shared constraint isn’t a program at all; it’s just a list of projects sharing a logo. The discipline comes from the constraint, not the org chart.
Why this matters far from a stadium
You are unlikely to run a World Cup. But you have almost certainly seen the failure that comes from calling a program a project.
It looks like this. An organisation launches something genuinely large — a transformation, a merger integration, a multi-site rollout — and appoints a single project manager to run it, because that is the word everyone reached for. The project manager, being good at their job, does what project managers do: builds one plan, one schedule, one risk register, and tries to drive the whole thing down a single critical path. For a while it holds. Then the constituent parts begin to pull in different directions, because they were always separate projects wearing one name, and the single plan cannot absorb the divergence. By the time anyone reaches for program governance, the trade-offs have already been made badly, by default, in a dozen rooms that never spoke to each other.
The fix is not heroics. It is recognising the shape of the thing early. Ask one question of anything large: does this have a single, optimisable outcome, or several outcomes that must be reconciled against a shared constraint? If it is the first, you have a project — staff it tight and let one person obsess over it. If it is the second, you have a program, and you need someone above the projects whose entire job is the reconciling. Get that diagnosis right at the start and most of the later pain never arrives.
The unglamorous conclusion
The World Cup looks, from the outside, like one enormous event. It is in fact dozens of separate deliveries, each run by people you will never hear of, held in alignment by a coordinating layer whose only real authority is the calendar everyone agreed to honour. That is a program, and seeing it as one is the difference between governing it and merely hoping it holds.
Most things are smaller than a World Cup. But the question that organises a World Cup — is this one outcome or many, held together by what? — is worth asking of almost anything you are about to lead. The word you choose at the start decides how you build everything after it.
This piece sits alongside two others in the series: The Governance Behind the FIFA World Cup and What the FIFA World Cup Teaches Us About Project Management.
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