Quick intro — who are you and what keeps you up at night?

• What is your primary role? Options: Director of Sports Science, Head Athletic Trainer, Head Coach, Performance Analyst, Team Physician/Medical Director, Strength & Conditioning Coach, Operations/Equipment Manager, Other
• Which program do you represent and what level do you operate at? Options: Professional club, National team, NCAA Division I, NCAA Division II/III, High performance institute, Other
• How many athletes would be in scope for roster-wide monitoring? Options: <15, 15–25, 26–40, 41–75, 76–150, 150+
• What single problem would you most want solved by wearable monitoring this season?
• When you think about success for your program, which three outcomes matter most? Options: Fewer soft‑tissue injuries, Better load management across season, Faster return‑to‑play decisions, Improved player availability, More objective coaching decisions, Integration with medical records/video, Player wellness & satisfaction, Other

If we keep doing what we're doing today, what's the cost?

• What evidence makes you worry that current practice is quietly failing (injury clusters, unexplained dips, coach distrust)?
• How often in the last season did you feel you missed an early warning that later became a problem? Options: Multiple times, A few times, Once, Never, Unsure
• Tell us about a specific recent incident where player workload or monitoring—or lack of it—changed a game plan or roster decision.
• How does unresolved monitoring friction affect team morale, staff workload, or coach confidence?
• If nothing changes this year, what is the single most likely negative outcome?

Where your data actually comes from — and the blind spots nobody talks about

• Which sources do you currently rely on to understand player workload and injury risk? Options: Wearables (GPS/IMU), Heart rate monitors, Video tagging/analysis, Electronic medical records (EMR), Subjective wellness questionnaires, Staff observations/logbooks, Other
• Roughly what percentage of on-field activity is captured by your current devices or systems? Options: <25%, 25–49%, 50–74%, 75–89%, 90–100%, Unknown
• What recurring data gaps or failure modes frustrate you most (missing sessions, sensor dropouts, syncing delays, inconsistent metrics)?
• Who on your staff owns data collection, cleaning, and interpretation today? Options: Sports Science lead, Head Athletic Trainer, Performance Analyst, Data/IT team, Shared responsibility, No clear owner
• How quickly do you need usable data after a session to act (real‑time, within hours, next day)? Options: Real‑time (during session), Within 2 hours, By end of day, Within 48 hours, Longer

Are we measuring what actually moves the needle for you?

• If you could only track three objective metrics that would change coaching plans, which would you pick? Options: Total distance, High‑speed running distance, Acceleration/deceleration counts, PlayerLoad™/composite load, Heart rate/HRV, Positional heat maps, Other
• What thresholds or success signals would make you comfortable changing practice intensity or resting a player?
• Who needs to be convinced by those signals for decisions to actually change (coach, medical, captain, director)? Options: Head Coach, Head Athletic Trainer/Medical, Director of Sports Science, Position Coaches, Player leadership, Other
• How do you currently validate that an alert is actionable versus noise?
• Give an example of a decision you wish you had objective data for—what would that moment look like with reliable sensors and alerts?

When alerts arrive — who actually moves the pieces?

