An Empty Data File in Da Nang: The Line Between Analysis and Fabrication

9:07 in the morning, mid-way through the regular season. I open the analysis file the coaching staff sent over, set it beside a coffee that has already gone cold, and find a completely empty data column.

No game name. No team name. No metrics. Not a single note about a player. Only the nine-dimension framework I use for every professional basketball team, and inside that framework, every cell left blank.

Outsiders assume a data consultant's job is built on beautiful numbers. The real work is far drier. Most of my hours go into verification, cross-checking, and discarding anything not reliable enough to use. When the input source breaks, I have to say it broke. There is no room for politeness.

I once watched a young analyst submit a report on a game he had never watched on film. He described the switching defense as if he had seen it. He described the pace of the game as if he had timed it. The report was clean enough that the coaching staff took it into a meeting. When the team lost the next game exactly along the invented script, nobody trusted him again. One fabrication erased three years of accumulated credibility.

That is why I keep one simple rule: if the data is not there, the correct answer is not enough information.

The nine-dimension framework and the trap of emptiness

My work runs on a nine-dimension framework, the tool I use to take apart any basketball team from the level of a single event to the level of the whole system.

The first dimension is tactics and technique. I measure offensive efficiency per 100 possessions, known as OffRtg; defensive efficiency, known as DefRtg; and pace. From that I assess ball movement, shot quality, and how well the personnel fits the scheme. A team with high OffRtg and poor DefRtg usually lives on inspiration, and inspiration does not survive the playoffs.

The second dimension is player data. Beyond points, rebounds and assists, I look at true shooting percentage, known as TS%; player efficiency rating, known as PER; usage rate, known as USG%; and estimated plus-minus, known as EPM. For each player I draw an age curve to see when efficiency begins to fall. A 27-year-old with a high usage rate is an asset; the same player at 33 with the same usage rate is a liability on the payroll.

The third dimension is team operations and the salary cap. This is where maximum contracts, mid-level deals, rookie-contract surplus, and the luxury tax threshold decide the next three years. A team above the luxury tax loses flexibility in trades, and loses future first-round picks along with it. None of that shows up in the box score, but it shows up in the standings two seasons later.

The fourth dimension is the league landscape. I sort teams into four tiers: contenders, playoff tier, play-in tier, and rebuilding tier. Each tier has its own contention window, tied to the age structure of the core and the flexibility of the cap sheet.

The fifth dimension is rules. Provisions on the salary cap, on extension rights, on load management, on disciplinary penalties. People inside the industry know that rules are not merely there to be followed; they are a board to be optimized.

The sixth dimension is the coaching staff and the locker room. Who really holds power inside the team, who has been pushed to the margins, whether two stars are willing to give up the ball to each other. This is the hardest dimension to measure and the most decisive one.

The seventh dimension is risk. Injury, contracts, personnel, rules, public opinion, and systemic risk as well.

The eighth dimension is media and expectation. A player celebrated for three weeks can become a target of criticism after a single game. I measure the gap between market expectation and objective assessment.

The ninth dimension is the ripple into the wider industry. Sneakers, broadcast, regional markets, the agency ecosystem, derivative markets, and international events.

All nine dimensions need exactly one thing to function: input data. And this morning's file contains nothing at all.

When every cell is left open

The first thing I do is write nothing.

On the tactical dimension, I cannot say whether the team switches well or badly on defense, because no team is named. On the player dimension, I cannot build a profile, because no player appears. On the cap dimension, I cannot say whether the team sits under the cap or above the tax, because there is no figure to compare against. On the league-landscape dimension, I do not even know which league this is, because the only remaining label says, generically, basketball.

Outsiders grow impatient in front of emptiness. They want a conclusion. They want a decisive answer to bet on or to argue about. That impatience is what produces fabricated reports. The writer fills the gap with intuition, then calls intuition analysis. Three days later, when the result goes the other way, they call it a surprise.

In this field there is a sharp distinction that outsiders often miss. A low-content report and a system-failure report look the same on the surface, but they are opposites in nature. A low-content report means the data exists, it simply carries little information. A system-failure report means the data never arrived. Confusing the two is a serious error, because it sets an entire downstream process running on an empty base.

