Trang chủInternational FootballAnatomy of the Gap Between Two Centre-Backs: PSG, Atalanta, and the Rhythm of a Predictable Collapse

Anatomy of the Gap Between Two Centre-Backs: PSG, Atalanta, and the Rhythm of a Predictable Collapse

Câu trả lời cốt lõi: PSG thua Bayern 0-1 ở chung kết Champions League 2020 tại Lisbon vì khoảng trống giữa hai trung vệ mở ra khi Marquinhos dâng cao đá tiền vệ, để Kingsley Coman ghi bàn ở phút 59 từ quả tạt của Joshua Kimmich. Sự kiện then chốt: - Ngày 23 tháng 8 năm 2020, Bayern Munich thắng PSG 0-1 tại Estádio da Luz, Lisbon. - Kingsley Coman, cựu cầu thủ lò đào tạo PSG, ghi bàn duy nhất ở phút 59. - Marquinhos được Thomas Tuchel kéo lên đá tiền vệ phòng ngự suốt mùa 2019-2020. - PSG thiếu một tiền vệ phòng ngự đúng nghĩa trước Bayern Munich. - Ligue 1 kết thúc ngày 30 tháng 4 năm 2020; Champions League tổ chức tập trung tại Lisbon. Nguồn: Phân tích chiến thuật gốc của Nguyễn Cường, xuất bản tháng Sáu năm 2020, kiểm chứng với dữ liệu trận chung kết ngày 23 tháng 8 năm 2020. | Cross-checked: VuaBong.vn Hỏi đáp liên quan: Hỏi: Vì sao PSG để lộ khoảng trống giữa hai trung vệ trước Bayern? Đáp: Vì Marquinhos dâng cao đá tiền vệ, khiến Thiago Silva và Kimpembe phải chơi với không gian phía sau mà họ thiếu tốc độ để bù đắp. Hỏi: Atalanta khác PSG ở điểm chiến thuật nào? Đáp: Atalanta gây áp lực bằng cách đọc vị trước khi bóng đến, dựa trên chỉ số PPDA thấp và dữ liệu chuyển động, thay vì chạy nhiều hơn đối thủ. Hỏi: Yếu tố nào ngoài chiến thuật quyết định cuộc sụp đổ của PSG? Đáp: Mật độ lịch thi đấu bị nén mùa 2019-2020 làm giảm khả năng phục hồi, khiến các quyết định vị trí ở phút 59 trở nên sai lệch.

The 59th minute, August 23, 2026, Estádio da Luz. Kingsley Coman rises to meet a cross from the right by Joshua Kimmich, and the ball goes into the PSG net. In the commentary booth in Lyon, I did not stand up. I had seen that moment coming since June, when I sat alone in my apartment, rewound the Dortmund tapes, and drew on paper a triangular gap between Marquinhos and Presnel Kimpembe. Coman's goal came precisely from that gap. That is why I did not cheer. A tactical analyst does not cheer when his prediction comes true; he records it, then goes looking for the next error.

I tell this story not to praise myself. I tell it because it opens a larger question I have pursued for fourteen years, from a television sports department in Belgrade to studios in France: can a collapse at the highest level of European football be foreseen through data, or only through the intuition of the lucky? My answer, after being wrong many times, is both — but the percentage is not where you think it is.

Context: a season compressed to the breaking point

To understand why PSG lost that final, you have to start where nobody wants to start: the schedule. The 2026-2026 season was cut in half by the pandemic. Ligue 1 declared its season over on April 30, 2026, awarding the title to PSG while they sat an unbridgeable distance ahead of the rest. The Champions League, the competition this club had poured a decade and billions of euros into, was postponed, then restructured into an eight-team tournament in Lisbon in August. Everything became a miniature cup competition, single-elimination, no second legs, no time to correct mistakes.

For most fans, that was an attractive format. For me, it was a frightening one, because it erased the very thing a big club needs most to survive a season: time. I have covered eight Olympic Games, eight World Cups, and many editions of the Giro d'Italia and the Tour de France. In every endurance sport, I learned the same lesson: the body does not fail because of a moment, the body fails because of a schedule. Football is no different. When you compress a nine-month season into three weeks, you do not create heroes; you create breaking points, and you are only waiting to see which one snaps first.

