You have conflicting stakeholder requests for Connect. How do you decide what ships first

Problem Statement Description

Product context: Stripe is financial infrastructure for internet businesses; its products include payments, Checkout, Billing, Connect, Radar, Issuing, Terminal, and tax tools.

You are a PM working on Stripe Connect, the product that lets platforms onboard, manage, and pay out connected accounts at scale. Multiple stakeholders are asking for different things to ship next: risk teams want stronger controls and fraud mitigation, go-to-market teams want improvements that help large platforms launch faster, engineering is concerned about platform reliability and tech debt, and compliance needs changes to support regulatory obligations across markets.

The interview focuses on how you would make an execution decision when these requests are valid but cannot all ship at once. You should treat Connect as a high-trust financial infrastructure product where sequencing decisions can affect merchant growth, conversion, fraud losses, platform trust, global compliance, and developer experience.

Your execution approach should consider:

- The stakeholders involved, their goals, and where their incentives may conflict

- How to define the decision criteria for what ships first

- The customer and business impact of each request, including risk, revenue, compliance, and reliability

- Dependencies across engineering, risk, compliance, support, and go-to-market teams

- Sequencing options, including whether work should be bundled, phased, deferred, or split by market or customer segment

- Go/no-go criteria, escalation paths, and how to handle unresolved disagreement

- Communication plans for internal teams and affected Connect platforms

- Launch risks, rollback considerations, and post-launch monitoring

The goal is to demonstrate how you would bring structure, judgment, and operational clarity to a real prioritization conflict in a payments infrastructure environment, without assuming that the loudest stakeholder or largest customer request should automatically win.