Meridian Field Services: instructional example, not project evidence
Why considered: the pilot has a continuous discovery backlog and behavioral baselines from the legacy system; WSJF's cost-of-delay fits program sequencing the single-hub pilot lacks; Kano needs a customer survey the internal rollout skips; MoSCoW's binary buckets lose the effort dimension the sizing already has. Who & how: M. Chen with the product owner, scored July 9 (prioritization framework[1]).
| Feature | Reach · Impact | Confidence (source) | Effort | Objective · stories |
|---|---|---|---|---|
| F1 ranked suggestions | every assignment · high | MEDIUM: the adoption assumption is unproven (ASM-02[2]) | large | objectives[3] · US-1, US-3[4] |
| F2 override + reason | every override · high | HIGH: a recorded requirement (FR-013[5]) | small | US-3[4] |
| F3 exception-review search | ops managers weekly · medium | LOW: the search UX is unvalidated | medium | none |
| F4 position ingestion | feeds everything · high | HIGH | large | the ENABLER |
| F5 mobile confirmation | every technician · high | HIGH | medium | US-1[4] |
Dependency: F1 scores highest but is BLOCKED BY F4 (no positions, no proximity ranking); F4 is sequenced first despite being infrastructure, not a headline feature.
| Disposition | Features | Basis |
|---|---|---|
| SHIPS AT PILOT | F4 (enabler) · F1 · F2 · F5 | The assignment loop end to end; success criterion: the week-6 value review (success measures[3]); capacity: one pilot team, four features fit, the count checks |
| DEFERRED | F3 exception-review search | Revisit trigger: the override rate clearing 40% sustained (the RSK-06 indicator, RSK-06[6]), when reviewing exceptions earns its build |
| DEFERRED | hub-six onboarding automation | Revisit trigger: the hub-two go decision (BD-2[1]) |
Sign-off: M. Chen, July 10; the sponsor informed. Every deferred item carries an event trigger; nothing below the line is a silent drop.
Trade stated to the sponsor: deferring F3 means ops managers review overrides in a spreadsheet through pilot; the cost is manual effort on a low-volume surface, accepted because F3's confidence is LOW and its value scales with override volume the pilot has not yet produced.
Re-scoring triggers, events: the adoption assumption invalidating (ASM-02[2]) reopens F1's confidence and could re-rank the whole loop; a competitor's dispatch product shipping suggestion-first would reopen impact scores; the week-6 metric miss reopens the cut line itself. No quarterly review substitutes.
| Question | Owner | Answer by | Blocks |
|---|---|---|---|
| Does F5 mobile confirmation ship in the pilot cut or ride the INT-2 push notification alone until hub-two (a scope question the mobile spec's platform decision informs, platform targets[7])? | M. Chen | At the mobile-platform decision | F5's cut-line row only |