The Crack on the Left Flank: The Manchester Derby and the Question Manchester United Stopped Asking

At 69, I do not believe in spectacular collapses; I believe in the quiet crack from last season. This crack is not in the attack, and it is not in the manager's chair. It sits on the left flank of Old Trafford, where Luke Shaw is waiting for the result of a fitness test taken close to kickoff.

Michael Carrick told reporters one short sentence: the club did not risk Shaw. To a news reporter, that is a quote. To anyone who reads the fixture list and the personnel file carefully, that is a clause. It says that right up to the day of the Manchester derby, Manchester United still did not know who would occupy the left flank — the position that governs both attacking width and the marking plan against Manchester City's wide overloads.

I traced three timestamps in the file. Shaw was withdrawn against Everton after a knock. He was absent for the midweek European fixture. And now comes a late fitness test, on the eve of the biggest match of the month. Three times, one position, the same question. That is not breaking news. That is a pattern. And a pattern, in my profession, is always more reliable than a quote.

To understand why a fitness test carries so much weight, it must be placed in the correct timeline of the season.

United enter the derby in eleventh place with four points from the opening rounds. That number forces most observers to pause, because it arrives after an almost flawless caretaker spell under Carrick. He won twelve of his first seventeen matches in charge. The INEOS-led hierarchy chose to hand him a permanent contract rather than pursue a big-name outside candidate. Four points and eleventh place, therefore, are no longer a pure result. They are a test of a personnel decision taken at the highest level of the club.

On the other side of the city, Manchester City arrive with a perfect record, sharing top spot with Arsenal. The form gap between the two sides is clear and needs no argument. But there is a timing variable few notice: United played a midweek European fixture immediately before the derby. This is not a derby in a rest week. It is a derby in the most congested week of the period, when players' bodies have not fully recovered and the coaching staff must weigh fielding their strongest XI against preserving personnel for the big match.

Carrick spoke of "a short space of time to recover and prepare." That sentence describes the real nature of the issue: this is a load-management story, not a tactical-design story. And when a club enters a major match with a personnel question ahead of a system question, you already know where that club stands in its development cycle.

I want to dwell on the left-back position, because in modern football it is the most underrated role relative to its actual importance. People talk about the number ten, the centre-forward, the holding midfielder. Very few spend time on the left-back. But the left-back is where the defensive system meets the attacking system, the hinge between the team's two states.

When United have the ball, the left-back determines the team's width. Without him pushing high, the midfield is compressed centrally, diagonal passes become harder, and the wide forward drops deeper to receive — meaning the advantage of space in the final third is lost. When United lose the ball, the left-back is the first man facing the opponent's transitions. Against a side like Manchester City, who overload the flanks and cut the ball back into the middle with relentless frequency, a loose left flank is not merely a weakness. It is an open door.

That is why Shaw's fitness test is not news about Shaw. It is news about the system. United enter one of their hardest matches of the season with an unanswered question in the position that controls both phases of play.

I once spent ten days reviewing all forty-seven attacking sequences of a national team to show that the problem was not the player but a system that had grown stale and was read nineteen times. I also once spent three weeks filtering data across one thousand two hundred matches just to prove something simple: the numbers do not lie, but the way we grip them in our hands does. That experience taught me that before a derby, the scariest thing is not a strong opponent. The scariest thing is that your own club has stopped asking the right questions.

So what is the right question here?

It is not "can Shaw play." That is the surface question. The right question is: why, after several seasons, does a club with resources at the highest tier in Europe still depend on the fitness of one individual at left-back?

That is a structural question, and it is not answered in a press conference. Nobody explains why United enter the derby without a sufficiently reliable backup on the left. Nobody explains why the club allowed one individual to become the linchpin of the whole system. Those questions tend to be buried under the headline "United worry over injury."

I have built my own personal data archive for each player across seasons. With injury-prone players, I mark patterns, not events. One withdrawal may be an accident. Three within a short cycle is a pattern. And when a pattern repeats in precisely the position where the club has no replacement of sufficient standard, it is no longer a medical issue. It is a squad-building issue, and squad-building is the responsibility of those in the boardroom, not the medical staff.

Carrick, in the press conference, said something worth crediting. He refused to let last season's derby result become a basis for confidence. He said the squad did not assume they would win again. Instead, he stressed "confidence built over a period of time." That is the language of a process-driven coach, someone who understands that the memory of a win is more dangerous than the memory of a defeat.

I rate that comment highly. I have seen too many teams live on the memory of an old win and then collapse in the next match. Confidence built on structure lasts; confidence built on a single result evaporates the moment the opponent scores first. Carrick, at least in his words, stands on the right side of that line.

But words and systems are two different things. And this is where I part ways with the majority who praise Carrick's calm.

When you enter a derby after a midweek European fixture, with four points and eleventh place, and with an unanswered question on the left, calm is no longer purely a virtue. It can become a form of psychological defence. It pre-frames a bad result by planting the ready-made line "we need time." I am not saying Carrick does this deliberately. But the pattern appears, and the pattern is data.

Here I must add a note on how football operates at club level. Every personnel decision leaves a mark on paper before it leaves a mark on the pitch. When a club fails to buy a backup left-back in a transfer window, that is not an accident. It is a choice — about budget, about wage structure, about which positions to prioritise. And those choices are signed. I have written many times that a contract is a signed confession. It tells you what the club believes, and what the club fears.

