DES-22 — Client feedback round & design revisions
Consolidate HOCO's feedback on the three solutions, revise, re-validate, publish design v1.1.
| Field | Details |
|---|---|
| Task code | DES-22 |
| Phase | P1 — V1 build & integration |
| Product scope | V1 |
| Status | Planned |
| Start | Tue 17 Nov 2026 |
| Due | Wed 18 Nov 2026 |
| Responsible | Akram — UI/UX designer |
| Co-responsible | — |
| Effort | 1.5 person-day(s) planned · 3 from scratch · size S |
| Area · app | Handoff · design |
| Depends on | DES-21 |
| Unblocks | DQA-01, DQA-06, DQA-07, DES-30, DQA-09, DQA-10, DES-23 |
| Milestones | — |
Summary
Consolidate HOCO's feedback on the three solutions, revise, re-validate, publish design v1.1.
Description
This task is the buffer after handoff. Akram consolidates HOCO's feedback on the three solutions and the reseller web (checkpoints 3–6), revises the frames, re-validates the changed screens with HOCO and publishes design v1.1, plus tokens v1.1 if any value changes. Inputs: the checkpoint feedback lists and the comments on the shared design, the decision register (prices before or after validation, TTC display, payment methods, credit policy, return window) and any template page specs that slipped from Day 19 or 20. Scope: revisions of existing V1 screens and closing pending decisions; new scope goes through change requests, and loyalty, packs and detailed credit go to DES-30 (V2). The development tasks are already running in this phase, so every change reaches Imad (MRA/MDA) or Anis (DSH/WEB) as a dated change request, never as a silent edit in Claude Design. DES-22 unblocks the document templates, copy, store assets, training materials and field kit (DQA-09, DQA-10, DQA-01, DQA-06, DQA-07) and DES-30.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | Consolidate the feedback from checkpoints 3–6 into one tracker: id, screen id, request, source, decision (accepted V1 / change request / V2 / rejected with reason), effort | Akram |
| 2 | Triage session: accept, defer or reject each item; record decisions in the decision register | Anis |
| 3 | Close pending decisions in the frames: keep the decided variant (prices before or after validation, TTC vs HT labels, enabled payment methods, return window) and remove the Decision pending stickers | Akram |
| 4 | Revise the accepted frames; mark them Changed after approval, with a visible before/after for each | Akram |
| 5 | Raise a change request per impacted build task (e.g. MRA-04, MDA-05, DSH-06, WEB-03) with the frame link, the change and the reason | Akram |
| 6 | Finish any template page specs that slipped from Day 19 (support, reports, administration) or Day 20 (reseller web) | Akram |
| 7 | Re-validation session with HOCO (30–45 min) on the changed screens only; silence is not approval | Akram |
| 8 | Publish design v1.1: v1.1 entry on the Cover, changelog page, tokens v1.1 (semver: value change = patch, new token = minor) sent to Anis and Imad if changed | Akram |
| 9 | Check the change requests' impact on the mobile build and plan the integration | Imad |
Deliverables
- Consolidated feedback tracker with a decision per item
- Design v1.1 in Claude Design with a changelog; tokens v1.1 if values changed
- Change requests filed for every impacted build task
- Re-validation notes from HOCO on the changed screens
Acceptance criteria
- Every feedback item has a decision and, if accepted, a revised frame
- No Decision pending sticker remains on a V1 frame, or each remaining one has a dated owner in the decision register
- Every change after handoff has a change request linked to the consuming task
- HOCO has re-validated the changed screens
- The v1.1 changelog lists each changed screen id and token
Test measures
- Diff review with Imad and Anis: each changed frame matches its change request
- Run the design QA checklist on the changed frames only
- Token build check if tokens v1.1 was released
Risks
- HOCO answers late (assumed 3 working days) — the frames stay Client review, developers build on the handed-off version, and changes arrive later as change requests.
- Feedback grows into new scope — anything that is not a revision of an existing V1 screen becomes a change request with an effort estimate, or goes to V2.
KPI
- Delivered by Wed 18 Nov 2026 within 1.5 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.
DES-21 — Day 21 — Prototypes, design QA & handoff
Clickable prototypes (reseller ordering, delegate visit day), consistency pass, specs and assets export, tokens v1.0 tagged, client presentation.
DES-23 — Smart notifications design — Notification Centre, action buttons, promotion tabs, flash-sale countdown
Designs the additions of HOCO's document 03: the home Notification Centre with its six groups, the action button on notification rows, the grouped inbox, group preferences, the Promotions / Ventes flash tabs and the flash-sale countdown card, on the reseller app and the reseller web.