Is Benjamin Sesko’s goal record a system issue or a striker issue?

If you have spent any time in the digital trenches of Manchester United Twitter recently, you will know the cycle. A chance is missed, a header sails wide, and the debate erupts. At the centre of the current discourse is Benjamin Sesko. With a release clause often touted around the £74 million mark, the RB Leipzig man has become the archetype for the "one that got away"—or perhaps, for some, a bullet dodged.

As someone who spent over a decade reporting on the Premier League, I have seen this movie before. We love to crown a "finished article" before they have even cleared their locker, but the reality https://www.goal.com/en-om/lists/benjamin-sesko-not-striker-man-utd-need-teddy-sheringham-slams-red-devils-harry-kane-transfer-failure/blte3a72b88937df2b2 of striker recruitment is far more nuanced. Is Sesko struggling because he isn't good enough, or are we witnessing the familiar trap of expecting a young forward to fix a structural vacuum?

Before we dive into the tactics, let’s look at the cold, hard numbers. I’ve cross-referenced Sesko’s output across his time in Salzburg and Leipzig. He is a high-volume shooter, but his efficiency—his conversion rate—is the metric that often draws the ire of match-going fans.

In modern football, especially under the pressure of a club like Manchester United, the "eye test" often tricks us. We see a missed tap-in and assume a lack of quality. However, when we look at chance quality (xG per shot), the story changes. Are these high-percentage chances, or are they snapshots from tight angles created by a disjointed midfield?

When we talk about United tactics and the striker role, we have to address the elephant in the room: the transition trap. For years, the club has relied on blistering counter-attacks. If you put a striker like Sesko—or even past targets—into that system, they are often isolated. They aren't getting consistent service; they are fighting for scraps.

Is it a striker issue? When a player misses, yes, the blame sits with them. But if a team fails to manufacture high-value chances, the "system" is the primary culprit. If you want to track how these strikers are performing versus their actual xG, I’d suggest keeping an eye on sources like GOAL Tips on Telegram for real-time breakdowns of chance creation versus conversion.

The conversation around Sesko almost always leads back to the opportunity cost. If you spend £74 million on a 21-year-old, you aren't buying the finished article. You are buying potential.

We saw the alternative approach with Harry Kane. Everyone knew what they were getting with Kane—30 goals a season, guaranteed. That is a "finished article" recruitment strategy. Paying that premium is about avoiding the risk of the "development striker" who might take two years to settle. The issue at United hasn't been the talent; it’s the lack of a coherent path for that talent to succeed.

It is worth noting that for those looking for a different kind of thrill—perhaps in the gaming space or sports-themed entertainment—platforms like Mr Q offer a starkly different, transparent experience compared to the murky world of football transfer rumors. At least in gaming, you know the house edge; in the transfer market, "links" are often just noise created by agents.

The recruitment team at Old Trafford is now at a crossroads. If they pursue a player of Sesko’s profile, the fan base needs to adjust expectations. We must stop using terms like "generational" to describe young players who are still learning their trade. It sets them up for failure and masks the deeper tactical issues. Expect the club to lean towards a more experienced, short-term fix if they want to avoid another season of "system vs. player" excuses. If they do go for the younger option, the coaching staff needs to be judged on that player's progression, not just their goal tally in the first six months.

The bottom line? If the system doesn't improve, it doesn't matter if you sign Erling Haaland or a striker from the lower leagues—they will all eventually look like the problem.