Decide Feature Rollback After Launch

Project Context

ShopWave, a mid-size e-commerce marketplace, launched a new one-page checkout flow to 20% of mobile users three days ago. The feature was intended to improve conversion before the company’s peak seasonal campaign, which starts in 11 days. You are the program manager coordinating product, engineering, analytics, support, and revenue stakeholders on whether to keep the feature live, pause the rollout, or roll it back.

The delivery team includes 1 PM, 1 engineering manager, 6 engineers, 1 designer, 2 data analysts, and 1 support lead. Early results are mixed: checkout completion is up 1.8% for logged-in users, but payment failure tickets are up 22%, page load time increased by 450 ms on older Android devices, and customer support reports confusion among guest users. Finance estimates each day of degraded checkout could cost up to $180K in gross merchandise value.

Key Stakeholders

The VP of Product wants to preserve the launch because the feature is tied to Q3 conversion goals. The Head of Engineering is concerned about rising payment errors and on-call load. The Support lead wants immediate action to reduce ticket volume. The Marketing director does not want instability during the upcoming campaign.

Constraints

• Decision deadline: within 24 hours
• Engineering capacity: only 2 engineers available full-time due to an unrelated fraud incident
• Rollback time: 90 minutes if full rollback; 4 hours if partial rollback with feature flags
• Budget: no additional headcount or vendor support
• Data limitation: experiment has only 72 hours of post-launch data and no clean segmentation for some guest checkout paths

Complications

1. A major payment processor also released an API update the same week, making root cause unclear.
2. The CEO has asked for a recommendation before tomorrow’s executive review.

Deliverables

1. Define the decision framework you would use to determine rollback vs. continued rollout.
2. Identify the metrics, thresholds, and guardrails that matter most in the next 24 hours.
3. Propose an immediate stakeholder communication and escalation plan.
4. Recommend a rollback approach (full, partial, or hold) and explain trade-offs.
5. Outline the first 72 hours of execution after the decision, including monitoring and customer impact mitigation.