The Report Came Back N/A: The Discipline of Not Faking the Numbers

The Report Came Back N/A: The Discipline of Not Faking the Numbers

It was 3:14 a.m. in Los Angeles. I opened the nine-dimension analysis frame I had built for the stretch after the All-Star break. The left column listed the categories: tactical transformation, player profiles, salary structure, league landscape, rules and governance, locker room, risk, media narrative, ripple effects. The right column was empty. Not a single number, not a single player name, not one line of data solid enough to stand on.

On the last row, the system printed a phrase it would repeat twenty-seven times that night: "N/A — insufficient information."

I stared at that table for about four minutes. Then I shut the machine down, left the table blank, and went to sleep. The next morning I published nothing.

That was the best professional decision I made all week.

---

The blank table and the ritual of filling it in

Seventeen years in basketball data analysis taught me that the biggest temptation for a report writer is not misreading numbers. A misread can be fixed. The real temptation lies elsewhere: filling the table in.

A table with seven empty cells looks like a defective product. A table with seven full cells looks like a finished product, regardless of whether those seven numbers mean anything. Editors need a long enough story. Readers need a clear verdict. Neither of them ever asked me to fabricate a nine-dimension model, yet the pressure of the blank table knows exactly how to push a writer there.

The nine-dimension frame I use is built on one principle: every conclusion must trace back to an original information point. Tactical transformation must be anchored to a specific possession in a specific game. Player profiles must be anchored to minutes, possessions and touches, not to feeling. Salary structure must be anchored to contracts and the cap. League landscape must be anchored to standings, remaining schedule and each team's time budget.

When the input is empty, all nine dimensions collapse at once. Not because the frame is weak. The frame is strong precisely because it collapses: it refuses to feed itself on inference.

Outsiders often read a report full of N/A as a sign of laziness or incompetence. In the profession, it signals the opposite. A system willing to say "I don't know" is a system you can trust when it says "I do."

Data is like a book. The crowd looks at the cover; smart people read every page. And the first page of an honest book usually states exactly what it is missing.

---

Three kinds of N/A, and only one of them is legitimate

Over the years I have sorted N/A into three groups with completely different natures. Confusing them is the source of nearly every serious mistake I have seen in sports analytics.

First: the data does not exist. You are asked about the defensive metric of a player who has never played a professional minute. You are asked about the efficiency of a five-man lineup that has never shared a floor. The N/A here is a complete answer.

Second: the data exists, but the sample does not — Dillon Brooks. This is the most dangerous kind, because it wears the clothing of a real number.

In 2026 I was twenty-four, newly hired at a data analysis blog in Los Angeles. At Summer League in Las Vegas I tracked undrafted and late-drafted free agents. One name surfaced: Dillon Brooks, the 45th pick of that draft, posting a 98.3 defensive rating across five games. His positional competitor, Troy Williams, posted 104.2. A six-point gap in defensive rating speaks. But it was measured across five games, two of which he played fourteen minutes, one of which he defended players who would not be on an NBA roster the next season.

My instinct was to finish the probability model before publishing. I spent three weeks. Three weeks building a predictive model on a sample I already knew was too thin. A rival blog honored Brooks three days before me. My piece ran later, methodologically cleaner, and nobody read it.

The lesson was not that I was slow. The lesson was that I had misclassified the N/A. With five games, the right answer was not "wait until my model is done" but "this is an early signal, low confidence, needs confirmation."

I call that the discipline of "good enough at the right moment." Since then every analysis carries an internal deadline: draft done forty-eight hours out, the final twenty-four reserved purely for checking numbers, not for chasing infinite perfection.

Third: the data is sufficient, but the question is wrong. This is the kind I took years to recognize. The table is full, the sample is large, every metric computes. Yet every conclusion is meaningless, because the question does not match the basketball being played.

The most familiar example is plus-minus. A player with a positive plus-minus across ten straight games looks like proof of value. But if in those ten games he only shared the floor with opposing benches that had already given up, the number measures the opponent, not him. Same for shooting. A guard hitting 41 percent from three in December may be improving, or may simply be defended more loosely because his star teammate returned from injury. One number, two entirely different stories.

In such cases the honest answer is still N/A — with one action attached: change the question. Move from "has this player improved" to "under what conditions has this player improved."

---

Kawhi Leonard: when schedule density is the culprit, not the knee

In 2026 I was twenty-seven, working at a sports data consultancy. The NBA suspended its season, then rebuilt it inside a bubble in Orlando with twenty-two teams from July 30. The calendar was compressed. Teams played eight games in just over two weeks merely to set seeding, then walked straight into the playoffs.

I spent four months of that shutdown doing something nobody asked for: re-reading the history of hamstring and knee injuries that followed long layoffs. I built a table of players over thirty, with prior injury history, used at heavy volume immediately after a break.

My model produced an estimate: a player in that cohort carried roughly 1.6 times the risk of hamstring re-injury if pushed into a two-games-per-week density right after a stoppage, compared with a load-managed group. I placed Kawhi Leonard in the highest-risk tier.