United enter this derby with a left flank dependent on one individual. Anyone who has followed the transfer market over recent seasons knows this is not new. What is new is that it happens in the exact week the club must face Manchester City.

I also want to raise another layer, rarely mentioned before a derby: the role of agents. For years, I have watched intermediaries generate noise around deals, shaping a player's value not by form but by narrative. That noise distorts the market, sometimes pricing an average left-back like a star. When the market is distorted at the price level, clubs are forced to choose between overpaying or buying nothing at all. And in the second case, they plant the seeds of exactly the personnel crises United now face on the left.

That does not mean United are blameless. It means the issue is more complex than a headline. But at 69, I no longer have patience for explanations that complicate a simple truth: a big club should not be waiting on a fitness test before facing the strongest side in the league.

To understand the contest better, look to the other side. Manchester City enter this match with a structure shaped over many seasons. They do not need to ask who plays where. They know who passes, who moves, who overloads. When a club reaches that state, it no longer depends on one individual's form — it operates like a machine that has been calibrated. The contrast with United is not in player quality. It is in the stability of the structure.

In a derby, that stability doubles in value. A derby is not a match for experimentation. It is a match where a settled system beats an unsettled one. And United, this week, are the unsettled side.

I have followed derbies across decades, and the pattern repeats: the club with a stable structure usually controls the tempo, regardless of the starting XI. A club in a building phase usually wins through inspiration, and inspiration is not reliable across ninety minutes. This is why I do not trust predictions built on "derby spirit." Derby spirit exists, but it cannot replace structure.

Back to load management. In modern football, when a club plays a midweek European game and then a weekend derby, the coaching staff face a series of hard decisions. They must calculate each player's minutes, weighing early substitutions in the midweek game against keeping the XI intact to preserve rhythm. These decisions are rarely seen by fans, yet they decide the derby's outcome before the derby begins.

Carrick is right to speak of a "short space of time." That is the reality of modern scheduling. But it is also why a club needs squad depth. If you must play a derby with an unanswered question on the left after a congested week, the problem is not that week. The problem lies in the earlier transfer windows, when you failed to buy.

Again, I must stress: this is not a personal criticism of Carrick. He has just taken the permanent job, and he inherited a squad built by others. But precisely for that reason, this derby matters more to him. If United lose, the question will no longer be "can Shaw play." The question will be "where is Carrick's project heading." And that is the question the hierarchy already asked itself when it chose him over an outside candidate.

I have said that memory is a legal code, not a nostalgia archive. That applies to this derby. The result of last season's derby — Carrick's first game in the dugout, and a win — should be treated as a clause to consult, not a talisman to carry. It tells us what can happen, not what will. Carrick himself seems to understand that, and that is his first mark in my book.

But I want to look beyond one match. The Manchester derby is a milestone in the season, but it is also a test of a governance philosophy. The INEOS-led hierarchy chose continuity over revolution. They chose to trust a coach who was once a player of the club, who understands its culture, rather than importing a big name from outside. This is a decision with an opportunity cost. If it succeeds, it reshapes how big clubs think about managerial appointments. If it fails, it becomes a lesson about patience misplaced.

So what will happen on the pitch?

If Shaw plays, I will watch whether he receives support from the wide midfielder or must mark one-on-one against City's overloads. I will watch whether United shift their defensive block toward the left to compensate, or keep the structure and accept the risk. If Shaw does not play, I will watch who replaces him and whether the system changes to cover the gap. The difference between these two scenarios says much about the maturity of the project the hierarchy chose to trust.

Here I want to return to my own caution. This analysis rests on a source that contains points requiring verification. In my profession, a reporter walks into a press conference and quotes a sentence, but a data writer must check whether the events surrounding that sentence match reality. Some details in this match's information flow — the European opponent, the domestic fixture list, Shaw's age, and Carrick's predecessor — need to be cross-checked against a database before they can serve as a foundation for any conclusion.

That does not weaken the analysis. It makes it more honest. Because the truth is that we live in an era where sports news travels faster than the speed of verification. A short item posted at ten in the evening can spread across forums before anyone reopens last season's file.

And this is the point I want to stress. United's problem before this derby is not the outcome of a fitness test. The problem is that the club allowed itself to reach a state where it must wait on a fitness test before the biggest match of the month. Every pundit talks about head-to-head records, form, psychology. Very few talk about squad structure. And squad structure, in modern football, is what determines the long-term survival of a project.

I once wrote about a player whose contract was scrutinised under every light, and then realised the problem lay beyond the numbers on the page. In the same way, every analysis of this Manchester derby will point at Shaw, at Carrick, at City's stars, at the pressure of four points. But the real problem lies elsewhere: a club of United's stature should not let its left flank depend on the result of a fitness test.

The numbers do not lie. The way we grip them in our hands does.

I will not predict the score of this derby. I do not believe in pre-match predictions, because football is a sport of variables, and the biggest variable of this match will appear in the first fifteen minutes — when we learn who plays left-back and whether United can cover the gap.

What I am waiting for is not a win. It is a structure. A mature club shows why it does not need to depend on one individual, even when that individual matters. If United manage that in this derby, Carrick's project has a foundation. If they do not, we will hear "we need more time" again — and at 69, I have heard that line enough to know what it usually hides.