The Hollow Left Flank and the Progression Problem: Manchester United Enter the Battle with Atletico Madrid with a Patched-Up Squad

This season, I wrote in my thick notebook a line I wasn't sure I should write: Manchester United are building a structure based on players they themselves know cannot be trusted. I wrote that line after reviewing ten seasons of Luke Shaw, and I left it there, waiting for a day it would be proven.

That day came this week.

When Shaw left the pitch against Tottenham clutching his thigh, when Kobbie Mainoo was confirmed absent, when Patrick Dorgu was ruled out until next month, and when Noussair Mazraoui was also unlikely to feature, Manchester United no longer had a complete left flank. They had only Diogo Dalot, Leny Yoro, and an academy youngster named Harry Amass to fill two full-back berths before the trip to Madrid to face Diego Simeone's Atletico.

But if you think this is a story about injuries, you have misread the essence of the problem. This is a story about a system. And that system, I fear, was designed wrong from the start.

The man blocked at the J.League gate in 2026 now writes about how data changes tactics. Forty years ago, I stayed two hours after a 1-1 draw in Mitsuzawa just to redraw a pressing map, and I discovered that the team I was watching had deliberately pushed its defensive line high to trap the opponent offside. The lesson from that year still holds: you cannot judge a team by its injury list. You must judge it by what remains on the pitch after that list is written.

That is why I do not want to begin this analysis by counting how many players Manchester United have lost. I want to begin with a different question: when the left flank disappears, what happens to the way this team moves the ball from the back to the front? And the answer to that question is what truly decides the outcome in Madrid.

Let me tell you about what I call the left-flank domino principle, a principle anyone who has sat in the press box long enough understands, but few bother to write down.

Context: When an injury is not just an injury

Before going into tactical detail, I need to reconstruct the context precisely, because precision is the only tool an analyst has. Manchester United enter this period with a cluster of availability problems concentrated in a single area of the pitch: the left corridor.

Luke Shaw, whom I have always regarded as the best left-back English football has produced in the past decade when he is fit, left the pitch with an injury whose nature the club itself has not clarified. Patrick Dorgu, bought as cover for Shaw, is injured and expected back next month. Noussair Mazraoui, who can play either flank, is likely also absent. And in midfield, Kobbie Mainoo, the youngster expected to become the midfield pivot, is also missing.

The first thing I want you to notice is the concentration of these injuries. They are not scattered across the squad. They are piled into one corridor and one position. And when injuries pile into one position, it is no longer a matter of luck — it is a matter of squad design.

I have followed Manchester United for years, and I have always been struck by the fact that this club builds its ball-progression system around two attacking full-backs. In modern football, that is not wrong. Big clubs do it. But there is a difference between depending on full-backs and depending on two specific individuals at full-back. Manchester United do the latter, and that is their mistake.

To help you understand better, I need to explain a foundational concept that I know many readers will need, including those who seem to already understand it. When a team builds from the back, it needs to create passing lines through the opponent's pressing lines. The most common way is to use high full-backs to stretch the opposing defensive line and open space in the middle. If the full-back cannot push up — through injury, fatigue, or any reason — the entire space-creating structure collapses.

And that is exactly what will happen to Manchester United in Madrid.

But before going deeper, I must pause here, because there is something I need to say about the nature of the information I am analyzing. When I read the original report on Manchester United's availability, I noticed several points that do not match the reality I know. There are details about the coaching staff and about the opponent that I cannot verify from any other source. This does not mean all the information is false, but it does mean I must analyze with a higher-than-usual level of skepticism.

Debating a legend on camera, I learned that the truth does not need permission. In 2026, when I challenged a legend live on television about Japan's defensive tactics, I learned a lesson I have carried my whole life: when information is unreliable, you are not allowed to pretend it is reliable. You must say so, and then continue analyzing what can be analyzed.

That is my approach here. I will focus on the verifiable tactical content while clearly flagging the points I consider unreliable.

Core analysis: The left-flank structure and the collapse of the progression system

Now let me take you into the heart of the matter. I want to split this analysis into four layers, because Manchester United's problem is not a single problem — it is a chain of stacked problems, and if you only look at the top layer, you will miss the most important thing.

Layer one: The full-back crisis and the problem of only three options for two positions

According to the information I have, Manchester United will enter the Madrid match with only three options for two full-back positions: Diogo Dalot, Leny Yoro, and Harry Amass. Of those three names, only Dalot is a right-footed full-back with elite experience on the right. Yoro is a center-back, though he can play right-back if needed. Amass is an academy youngster.

Let me be clear about the nature of this situation. In a normal match, having three options for two positions is enough, even generous. But this match is not normal. This match is an away trip to face a team coached by Diego Simeone.

I need to explain Simeone to those who do not yet fully grasp his philosophy. Simeone is one of the last coaches of the old school, building his team on a foundation of low-block defending and counter-attacking. His teams do not try to control the ball in midfield. They wait for the opponent to err, and when the opponent errs, they punish. This matters because it means Manchester United will have to play with the ball, they will have to break down a crowded defensive block, and they will have to do it with a patched-up defensive flank.

