DQA-08 — Pilot UX observation & feedback synthesis
Ride along with pilot delegates, interview pilot resellers, synthesise UX findings into prioritised improvements.
| Field | Details |
|---|---|
| Task code | DQA-08 |
| Phase | P2 — Acceptance, go-live & pilot |
| Product scope | V1 |
| Status | Planned |
| Start | Thu 31 Dec 2026 |
| Due | Sun 3 Jan 2027 |
| Responsible | Akram — UI/UX designer |
| Co-responsible | — |
| Effort | 2 person-day(s) planned · 3 from scratch · size M |
| Area · app | Research · design |
| Depends on | LCH-02 |
| Unblocks | — |
| Milestones | — |
Summary
Ride along with pilot delegates, interview pilot resellers, synthesise UX findings into prioritised improvements.
Description
During the two-week pilot that follows the production go-live and training (after LCH-02), Akram observes real use. That means ride-alongs with pilot delegates and interviews with pilot resellers. Akram then turns what was seen into prioritised UX improvements. Inputs: the pilot group (delegates and resellers chosen by HOCO), the production apps, the success KPIs of ANA-04 (adoption, field conversion, digitalisation share, tour performance, operational quality), the invitation funnel and the support tickets of the pilot. Scope: observation, interviews and synthesis, not fixes. Findings feed Anis's LCH-04 and Imad's MOB-18 (pilot improvements), the pilot go / no-go and the generalisation backlog (OPS-06).
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Observation plan: objectives, questions, consent wording, schedule (2–3 ride-alongs on full tours, 5–8 reseller interviews mixing Super-gros, Demi-gros and Détail, guest-to-signup cases) | Akram |
| 2 | Delegate ride-alongs: time per visit, check-in failures and distances, sync and offline incidents, one-hand and sunlight use, time to close the tour, workarounds | Akram |
| 3 | Reseller interviews (in store or by phone): first order, filter use, understanding of prices and availability, WhatsApp support, live tracking, after-sales and returns | Akram |
| 4 | Back-office shadowing: a commercial admin working the orders-to-confirm queue and the validation queue (time to confirm, blockers) | Akram |
| 5 | Pull pilot metrics: invitation funnel, sign-ups, first orders, confirmation times, not-done visit reasons, ticket types | Anis |
| 6 | Synthesis: affinity mapping; issues rated by severity × frequency; each finding with evidence, affected screen ids and a proposed fix | Akram |
| 7 | Readout with Anis and Imad: quick wins for LCH-04 / MOB-18, generalisation backlog, V2 candidates | Akram |
| 8 | Update the Claude Design frames of the accepted quick wins (design v1.2) and raise the change requests | Akram |
Deliverables
- Pilot UX findings report: prioritised issues with evidence, screen ids and proposed fixes
- Updated frames for accepted quick wins (design v1.2) with change requests to LCH-04 and MOB-18
- Interview and ride-along notes (anonymised)
Acceptance criteria
- At least 2 full-tour ride-alongs and 5 reseller interviews are done and documented
- Every finding has evidence, a severity, a frequency and the affected screen ids
- The prioritised list is reviewed with Anis and Imad before the pilot go / no-go
- Accepted quick wins have updated frames and change requests
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| OPS-06 | Pilot with a limited group of delegates and resellers, then progressive generalisation | V1 |
Test measures
- Cross-check qualitative findings against pilot metrics (e.g. check-in failures vs GPS_OUT_OF_TOLERANCE counts)
- Readout session: each top-10 finding has an owner and a decision (fix in pilot, generalisation, V2, rejected)
Risks
- Pilot participants are hard to schedule — book the ride-alongs during training (LCH-02) and use phone interviews for resellers.
- Observation turns into ad-hoc support — note the support request, hand it to Anis or Imad, and keep observing.
KPI
- Delivered by Sun 3 Jan 2027 within 2 person-day(s).
- Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
- Zero open critical defects, permission gaps or data-integrity regressions at sign-off.
Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.