There is a moment, perhaps eleven months out from a World Cup, when someone in a quiet office realises the date will not move. It is a strange thing to watch settle over a room. The tournament has a kickoff time. It has had that kickoff time for years. And no amount of slippage, goodwill, or carefully worded status report will persuade the planet to wait while the broadcast compound is finished.
I have spent a good part of my working life in rooms like that one, and I have come to believe something the profession would rather I didn’t. Most of what we call project management is theatre. The documents, the ceremonies, the reports nobody reads, the risk register opened once and never again. We have taken a practical craft and dressed it as an industry, and somewhere in the costume change a great many people came to believe the costume was the work.
It isn’t. The work is delivery. The match starts on time or it does not, and everything else is either in service of that or it is waste.
The deadline that cannot be charmed
Most projects run on soft deadlines, and soft deadlines breed a particular kind of dishonesty. There is always a next sprint, a next phase, a next quarter in which the sin will be absolved. Teams slip, and the slippage is folded into a revised plan, and the revised plan is presented with the quiet confidence of people who have never once been held to the first one.
A World Cup offers no such mercy. The opening fixture is printed on tickets held by people flying in from forty countries. It is sold to broadcasters in contracts measured in the hundreds of millions. It cannot be charmed, escalated, or workshopped into a more convenient shape.
What that immovability does to a project is clarifying, almost violently so. When the date genuinely cannot move, you discover with great speed which of your activities were holding the thing together and which were merely keeping people occupied. Much of what fills an ordinary project would not survive a deadline like this. It exists because no one has yet been forced to ask whether it changes the outcome.
People are the means, not the message
It has become fashionable to say that projects are really about people. It is the kind of line that earns warm nods in a conference room, and it is half true, which is the most dangerous thing a line can be.
The organisers of a tournament command almost no one directly. The people who build it work for governments, for contractors, for sponsors and broadcasters and city councils, and not one of them can be issued an instruction. They can only be persuaded, aligned, occasionally flattered, and brought to move in roughly the same direction at roughly the same time. This is the real content of stakeholder management, and it is far less tender than the conference-room version suggests.
I have watched projects with immaculate culture and beautiful plans drift quietly past their dates because the relationships were being tended as an end in themselves. Warmth is not delivery. The reason to spend time on people is that nothing gets built without them — and the moment relationship-building becomes a polite way of avoiding a hard call, it has stopped doing its job.
The register is not the work
Every serious project keeps a risk register, and most of them are worse than useless, because they grant the people who write them the sensation of having done something. The word power failure sits in a spreadsheet, neatly coloured amber, and everyone feels a little safer. The spreadsheet does nothing on the night the power actually fails.
At the scale of a tournament the illusion is unaffordable. You plan for weather and transport collapse and a broadcast feed dying in front of a billion people, and what protects you is not the document but the standby generator, the second venue, the rehearsed thing you do when the first thing breaks. The register is a list. Readiness is a state. They are not the same, and confusing them is how projects walk confidently off a cliff they had carefully catalogued in advance.
Governance, or friction in a suit
Here I will irritate the part of the profession that loves a steering committee. A great deal of project governance exists to make senior people feel in control rather than to help the thing get delivered, and the two are easy to tell apart once you know what to look for.
Good governance draws a boundary and then trusts people to move freely inside it. Bad governance pulls every decision upward until the project advances only as fast as the busiest executive can clear their inbox. A tournament cannot tolerate the second kind. Thousands of people across dozens of organisations cannot funnel every choice to one desk; the whole apparatus would seize. So authority is pushed down to the people standing closest to the problem, and they are trusted to use it. Governance that adds sign-offs without adding outcomes is not governance. It is friction wearing a suit.
The invisibility is the proof
Delivered well, a major event looks like nothing at all. The crowd sees a ceremony unfold smoothly and assumes it was always going to. They do not see the eighteen months behind it, or the hundred problems solved quietly in the hours before the gates opened, and they are not meant to.
I have made my peace with this, and over the years I have come to think the invisibility is the point rather than its melancholy side effect. If the audience is aware of your project management, something has usually gone wrong. The result should speak so completely that the machinery behind it disappears. The project managers I trust least are the ones who need the machinery to be admired.
What survives the lights
None of this requires a tournament. It scales down without losing its shape — to a product launch, an office move, a fundraising campaign run out of a borrowed room.
Hold a single question over everything you do: does this bring delivery closer, or does it merely feel like progress? Treat the deadline as real before anyone forces you to. Spend time on people because it builds the outcome, not because it is pleasant. Make risk a change in your readiness rather than an entry in a file. And when a process cannot show what it adds to the result, find the nerve to end it.
The World Cup is simply project management with the lights on and nowhere to hide, and its verdict is brutally plain. The match began on time, or it did not. We would all deliver better, I suspect, if we judged ourselves by that line and no other — not by how the plan looked on the wall, but by whether the thing actually worked.
Two other pieces in this series push on threads above: Why the FIFA World Cup Is Really a Program, Not a Project and Stakeholder Management Lessons from 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