PSG arrived in Lisbon as French champions, with the most expensive squad in Europe at the time, with Neymar and Kylian Mbappé at the peak of their form, and with a collective belief that this was their year. I had watched them all season. I had taken notes on every match. And what I recorded was not dominance but a worrying repeating pattern: PSG won through individual quality in the first half, then shrank in the second, allowing opponents to control the ball and create chances. They won because their best players were better than the opponent's best players, not because their system was better.

I once wrote, in an analysis sent to an editor in early June, a line colleagues would later quote many times: "I predicted PSG would break down from mid-season; they simply chose the right schedule to break." That line was not a curse. It was a conclusion drawn from data. When a team tends to reduce its pressing intensity after the 60th minute, and when it enters a knockout format with no second legs, its match will be decided in the period where it is weakest. The only question is which opponent is patient enough to wait for that moment.

Mechanism: the gap between two centre-backs

Let us talk about what actually decided that final. Not Neymar. Not Mbappé. But the position of Marquinhos.

All season, Marquinhos — a centre-back by instinct — was pushed forward by Thomas Tuchel into defensive midfield. This was a smart tactical decision in a specific context: it gave PSG a player capable of reading the game, winning the ball, and launching counters from midfield. But every tactical choice has a price, and the price here was not discussed enough. When Marquinhos pushes up, the PSG defence loses its last screen. Thiago Silva and Kimpembe must play with space behind them, and they are not the type of centre-backs with the pace to compensate for that space.

This is the mechanism I want you to see clearly. In modern football, goals are not created where the ball arrives, but where the ball leaves. When Marquinhos leaves the centre-back position, he leaves a zone of space that an opposing midfielder can exploit with a single straight pass. Bayern Munich under Hansi Flick were the perfect team to exploit that zone, because they do not need to control the ball to create chances — they need one transition moment. And PSG, with a midfield thinned by Marquinhos's own advancement, were the perfect team to be exploited that way.

I mapped heat diagrams for five of PSG's Champions League matches that season. In the first four, Marquinhos tended to stay in the centre-back position when PSG lost the ball. In the final, he pushed higher, because Tuchel needed him to deal with Bayern's ability to switch the ball quickly in midfield. It was a gamble. And when the ball went into the gap between Thiago Silva and Kimpembe in the 59th minute, that gamble lost.

What is worth noting is that Coman's goal was not a counterattack. It was a set piece converted into a wing attack, and it came from a player PSG had let go for free years earlier. Coman, a product of PSG's own academy, scored against his former club. There is an irony there I do not want to romanticise, but cannot ignore: a club that spent hundreds of millions of euros on outside stars was beaten by one of its own, in a position it had sold cheaply.

Verratti and the question of a defensive midfielder

In the three months before the final, I spent most of my time analysing Marco Verratti's passing. This is a player I deeply respect technically: he has a capacity to handle the ball under pressure that very few midfielders in Europe possess. But when you look at Verratti through a tactical lens, you see a different problem. Verratti is a deep-lying playmaker, not a defensive midfielder in the traditional sense. He breaks up passing lanes by reading them early, not by tackling. That works in Ligue 1, where PSG dominate most opponents in possession. It does not work against Bayern Munich.

I said this in an early-June piece, when the Champions League was still suspended and nobody wanted to talk about a final that had not yet been scheduled. I wrote that PSG lacked a true defensive midfielder against Dortmund, and that if they advanced, the problem would return larger in the next round. Three warning pieces about the gap between the centre-backs when Marquinhos pushed up. One of them was published. Two remained in an editor's inbox, never printed.

When PSG reached the final and lost 0-1, the goal came from the gap I had sketched in the June piece. Colleagues began calling me a "tactical prophet". I do not like that title. It places me in a position I do not want: the position of the person who is always right. I know exactly how many times I have been wrong. I know that behind every correct prediction are dozens of wrong ones nobody remembers, and that is why I started keeping a public prediction tracker, to check myself at the end of every season.