Data is a monastery: the less noise there is, the more clearly you hear something trying to speak. But a silent monastery can also be silent because nobody is inside.

This is where I have to tell an old story to show the principle is not academic. In 2026, I analyzed a major team using qualifying metrics, saw a clear decline signal, and predicted it would be eliminated early. Colleagues called me a data fanatic. The result was correct. But the lesson I kept was not about being right. It was something else: a forecast only has value because I published the method, the assumptions, and the conditions under which I would be wrong. I did not invent a beautiful conclusion. I simply stated the signal plainly.

People watch goals to remember a match. I watch metrics to understand how the match failed to happen. In basketball, people remember the deciding shot. I remember the twelve possessions before it, where the team lost the game without anyone noticing.

But this morning, I do not even have those possessions. I only have an empty framework.

What a complete file normally looks like

To grasp how serious an empty file is, picture a complete one.

A standard report on a basketball team contains a roster with minutes, shooting percentages, shot locations, and month-by-month trends. It contains efficiency metrics for every five-man unit on the floor. It contains a payroll sheet with each player's contract expiry date. It contains the schedule, the travel itinerary, and the number of rest days between games. It contains injury reports updated to each training session.

Only from that source can I answer the three questions a coaching staff actually cares about. First, what this team wins with and what it loses to. Second, where the team lands in twenty more games if the roster stays unchanged. Third, if one player has to be replaced, which position should be upgraded for the best return.

Without a source, those three questions have no answers. I can phrase them beautifully. I cannot answer them truthfully.

A small example shows how counter-intuitive the data can be. Nikola Jokić was taken in the second round of the 2026 draft, in the range most teams treat as a place to fill roster spots. Stephen Curry was passed over by many teams in the 2026 draft. Those two cases remind me that judging people from a single slice in time is always wrong. Numbers do not lie, but they also do not tell the whole story. And for exactly that reason, when the numbers are absent, I must not replace them with a story.

The pressure to fabricate: a blind spot in Vietnamese basketball culture

In Vietnam, professional basketball is young, and the analytics profession is younger still. The number of people who genuinely read advanced metrics can be counted on two hands. Most domestic basketball writing runs on feeling: this team is in form, that player is hot, the next game is hard to call.

Those lines are not wrong emotionally. They are simply not enough to decide on.

The problem is this: when nobody checks, whoever speaks loudest is trusted. A commentator who says a team will win because morale is rising can be right three times in a row and become an expert. By the fourth time, when the team loses, nobody remembers to ask again.

I once argued with a young coach about an import player with a high shooting rate but a low conversion rate. He said the player just needed belief. I produced the next twelve games of data. The team collected 9 of a possible 36 points. He apologized publicly. But what I remember is not the apology. It is the question he asked afterward: if the data said so, why did nobody tell me?

The answer is that somebody did. They just said it in a language he had never learned.

Every coach talks about feel. I do not have feel, I have standard deviation. But I also know something newcomers forget: standard deviation only means anything when there is a sample. Without a sample, mean error is just a decorative figure on a blank page.

There is a subtler blind spot too. People inside the industry tend to believe they fully understand the quirks of the domestic market. I used to think so as well. But thirteen years of observation taught me to separate two things cleanly: what is measurable, and what is inferred from experience. An import player struggling to adapt to central Vietnam's climate is a reasonable hypothesis. It only becomes a conclusion with enough games, enough fitness data, and enough cross-checking. Before that, it remains a good story.

The signal for the next cycle

This morning's empty file is not a disaster. The disaster would be treating it as a low-content analysis and writing on regardless.

In the process I am building for domestic teams, I have added a gate: if the input contains fewer than one information point and one named entity, the report does not move forward. The gate is not glamorous. It only stops a small error from becoming a large decision.

Vietnamese basketball is at a stage where every wrong call on an import or on a training schedule costs a whole season. At that stage, the most valuable thing is not a clever prediction, but a process brave enough to say it does not yet know.

As for the signal for the next cycle, it is simple. The team that starts sharing one metrics system will save itself a season or two. The team still deciding on inspiration will keep calling its failures surprises.

I close the file, write one line in my notebook: input data missing, no conclusion. Then I call the person who sent it.