That is the worst possible combination. When you face a low-block, counter-attacking team, you need two things: the ability to circulate the ball quickly on both flanks to stretch the block, and the ability to defend transitions well against the counters. With a young full-back or a center-back playing full-back, you lose both.

I have seen this too many times in my career not to recognize it. The teams that beat Simeone are the teams with full-backs good enough to attack and defend in the same phase. The teams that lose to Simeone are the teams trapped in a dilemma: they cannot push their full-backs up for fear of the counter, but they cannot keep them back because they need to stretch the block.

And when a team is trapped in that dilemma, it usually picks a half-measure: one full-back pushes up, one stays home. That is the structure I call the fake left flank, and it is one of the most exploitable structures in modern football.

Layer two: The disappearance of the progression profile and the low-block trap

Now let me move to the element I consider the most important, yet the most underrated in this story: the absence of Kobbie Mainoo.

In most articles, Mainoo is mentioned as an injured young midfielder. But if you look at Mainoo through a tactical lens, you see something else. You see a player with ball-progression ability, meaning a player who can receive the ball from deep and carry it forward by dribbling or by line-breaking passing.

I need to explain why this profile matters so much, and I will explain it thoroughly, because this is the point many readers will need.

When a team faces a low block, its biggest problem is not creating chances — it is getting the ball into a position to create chances. A low block works by closing space in midfield, forcing the opponent to pass sideways or backward. Every sideways pass is an opportunity for the block to shift and hold its structure.

To break that structure, you need a progression player — someone who can receive the ball in midfield and move it past the first line of the block. Mainoo is such a player. He can receive under pressure, turn, and advance.

And here is what I want you to remember: the absence of a progression player is more damaging than the raw count of injuries, because it attacks the very mechanism for breaking a low block — the thing Simeone wants you to lack.

Let me put it another way. If Manchester United lose three center-backs, they can replace them with three other center-backs and play the same way. But if they lose their only progression player, they cannot replace him with another player and play the same way — they must change the way the whole team plays. And changing the way the whole team plays just three days before a big match is something no coach wants to do.

I witnessed this in the match I analyzed in the J.League in 2026, when Kawasaki Frontale beat Urawa Reds 4-3. In that match, I modeled 1,200 games and realized that the xG metric alone could not explain the result. What I needed to add was the position where the attack began. And when I added that factor, I realized that teams with good progression players in midfield had a far higher ability to break low blocks than teams relying only on long passes.

Manchester United, without Mainoo, will have to rely on long passes or individual dribbles from the flanks. And both of those options are exactly what Simeone expects.

Layer three: De Ligt's return and the two-sided nature of a compensating solution

There is good news in this picture, and I want to spend time analyzing it fairly, because I do not want my analysis to be merely an indictment.

Matthijs de Ligt, the Dutch center-back, has returned to training after a long absence since last November. According to the information I have, he returned to training this month and may feature in the Madrid match.

De Ligt's return is an important structural offset, and I want to explain why.

In modern football, there is a type of center-back I call the ball-playing center-back. This is a center-back capable of stepping into midfield and participating in build-up. When such a center-back is present, he relieves pressure on the full-backs, because he can take on part of the build-up responsibility that normally belongs to the full-backs.

De Ligt is a ball-playing center-back. His return means Manchester United can play a structure in which the center-back steps up, the full-backs stay back, and midfield is reinforced by one extra man in the build-up phase.

This is a clever solution to the full-back problem. But it also has its downsides.

The first downside is re-injury risk. A player absent since last November — roughly eleven months — cannot return to peak intensity immediately. A player's body needs time to readjust to peak match intensity, and pushing him into a high-intensity match immediately upon return is a major risk.

The second downside is the rhythm problem. A player returning from a long injury often plays at a different rhythm from his teammates. He may be a beat slower in reading the game, and in a match against Simeone, where every second matters, one beat slower can be the difference between a successful defensive action and a conceded goal.

So when I say De Ligt is a compensating solution, I say it with a certain caution. He is a better solution than not having him, but he is not a perfect solution.

Layer four: The build-up structure and the question of what remains

Now let me stitch all these layers together and show you the whole picture.

Manchester United will enter the Madrid match with a build-up structure broken on the left flank. They will have a makeshift left-back, possibly a youngster or a player out of position. They will not have a progression player in midfield. And they will face a team coached to exploit exactly these weaknesses.

This is a situation in which, in my experience, coaches usually choose one of two solutions. The first is to shift to a more defensive structure, accepting that they will not control the ball and will try to counter. The second is to shift to a three-center-back structure, in which the full-backs play as wing-backs and the center-backs take on build-up responsibility.

I lean toward the second solution, because it fits the players Manchester United have better. If De Ligt returns, they can play with three center-backs, with De Ligt stepping up. This lets them protect the left flank by putting a center-back into that position while maintaining attacking width from the flanks.