But before leaving this subject, I want you to notice a detail few people mention. PSG's problem was not that they lacked stars, but that their stars occupied too much space in the structure, to the point that the structure no longer had room to operate on its own. When you have Neymar and Mbappé on the flanks, your full-backs must play high to create width, and when they play high, your midfield must shrink to compensate. When your midfield shrinks, the gap between the centre-backs opens. That is not one individual's fault. It is the mathematical consequence of stacking too much individual talent into a structure not designed to hold it.

Atalanta: when pressing is reading, not running

To see this mechanism more clearly, compare PSG with a team at the opposite pole philosophically: Gian Piero Gasperini's Atalanta. I started following Atalanta in 2026, after watching them face Juventus in Serie A. In that match, Gasperini's side pressed high 62 times in 90 minutes, cutting off every pass from Juve's back line. Nobody in the French media noticed. I wrote a 3,000-word analysis of the system I called "zonal pressing defence" and sent it to two editors.

The piece was published. But I declined an invitation to go on television in order to keep studying the movement data of Atalanta's eleven players over five more matches. I needed to understand what actually happens when a team presses, not what commentators say about it. And what I found changed the way I write forever.

Atalanta do not press, they read the opponent before the referee blows the whistle. That is the line I wrote in that analysis, and it remains the line I am proudest of. What I meant is not a pretty metaphor. It is a quantitative observation. When I tracked Atalanta's movement data, I realised their players do not run more than their opponents. They run less in some matches. What they do differently is initiate pressure earlier, based on reading the opponent's passing habits. They do not react to the ball; they react to the passer's intention, and they do so before that player realises he has revealed his intention.

That is why I began rejecting "pressing" as a framing term. Pressing, in the ordinary sense, is running toward the ball. What Atalanta do is occupy space before the ball arrives there. The difference matters because it changes how you build a squad. If pressing is running, you need fast and strong players. If pressing is reading, you need intelligent and disciplined players. Gasperini builds his team the second way, and that is why Atalanta, on a budget far smaller than Serie A's big clubs, can compete in the Champions League.

I have used pressure metrics (PPDA — passes allowed per defensive action) in every tactical analysis since. But I also learned that PPDA alone is not enough. You need heat maps to see where pressure is applied, and movement data to see when it is applied. A team can have a low PPDA and still defend badly, if they press in the wrong zone. And a team can have a high PPDA and still defend well, if they read the opponent so well they do not need to press.

This brings me back to PSG. If Atalanta are the team that reads opponents, then PSG in 2026-2026 were the team being read. Bayern did not need to press PSG continuously; they only needed to wait for the moment when Marquinhos pushed up and Verratti lost position, then attack the gap. They did it once, and once was enough.

The blind spot: schedule and injury

This is the part I want to spend the most time on, because it is the part most analysts skip. When we talk about a tactical collapse, we usually talk about the manager's mistake, a player's weakness, luck. But there is a larger factor behind all of it: fixture density.

I have covered endurance sports for years, and I learned something football often forgets. Fixture density is the biggest culprit behind injuries; no medical staff can save you from two matches a week. This is not an opinion. It is a conclusion supported by decades of data from every professional sport. When the body must compete at high frequency continuously, it does not recover enough, and when it does not recover enough, soft tissues begin to accumulate micro-damage. That damage does not show immediately. It shows in a sprint in the 75th minute, in a jump in the 59th minute, in a moment when the body is no longer fast enough to compensate for a wrong decision.

Looking back at the Lisbon final, I wonder whether Coman would have scored that goal if both teams had been fully rested. This is a question that cannot be answered with certainty, and I do not want to fall into the trap of unverifiable speculation. But I can say this: both PSG and Bayern entered the final after a compressed season, and both had players who had competed at high frequency for weeks. Under those conditions, the gap between the centre-backs is not just a tactical problem; it is a physiological one. A tired centre-back does not react in time to a pass, even if he reads it.

