Create a metric dashboard for the executive team reviewing Issuing
- Metrics
- Stripe
- Medium
- 10 min
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’s executive team is reviewing the health and trajectory of Stripe Issuing for subscription businesses. These customers may use virtual or physical cards to manage vendor spend, employee purchasing, payouts, usage-based operations, or embedded financial workflows tied to recurring revenue models. The dashboard needs to help executives understand whether Issuing is growing, reliable, profitable, and strategically strengthening Stripe’s broader payments and financial infrastructure business.
Your task is to define the executive-facing metrics dashboard for this review. The audience is senior leadership, so the dashboard should support fast decision-making across product performance, customer adoption, transaction quality, risk, compliance, and business outcomes. It should make clear what is happening, why it matters, and where leadership may need to intervene.
The scope should include metric definitions, denominators, segmentation, instrumentation assumptions, and guardrails. Focus on what executives need to monitor at a recurring business review cadence, not on designing a customer-facing analytics product.
The experience should consider:
- The core business outcomes Issuing should drive for Stripe and for subscription-business customers
- How to define adoption, activation, engagement, and retention for Issuing users, accounts, cards, and programs
- Transaction-level metrics such as authorization performance, spend volume, declines, disputes, refunds, and failure reasons
- Revenue, cost, profitability, and risk indicators that matter for an issuing product
- Cohorts and segments such as customer size, geography, industry, card type, use case, and maturity stage
- Instrumentation needs across card creation, card usage, authorization events, ledger movement, fraud signals, and customer support
- Guardrail metrics around compliance, fraud losses, platform reliability, customer trust, and operational burden
- How the dashboard should distinguish between growth problems, product friction, risk issues, and external market or network effects
The goal is to produce a dashboard framework that would help Stripe executives assess the current state of Issuing, spot meaningful trends or anomalies, compare performance across customer segments, and decide where to invest, investigate, or change course.
What this question tests
- Metric Definition
- Instrumentation
- Counter-metrics
- Decision Quality
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Metrics questions
- What metrics would you use to evaluate a new Checkout feature for enterprise merchantsStripe · Metrics · Easy
- How would you detect unhealthy growth in BillingStripe · Metrics · Easy
- Design an experiment to measure whether Terminal improved outcomes for developersStripe · Metrics · Easy
- Design an experiment to measure whether Terminal improved outcomes for developersStripe · Metrics · Hard
- Define the North Star metric for Atlas serving SaaS companiesStripe · Metrics · Hard
- Create a metric dashboard for the executive team reviewing PaymentsStripe · Metrics · Hard
All Metrics questions · Product manager interview questions by skill area