0001 — Reprioritize Customer Segmentation ahead of Mention User in CDP Notes

Delivery / Program Management — decision record (ADR-style).

Context

The CDP H2 2026 roadmap Priority table ranked Mention User in CDP Notes as P1 and Customer Segmentation as P2. Mention User in CDP Notes was already flagged as a Program-level risk: its derived forecast (p50 2026-08-10 / p85 2026-08-19, timeline-mapper 2026-07-01) lands well past its revenue commitment, with no external dependency blocking it — the gap is pure BE→FE→QA critical-path length against a tight window. Customer Segmentation carries its own revenue commitment (2026-07-28) and, under the roadmap's sequencing policy (priority + hard date + dependency order first), a P2 ranking meant it queued behind Mention User for shared capacity (notably QA).

The PM made the call to move Customer Segmentation ahead of Mention User in CDP Notes during CDP's Sprint Planning on 2026-07-07 (the same date the active sprint, cdp/delivery/sprints/2026-07-07-sprint-01.md, opened).

Decision

We will reprioritize the CDP roadmap ## Priority table: Customer Segmentation → P1, Mention User in CDP Notes → P2. All lower ranks (P3–P10) are unchanged. Legacy Migration: CRM Notes → CDP (P4), which depends on Mention User in CDP Notes, now cites its dependency as "P2 — Mention User in CDP Notes" rather than P1.

Option not chosen: leaving the original P1/P2 order and instead pulling in extra capacity to close Mention User's forecast gap — rejected as a resourcing question separate from the prioritization call the PM wants reflected now.

Consequences

• Customer Segmentation gets first claim on shared capacity (notably QA Hendry) ahead of Mention User in CDP Notes, per sequencing policy rule 1.
• Recomputed via initiative-timeline-mapper (2026-07-09): no material forecast/capacity impact. The two initiatives share no BE/FE/Mobile staff (Segmentation runs on Julio Jeffer/ Azani/DATA Team; Mention User runs on Berlianto/Jovi/Alfi) — their only shared resource is QA Hendry, who sits at load 0.60, well under capacity. Re-ordering whose QA slice he executes first does not push either date: Mention User's forecast stays p50 2026-08-10 / p85 2026-08-19 (already at risk against its own commitment, independent of this reorder); Customer Segmentation's stays TBD (Data/Design still unscoped).
• Legacy Migration: CRM Notes → CDP (P4) still cannot start until Mention User ships; that dependency and its schedule risk are unchanged by this reorder.
• Follow-up surfaced, not yet resolved: the active sprint (cdp/delivery/sprints/2026-07-07-sprint-01.md) still carries the pre-reorder ranks (Mention User P1 / Segmentation P2) in its sprint_goal and per-engineer queues — flagged by lint-delivery.mjs as SPRINT_PRIORITY_DRIFT. Reconciling it is sprint-resync's job, not this decision's.
• Separately noticed and not addressed by this decision: the roadmap Priority table lists Mention User in CDP Notes' commitment as 2026-08-14, while the Program-level risks section cites 2026-07-14 for the same initiative. This pre-existing data inconsistency should be reconciled with the DRI independent of this reprioritization. Resolved 2026-07-09: DRI confirmed the commitment is 2026-08-14 (W2 August); the stale 2026-07-14 restatements in the README forecast comment, timeline.md, the roadmap risk narrative/capacity notes, and the sprint queues were reconciled to 2026-08-14 (forecast now fits at p50 08-10, misses at p85 08-19 by ~5 days). Dated status/ reports are left as point-in-time memory. Surfaced going forward by the new COMMITMENT_DRIFT README-scan check.