This is why I track recovery metrics with as much attention as tactical metrics. When I analyse a team, I do not only ask how they play; I ask how many matches they play in how many days. A team can have the best system in Europe and still collapse if that system is operated by exhausted bodies. Modern football is increasingly becoming a war of medical and fitness departments, and analysts like me must admit that.

I have covered eight Olympic Games. There, I saw athletes managed to the minute in training load, and national teams with an entire sports-science apparatus behind them. Football does not have that luxury. A club plays three matches a week in December, then three matches a week in April, and we are surprised when its stars get injured. That surprise is unwarranted. It is simple mathematics.

Personal error as an analytical tool

I must tell you a personal story, because it relates directly to how I write today. In 2026, at 28, I worked as a pitchside commentator for France vs Sweden in the 2026 World Cup qualifiers on a new sports channel. In the first half, I mispronounced the name of midfielder Ola Toivonen three times. The director had to correct me through my earpiece. After the match, I felt shame in a way only media professionals understand: you have spoiled a moment millions are watching, not because you lack knowledge, but because you lack preparation.

I spent a month reviewing all the footage, noting the correct pronunciation of 200 European players, and building my own phonetic table by source language. Since then, every analysis of mine carries international phonetic notes beside player names, and I cross-check data before publishing. This habit did not only help me avoid identity errors; it changed how I approach the whole craft of writing.

When I mispronounced a player's name, I learned to listen to the rhythm of the match. This is a line I wrote in my professional journal, and I mean it literally. When you are forced to pay attention to every syllable of a name, you also begin to pay attention to every rhythm of a match. You realise that a match is not a series of discrete events; it is a rhythm, and that rhythm can be heard if you listen carefully enough. Static data never reaches that rhythm. You must watch the match, many times, and you must notice details you usually ignore.

I say this because I believe accuracy is not a minor virtue in this profession. It is the foundation. If you are not accurate about a name, how can you be accurate about a system? If you are not accurate about a number, how can you be accurate about a conclusion? This is why I refuse to draw hasty conclusions without sufficient quantitative data. My style became systematic, building arguments from a view of squad space rather than emotion, not because I am cold, but because I am afraid of making mistakes.

Probability scenarios: three paths of a match

Since I began writing for the French market, I have developed a method I apply to every analysis: build three scenarios for how a match will unfold and rank probabilities by data. This is not an intellectual game. It is a tool for controlling error.

When I analysed PSG vs Bayern, I built three scenarios. Scenario one, highest probability: PSG defend and counter, keep Marquinhos at centre-back, and use Mbappé's pace. Scenario two, medium probability: PSG push forward for a goal, expose space behind, and get punished. Scenario three, low probability: PSG control the ball and impose tempo, which I judged unlikely against a pressing team as good as Bayern.

Reality followed scenario two. This is why I say my prediction was not luck. It was a verified probabilistic conclusion. But I must admit one thing: I rated scenario two as medium, not high. If I was right about the outcome but wrong about the probability, then I was still not truly right. This is the kind of self-criticism I consider necessary to maintain the integrity of the method.

Football has no luck, only details that have not yet been lined up. This is a line I use in many pieces, and it is often misunderstood. I am not saying everything in football is predictable. I am saying that what we call luck is usually a detail we have not noticed enough to include in the model. A ball hitting the post, a referee missing a foul, a player slipping on wet grass — all of these seem random, but they occur within a probabilistic context. The post is not random; it is the result of a shot at a certain angle, from a certain position, in a certain situation. If you model it in enough detail, you can assign it a probability.

Of course, there is another line I also use, and it seems to contradict the one above: "football is a game of luck". I use both because I believe both are true to some degree. Football is a game of luck at the level of a single match, where one moment can decide everything. But football is not a game of luck at the level of a season, where patterns and structures are verified across dozens of matches. The tension between these two lines is the space in which I work.

Looking at the bench before the goal

There is a habit I developed over years, and it changed how I watch football. When a team wins, I look at the bench before the goal. This is a line I wrote in an analysis of substitution tactics, and it became a working principle.

