Project Background
You are the program manager for ShopSphere, a global e-commerce marketplace with 38M monthly active buyers and 2.4M active sellers. ShopSphere’s core revenue comes from seller fees: a referral fee (percentage of item price) plus a fixed per-order fee that covers payment processing, fraud, and customer support.
The CFO has asked your team to validate a new fee structure intended to increase contribution margin by +60 bps without materially harming seller retention. The proposal is to reduce referral fees slightly for high-AOV categories (to remain competitive) while introducing a tiered fixed fee based on order value (to better cover costs on low-AOV orders). Leadership is open to a phased rollout, but wants statistically credible results quickly because FY planning closes in 10 weeks.
The cross-functional team is distributed across Seattle and Dublin: 6 backend engineers (pricing/fees service, ledgering, payments), 2 data scientists (experimentation + causal analysis), 1 analyst (seller cohorts), 1 designer (seller-facing comms), 1 legal counsel (consumer protection + seller terms), 1 finance partner, and 1 customer support ops lead. You own the end-to-end execution plan, including experiment design alignment, launch readiness, monitoring, and rollback.
Stakeholder Landscape (and competing priorities)
- CFO / Finance: Wants measurable margin lift and a decision by the end of week 10 to lock FY guidance. Prefers a broad pilot to speed learning.
- VP, Seller Experience: Worried about seller backlash, social media amplification, and churn—especially among long-tail sellers. Wants conservative exposure and strong comms.
- Payments Engineering Director: Concerned about ledger correctness, refunds/chargebacks edge cases, and operational load. Requires a clean rollback path and auditability.
- Legal & Compliance (EU + US): Requires updated seller terms, clear disclosures, and region-specific constraints (e.g., EU unfair commercial practices). Will block launch if comms are unclear.
- Customer Support: Wants tooling and macros ready; expects ticket volume spikes if fees change without clear explanations.
These priorities conflict: Finance wants speed and scale; Seller Experience and Legal want caution; Engineering wants correctness and minimal operational risk.
Constraints
- Timeline: 10 weeks to deliver a go/no-go recommendation with credible results.
- Exposure limits: Leadership sets a hard cap of max 15% of sellers in the pilot at any time.
- Market scope: ShopSphere operates in 12 markets (US, CA, UK, IE, DE, FR, ES, IT, NL, SE, AU, JP). Legal will only approve a pilot in US, CA, UK, DE initially.
- Technical dependencies:
- Fees are computed by a legacy Fees Service v1 and posted to a double-entry ledger.
- Refunds, partial refunds, and chargebacks are handled by a separate Disputes system that assumes the current fixed-fee model.
- Seller dashboards show fee breakdowns; they update daily via batch ETL (not real-time).
- Operational constraints: Only one SRE is available for launch week due to an ongoing data center migration.
What you need to produce (deliverables)
- Rollout strategy: Define the pilot population, segmentation, and ramp plan (e.g., 1% → 5% → 15%), including which markets and seller cohorts you would include/exclude and why.
- Decision framework: Define success criteria and guardrails (quantitative thresholds) to determine whether to expand, iterate, or roll back.
- Launch plan: A week-by-week execution plan covering engineering readiness, legal/terms updates, seller communications, customer support readiness, and monitoring.
- Risk plan: Identify top risks (technical, reputational, regulatory, analytical) and propose mitigations and rollback procedures.
- Stakeholder alignment plan: How you will drive agreement across Finance, Seller Experience, Engineering, and Legal—especially when trade-offs arise.
Complications (realistic curveballs)
- Seller forum leak risk: A similar pricing change leaked last year and triggered negative press. Comms wants to avoid any in-product messaging until the pilot is stable, but Legal insists on clear disclosure to impacted sellers.
- Category seasonality: Weeks 6–10 include a major promotional event (ShopSphere Deal Days) that changes order mix and could confound margin and seller behavior metrics.
- Ledger correctness incident: Two months ago, a fee miscalculation caused incorrect seller payouts in the UK. Engineering will require additional validation and audit logs before approving any fee experiment.
Your answer should demonstrate how you would execute a controlled rollout of a new fee structure to a subset of users, balance stakeholder priorities, and generate a reliable recommendation under tight constraints.
