“The pilot will begin with 40 drivers and expand to 150 active drivers within six weeks if service targets are met.”
MetroMove pilot management requirements
Open complete sourceThe pilot is expected to expand quickly, but urgent incident ownership, after-hours coverage, severity levels, and response targets are not defined.
Source alignment
Every quote below is an exact substring of its linked fixture source and is checked against stable chunk offsets.
“The pilot will begin with 40 drivers and expand to 150 active drivers within six weeks if service targets are met.”
MetroMove pilot management requirements
Open complete source“Incident escalation, after-hours ownership, response targets, and responsibility for service-wide failures have not been assigned.”
Pilot budget and operating assumptions
Open complete source“In the current rehearsal, support agents could not identify who owns an urgent escalation after business hours or how quickly an incident should be acknowledged.”
Rider support feedback summary
Open complete source“The product has no incident severity, escalation schedule, assigned incident owner, after-hours rotation, or response target.”
Current architecture and feature summary
Open complete sourceOperational / business
Urgent rider or driver incidents may be handled inconsistently as volume grows, damaging trust and delaying recovery.
Technical
The current shared inbox cannot assign severity, ownership, or service targets to incidents.
Define escalation tiers, accountable roles, response targets, and after-hours coverage, then rehearse the process before expansion.
Acceptance criteria
Linked deployment workstream
Give every pilot incident a severity, accountable owner, response target, and escalation path.