The reason is simple. A goal is an event. It can come from individual talent, from an opponent's mistake, from a lucky moment. But a bench is a structure. It shows you what the manager thinks about the match, which scenarios he has prepared for, and which players he trusts. When Tuchel made his substitutions in the Lisbon final, I looked at his bench and saw a problem: PSG had no true defensive midfielder to bring on when they needed to protect a result or reinforce midfield. They had attacking players, but they lacked players who could change the defensive structure.

This is a problem built beforehand, not during the match. It stems from how PSG built their squad over years: focus on attacking talent, neglect balance. When you look at their bench in the final, you see a team designed to win 3-2, not to protect 1-0. And in a final, the ability to protect a result matters as much as the ability to create one.

I apply this principle to every match I analyse. Before I write about the decisive goal, I write about the bench. Before I write about the star who shines, I write about the player substituted off. Football is decided in places few people look, and the bench is one of them.

Peeling off labels: reading real behaviour instead of terminology

One of the things I try to do in every piece is avoid framing terms. "Pressing" is one example. "Counterattacking" is another. "Possession" is a third. These terms are useful as starting points, but they become dangerous when we use them in place of observation.

I prefer describing behaviour to applying labels. Instead of "Atalanta press high", I say "Atalanta occupy space before the ball arrives". Instead of "PSG control possession", I say "PSG keep the ball in low-danger zones and lose it in high-danger zones". The difference is not just words. It changes how you analyse, because it forces you to specify who does what, where, when.

This is why I often begin an analysis with a specific moment, not an abstract concept. A moment can be verified. A concept cannot. If I say "PSG lack tactical balance", you cannot verify that. If I say "In the 59th minute, Marquinhos is in midfield, and the gap between Thiago Silva and Kimpembe is 12 metres wide", you can rewind the tape and check. This is the standard I hold myself to.

I once got a person's name wrong, but I have never got the essence of a match wrong. This line sounds arrogant, and I must admit it partly is. But it is also a commitment. It means I accept mistakes at the level of detail, but I do not accept mistakes at the level of essence. When I say a match is decided by the gap between two centre-backs, I mean it, and I am ready to defend it with data. When I am wrong at that level, I will admit it, and I will fix my model.

The blind spot of execution: when the tactic is right but the body is wrong

This is the most counterintuitive part of the story, and the part I consider most important. We usually talk about tactics as if it were a plan on paper, and as if players only need to execute it. But there is a gap between plan and execution, and that gap is usually filled by factors we do not call tactics.

In the Lisbon final, PSG had a reasonable plan. They wanted to defend tightly, exploit Mbappé's and Neymar's pace on the counter. That plan was not wrong. But it required a level of discipline and fitness PSG did not have at that moment. When players tire, they no longer hold positional discipline. Marquinhos pushed up not because it was the plan, but because he felt he needed to help the team win the ball in midfield. That was the decision of a tired player, not the decision of a manager.

This is the blind spot I want you to notice. A correct tactic does not mean correct execution, and poor execution is usually not the player's fault, but the fault of whoever put him in that situation. When you ask a team to play at high intensity in a compressed season, you are creating the conditions for execution errors. You are asking the body to do what the body cannot reliably do.

I have seen this in many other sports. In cycling, a rider can have a perfect tactic for a mountain stage, but if he has not recovered enough from the previous stage, that tactic collapses in the final kilometre. In the marathon, a runner can have a sensible pacing plan, but if he has not slept enough in the week before the race, that plan collapses at kilometre 35. Football is no different. A tactic is a plan for a healthy body; it is not a plan for an exhausted body.

This is why I believe tactical analysts need to understand sports physiology. Not to become experts, but to avoid making mistakes when assessing a team. If you only look at the tactical diagram, you will miss the decisive factor. If you only look at fitness data, you will miss the tactical factor. You need both.

When a team breaks down: reading a weakening structure from mid-season

One of the skills I am proudest of is the ability to point to a team's day of collapse before it happens. I do not comment after the match; I track a weakening structure from mid-season and show how a team picks the right schedule to break.

This is not a gift. It is a method. When I track a team, I do not only look at results. I look at process metrics: xG (expected goals), xGA (expected goals against), PPDA, shots from inside the box, losses of possession in dangerous zones. When these metrics begin to diverge from results, I know that team is living on luck, and luck always runs out.

