When Data Goes Silent: The Fragile Line Between Analyst and Fabricator

On the night of June 27, 2026, at Kazan Arena, the scoreboard displayed two numbers that left all of Germany frozen: Germany 0, South Korea 2. In the stands, white shirts buried their faces in their hands. In the press room, coach Joachim Löw repeated the phrase "lack of luck." More than eight thousand kilometers away, in a small apartment in Jakarta, I sat in front of three screens holding the data of all 64 matches of the 2026 World Cup. One metric was screaming, and it never mentioned luck.

Germany's total xG in that do-or-die match against South Korea was 1.2. This is the lowest figure in the national team's history at any World Cup. Germany took 26 shots, controlled nearly seventy percent of possession, but almost every chance was a harmless long-range effort. An empire collapsed, and this time one could measure every falling brick. But what haunted me for years afterward was not Germany's collapse. It was another, colder question: what happens when data goes silent?

Because the job of a football data analyst is not always about having beautiful numbers ready to tell a compelling story. Most of the time, we face gaps. A data pipeline returns empty. A match where the wide-angle camera broke, so there are no tracking coordinates. A player whom the statistics provider does not monitor. And in those moments, the line between an honest analyst and a fabricator becomes terrifyingly thin.

I entered this profession in March 2026, when I was a twenty-four-year-old assistant analyst at Persija Jakarta. That day, I learned the first and most important lesson of my entire career: data never lies — only our way of listening is wrong. But it took many more years, through the great shocks of world football and my own crises, before I understood the flip side of that sentence. When there is no data, people easily fill the gap with imagination. And imagination, in my profession, is a double-edged knife.

Context: When Southeast Asian Football Learned to Count

To understand why the story of data gaps matters, we need a broader context. Over roughly the past decade, Southeast Asian football in general and Indonesian football in particular have undergone a silent revolution in how matches are read. Concepts such as xG (expected goals), PPDA (passes allowed per defensive action), and high-intensity running distance have crept from the analysis rooms of European clubs into regional leagues.

When I started at Persija, most of the coaching staff still made decisions based on feel and experience. A young assistant analyst like me, with tables crammed with numbers, was often met with skeptical eyes. But within just a few years, everything changed. Clubs began hiring data specialists. Matches were tagged ball by ball. Liga 1, Indonesia's top flight, gradually acquired official data providers.

Alongside football, another arena was undergoing a similar process: esports. Early in my career I spent time in esports — first as a player, then as a tournament organizer, before moving into media and analysis. And I realized that, whether football or esports, the story of data shares the same structure: people crave numbers to justify beliefs they already hold, and they readily ignore the truth that most of the most useful data lies in regions no one bothers to look at.

In esports, where patches shift the meta within weeks, the pressure to have numbers is even harsher. A team can win with a tactic, only for that tactic to be neutralized after a single patch. Analysts must constantly update win rates, pick-ban rates, and match durations. But when a new tournament begins without enough data, or when a statistics pipeline returns an empty result, what happens?

The honest answer is: nothing. A decent analyst will say "I don't have enough information." But temptation is always present. People want an answer. Audiences want a story. Editors want a headline. And so, unconsciously, people begin to invent numbers that do not exist, or worse, to assign to real numbers a meaning they never carried.

That is exactly when the line blurs. And to see this clearly, I want to recount three stories from my own career, each one a different level of the relationship between people and data.

Persija 2026: Forty Pages and a Player Who Ran 8.2 km

In March 2026, I was twenty-four, working as an assistant analyst for Persija Jakarta. That was the period when I learned that data never speaks for itself. People have to make it speak.

In a Liga 1 match against Bali United, I happened to notice a young midfielder named Septian David Maulana. He ran only 8.2 km over the whole match — a modest figure, even low by the standards of a modern midfielder. If you looked only at running distance, a hasty analyst would conclude that Maulana was lazy, lacking effort.

But when I dug deeper, a different picture emerged. Maulana had 11 passes into the opposition's final third — the highest on the team. He did not run much, but every run had a purpose. He did not duel fiercely, but he read the spaces before they opened. He was the kind of player that crude metrics like running distance cannot capture.

I spent many days writing a forty-page report proposing to move Maulana from the wing to the number 10 role — the attacking midfield position where his reading of the game and his decisive passing could be maximized. The coaching staff initially dismissed it. They said a player who ran so little could not be the center of the game plan. I patiently presented again, this time not only with numbers but with clipped video showing how each of Maulana's off-ball movements created space for his teammates.

After three trial matches, the results came faster than I expected. Maulana scored two goals and assisted three. Persija won four consecutive matches. The coaching staff began calling me by an affectionate yet wary nickname: "the mad assistant."

