Designing an Athlete Profile for Discovery, Not Just Display

A profile page can look complete to a person while remaining almost useless to a discovery system.

If an athlete’s position, history, statistics, achievements, and media exist only as an unstructured biography, a scout can read the page after finding it—but the platform has limited ability to help the scout find the athlete in the first place.

For an athlete discovery platform, the profile is not just a presentation page. It is a structured record that connects evidence to search and evaluation workflows.

Separate facts by meaning

Useful profile data has different types and lifecycles:

• identity and basic athlete information;
• playing position and relevant attributes;
• team or playing history;
• achievements;
• statistics with appropriate context;
• video and other media;
• publication or completeness state.

Placing all of this into a single text field may make initial development faster, but it weakens validation, filtering, ordering, and future changes.

Structure should still be proportional. Not every sentence deserves its own table. The objective is to identify information that users search, compare, validate, update independently, or connect to another record.

Media needs organization

Video is important evidence in a scouting context, but a collection of uploads is not automatically useful. Athletes need a manageable way to add and organize highlights, including interfaces that work across mouse and touch devices.

The data model should preserve ownership, ordering, review or publication state where required, and the relationship between the media and the athlete. A visual drag-and-drop interaction is only the surface; the underlying ordering change must be validated and stored reliably.

Discovery creates derived views

Scouts need to find relevant athletes through search and filters, then evaluate profiles in their own context. Watchlists and ratings should not overwrite the athlete’s profile. They are records of a scout’s workflow, linked to the athlete but owned by the evaluator.

This separation supports multiple scouts evaluating the same athlete without exposing one scout’s private assessment to another or treating it as athlete-authored information.

Trust requires state

The platform may also need to distinguish draft, discoverable, reviewed, or restricted content. A profile being stored is not the same as it being ready for discovery. Similarly, a scout account existing is not the same as it being verified.

Explicit states make those trust decisions visible and enforceable. Hiding them inside a collection of loosely related flags makes authorization and reporting harder to reason about.

A profile is part of a system

The best-looking profile cannot compensate for unclear ownership, weak search structure, or mixed evaluation data. Conversely, a well-modelled profile can support several experiences: athlete editing, scout discovery, administrative review, and future reporting.

My current conclusion is that a discovery profile should be designed from both directions. It must help the athlete represent themselves accurately and help the authorized evaluator find and assess relevant evidence. Display is one output of that model—not the model itself.

Related work: Athlete Discovery & Scouting Platform.