From the College Athletics edition of September 6, 2026
Athlete interviews show why more data engagement is not always better
University of Florida research team · Collegiate athletics · United States
- Publisher
- Improve my Performance, Protect my State of Mind: How Student-Athletes Engage with their Sports Data
- Original publication
- April 2026; author copy of CHI 2026 paper
- Source retrieved
- 2026-09-07
What happened
Interviews identify multiple ways athletes use sports data, including stepping back to protect confidence or avoid overload.
Why it matters
Empirical collegiate user evidence for AI-derived dashboards; not a test of a particular AI system.
Evidence and measured results
Twenty athletes across six sports at one large, well-funded university were interviewed November 2024–February 2025. The authors used thematic analysis. This is qualitative evidence without a treatment baseline or measured performance effect.
Limitations and uncertainty
Single-institution, moment-in-time self-reports; staff-assisted recruitment may inhibit criticism. Author copy differs in title/format from publisher listing. Exact publication day not established from the inspected PDF.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-07; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
The customer problem is an analytics investment that athletes may find intrusive or overwhelming. Engage athlete representatives, sports performance, student support and the technology owner. Ask when athletes want information, who sees it, and what happens when a person declines a feature. A bounded engagement could examine one dashboard and conduct confidential usability sessions. The value hypothesis is a more usable service with clearer expectations, not a promise of improved mental health. Budget for participant support and independent facilitation where feasible. The study informs discovery questions but cannot establish how prevalent any concern is across other universities, divisions or sports.
Pre-sales engineering
Role takeaway
Fit is evaluating the athlete-facing layer of existing analytics. Inventory raw and derived signals, recipient roles and downstream integrations before designing preference controls. Test display suppression, sharing restrictions and notifications separately so an interface choice does not falsely imply deletion. Prerequisites include an approved data map and meaningful explanations of model uncertainty. Use synthetic fixtures for permission tests and approved representative sessions for usability work. Proposed validation should compare task comprehension and perceived burden across interface variants; do not equate reduced dashboard use with failure. Cloud versus local deployment is secondary to enforceable data boundaries. Generative explanation features need separate factual and safety evaluation.
Delivery
Role takeaway
Assign a product owner in athletics and a confidential feedback lead who is outside selection decisions. Dependencies include athlete availability, support resources and cooperation from the platform vendor. Train coaches to interpret preferences without treating them as poor commitment. Governance checkpoints should review recruitment, usability findings and unexpected concerns before broader rollout. Proposed acceptance criteria include successful completion of all approved sharing-control tests, accurate participant explanation of who receives data, and resolution of critical usability issues. Record opt-outs and complaints without punitive escalation. Do not use this qualitative study to diagnose distress or infer clinical benefit; obtain specialist input when the proposed service crosses those boundaries.
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Make sharing controls and display preferences testable; distinguish hiding a display from stopping collection.
Governance
Who approves, reviews and stays accountable for outcomes?
Assess whether athlete choices are meaningful under coaching authority.
Security and privacy
What data, permissions and controls need testing?
Keep individual feedback confidential and avoid identifying respondents through small-team reporting.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Evaluate cognitive burden and staff-mediated explanations alongside interface accessibility.
Procurement
What should contracts, pricing and exit terms secure?
Require demonstrations of controls instead of assuming every dashboard supports athlete agency.
Operating model
Which teams own the service once it runs?
Measure usefulness and burden, not login frequency alone.
Publication history
- 2026-09-06College Athletics · Issue 014 resources
Stable resource ID: brewer-student-athlete-data-engagement-chi-2026