# Coaches JTBD And Workflow Map

## Status
- Stage: template
- Evidence rule: do not convert hypotheses into facts until interview evidence exists

## How To Use This Doc
- Start with one segment only.
- Fill this from interviews, not from imagination.
- If evidence conflicts across segments, split into separate workflow maps.

## Target Segment
- Segment: group-class coach or coordinator
- Evidence count: 0 interviews documented
- Confidence: low, hypothesis only

## Primary Job To Be Done
- When: I am planning and running repeated weekly classes with students and club constraints
- I want to: keep classes coordinated without constant manual follow-up and chaos
- So I can: protect my time, reduce failures, and run sessions more reliably

## Trigger
- What usually starts the workflow? weekly planning, schedule changes, student cancellations, or club-side constraints
- How often does this happen? likely weekly with reactive spikes
- Is it planned, recurring, or reactive? both recurring and reactive

## Current Workflow
1. Step 1: define class slots and expected students
2. Step 2: coordinate timing and logistics manually
3. Step 3: react to changes, conflicts, or cancellations
4. Step 4: confirm who attends and what still needs follow-up
5. Step 5: update everyone and keep the week coherent

## Tools Used Today
- WhatsApp: likely primary communication layer
- Sheets/Calendar: likely planning fallback
- Club staff: likely involved when courts or logistics depend on club coordination
- ATC or booking system: unknown in practice yet
- Notes/manual work: likely common
- Other: unknown until interviews

## Main Frictions
- Friction 1: too much manual coordination across people and tools
- Friction 2: class changes create reactive admin work
- Friction 3: weak visibility into what changed, who is confirmed, and what is still unresolved

## Cost Of Failure
- What goes wrong: classes get messy, changes propagate badly, and follow-ups get dropped
- Time lost: likely several hours per week for the right segment
- Revenue lost: potential missed or degraded classes, lower fill, or weaker retention
- Stress / trust cost: high if coaches feel disorganized in front of students or clubs
- Who is affected: coaches first, students second, clubs/coordinators if they depend on that operation

## Current Workarounds
- Workaround 1: message threads and ad hoc reminders
- Workaround 2: calendar/sheet tracking plus memory/manual notes
- Why they are insufficient: fragmented tools do not provide one operational loop for repeated classes

## Where ATC-Like Data Could Matter
- Does real court availability help? yes for scheduling and reprogramming, maybe less for base coordination
- Does booking status help? yes if class changes are tied to actual court bookings
- Do player or club records help? likely yes later, unclear for first loop
- Is ATC required or only helpful? current founder direction: ATC is strategically required; open question is whether first value needs read access only or deeper write access

## Signals This Is A Strong Wedge
- Frequent
- Painful
- Manual today
- High error cost
- Clear before/after outcome

## Signals This Is A Weak Wedge
- Rare
- Already solved
- Too custom to one club/coach
- Valuable only with heavy integration and broad scope

## Evidence Log
- Interview / quote:
- Interview / quote:
- Interview / quote:

## Current Conclusion
- Leading workflow hypothesis: group/class coordination
- Confidence level: low but currently best-aligned with Ballbox context
- What still needs validation:
  - whether this is really more painful than reprogramming
  - whether coaches or clubs feel the pain most strongly
  - how ATC should enter the first lovable workflow