With PSG in 2026-2026, I saw a clear pattern. In group-stage matches, they won by wide margins, but their xG was not that high. They scored from difficult chances and missed easy ones. This is the sign of a team dependent on individual talent rather than system. When you depend on individual talent, you can win many matches, but you cannot win a knockout tournament. Because in a knockout tournament, you will meet an opponent with comparable talent and a better system.

I wrote about this in many analyses. I said PSG would break down when they met a team able to withstand their pressure and punish them in the space behind. Bayern were that team. And the final was the moment that prediction was verified.

Verification: my claims can be challenged

One of my principles is to end each piece with a verifiable claim, with a statement of the conditions in which it applies. I do not want to make vague predictions nobody can challenge. I want to make predictions that, if I am wrong, you can point out that I am wrong.

With the PSG case, my claim is this: a team that tends to depend on individual talent up front and lacks a true defensive midfielder will collapse in the Champions League when it meets a team with a well-organised pressing system and quick transitions. Application condition: that team must have a dense fixture schedule and insufficient recovery time between matches. If both conditions are met, the probability of their collapse rises significantly.

This is a verifiable claim. You can apply it to other teams and see whether it holds. You can find cases where it fails, and if you find enough, you can refute it. That is what I want. A claim that cannot be refuted is a worthless claim.

What I learned from a mispronounced name

Back to the Ola Toivonen story. I tell it not to boast that I fixed my mistake. I tell it because it illustrates something important about this profession: attention to detail is the foundation of everything else.

When I began building my phonetic table, I realised I had not paid enough attention to small details for years. I had overlooked names, and because I overlooked names, I also overlooked rhythms. I had watched football as a series of events, not as a rhythm. And when I began paying attention to rhythm, I began seeing things I had not seen before.

This is why I say static data never reaches the rhythm of a match. Data tells you what happened. Rhythm tells you what is about to happen. And to hear the rhythm, you must notice details data does not capture: how a player moves before receiving the ball, how a team changes shape when it loses the ball, how a manager reacts when his team falls behind.

I write slowly, and I write coldly. But I try to place every number in my pieces within the breathing of the match. I do not want the number to become a financial report. I want the number to become part of the story, part of the rhythm. When I write "Atalanta's PPDA was 6.8 in that match", I am not just giving a number. I am saying Atalanta pressured the opponent at such frequency that they forced Juventus to pass the ball for fewer than seven passes before losing it. That is a rhythm, not just a number.

On what cannot be measured

I must admit there are things in football I cannot measure, and I do not pretend I can. The spirit of a team, the confidence of a player, the pressure of a final — these do not appear in my data, and I do not try to model them.

But I also do not ignore them. I acknowledge they exist, and I try to understand them through what I can observe. When I see a player hesitate before a challenge, I note it. When I see a team lose organisation after falling behind, I note it. These observations are not quantitative data, but they are data. They are pieces of a larger picture.

This is why I never give an absolute conclusion. I always give probability and condition. I say "high probability", not "certain". I say "under this condition", not "in all cases". This is not evasion of responsibility. It is the acknowledgment that football is a complex system, and in a complex system, nothing is certain.

But I also believe this acknowledgment should not become an excuse for not making predictions. If I only said everything can happen, I would say nothing. I want to make specific predictions, and I want to be responsible for them. If I am wrong, I want to know I am wrong. That is the only way to improve my model.

From Belgrade to Lyon: a journey in learning to listen

I began my career in 2026, in the sports department of a television station in Belgrade. That is where I learned the discipline of writing from early-career observation. I did not have much experience, but I had time, and I used that time to rewatch matches many times, take notes, and learn from those who came before.

I have covered eight Olympic Games, eight World Cups, and many editions of the Giro d'Italia and the Tour de France. These experiences broadened my perspective across fields and borders. They taught me that every sport shares common principles: preparation, execution, recovery, and luck. And they taught me that the best way to understand one sport is to learn from another.

