# 14. Will the supplier work when ordinary staff use it without the demonstration team?


**Interview objective:** Test operational usefulness, maintenance and access controls under the club’s real constraints.

**Put to:** Arielle Dror, the club’s working scouts and analysts, and supplier implementation staff.

**Why it matters to buyers:** Nashville SC’s published data-analyst role combines short-turnaround questions, recurring reporting and reproducible work within an existing Python environment. It is evidence of one club’s requirements—not proof of universal staffing levels—but it offers a concrete basis for asking whether another feed fits ongoing work. ([teamworkonline.com](https://www.teamworkonline.com/soccer-jobs/nashville-sc/nashville-sc/data-analyst-2195561))

**A strong answer should cover:**

- A normal user completing the task after a defined onboarding period.
- The hand-off from discovery to video review, report writing and decision meeting.
- Export friction, corrections, failed jobs and manual reconciliation.
- Access permissions for scouts, analysts, contractors and departing staff.
- Support availability, escalation routes and ownership of recurring maintenance.
- A recovery demonstration when data delivery or an integration fails.

**Sharp follow-up:** Turn off the supplier’s live assistance. Can another authorised staff member reproduce the report and understand its sources?

**Request this artefact:** An observed workflow test recording setup time, active work, verification time, interruptions and assistance. Add an incident exercise using an expired credential or deliberately malformed sample record.

The desk recommends treating successful unattended operation and successful human hand-off as different acceptance tests. A technically functioning feed is not yet proof of a usable recruitment workflow.

Proposed expert interview; not yet conducted. No expert quotation is attributed.