← Back to Compstellation

COMPSTELLATION

How to read a prospect stat line without losing the context

Compstellation · October 17, 2026 · Original explainer

AI-assisted editorial content. This is a general framework, not original reporting about a particular player.

Start with the job the player was asked to do

A stat line describes what happened within a role. It does not tell you everything a player could do in another role. A guard who brings the ball up, runs most of the pick-and-rolls and takes late-clock shots faces different decisions from a guard asked to defend and shoot when open. Before comparing their points or assists, describe those jobs in plain language. Was the player creating advantages, finishing advantages made by teammates, or keeping possessions moving?

Keep volume and efficiency together

A percentage without an attempt count can make a small sample look decisive. Write both down: makes, attempts and the period covered. Then ask how the shots were generated. Open catch-and-shoot attempts and contested pull-ups place different demands on a shooter. A hot week is a reason to watch the next games, not a reason to erase the rest of the season. Likewise, an expanded role can produce more difficult attempts and a lower percentage without proving that the player became a worse shooter.

Use minutes as context rather than a shortcut

Raw totals reward time on the court. Per-minute comparisons can help reveal differences in opportunity, but they should not imply that a reserve could reproduce the same output over starter minutes. Fatigue, opponent quality, defensive attention and lineup changes matter. Put minutes next to production and look for games with comparable responsibilities. If the roles cannot be matched, keep that limitation visible instead of forcing a ranking.

Ask what assists and turnovers leave out

An assist count is connected to teammates making shots. It can miss a pass that creates the advantage before the final pass, and it cannot by itself distinguish a difficult live-dribble read from a routine handoff. Turnovers also need description: a missed ambitious passing window differs from repeatedly losing the ball against pressure. Use the numbers to identify possessions worth reviewing, then explain what the player saw and what alternatives were available.

Check the defensive possessions behind the highlights

Blocks and steals are visible events, but many useful defensive possessions end without either. Watch whether the player contains the first action, communicates a switch, closes out under control and finishes the possession with a box-out. A spectacular recovery can follow an avoidable mistake. Conversely, a disciplined rotation may prevent an attempt entirely. A short highlight package rarely provides enough of these ordinary possessions.

Finish with a testable question

A useful scouting note separates observation from projection. “Made four open corner threes in this game” is an observation. “Will be a dependable NBA shooter” is a projection requiring more evidence. End with the next question: does the release hold up against faster closeouts, can the handle survive pressure, or can the defender repeat the same decisions without gambling? Track that question across games. The goal is a better-supported judgment, not certainty from a spreadsheet.

More analysis and explainers · Corrections and feedback