The Manchester Derby and the Limits of Reading a Match Through the Word 'Controversy'

On January 14, 2026, at Old Trafford, Marcus Rashford sprinted onto a long through ball. He was in an offside position. He never touched the ball. He ran across the eyeline of two Manchester City defenders and then stopped, letting Bruno Fernandes behind him slot the ball into the net. The assistant referee kept his flag down. VAR reviewed and upheld the goal. Manchester United won 2-1, and England got another argument that lasted weeks.

I sat with that match for a long time afterwards — not to rewatch the phase, but to reread IFAB's Law 11. What I found annoyed me more than the goal itself. The referee's decision had a clear basis in the written law, and yet it ran completely against the instinct of anyone who has ever played the game at any level.

As a former player, I do not need to watch footage to know who is running into the wrong space. But I have also learned that some moments cannot be resolved by footage, because the problem lies in the wording, not in the movement.

CONTEXT: ONE DERBY, TWO STORIES

The Manchester derby is the match the media loves most and the analytical community finds most exhausting. Loved because there is always something to write. Exhausting because most of what gets written orbits a single moment rather than a system.

In the press-conference cycle around Premier League weekends, a familiar list appears: Andoni Iraola of Bournemouth, Roberto De Zerbi of Marseille, Álvaro Arbeloa of Real Madrid Castilla. These names surface in roundups, and after a few rounds of copying they get attached to the wrong clubs. Iraola does not manage Liverpool. De Zerbi does not manage Tottenham. Arbeloa does not manage Fulham. Yet read enough online aggregations and you would come away believing otherwise.

I raise this not to catch out one particular outlet but to point at a mechanism: when speed outranks verification, a football event can be retold in a way that bears little resemblance to what happened on the pitch, with nobody held responsible for the drift.

Meanwhile the derby becomes a pretext for two very different stories. The first is about power: Pep Guardiola's Manchester City, the apex of possession football, a machine built with money and refined with data. The second is about inheritance: Manchester United, a club of memories, still searching for a rebuild across multiple managerial regimes.

Those two stories meet at exactly one point: both need an incident. And the cheapest, most sellable incident is always a controversial refereeing decision.

I once wrote a piece nobody read. Three years later it became my coaching manual. The lesson was simple: if you want to understand a match, start with what does not change — shape, space, the rhythm of transitions — not with what changes every week.

Every derby passes. Structure remains.

THE CORE: LAW, SPACE, AND WHAT ACTUALLY DECIDES THE MATCH

Start with the law, because that is where most of the misunderstanding lives.

IFAB's Law 11 states that a player in an offside position is penalised only for one of three categories of behaviour: interfering with play, interfering with an opponent, or gaining an advantage from that position. Interfering with an opponent covers three specific situations: challenging an opponent for the ball, clearly attempting to play a ball which is close while that action impacts an opponent, and making an obvious action which clearly impacts an opponent's ability to play the ball.

In the Old Trafford phase, Rashford did not challenge for the ball. He did not touch it. The only remaining question was whether his run impacted the City defenders' ability to play the ball.

That is the crux most of the debate skips. People argued about whether Rashford was offside, when that was never in question. He was. Everyone knew he was. The issue was whether the run of an offside player who never touches the ball counts as impact.

VAR read it this way: the City defenders retained the ability to reach the ball and to intervene, and their failure to do so came from Bruno Fernandes's distance and speed, not from Rashford. That is a technically defensible reading.

And that is precisely the problem.

A rulebook written to protect consistency of decision-making can end up protecting decisions nobody on the pitch believes are right.

I am not saying VAR got it wrong. I am saying the written law and the felt experience of the game are drifting apart, and that gap will keep generating controversy in every derby, whoever sits in the VAR room.

Now set the law aside and look at what actually decides results.

Between 2026 and 2026 the Manchester derby became a repeating experiment. On October 29, 2026, City won 3-0 at Old Trafford with two goals from Erling Haaland and one from Phil Foden. On March 3, 2026, City won 3-1 at the Etihad; Rashford opened the scoring and Foden turned it around with two goals. On May 25, 2026, United won 2-1 in the FA Cup final at Wembley through Alejandro Garnacho and Kobbie Mainoo. In December 2026, United won 2-1 at the Etihad under Rúben Amorim.

Four matches, four scripts, one common denominator.

The team with more of the ball was not the team controlling the match. In all four games the side dictating possession struggled in exactly one zone — the half-space in front of the penalty area.

When City build from the back they pull full-backs inside to create numerical superiority in central areas. That is a founding principle of positional play. It also opens the space behind the inverted full-back, and that space only appears in the precise instant the ball travels square or backwards.

United did not need constant high pressing. They needed to be in the right place within roughly three seconds of losing the ball.

Having watched a great many derbies this way, what stands out is not the goal count but the number of tactical fouls a possession side is forced into in midfield. Those fouls never appear in attacking statistics, but they are the clearest signal that a system is being bent out of shape.

Take Foden's goal in March 2026. It came from a transition after United lost the ball in midfield. Foden received in the half-space, exactly the zone United's midfield vacated as it pushed up. That was not luck. It was geometry.

Take the December 2026 game, when United won 2-1 at the Etihad. The method was geometric too. They did not try to impose themselves. They ceded the ball, kept compact distances between the lines, and waited for the moment City's defensive balance broke after an attacking phase.

What is striking is that both sides knew this beforehand. City knew United would wait. United knew City would push up. Yet the results changed season by season. The reason lies in execution quality, not tactical ideas.

