Project Context

You are the program manager for ShopSphere, a global e-commerce marketplace with 38M monthly active buyers and 1.2M active sellers across North America and Western Europe. The company is migrating its legacy Order & Payouts system (built 9 years ago) to a new event-driven platform to reduce payout delays and support new payment methods. The migration must be completed before Peak Holiday traffic begins.

This is not a “big bang” rewrite: the plan is a zero-downtime, incremental cutover using dual-write, backfill, and progressive traffic shifting. The business stakes are high: Order & Payouts touches $4.5B/month GMV, and any payout regression can trigger seller churn, regulatory scrutiny, and chargeback losses. The CEO has asked for a weekly readout after a competitor suffered a public outage during a similar migration.

The cross-functional team includes 3 backend teams (18 engineers total), 1 data platform team (5 engineers), 1 SRE team (4 engineers), 1 product designer, 2 product managers, 1 finance operations lead, and 1 compliance counsel. You also depend on two external payment partners: Adyen (card processing) and Tipalti (seller payouts) for certification and settlement file changes.

Stakeholder Landscape (Competing Priorities)

Different leaders want different things from “status,” and they interpret the same facts differently:

• CFO (high influence): cares about payout accuracy, reconciliation, and financial controls. Wants crisp risk flags and confidence levels; low tolerance for “engineering optimism.”
• VP Engineering (high influence): wants a realistic burn-down, dependency management, and clarity on what is blocking the teams. Wants to avoid thrash from exec escalations.
• Head of Seller Experience (medium-high influence): wants seller-facing impact, support readiness, and comms timing. Pushes for early launch of “instant payouts” even if it increases migration complexity.
• Compliance Counsel (high influence): focused on SOX controls, audit trails, and PSD2/PCI implications for EU flows. Prefers delaying cutover over any ambiguity.
• Payment Partners (medium influence): care about certification timelines and minimizing last-minute changes; they provide limited transparency and sometimes miss SLAs.

You have a standing Monday exec review (CEO, CFO, VP Eng), a Wednesday cross-functional working session (PM/Eng/SRE/Data/Finance Ops), and a daily engineering standup.

Constraints

1. Timeline: 10 weeks until Peak Holiday code freeze. The CEO expects “migration complete” by Week 8 to allow two weeks of stabilization.
2. Reliability: Must maintain 99.95% checkout availability and 99.9% payout job success during the migration.
3. Financial correctness: 0 material reconciliation breaks; any discrepancy above $25K/day must be detected within 24 hours and resolved within 72 hours.
4. Resourcing: No additional headcount approved. Two senior engineers are on-call for a legacy incident rotation and can only spend 60% on the migration.
5. External dependency: Tipalti requires 3 weeks for certification after receiving final settlement file specs; Adyen requires 2 weeks for webhook schema changes.

Current Status (Week 3)

• Dual-write is implemented for orders but not for refunds.
• Backfill for historical orders is 40% complete; data team reports inconsistent event ordering for 0.6% of records.
• SRE has not signed off on the rollback plan; they want chaos testing evidence.
• Finance Ops found a reconciliation mismatch in a staging run: 0.2% of payouts differ by small rounding amounts (likely currency conversion rules).
• Head of Seller Experience is pushing to announce “instant payouts” at a seller conference in Week 6.

Complications

1. Scope pressure: Product wants to bundle “instant payouts” into the migration launch to maximize impact at the seller conference. Engineering believes this adds 2–3 weeks and increases risk.
2. Partner uncertainty: Tipalti is slow to confirm certification slots; they will not commit to a date until they see final specs, but final specs depend on rounding rule decisions with Finance.
3. Executive trust gap: The CFO believes prior status reports have been “too green” and wants a new reporting format that clearly separates facts, risks, and assumptions.

Your Task (Deliverables)

Create a status reporting approach that tailors content, depth, and framing to different audiences while keeping a single source of truth.

1. Design three audience-specific status reports (1 page each, outline is fine):

   • Daily engineering/SRE update
   • Weekly cross-functional working session update
   • Monday exec review update (CEO/CFO/VP Eng)

2. Define a consistent reporting taxonomy (e.g., RAG definitions, confidence levels, risk vs issue, decision log) that prevents teams from “gaming” status.

3. Propose a cadence and workflow for producing the reports (inputs, owners, cutoffs, review steps) that fits within the team’s bandwidth.

4. Show how you would communicate two trade-offs in a way that drives alignment rather than debate:

   • Whether to bundle instant payouts into the migration
   • Whether to delay Tipalti spec finalization to resolve rounding rules perfectly vs ship with a controlled workaround

5. Include an escalation and decision mechanism: what gets escalated, to whom, and within what SLA.

Your answer will be evaluated on clarity, audience empathy, ability to preserve integrity of the underlying facts, and how effectively your reporting system drives decisions under time pressure.