The lesson from March 2026 was not that I was right. It was that I did not rush to a conclusion when the data was insufficient. If I had looked only at the 8.2 km figure and nodded at the prejudice that "this player is lazy," I would have missed one of the most creative midfielders I ever analyzed. A player's value is not in the contract; it is in every off-ball movement. That was the first principle, and it remains true to this day.

I began writing in a "data first, story second" style. Every analysis of mine opens with a shocking number, then explains the context. I learned to turn dry tables into tactical arguments with weight — and never to make a judgment without supporting data. But from here, a new question arose in my mind: if the data is not enough, what will I do?

World Cup 2026: When the German Machine Forgot How to Press

In June 2026, I followed the World Cup in Russia from Jakarta, analyzing all 64 matches for my personal blog. That World Cup reshaped my entire professional philosophy.

Germany entered the tournament as defending champions. They carried a system built and refined over years. But from the very first match, I noticed something unusual. Their pressing-related metrics had declined. The intensity of pressure — the weapon that had taken them to the summit four years earlier — seemed to vanish.

I began building a metric of my own, which I later called the Persistent Pressing Index. It measures a team's ability to sustain pressing intensity across the phases of a match, rather than merely averaging it over the whole game. The result startled me: Germany's index at the 2026 World Cup was 23% lower than at the 2026 World Cup. Not a slight decline. A systemic collapse.

What was interesting was that the German coaching staff seemed not to notice. They still believed they were playing the football that had won them the title. They still controlled possession, still attacked, still generated shots. But they had lost the most important thing: the ability to win the ball back high up the pitch, and the ability to turn pressure into goals.

I wrote an analysis titled "The Collapse of a System: When Germany Forgot How to Press." In it, I did not merely list numbers. I told a story about a perfect machine rusting from within, about a generation of players past their peak, and about a philosophy abandoned by the very people who created it. The article was shared more than fifteen thousand times. My Persistent Pressing Index was cited by many Southeast Asian analysts. An ESPN journalist reached out and invited me to contribute to their data column.

But that success also taught me a lesson in humility. As the article spread, I began receiving questions I could not answer. People asked me to predict the champion. People asked me which team would win the 2026 World Cup. And I realized that crowds always want data to give a certain answer. They do not want to hear that a model is only a way of seeing, not a prophecy.

The 2026 World Cup did not break my model; it expanded my definition of data. I learned that the best data is not data that gives the right answer, but data that forces us to ask the right questions. And the right question, in Germany's case, was not "who will win," but "why can a perfect system destroy itself."

My model is only as bad as my cowardice in not asking it the hardest question. I wrote that on the whiteboard in my office, and it remains there to this day.

Persib 2026: Empty Stadiums and Twelve Percent More Running

In March 2026, when the global pandemic forced leagues to suspend, I was twenty-seven, serving as head of the data department at Persib Bandung. That was the most testing period, but also when I understood that data is not something to display, but a survival tool in a crisis.

As football prepared to return with matches played without spectators, I took on a task many considered pointless: studying the impact of playing in empty stadiums on player performance. Without cheering, without the pressure of the stands, home advantage almost vanished. But how did that affect the players?

I built a detailed report proposing to increase high-intensity running distance by twelve percent to compensate for the loss of home advantage. My reasoning was simple: when there are no fans to fuel you, players must generate their own energy with their own legs. A team cannot rely on the crowd's pressure to win the ball back; they must press higher, run more, and compete harder.

When Liga 1 returned in October 2026, Persib went unbeaten in their first eight matches — the club's best run in history. The coaching staff called me "the mad professor." But I did not take it as praise for me personally. It was praise for the honesty of the data. We did not invent a new tactic. We simply listened to what the data was telling us about an unprecedented situation.

Yet it was precisely during this period that I witnessed the flip side. Other clubs, seeing Persib's success, began copying our model without understanding its essence. They increased running distance mechanically, without considering each player's condition, the fixture list, or the overall tactics. The result was a wave of injuries. Data, when misunderstood and applied dogmatically, can become a self-destructive weapon.

That was when I realized that the role of an analyst is not only to produce numbers, but to explain the limits of those numbers. A bad analyst says: "Here is the number, follow it." A good analyst says: "Here is the number, but it is only true in this context, with these players, and under these conditions." The difference between the two approaches is the line between science and superstition.

When the Data Pipeline Returns Zero

Now I want to return to the question that has haunted me since that night in Kazan in 2026. What happens when data goes silent? What happens when you sit in front of the screen, and all the system returns is a blank?

In the analytical profession, we have a concept called the null-value protocol. It is a set of rules governing how to treat empty data cells. The first and most important rule: you are not allowed to invent. You are not allowed to infer a number that does not exist. You are not allowed to assign to a team, a player, or a tactical patch a characteristic simply because you want your story to feel complete.

It sounds simple, but in practice it is extraordinarily hard. Because pressure comes from every direction. Audiences want judgments. Editors want articles. Sponsors want reports. And above all, the analyst himself — with his ego and professional pride — wants to prove he is useful. In that moment, admitting "I don't have enough information" is a far braver act than rushing to a premature judgment.