Here is the point I want to underline: in a derby, the gap between two teams rarely lies in tactical ideas. It lies in the speed of decision-making in the three seconds after possession changes.

Those three seconds are not measured by possession share. They are not measured by pass counts. They only become visible when you watch continuously, match after match, and realise the team that wins the derby is always the one that reacts faster in that exact instant.

One more factor gets too little attention: squad depth and load management. The Manchester derby usually falls in a congested stretch of the calendar. In those periods, the deeper squad not only has more substitution options, it can sustain pressing intensity into the second half.

That is why decisive derby goals so often arrive after the 70th minute. Not luck. That is when the gap in fitness and depth starts to show.

One transfer-market detail belongs beside this analysis. When City signed Jack Grealish in August 2026 for £100 million — then a British transfer record — they were not buying a goalscorer. They were buying someone to hold the rhythm in the half-space, the zone where derbies are settled. When Erling Haaland arrived in summer 2026 for a reported fee of around £51 million, that deal was designed to solve one problem: matches City dominated without killing off.

I read a transfer not through its price, but through where the player will stand in the system. Placed side by side, those two deals say more about how City build for derbies than any television tactical breakdown.

One historical detail is worth remembering: by the most recent season, the two clubs had met more than 190 times in all competitions, and in the Premier League era City had moved ahead on wins. That number does not just reflect a financial gap. It reflects the stability of one system over more than a decade.

But stability is not permanence. The 2026-25 season proved it. United finished 15th in the Premier League and lost the Europa League final 0-1 to Tottenham in Bilbao on May 21, 2026 — their worst modern season. City finished third, behind Liverpool and Arsenal.

Both clubs declined, in different ways. City lost sharpness in decisive moments. United lost structure.

When both decline at once, the derby becomes a strange fixture: still marketed as a summit meeting, while the reality on the pitch is two teams wrestling with themselves.

THE CONTRARIAN ANGLE: WHAT xG CANNOT EXPLAIN

This part belongs to a bigger problem than any single derby.

Over the past decade, expected goals has become the default measure in every football argument. A team that wins with low xG is called lucky. A team that loses with high xG is called robbed. These claims sound scientific, which is exactly what makes them dangerous.

xG measures the quality of a shot based on location, angle, type of delivery and the number of players around it, drawn from a vast historical dataset. It is a good tool. But it measures one thing, and people are using it to explain everything.

xG cannot explain why a defender left the half-space open in the 80th minute but not the 20th. It cannot explain why a player returning from injury chose the safe pass instead of the decisive one. It cannot explain why a team dropped its block after taking a one-goal lead, or whether that drop was a tactical instruction or a psychological reaction.

Most importantly, xG cannot explain a referee's decision.

In that Old Trafford phase in January 2026, no xG figure describes what happened. The goal was lawful and instinctively absurd. No data model reconciles those two things, because they belong to different frames of reference.

The same holds for officiating standards. A referee may whistle a challenge in the 15th minute and let an identical one go in the 85th. That is a fact of football, and it appears in no dataset. People call it inconsistency. In many cases it is how a referee manages a match, not a technical error.

The problem is that xG has produced a generation of viewers who believe everything on a pitch is quantifiable. When reality does not match the number, they do not doubt the number. They doubt the match.

That is the biggest blind spot in football analysis today.

Another, less discussed blind spot: the press-conference loop. After every matchday, managers sit down and say things that contain almost no information. They talk about spirit, focus, the need to improve. Those remarks get recorded, published, circulated, and eventually form a fog over what actually happened.

The lesson from the tunnel: the silence before a match says more than any press conference. I have stood there often enough to know that when a team emerges and nobody speaks, it usually signals a plan already agreed. When everyone talks, usually nobody yet knows what they will do.

That brings me back to Iraola, De Zerbi and Arbeloa. Those names were attached to the wrong clubs in roundups, and nobody corrected it. A small error. But it reveals a larger habit: football media increasingly prioritises volume of content over accuracy of content.

I am not making that point from a moral high ground. I am making it from a practical one. Once small distortions go uncorrected, large ones go undetected.

The 2026 World Cup taught me something: hesitation is the thing that ruins every plan. It also taught me the reverse: deciding too fast without verified data ruins plans too, just more quietly.

WHAT TO WATCH NEXT TIME

If the data is right, the decisive variable in the next Manchester meeting is not the starting XI. It is three things.

First, the speed of the second transition — the counterattack immediately after a team snuffs out the first wave. In recent derbies, most goals have come from second transitions, not first.

Second, where the holding midfielder stands while his team attacks. If he pushes level with the other two central midfielders, the half-space behind him opens. If he stays lower, the team has fewer attacking options and is harder to hurt.

Third, how both sides handle late set pieces. In high-tension derbies, corners in the 85th minute are often rehearsed more carefully than open play.

In a chaotic season, what a strategist needs most is the clarity of an outsider. I do not know how the next meeting will end, and I will not pretend to. What I do know is this: if the derby is once again retold through the word "controversy", that is a signal nobody really wants to talk about what decided the result.

One final thought is worth keeping. For more than a decade the Manchester derby was defined by the distance between two systems. That distance is narrowing, but in a way few expected: not because United have caught up, but because both clubs are rebuilding from different foundations.

In 2026 everything collapsed. I got up and rebuilt from the rubble. In football, a club's rubble is not cleared in one season, and it is not cleared by one signing. It is cleared by hundreds of small decisions, most of which nobody ever sees.

The next derby will not tell us which team is stronger. It will only tell us which one has finished clearing its rubble.