Judging technique when the outcome is already known

Knowing the result changes the judgement

An attempt that succeeded is described as audacious and one that failed is described as reckless, even when the decision was identical. This is a general feature of how people evaluate decisions, and it is particularly strong when the outcome is visually dramatic. Moment rankings are built entirely from successes, so every entry benefits from the most favourable possible framing of the choice behind it.

The unsuccessful attempts that were equally well judged are absent from the archive of celebrated moments and from the discussion. Any conclusion about decision quality drawn from such a list is therefore based on a sample selected on the outcome. Selecting on the outcome is the oldest way to reach a confident and wrong conclusion about how a decision should have been made.

The invisible denominator

Assessing whether an ambitious attempt was a good idea requires knowing how often comparable attempts succeed, which requires counting the failures. Those failures are recorded in match data and almost never in the material from which moment lists are compiled. A shot type that succeeds rarely produces spectacular highlights and a poor expected return, and only the highlights survive in memory.

Presenting such attempts as evidence of vision therefore rewards a choice that was probably incorrect in the situation it was made. The corrective is to consult the frequency of success, which converts an anecdote into something closer to an assessment.

Where the ambitious choice is correct

A low-probability attempt is justified when the alternative is worse, which happens when time is short or when the conventional option is unavailable. The same attempt in an unpressured situation, with better options available, is a poorer decision that happened to produce a memorable result. Distinguishing the two requires seeing what else was available, which is exactly the information a tight replay removes.

This is why the wide angle matters so much for any honest assessment of a moment beyond its aesthetics. A ranking built on replays alone is structurally unable to make the distinction. It can still describe what happened accurately, provided it stops short of explaining why the attempt was the right one to make.

Technique against decision

It is worth separating whether the action was well executed from whether it was well chosen, because these are independent properties. A poorly chosen attempt can be executed superbly, and a well chosen one can succeed despite unconvincing execution. Moment lists usually reward the first combination, since spectacular execution is visible and decision quality is not.

Stating which of the two the list is ranking makes it coherent and immediately explains several entries that otherwise look arbitrary. It also creates room for a list of well-judged moments, which would look nothing like the conventional one.

Assessing with the bias acknowledged

The bias cannot be removed, because the material available for assessment is defined by success and always will be. It can be named, and naming it changes how confidently a compiler describes the thinking behind a celebrated moment. Language that describes what happened rather than what the competitor must have been thinking avoids most of the overreach.

Where intention genuinely matters to the entry, saying that it is inferred rather than known is a small and worthwhile precision. These habits cost nothing and they distinguish an assessment from an appreciation, which is a distinction most such lists never attempt. An appreciation is a perfectly respectable thing to write, and the only error is publishing one under the heading of an evaluation.