When I moved to Lyon and began working for the French market, I had to relearn everything. I had to learn the language, I had to learn the culture, and I had to learn to write for a different audience. It was a difficult process, but also a rewarding one. It forced me to question my assumptions, and it forced me to explain what I knew in a new language.

This is why I try to write clearly and avoid unnecessary terminology. I know my readers are not all experts. I know I have a responsibility to explain what I know in a way others can understand. And I know that if I cannot explain a concept simply, perhaps I do not truly understand it.

On perfectionism and deadlines

I am a perfectionist. This is a trait I have had to learn to manage, because it can be a strength or a weakness. When it helps me cross-check data and avoid errors, it is a strength. When it makes me delay submission because I am not satisfied with a sentence, it is a weakness.

After an editor's angry reaction to a late submission, I learned to balance perfectionism and punctuality. I began setting internal deadlines earlier than the actual ones, and I began accepting that a piece does not have to be perfect to have value. Sometimes, a good piece submitted on time is worth more than a perfect piece submitted late.

This is a hard lesson for a personality like mine. I want everything to be right. I want every number checked. I want every sentence weighed. But I also understand that my job is communication, and communication requires a recipient. If I never submit, I communicate nothing.

On building probability scenarios

Colleagues call me a "tactical prophet", and I do not like the title. But I understand why they call me that. I build probability scenarios for every match I analyse, and sometimes my scenarios come true. That makes people think I have a special ability. The truth is I just work a little harder than average.

My scenario-building process begins with collecting data. I watch at least five recent matches of each team, and I note process metrics. I consider their schedule, their injury status, their head-to-head history. Then I build three scenarios: a high-probability one, a medium one, and a low one. I assign probabilities to each based on data, not feeling.

After the match, I check my scenarios. I ask: which scenario happened? Was the probability I assigned to it reasonable? What did I miss? This is a continuous process, and I try to learn from every match.

On my mistakes

I must admit I have been wrong many times. I predicted a team would win a title and they were eliminated in the group stage. I predicted a player would shine and he was injured in the first match. I predicted a manager would be sacked and he was given a contract extension.

These mistakes do not make me lose faith in my method, but they remind me that my method is imperfect. Football is a complex system with countless variables, and no model can capture everything. The best I can do is keep improving my model, and accept that I will always be wrong to some degree.

This is why I keep a public prediction tracker. I want people to see how often I am right and how often I am wrong. I do not want to publish only correct predictions and hide the wrong ones. That would be dishonest, and honesty is the foundation of everything I do.

What I want you to carry away

If you have read this far, you may be wondering what the main point is. I will not summarise it for you, because I believe a good piece does not need a summary. Instead, I want to leave you with a few thoughts.

First, football has no luck the way we usually think. What we call luck is usually a detail we have not noticed enough to include in the model. If you pay more attention, you will see more.

Second, a tactic is a plan for a healthy body. If you ignore fitness, you will misunderstand tactics. Fixture density is an important variable, and it is often overlooked.

Third, accuracy is the foundation. If you are not accurate about a name, how can you be accurate about a system? If you are not accurate about a number, how can you be accurate about a conclusion?

And finally, I want you to remember that all my predictions are probability scenarios, not absolute statements. I can be wrong, and I will be wrong. But I will keep working, keep learning, and keep trying to hear the rhythm of the match.

The next rhythm

The next season is approaching, and I have begun preparing. I am reviewing last season's matches, noting patterns, and building scenarios for the new one. I am tracking teams that are changing, managers who are adapting, and players who are maturing. I am looking for new gaps, new rhythms, and new stories.

If there is one thing I have learned in fourteen years, it is that football never stops changing. The systems I analyse today will be obsolete tomorrow. The players I track today will retire tomorrow. The teams I study today will collapse tomorrow. And my task is to keep tracking, keep analysing, and keep learning.

Football has no luck, only details that have not yet been lined up. And my job is to line up those details, one by one, until a match becomes clear — or until I realise I have missed an important detail, and must start over.

When a team wins, I look at the bench before the goal. That is where the match is truly decided. And that is where I will keep looking, season after season, until I understand its rhythm.