But even this solution has its problems. A three-center-back structure demands mutual understanding among the center-backs, and with a shuffled defense, that understanding cannot be built in a few days. This is why I say Manchester United's problem is not a problem of one match — it is a problem of an entire structure.

All my life I watched the ball roll, but only when I stepped away from it did I truly understand. When I sat in the press box every week, I looked at each match as a separate event. But when I began analyzing seasons as chains of linked events, I realized a match is never a separate event. It is the endpoint of a long process, and what you see on the pitch is only the result of decisions made months, even years, earlier.

And those decisions, in Manchester United's case, created a structure dependent on players who cannot be trusted.

Contrarian view: The crisis story and what it hides

Now I want to offer a view I know will displease many, but which I believe needs to be said.

The story the media are telling is a story of a squad crisis. Manchester United lose two key players before a difficult match. That is the headline. And it is a compelling headline, because it touches fans' fears and creates pre-match tension.

But I have looked at the structure of this story, and I noticed something I consider notable.

First, the information in this story is not attached to any specific source. No journalist's name, no original outlet, no official club statement. This is a sign I have always regarded as suspicious, because in my profession, information without a source is unverified information.

Second, this story admits that the nature of Shaw's injury is unclear. This means that even if you believe the other information, you still lack the data to model his return timeline.

Third, and most importantly, this story is built on a pattern I have seen hundreds of times: a headline about a crisis, followed by details of absences, followed by a little worry about the upcoming match. This is a pattern of aggregated content, not tactical analysis.

And when I speak of this pattern, I am not speaking only of one specific article. I am speaking of an entire industry.

Let me explain this the way I learned it at 58, when I was forced to learn Python to model matches. At 58, I typed every line of Python to prove the youngsters wrong. But in that process, I also learned that data can be misused, and that a number without context is a meaningless number.

The same holds for news. An injury without tactical context is a meaningless injury in analytical terms. And the football media industry, especially in markets where the English Premier League dominates traffic, often produces injury news with no tactical context at all.

Why? Because injury news does not need tactical context to generate traffic. It needs only a big name and an alarming headline. It is a product of attention, not of analysis.

And here is what I want you to think about: if an article about a squad crisis gives you no information about how that crisis affects tactics, what does it actually give you?

The answer is: it gives you the feeling of being informed, without actually informing you. And that is an important distinction.

I want to add one more aspect of this story, one I consider more important than everything I have said.

The story of Manchester United's squad crisis hides another story, one the mainstream rarely wants to tell: the story of squad construction.

When a club depends on a player like Luke Shaw, who has a dense injury history, and has no commensurate backup, that is not an accident. It is a decision. It is a decision about resource allocation, about risk assessment, and about building a squad.

I have followed football long enough to know that the most successful teams are not the ones with the fewest injuries. They are the ones with structures least dependent on specific individuals. They build their systems so they can withstand the absence of any player.

Manchester United, in this period, do not do that. And that is the real story.

On the subject of injuries, I hold a view I formed over decades of observation, and I will state it plainly: fixture density is the single biggest cause of injuries, and no medical team can save a club playing two matches a week. When you play at that intensity for months, the human body reacts. And what we call an injury crisis is often merely the inevitable result of an unsustainable calendar.

This does not mean I exempt the medical staff from responsibility. It means I place responsibility where it belongs: at the level of fixture planning and player load management.

What I will watch in the match

Now let me move to the part I consider most useful to the reader: what specifically I will watch as the match unfolds, and why.

I always tell my younger colleagues that a good analyst does not merely describe what happened. They predict what will happen, and then verify their prediction. That is the only way to improve.

The first thing I will watch is the structure of Manchester United's defense in the build-up phase. Specifically, I will see whether they play with four defenders or three center-backs. If four, I will see how much their left-back pushes up and how much stays back. If three, I will see whether De Ligt steps into midfield.

The second thing I will watch is how Manchester United move the ball through midfield. Without Mainoo, they will need another player to take on the progression role. I will see whether they use another midfielder for it, or rely on long passes from the center-backs.

The third thing I will watch is how they react to Atletico's counters. This is the ultimate test for any makeshift defense. If they expose space on the left flank in transition, that will signal their structure is not yet built correctly.

And the fourth thing, which I consider most important, is De Ligt's rhythm. I will watch him in the first fifteen minutes to see whether he catches the pace of the match. If he is a beat slower than his teammates, Manchester United will have to adjust their structure to protect him.

Progressive thought

I want to close this analysis with a thought I have carried for a long time, one this match only reinforces.

In modern football, we talk a great deal about tactics, systems, and numbers. But we talk less about something more basic: the sustainability of a structure.

A sustainable team is one whose structure does not depend on the presence of any individual. It is a team where, if you remove a player, the structure still stands, merely changing shape.

Manchester United, in this period, are not such a team. And that is why their squad crisis is not a surprise event — it is a predictable outcome.

The question I want to leave you with is not whether Manchester United will win in Madrid. The question is: will they learn the lesson of building a structure on players who cannot be trusted? Because if they do not, the next crisis is only a matter of time.

And I, with my notebook, will be here to record it.