The long season

Football has a fixture list, a rotation policy, a welfare case for five substitutes and a summer off, and it still can't stop its best players running down. Engineering teams have most of the same problem, a rota for the part they can count, and no end of season at all.

When Jürgen Klopp announced in January 2024 that he would leave Liverpool at the end of the season, two years before his contract ran out, he didn't reach for anything about a new challenge or the needs of the club. "It is that I am, how can I say it, running out of energy," he said, adding that "I know that I cannot do the job again and again and again and again" and that he had told the club in November. This was a manager who had won the league, the Champions League and both domestic cups since arriving in October 2015, so he isn't a cautionary tale about doing the job badly; by most measures he did it about as well as anyone in his era, and by his own account it still emptied him. Football has an elaborate apparatus for managing the load on its players, and almost none of it applies to the person who runs that apparatus, which is a fair place to start for anyone in engineering who has managed a team's pace while ignoring their own.

The apparatus for players is real, though, and much of it is written into the rules. When IFAB allowed five substitutes in May 2020, the stated reason was player welfare in a season that would now be played in a condensed period, and the evidence behind rotating players through a congested run of fixtures is fairly specific. An 11-season follow-up of the UEFA Champions League injury study found that league matches played after four days' recovery or fewer had a higher muscle-injury rate than those after six or more, with a relative risk of 1.32, mostly hamstrings and quads, while results were largely unaffected. That last finding is the uncomfortable one, because it means a manager who never rotates won't necessarily see it in the table, at least not straight away; the cost turns up in the medical room weeks later, and a club only rotates if it has decided that cost counts.

Engineering has its own version of this for the one part of the job that looks most like a fixture list, the on-call rota that feeds the incidents in Game state. Google's Site Reliability Engineering book is unusually blunt about on-call: SREs spend no more than half their time on operational work and "no more than 25% can be spent on-call"; "the maximum number of incidents per day is 2 per 12-hour on-call shift"; and a single-site rotation needs at least eight engineers to be sustainable, or six per site across two. Those numbers can be written down because pages are countable, in the same way that minutes and matches are. The trouble is that most engineering load isn't a page, and nothing in the industry's canon gives a project the equivalent of "two incidents per shift".

In my experience as a manager and a tech lead, long, tedious projects can lead to burnout, and usually will if the timelines and the goalposts keep moving, which matches the research on the engineering side. DORA's 2024 report found that "unstable organizational priorities cause meaningful decreases in productivity and substantial increases in burnout", and that the effect is "highly resistant to mitigation", persisting even on teams with strong leadership and good documentation. The WHO's definition of burn-out in ICD-11 describes it as a syndrome "resulting from chronic workplace stress that has not been successfully managed", and the word doing the work there is chronic; a moved deadline is a fixture added to a season that was already full, except that nobody publishes the fixture list and nobody sets a recovery window between the matches.

The second thing I've seen is that key people, the star players of a project, typically don't get the breathing room they deserve, even though they're the ones who most need it. Elite football does two things for its stars that software doesn't: it gives them a level of recognition, and it gives them a season with a clear start date and a clear stop date. A star on an IT project has neither, and the hero engineer is the name we give to a star player whose minutes nobody is counting.

That contrast flatters football, and the most recent evidence from the players' own union says the stop date is eroding at the very top of the game. FIFPRO's workload report for 2024/25 uses an expert consensus that players should get 28 days of off-season rest followed by 28 days of pre-season, and found that only 14% of Euro 2024 participants in its sample got the 28 days off. After the expanded Club World Cup in the summer of 2025, Chelsea's players had barely three weeks of holiday and 13 days of pre-season, and PSG's had seven days of pre-season; by comparison, NBA and AFL players get 14 weeks off and baseball players 15. FIFPRO is a party to the dispute over the calendar, but the direction is hard to argue with, and the players have started saying so in public. Rodri told a press conference in September 2024 that players were "close" to striking over the number of games, and that "there will be a moment where we have no other option."

So the analogy breaks, though not quite where it seems to. The obvious break would be that a squad has a defined season and a summer while engineering teams don't, which is still true for most of the game, but at the elite end football is drifting towards the engineering condition rather than away from it: the calendar fills up, the off-season shrinks to a couple of weeks for the players who matter most, and the recovery window becomes something negotiated case by case rather than guaranteed. The difference that remains is that footballers can see it happening, because their minutes and matches are counted in public and their union can publish a report on them, whereas the engineering version mostly runs invisibly, project by project, with the only measurement being whoever burns out. The other difference runs back to Klopp. Even with all that machinery for the players, nobody in football rotates the manager, and the person setting everyone else's load is the one with no substitute on the bench.

What I don't have a good answer to is what the engineering equivalent of a stop date would even look like. On-call got its caps because someone decided the pages were worth counting; a project's moving goalposts could be counted too, in reschedules and re-scopes and weeks past the original date, but would anyone treat that number the way an SRE treats an incident count, as a reason to stop and rest the people carrying it? If football, with its public scrutiny and its union and its calendar, still can't protect its season's end, who in an engineering organisation would be in a position to declare one?

No comments yet