I have seen colleagues turn themselves into fabricators without realizing it. They take a small sample — a few matches, a few weeks — and draw grand conclusions about an entire season. They look at a single metric and assign it the power to explain everything. They build compelling stories on a foundation of ambiguity.

In esports, where I also have experience, the problem is even more serious. A new patch arrives, and immediately a flood of analyses appears, asserting that this patch will change the landscape, create a new meta, and lift this team to the top. But most of those analyses are written before a single official match has been played. They are built on numbers from the practice server, where conditions differ from real competition. They are castles built on sand.

The biggest lesson I learned about null values came from my own process of building models. There were times I spent days designing a prediction model, only for it to return an empty result when I ran it, because the input data was insufficient. That feeling is deeply unpleasant. You want to throw the computer out the window. You want to believe there is some technical error, that fixing one line of code will make everything work. But sometimes the simple truth is that you do not have enough data. And the only way to be honest with yourself is to admit it.

When I wrote the report on Maulana in 2026, I had enough data: running distance, pass count, average position, heat map. When I analyzed Germany in 2026, I had data from sixty-four matches and years of observation. When I proposed increasing Persib's running in 2026, I had data from the entire league across several seasons. But if that data did not exist, would I dare to say "I don't know"? That is the question every analyst must answer before the mirror.

Liga 1 and the Small-Sample Trap

In Indonesia, where I work, the small-sample trap is especially dangerous. Liga 1 is a league of uneven technical quality, a dense fixture list, and differing facilities among clubs. In such a context, it is very easy to fall into the trap of evaluating a player or a team based on just a few matches.

I once watched a player be praised as "the discovery of the season" after only three good matches. His metrics were impressive: an average of one goal per match, a high pass completion rate, superior running distance. But when I dug into the data, I found that those three matches were all against the weakest opponents in the league, and all at home. When the sample was expanded across the season, those impressive numbers fell sharply.

What is worth noting is that no one invented anything. Every number was true. But the interpretation was wrong. This is a more subtle form of fabrication: not inventing data, but inventing the meaning of data. A small sample presented as if it represented a grand trend. A random phenomenon dressed in the robe of a law.

In esports, people call this phenomenon by another name: small data inflated into meta. A team wins three matches with a new tactic, and immediately the whole community rushes to copy it. But sometimes that tactic was only effective because opponents had not yet studied it, or because of a lucky draw. When the sample expands, the truth emerges.

The only defense against this trap is discipline about sample size. I always remind myself that, in football, you need at least ten to fifteen matches before you can begin talking about a reliable trend. In esports, that number may be lower because there are more matches in a tournament, but also higher because the meta shifts faster. No absolute number is right for every case. What matters is always asking: is this sample large enough and representative enough for me to make this judgment?

I have made mistakes by ignoring that question. In the 2026 season, I made a prediction about a young player based on four early matches. I told the coaching staff he would be the breakout figure of the season. But the player suffered an injury in the fifth match, and when he returned, he could not recapture his form. I was right about the potential, but wrong about the prediction. The lesson: data only speaks of the past, never of the future. Every prediction is a gamble, and an honest person must call it by its true name.

The Transfer Market: Value Lies in Off-Ball Movement

One of the fields where data is most abused is the transfer market. Every transfer window, thousands of articles appear, assigning players prices, potentials, and evaluations based on numbers presented without context.

I always tell my colleagues that a player's value is not in the contract; it is in every off-ball movement. A goal can be scored by one player, but it is often created by another — the one who ran to stretch the defense, the one who played the pass before, the one who created the space no one sees on the scoreboard.

I once analyzed a transfer case in which an Indonesian club spent a large sum to buy a striker with an impressive scoring record in the previous league. Looking at the numbers, it was a reasonable deal. But when I reviewed all his goals, I found that most came from set pieces, or from the decisive passes of a creative midfielder the club did not buy along with him. When that striker moved to his new team, without that midfielder, he was almost paralyzed. The deal failed.

This is a classic example of reading data while ignoring context. The goal count was real. But its meaning depends on how it was produced. A goal from a free kick is entirely different from a goal from a ten-pass team move. A player who scores twenty goals in a weak league is not at all the same as a player who scores ten in a strong one.

On the international stage, I hold a fairly blunt view about a current trend: the leagues of the Gulf, especially the Saudi Pro League, are not truly developing football. They are turning the aging stars of European football into tourism ambassadors. It is not a football project; it is a media and image project. The enormous transfer figures are presented as evidence of development, but they actually measure only financial power, not competitive quality.

Of course, this is a debatable judgment. And I am ready to admit I may be wrong. But what I am certain of is this: a football nation only develops when it builds a youth academy system, a competitive domestic league, and a tactical culture. Buying thirty-five-year-old stars creates none of those.

