Conversion in Issuing fell after a redesign. How would you investigate

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.

Stripe Issuing enables businesses and developers to create, manage, and programmatically control payment cards. After a recent redesign of the Issuing experience, overall conversion has fallen. You are asked to investigate the drop as a product manager responsible for understanding whether the decline is caused by the redesign, measurement changes, user behavior shifts, operational issues, or external factors.

The affected journey may include developers discovering Issuing, evaluating documentation and pricing, starting an application, completing required business and compliance steps, creating test or live cards, integrating APIs, and moving into successful usage. Because Issuing touches financial infrastructure, compliance, fraud controls, and developer workflows, the investigation should separate true conversion loss from expected friction, eligibility effects, instrumentation issues, or changes in traffic mix.

This is a root-cause analysis exercise. Focus on how you would frame the anomaly, break down the funnel, validate data quality, prioritize hypotheses, gather evidence, and decide what mitigations or follow-up actions are appropriate without jumping directly to a redesign rollback or a single explanation.

The experience should consider:

- The exact conversion metric that declined, including numerator, denominator, time window, and whether it reflects signup, application completion, API activation, card creation, or live transaction usage.

- Segmentation by user type, geography, company size, traffic source, device/browser, new vs. returning users, developer vs. non-developer users, and eligibility or compliance status.

- Funnel step analysis across the redesigned Issuing journey, including documentation discovery, onboarding, KYC/KYB, API key usage, sandbox testing, card issuance, and first successful transaction.

- Instrumentation checks to confirm whether events, attribution, redirects, consent flows, or tracking definitions changed during the redesign.

- Hypotheses spanning UX friction, copy or pricing clarity, API/documentation discoverability, latency or errors, compliance review changes, fraud controls, sales handoff issues, and external market or traffic changes.

- Evidence required to distinguish correlation from causation, such as pre/post comparisons, cohort behavior, experiment data if available, user session analysis, support tickets, sales feedback, and engineering logs.

- Immediate mitigation options, monitoring needs, stakeholder communication, and criteria for rollback, iteration, or continued investigation.

- Prevention mechanisms such as launch checklists, funnel observability, experiment guardrails, and post-launch reviews for high-risk financial product changes.

Your goal is to present a structured investigation plan that would help Stripe quickly determine why Issuing conversion fell, quantify the business and user impact, reduce further harm, and build confidence in the next product decision.