I wrote a forty-page report and sent it to the team's medical staff. It was ignored. Not because the conclusion was wrong, but because the format was excessive — forty pages for a recommendation that needed one.

In June 2026, in the Western Conference semifinals, Kawhi Leonard tore his ACL. He missed the rest of the playoffs, then the entire 2026-22 season.

Nobody read the report on Kawhi's knee. The market only read it after the sound of the tear.

I tell this story not to boast that I was right. I tell it to show where I was wrong: right on the conclusion, wrong on the format. A finding that is not communicated properly stays in a drawer, and a finding in a drawer saves nobody.

Since then every report I write opens with a one-page executive summary: conclusion on top, recommendation below, all evidence pushed back. And since then I hold a fairly hard professional position: schedule density is the biggest single driver of injury; no medical staff saves a team playing two games a week for six months. Human bodies do not negotiate with the calendar.

---

Croatia 2026: a number only becomes legend when it has a character

In 2026 I was twenty-five, applying my self-built "early signal" frame combining expected-goal differential and pressing indices toward the opponent's box.

When the World Cup in Russia began, consensus saw Croatia as a side with a pretty midfield and no nerve. I saw the opposite. Croatia controlled 74 percent of possession in the middle third. Luka Modrić created 12 key passes across the knockout rounds. All three of their knockout matches went to extra time and penalties.

I wrote "The Croatians Are Not Lucky" right after the group stage. Nobody read it. When Croatia reached the final on July 15, 2026, the piece was shared more than three thousand times in a single night.

That taught me something I still apply: accurate data does not automatically become a story. Crowds do not read tables. Crowds read people. World Cup 2026 taught me that a number can become legend if it is told well.

---

Enzo Fernández: the power of two pages

In 2026 I was twenty-nine. A brokerage firm asked me to evaluate South American talent ahead of the World Cup in Qatar. I reused the refined early-signal frame and scanned under-23 midfielders. One name jumped off the board: Enzo Fernández, then at Benfica, with 11.4 progressive passing metres per ninety minutes and a 78 percent success rate under pressure — the best in his age cohort at the tournament.

I wrote a two-page report recommending acquisition at a reference price of thirty million euros and sent it to a Premier League sporting director.

In January 2026, Chelsea signed Enzo Fernández for 121 million euros. My two-page report later leaked on a data forum.

Two lessons. First, professionally: systematic brevity beats sprawling completeness. The forty pages of 2026 were ignored. The two pages of 2026 were read, forwarded, and eventually leaked. Second, ethically: after that leak I set a rule — in all internal documents, player names are encoded as numbers. Only when a contract is signed does the real name appear in public writing.

What I write today may be forgotten. But the system it builds will not.

---

The contrarian angle: this industry rewards the appearance of completeness

An honest table full of N/A is usually rated lower than a full table built on bad method. Readers have no way to tell them apart without verifying, and most readers do not verify.

That creates a system of skewed incentives. Writers are incentivised to fill the table. Editors are incentivised to pick the fuller piece. Distribution platforms are incentivised to push the decisive headline. The result: a market flooded with confident conclusions built on samples thin as paper.

But here I must consciously contradict myself. An honest N/A is only valuable when it is rare. If I turn it into a habit, I have traded one vice for another. An analyst who always says "not enough data" is as useless as one who always says "I called it."

The line I draw is this: N/A applies to facts you do not have; judgement applies to facts you have that remain ambiguous. Kawhi in 2026 was a fact I had — injury history, workload, schedule density. My job was to issue a judgement with a confidence level, not to hide behind N/A.

And here is the final contrarian point, the one I believe most: the analyst's greatest failure is not being wrong, but being silent at the moment speech was required. Wrong can be corrected. Silence cannot, because there is nothing to correct.

Correct data that goes unread has already lost its value — it becomes the debt of those who refused to read it.

---

Next-game variables and the verification milestones I set myself

Back to that blank table. I left it blank, but I did not leave it alone. An N/A table is only useful if it becomes a to-do list.

I have set three verification milestones, recorded here so readers can check back.

First, ten games from now, I will re-check the over-thirty players with the highest workloads. If their absence rate exceeds the league average, my schedule-density hypothesis is confirmed once more. If not, I rewrite the model.

Second, in the playoffs, I will track teams dependent on a single primary ball handler. History suggests these teams lose offensive efficiency when opponents get seven games to prepare. This is a hypothesis, not a conclusion.

Third, I will revisit my scouting board for young players in European leagues. If a name on it breaks out into a major transfer, I will publish the date I first listed that player, along with the original reference price.

All three can be wrong. I accept that, because a judgement with a verification date beats a judgement without one.

As for that blank table: it is a reminder that in an industry living on emotion and fast verdicts, the ability to say "I don't know yet" is a professional skill, not a weakness. But it only counts as a skill when it comes with a concrete plan to turn the unknown into the known.

The market always reads late. The writer's job is to choose the right moment to say what he believes — and to own that moment.