Gegenpressing Has Been Decoded

There is a professional view I have pursued for years, and it is increasingly being proven right: gegenpressing has been decoded. Mid-table teams have learned how to counter it, and instead of seeking more refined tactical solutions, they turn football into athletics.

Gegenpressing — the style of pressing immediately after losing the ball — was once a revolution. It turned defending into an attacking weapon. Teams like Dortmund or Liverpool under Jürgen Klopp proved that if you win the ball back within five seconds of losing it, you create the most dangerous chances. But when every team learns to do it, the advantage disappears.

Today, mid-table teams respond by doubling down on physicality. They run more, duel more, and foul more. The match becomes a pure battle of stamina. Technical quality is pushed down the priority list. And the sad part is that data is used to justify this trend. Running distance rises, duel counts rise, and people praise it as progress.

But the truth is: we are witnessing a tactical degeneration disguised by impressive numbers. I once analyzed a Liga 1 match in which both teams combined ran more than two hundred and thirty kilometers. It sounds heroic. But when I watched it back, I counted fewer than ten truly imaginative passing sequences. Most of the time was long balls, duels, and throw-ins. That is not football; that is a marathon.

A good coach treats a defeat as an update, not a verdict. But to do that, he must have the right data, and must read it honestly. A coach who looks at low running distance and concludes his team is lazy is a coach reading data wrongly. A coach who looks at the same number and asks "why did they run less" is the one who truly understands the game.

Perhaps that team ran less because they controlled the ball better, because they did not need to chase it. Perhaps they ran less because they read the game and occupied better positions. Low running distance, in many cases, is a sign of intelligence, not laziness. That is the paradox only patient analysts can see.

Contrarian: Correlation Is Not Causation

Here, I must address what I consider the golden rule of the analytical profession, and also the one amateur analysts violate most: correlation is not causation.

When two phenomena occur together, the human brain tends to seek a causal link between them. This is an evolutionary trait that helps us survive, but in data analysis it is a deadly trap. A team winning when wearing red does not mean the color brings victory. A player scoring many goals when his team wins does not mean that player is the cause of the win.

In football, false correlations appear everywhere. Teams that dominate possession often win — but is that because they control the ball well, or because they took the lead, forcing opponents to push up, so that possession is merely a consequence of leading? Players who run a lot are often rated highly — but is that because running a lot is good, or because players who run a lot tend to be young, fit, and given more chances to shine?

This is why I am always cautious about analyses based on a single metric. One metric, however perfect, is only one piece of the puzzle. And the most dangerous thing is when a metric becomes a religion — when people believe in it blindly, ignoring all contrary evidence.

xG is a prime example. It is a wonderful metric, helping us evaluate the quality of chances rather than merely counting goals. But xG cannot measure psychological pressure, cannot measure the quality of the pass leading to the shot, cannot measure whether the goalkeeper read the direction of the shot. A player with high xG who does not score may be judged unlucky — or may be judged to lack the nerve in decisive moments. The same number, two entirely different readings.

In esports, the problem is even more complex. A team can win with a specific tactic, but that tactic is only effective because opponents have not studied it well. Once opponents have studied it, the same tactic may fail. So what is that tactic's win rate? The answer depends entirely on which sample you choose, and whether you account for the factor "opponents already know."

What I want to say is this: every model has blind spots. And a good analyst is not one who hides his blind spots, but one who discloses them. When I make a prediction, I always attach a warning about what my model cannot see. That is the only way to retain credibility in the long run.

I have been criticized for being too cautious. Some say an analyst must dare to make bold predictions. I agree — but bold does not mean reckless. Bold is daring to make a specific prediction, with a specific reason, and daring to admit being wrong when the data proves otherwise. Those who bet on data were once called mad; those who did not bet are now former coaches.

Conclusion: The Signal of the Next Round

The season is underway, and every round brings new signals. But the most important signal I track is not on the league table. It is in how teams treat their own data.

In the last three matches, I have noticed a worrying trend: mid-table teams are increasingly dependent on easily measured metrics — running distance, duel counts, pass counts — and ignoring harder-to-measure ones such as the quality of off-ball movement, reading of the game, or patience in build-up. This is a sign that football is gradually becoming a sport of numbers rather than of ideas.

The question I carry into next season is: will any team dare to go against this trend? Will anyone dare to build a style of play on tactical intelligence rather than pure physicality? And if so, will data be subtle enough to recognize their value, or will it continue to praise those who run the most?

Data never lies — only our way of listening is wrong. And in a long season, where every signal is muddled by pressure and emotion, the ability to listen correctly is the only thing that helps us see what others miss.

When data goes silent, do not invent its voice. Learn to hear the silence too. Because sometimes, what a number does not say is the most important thing it wants to tell.