• Who holds final decision authority when monitoring suggests a medical or performance change is needed? Options: Team Physician, Head Athletic Trainer, Head Coach, Director of Sports Science, Case-by-case committee, Other
• Describe your ideal escalation path for an alert that indicates elevated injury risk—what are the steps and timelines?
• What level of false positive rate (alerts that don't require action) would be tolerable before staff lose trust? Options: Very low (<5%), Low (5–15%), Moderate (15–30%), High (>30%), Not sure
• Has data ever been ignored by coaching staff? If so, what would have changed that outcome?
• Which visualizations or alert formats have historically helped you get buy‑in (simple red/amber/green, trend lines, player comparisons, video clips)? Options: RAG status (red/amber/green), Trend graphs with context, Individual athlete dashboards, Video-synced clips, Automated recommendations, Other

Tech reality check — can we actually make this work with what you have?

• Which integrations are must-haves for any solution to be usable (pick all that apply)? Options: Live video integration, EMR / medical record sync, Proprietary athlete ID system, SIS/roster systems, Single sign-on (SSO), None required right now, Other
• What connectivity and venue constraints should we plan for (indoor GPS loss, limited Wi‑Fi, shadowed stadium areas)?
• Who on your IT or data team will be our technical point of contact, and how do they prefer to work with vendor projects? Options: In‑house IT lead, Outsourced IT partner, Performance/data team, No dedicated contact yet, Other
• Are there any security, privacy or regulatory requirements we must meet (e.g., HIPAA, GDPR, federation rules)? Options: HIPAA, GDPR, Local federation data rules, University/Institutional rules, No special requirements, Unsure
• Do you have preferred or existing vendors for hardware or video that we need to integrate with?

Will players wear it — and what will they actually do with the feedback?

• How do players typically react to wearable tech pilots on day one, and how does that change over time?
• What consent, privacy, and wearable policies are required before you can deploy on players?
• Which incentives or engagement tactics have worked to increase wear time and honest reporting? Options: Player education sessions, Coach endorsement, Personal performance insights, Gamification/leaderboards, Mandated wearing by policy, Other
• Share an example of a past pilot where player behavior undermined or boosted results—what happened and why?
• What level of data granularity (individual vs anonymized team trends) will you allow us to show to players? Options: Individual dashboards visible to players, Anonymized team-level only, Mixed (player chooses), Undecided

Designing a pilot that proves value — what would make us celebrate at the end?

• What minimum pilot size and duration would convince you whether this approach works? Options: Small group (5–10) for 4–6 weeks, Positional group (10–20) for 2–3 months, Half roster for one competitive block, Full roster for full season, Unsure—need recommendation
• List the three objective metrics you’d include as pilot success criteria.
• Who must approve pilot results before the program can scale (names or roles)? Options: Head Coach, Medical Director, Director of Sports Science, General Manager/AD, Player leadership, Other
• What level of commercial commitment or budget allocation are you comfortable testing in a pilot? Options: No cost pilot required, Partial cost share, Paid pilot within small budget, Committed budget for pilot, Unsure
• If the pilot fails to meet criteria, what would be your preferred next step? Options: Iterate and re-run, Pause and reassess scope, Shift to different use case, Stop pursuing wearables, Undecided

Governance and accountability — who signs off when decisions matter?

• Which governance model best fits your organization for medical/performance decisions driven by data? Options: Medical-led with coach consultation, Coach-led with medical oversight, Joint committee (medical + sports science + coach), Director-level signoff only, Other
• What data ownership and sharing expectations do you require (team owns, vendor access limited, aggregated export only)? Options: Team owns raw data, Vendor hosts with shared access, Aggregated exports only, Medical records integration only, Undecided
• How quickly do you expect vendor SLAs for uptime and data delivery during a pilot or season? Options: Real‑time/continuous, 99% daily availability, Daily sync, Weekly sync, Flexible
• Describe your preferred incident response for data outages or sensor faults—who must be notified and in what timeframe?
• Are there internal legal or institutional approvals needed before any data platform goes live? Options: Yes—legal review, Yes—university IRB, Yes—medical ethics, No approvals needed, Unsure

Timing, budget, and the least sexy but most important details

• What is your target timeline to decide and start a pilot? Options: Immediately (0–2 weeks), This month, Next 1–3 months, This season start, Next off‑season, TBD
• What budget range is realistically available for a pilot and initial deployment? Options: No budget (must be free), < $10k, $10k–$50k, $50k–$150k, $150k–$500k, $500k+
• What internal approvals or budget cycles could delay a decision?
• Who needs to be in the room for an executive decision review (roles or names)?
• If we could show a clear ROI within a single season, what would you be willing to commit to? Options: Expand to full roster, Multi‑season contract, Repeat pilot with adjustments, Not sure until proven

Final check — if we started tomorrow, what would success look like in 30/90/365 days?

• Rate your current readiness to start a pilot on a scale from 1 (not ready) to 5 (ready tomorrow). Options: 1, 2, 3, 4, 5
• What are the top three blockers we should solve before a kickoff?
• Who will be the named owner(s) from your side for a pilot rollout (please provide names/roles and best contact method)?
• Which communication cadence works best for status updates (daily during rollout, weekly, biweekly, milestone only)? Options: Daily during rollout, Weekly, Biweekly, Milestone only, Ad hoc
• Any final concerns, hard constraints, or must‑have items we haven't covered?

Start with the room: What your team is actually doing today

• How do you currently measure player workload and readiness during training and matches? Options: Wearables (GPS/IMU), Heart-rate monitors, Video tagging, EMR/medical notes, Athlete self-report / RPE, Manual logs (spreadsheets), None / informal observations, Other
• Who is primarily responsible for collecting and owning that monitoring data day‑to‑day? Options: Head of Sports Science, Lead Athletic Trainer / Medical, Head Coach, Operations / Equipment Manager, Performance Analyst, Shared ownership, Other
• How consistently is monitoring applied across the roster (e.g., starters vs reserves, by position)? Options: Full roster nearly every session, Most starters only, Position groups covered unevenly, Rotation/shared devices — inconsistent, Only select players are monitored, Unsure
• Tell me about the last session you monitored end‑to‑end — what went smoothly and what surprised you?
• What single frustration with your current setup would you fix first if you could? Options: Data reliability, Battery / logistics, Coach buy‑in, Player comfort/compliance, Integration with video/EMR, Actionable alerts, Other

Are you unknowingly flying blind in ways that cost player availability?

• Where do you suspect you have the biggest blind spots in monitoring (the things you only discover after a problem occurs)? Options: Acute high‑intensity spikes, Cumulative season workload, Subtle decelerations/changes of direction, Contact events, Recovery / sleep / HRV, Data gaps during travel/matches, Other
• How often do blind spots lead to reactive (instead of proactive) decisions about training or return‑to‑play? Options: Almost always, Often, Sometimes, Rarely, Never, Not sure
• Describe a recent incident where missing or delayed data changed the outcome for a player or session.
• Which stakeholder (sports science, medical, coaching, ops) most feels the pain of those blind spots? Options: Sports Science, Medical, Coaching, Operations / Equipment, Performance Analysis, Multiple equally, Other
• If those blind spots persisted for another season, what would it likely cost you (availability, wins, player trust, budget)? Options: Loss of availability, Increased injuries, Coach distrust of data, Higher costs (medical/rehab), Reputational risk, Other

Which data streams actually move the needle for your staff?

• Which raw data sources do you currently integrate or wish you could integrate (select all that apply)? Options: Inertial/GPS device telemetry, Heart rate / HRV streams, Local match/training video, EMR / injury notes, Lab testing (force plates, sprint times), Subjective wellness / RPE, GPS + video synced timecode, Other
• How confident are you in the timestamp and synchronization quality between your sensors and video/EMR? Options: Highly confident, Mostly confident, Some issues occasionally, Regularly unreliable, We don't attempt sync
• Which derived metrics do you trust most when making load / return‑to‑play choices? Options: Total distance, High‑speed distance, Acceleration / deceleration counts, PlayerLoad / composite load, Heart‑rate recovery, Positional heatmaps, Inertial event detection (tackles, jumps), Other
• Give an example of when a specific data stream or metric changed a decision — what happened and who acted on it?
• What minimum data latency do your staff require for in‑session decision making? Options: Real‑time (<5s), Near real‑time (5–60s), End of session (minutes), Same day, Next day

How much of the roster is truly covered and why isn’t it 100%?

• What percentage of the active roster typically wears devices in a given session? Options: 100%, 75–99%, 50–74%, 25–49%, Less than 25%, Varies wildly session to session
• Which groups are easiest or hardest to outfit (positions, youth prospects, travel squads)? Options: Starters, Reserves, Younger players, Goalkeepers/specialists, Traveling substitutes, None of the above — uniform coverage
• What practical constraints stop full‑roster coverage today? Options: Budget / device cost, Device availability / turnaround time, Uniform / kit compatibility, Player discomfort, Staffing to manage devices, Regulatory / consent issues, Other
• How do you handle gaps when an athlete lacks data for a session (assumptions, imputation, exclude from analysis)? Options: Exclude from reports, Impute / estimate, Use last known values, Manual coach judgment, Flag as incomplete, Other
• If you were to pilot full‑roster monitoring for a month, what concerns would keep you from doing it?

What breaks when technology meets the chaos of practice?

• Which failure modes do you see most often in your monitoring stack? Options: Battery depletion, Device pairing/sync failures, Gateway / connectivity dropouts, Data corruption / loss, Incorrect athlete assignment, Sensor miscalibration, False positives/alerts, Other
• How frequently do these failures occur (per week/month), and which are most disruptive? Options: Daily — highly disruptive, Weekly — disruptive, Monthly — manageable, Rarely — minor, Unsure / no tracking
• When something fails mid‑session, what is your typical escalation and time‑to‑recovery? Options: Immediate fix by ops (minutes), Resolved within session (tens of minutes), Deferred to post‑session (hours/days), Requires vendor support (days), No formal process — ad hoc
• Who owns responsibility for technical troubleshooting across vendor, ops, and coaching? Options: Operations / Equipment, Vendor support, Performance Analysis, Sports Science, Shared / rotating owner, No clear owner
• Share a short story about a technical failure that changed a match or training decision — what happened and what did you learn?

Are players quietly opting out — and what would make them stay?

• What signs do you see that athletes are resistant to wearing or using the tech (complaints, removal, altered behavior)? Options: Refuse to wear, Ask to remove mid‑session, Give false info / avoid devices, Complain about comfort, No visible resistance, Other
• Which reasons drive player resistance most often? Options: Comfort / chafing, Perceived surveillance / privacy, Distrust of how data is used, Interferes with performance, Unclear benefit to player, Aesthetic / uniform rules, Other
• What consent and privacy processes do you have, and where do they fall short? Options: Written consent forms, Verbal agreement only, Data access controls, Player education sessions, No formal process, Other
• What incentives or messaging have improved athlete compliance (e.g., personal metrics, recovery programs, rewards)? Options: One‑on‑one feedback, Individual performance dashboards, Team incentives, Medical recommendations, Technical comfort improvements, None yet, Other
• Tell me about the most resistant player you've worked with — what convinced them to engage (if anything)?

Who actually acts when the system raises an alarm?

• Which roles receive real‑time alerts or daily risk summaries today? Options: Head Coach, Assistant Coaches, Sports Scientist, Team Physician / AT, Performance Analyst, Operations / Kit, Other
• Who has final authority to change a player's session load or remove them from practice? Options: Head Coach, Medical (AT/Physician), Sports Science Director, Joint decision (medical + coach), Other
• What protocol exists when a workload threshold is breached (alert acknowledgement, mitigation steps, documentation)? Options: Formal SOP with checklist, Informal verbal agreement, Documented in EMR, Ad hoc conversation, No formal protocol
• How often do coaches override system recommendations, and why? Options: Frequently — trust issues, Occasionally — tactical reasons, Rarely — usually follow suggestions, Never — always followed, Not tracked
• Give an example where an alert led to a meaningful change in practice or selection — what was the outcome?

Where does your data need to land to actually fit existing workflows?

• Which systems do you need the wearable/analytics platform to integrate with (choose all that apply)? Options: Match / training video system, EMR / injury management, Player management / roster system, Coaching dashboards (Tactical tools), Data warehouse / BI tools, None / standalone, Other
• What minimal export formats and APIs are required for your analysts (CSV, JSON, realtime webhooks, FTP)? Options: CSV, JSON, Realtime Webhooks / MQTT, REST APIs, SFTP/FTP, Proprietary integrations only, Other
• What access controls and data governance rules must be enforced (who sees what, anonymization, retention)? Options: Full access to coaches, Restricted medical-only fields, Player-level anonymization, Role-based dashboards, Custom agreements per role, Unsure — need guidance, Other
• What latency and uptime SLAs are realistic for your in‑session needs? Options: Real‑time (<5s), 99.9% uptime, Near real‑time (5–60s), 99% uptime, End of session, 95% uptime, Daily sync acceptable, No formal SLA required
• Who internally would sign off on integrations and data sharing (names/titles are helpful)?

If this were resolved well, what would it actually change for you next season?

• Which outcomes would make you call a pilot a success (select primary and secondary)? Options: Reduced soft‑tissue injuries, Improved player availability, Measurable workload management, Coach adoption of alerts, High player compliance, Seamless video/EMR integration, Other
• What specific, measurable signals would prove success (e.g., % fewer training injuries, minutes saved, alert precision)? Options: % fewer soft‑tissue injuries, % reduction in high‑risk spikes, Time saved for staff (hours/week), Coach adherence to recommendations (%), Player compliance rate (%), Alert precision / false positive rate
• What pilot roster size, duration, and resources would you realistically commit to test a new system? Options: Small group (5–10) for 4–6 weeks, Partial roster (25–50%) for a season segment, Full roster for pre‑season (4–12 weeks), Unsure — need recommendation, Other
• What would stop you from moving forward even if the pilot met its technical goals? Options: Coach resistance, Budget constraints, Player privacy concerns, Operational inability to scale, Disagreement over data ownership, Other

Starting Point: The Real-World Snapshot

• Who will be the single point of contact (POC) for this rollout on your side? Please include name, role, and best contact method.
• How many athletes do you plan to include in the initial pilot and how many across the full roster? Options: Pilot: 1–10 / Full: 11–25, Pilot: 11–25 / Full: 26–50, Pilot: 26–50 / Full: 51–100, Pilot: 50+ / Full: 100+
• What’s your target go-live date for the pilot, and are there immovable season events that affect that window? Options: Within 2 weeks, Within 1 month, 1–3 months, 3+ months
• Have you used wearable tracking or our platform (or a competitor) before? Please name the systems and describe one positive and one negative memory from that experience.
• Which departments need to be involved in deployment sign‑off (pick all that apply)? Options: Sports Science, Medical, Coaching, Operations/Facilities, IT/Security, Legal/Compliance, Athlete Relations

What Would It Cost If One Thing Failed?

• Imagine a single critical device or gateway fails during an important session—what would that cost you in operational pain or competitive loss? Options: Minor inconvenience, Missed data but manageable, Significant preparation disruption, Potential player safety risk, Unknown / depends
• Tell us about a past technology failure (device, network, or integration) and the ripple effects it had on practice, games, or staff trust.
• How much data loss is acceptable during a session before you consider the session a failed data capture? Options: <1% loss, 1–5%, 5–15%, 15–30%, >30%
• What contingency processes do you currently have when monitoring data isn’t available (e.g., manual workload tracking, video review only)? Options: Manual logs, Video-only analysis, Phone/text alerts, Reschedule/retest, No process defined
• Who on your staff gets notified first when a system outage occurs, and how quickly do you expect a response? Options: Sports Science lead, Medical lead, Ops/Facilities, IT/Security, Coaching lead, Other

Where Are Your Data Doors Open or Locked?

• If integrating with your EMR or video is required, what systems are we connecting to and who owns those APIs or data feeds? Options: EMR vendor: Epic, EMR vendor: Other/Custom, Video: Hudl/Veo/Other, No existing EMR/video, Unsure — need contacts
• How would you describe your current IT/security posture for third‑party device integrations (e.g., whitelist IPs, VPN, no external connections)? Options: Open external connections allowed, Requires VPN, Firewall whitelist only, Requires on‑prem gateway, Unknown — need IT input
• What data fields are non‑negotiable to share with your coaches and medical staff (examples: heart rate, distance, timestamps, raw inertial data)? Options: Summary metrics only, Individual athlete metrics, Raw sensor streams, Event timestamps, Video sync metadata, Other
• Do you have a preferred integration approach—direct API, SFTP batch, or manual export/import—and why? Options: Direct API (real-time), SFTP or batch, Manual CSV export/import, Video sync only, Undecided
• Who in your organization will approve data sharing and privacy terms (name, role)?

Who’s Comfortable Pushing the Red Button?

• If a high-risk alert requires benching a player, who has final authority to act and who must be informed? Options: Head Coach, Medical Director/Head Athletic Trainer, Sports Science Lead, Combined committee, Other
• Walk us through your decision‑making workflow today for player availability—who sees what data, and in what order?
• Where do you feel there is the most ambiguity in ownership or accountability during a rollout (training distribution, device care, data review, escalation)? Options: Device distribution, Device maintenance, Data monitoring, Escalation path, Player consent handling, Other
• Who will be responsible for device inventory (tracking, charging, replacements) and do they have existing asset management tools? Options: Ops/Equipment Manager, Sports Science admin, IT asset team, No one assigned yet, Other
• If we name rollout owners together now, what does success look like for each owner in measurable terms (list owner: success metric)?

Can Your Venue Carry the Load?

• Do your training facilities and competition venues have reliable Wi‑Fi and power for continuous gateway operation, or will we need additional infrastructure? Options: Reliable Wi‑Fi/power everywhere, Reliable at training site only, Competition venues are unreliable, No reliable infrastructure — need installs, Unsure
• When was the last time you performed a wireless site survey at each venue, and can we get the report? Options: Within 3 months, 3–12 months, Over 12 months, Never / unknown
• Where are the high‑risk connectivity spots (stadium tunnels, indoor courts, remote fields) and how do those gaps affect planned sessions?
• Do you have preferred install windows for hardware (e.g., overnight, between practices, during off-season)? Options: Overnight, Between practice sessions, Off-season only, Flexible
• Who is your IT/security contact for venue installs and firewall changes (name, role, contact)?

How Will Players Really Feel About This?

• If players could push back on being monitored, what are the three most common objections you expect to hear?
• Have any players previously opted out of wearable monitoring, and if so, how was that handled operationally and culturally? Options: Yes — formal opt‑out process, Yes — ad hoc handling, No opt-outs to date, Unsure
• What consent model does your organization prefer for athlete data (signed consent, verbal consent, implied via participation, consent via parents/guardians for minors)? Options: Signed consent, Verbal consent, Implied participation, Parental/guardian consent required, Other
• How important is anonymization or role‑based access (coaches vs. medical) to gaining buy‑in from players and staff? Options: Critical, Important, Nice to have, Not important
• What incentives or communication strategies have worked best to increase player acceptance (examples: education sessions, anonymized reports, performance benefits)?

If We Could Make Deployment Unmistakable, What Would That Look Like?

• What are your non‑negotiable acceptance criteria for the pilot (metrics, uptime, player adherence, coach usage)? Please be specific with numbers where possible.
• Which three outcomes would make leadership say the pilot was a clear success?
• What training format do you prefer for staff and players (in-person workshop, recorded video, written SOPs, blended), and how many sessions are realistic? Options: In‑person workshop, Recorded video, Written SOPs, Blended approach
• Which dashboard views and alert types must be configured before go‑live to consider the pilot usable (examples: per‑player load, team summary, threshold alerts)? Options: Per‑player dashboards, Team workload summary, Threshold alerts, Video-sync events, Medical notes integration
• If we set a firm pilot end date, what internal approvals or milestones need to happen before that date to avoid delay?

Micro-Commitments: Who Does What Next?

• Who on your team can commit today to the first on-site readiness task (device inventory, site survey, or consent collection)? Please name the person and the task.
• Which of these would be the highest‑impact next step to schedule within the next two weeks? Options: Device inventory audit, Site wireless survey, Player consent session, Owner/roles workshop, Pilot kickoff meeting
• What are the top three blockers that, if unresolved, would delay deployment beyond your target date?
• What support or documentation would make your named owners feel confident to move forward (examples: deployment checklist, runbook, on‑site engineer)? Options: Deployment checklist, Runbook / SOPs, On‑site engineer, Training videos, Integration playbook
• Realistically, when can we schedule the first readiness checkpoint call to validate inventory, connectivity, and consent status? Options: Within 48 hours, Within 1 week, 1–2 weeks, 2+ weeks

Quick Check: Who’s in the Room?

• Which role best describes you for this project? Options: Director of Sports Science, Head Athletic Trainer / Medical lead, Head Coach / Coaching staff, Performance Analyst, Operations / Equipment Manager, Athletic Director / Admin, Other
• Which timeline feels realistic for you to get a pilot running? Options: < 1 month, 1–2 months, 2–3 months, This season (within 6 months), Next season / long lead
• How large a pilot roster would you consider meaningful? Options: Small group (5–10 athletes), Position group (~10–20 athletes), Half roster (~25–40 athletes), Full roster, Undecided
• Roughly what range is allocated for this technology pilot (if known)? Options: <$10k, $10k–$50k, $50k–$100k, >$100k, Not yet budgeted / unclear
• Who else do we need in the room from your side to move this forward?

What Decisions Are You Making Blindly?

• Which regular coaching or medical decision do you feel you make without reliable data? Options: Training load adjustments, Return-to-play timing, Substitutions during games, Individual recovery protocols, Selection for contact drills, Other
• Give a recent example of a decision where better monitoring would have changed the outcome—what happened?
• How often do you feel decisions are made on intuition rather than measurable thresholds? Options: Almost always, Frequently, Sometimes, Rarely
• If you had one single measurement you trusted every day, which decision would you change first? Options: Reduce practice intensity, Rest a player, Adjust individual load, Change substitutions, Other
• Who on your staff needs to trust the data for it to actually change behavior? Options: Head Coach, Assistant Coaches, Sports Scientist(s), Medical Staff / ATs, Strength & Conditioning, Players, Other

When Workload Spikes Become Problems

• Tell me about the last time a workload spike led to a problem—what were the early signals you missed?
• How many soft‑tissue or workload-related injuries did you record last season? Options: 0–2, 3–5, 6–10, 10+
• Which workload metrics do you currently use or trust (select all that apply)? Options: Total distance, High-speed running, Acceleration / deceleration counts, PlayerLoad / composite metric, Heart rate / HRV, Session RPE, We don’t use consistent metrics
• How often do you review workload data as a team (daily/weekly/only after injury)? Options: Daily, Every session, Weekly, Only after incidents
• How would you describe coaching staff's willingness to rest a key player when data suggests they should? Options: Eager to trust data, Cautiously open, Reluctant, Firmly opposed

Where Your Data Fails You

• Which part of your current monitoring setup do you find most unreliable or incomplete? Options: Sensor accuracy, Device coverage across roster, Connectivity at venues, Data sync delays, Integration with video/EMR, Interpretation & alerts
• How often do devices fail (battery, fit, loss of signal) during sessions? Options: Never / very rare, Occasionally (1–2 per month), Regularly (weekly), Multiple times a week
• What specific failure modes cause the most disruption (e.g., missing halves, corrupted sessions, mis‑tagged players)?
• Do you currently tie monitoring data to video or your EMR? If not, what's stopped you? Options: Yes — both, Video only, EMR only, No — technical barriers, No — governance/ownership concerns, Other
• How much staff time is consumed each week cleaning and interpreting raw data? Options: <1 hour, 1–4 hours, 5–10 hours, 10+ hours

If Next Season Looks Different — What Changed?

• If you woke up next season with fewer soft‑tissue injuries and coaches praising the insights, what was the single biggest change that made that happen?
• Which measurable outcomes would make you call the pilot a success? Options: % reduction in injuries, Reduced days lost per player, Increase in practice quality metrics, Coach adoption rates, Player compliance rates, Faster return-to-play decisions
• What behavioral changes among coaches or players would indicate real adoption, not just pilot curiosity? Options: Regular use of alerts in meetings, Adjusting practice plans based on thresholds, Pulling players proactively for recovery, Referencing dashboards in debriefs, Other
• What constraints would make a successful outcome still unacceptable (e.g., cost, data ownership, inability to integrate with EMR)?
• Which audience’s endorsement matters most to scale beyond a pilot (select up to two)? Options: Head Coach, Medical Director, Director of Sports Science, Athletic Director / CFO, Player leadership

What Would It Take to Roll This Out?

• What's the single logistical obstacle that will stop a roster-wide rollout before it starts? Options: Player consent / buy-in, Budget / procurement, Staffing for deployment, Venue connectivity, Device inventory and fittings, Other
• Who on your team will own day-to-day pilot execution and troubleshooting?
• Which deployment tasks must be completed before first capture (select all that apply)? Options: Device fitting, Gateway install, Player consent forms signed, Coach training session, Data integration configuration, Baseline athlete profiles
• How comfortable are you with a staged rollout (start with 1 position group → scale) vs. all-at-once? Options: Prefer staged, Prefer all-at-once, Flexible either way, Undecided
• What internal approvals or procurement steps must happen before you can sign a commercial agreement?

Validation & Acceptance — How Will You Know It’s Real?

• What would make your coaches say out loud: “We trust this system”?
• Which technical validation checks are non‑negotiable for you before acceptance? Options: Sensor calibration verification, Complete session capture rate, Latency within acceptable window, Dashboard thresholds match raw signals, Alerts behave as expected
• What pilot metrics will you require to declare success (select up to three)? Options: % athlete compliance, Session capture completeness, Reduction in days lost, Coach action rate on alerts, False positive rate of alerts, Integration uptime
• Who must sign off on data ownership, access, and retention before deployment? Options: Medical Director, Legal / Compliance, Athletic Director, IT
• Are there governance rules we need to honor (e.g., who can act on alerts, what needs physician sign‑off)?

Next Steps — Commitment, Timeline, and Risks

• If we agreed today, what is the earliest practical date you could start device fitting and baseline captures? Options: <2 weeks, 2–4 weeks, 1–2 months, Longer than 2 months
• Who are the decision-makers and what approvals are required to sign a pilot agreement?
• What are the top three open risks you want us to mitigate before contract signature?
• Which reporting cadence would you prefer during the pilot? Options: Daily operational check-ins, Weekly summary reports, Bi-weekly strategic reviews, Ad-hoc when issues arise
• What would you need from us this week to move toward a formal pilot plan? Options: Detailed commercial proposal, Technical integration checklist, Deployment timeline & owners, Reference calls with similar teams, Pilot acceptance criteria document