Tax engagement dropped 20% in two weeks among enterprise merchants. Diagnose the issue

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 Tax helps businesses calculate, collect, and report taxes across jurisdictions as part of their payments and billing workflows. Enterprise merchants often rely on it across multiple markets, integrations, teams, and checkout surfaces, so a sudden engagement decline can indicate anything from a measurement issue to a product regression, compliance workflow friction, integration breakage, or a shift in merchant behavior.

You are investigating a reported 20% drop in Tax engagement over the last two weeks among enterprise merchants. Treat this as a root-cause analysis scenario: clarify what “engagement” means, determine whether the drop is real, isolate where it is happening, form hypotheses, identify the evidence needed, and propose immediate mitigations and longer-term prevention mechanisms.

Your diagnosis should reflect Stripe’s context: high reliability expectations, developer-led integrations, global compliance sensitivity, revenue and conversion impact for merchants, and the complexity of enterprise account structures.

The experience should consider:

- How to define the anomaly, including the exact engagement metric, denominator, baseline period, seasonality, and statistical significance.

- How to segment the decline by merchant size, geography, tax jurisdiction, integration type, API version, checkout flow, billing product, platform account, and customer lifecycle stage.

- How to validate instrumentation, logging, dashboards, event schemas, data pipelines, and recent metric-definition changes before assuming user behavior changed.

- How to generate hypotheses across product changes, API or SDK regressions, pricing or packaging changes, compliance rule updates, merchant-side implementation issues, support incidents, and external market factors.

- What evidence you would seek from product analytics, payment/tax calculation logs, error rates, latency, merchant support tickets, account-manager feedback, changelogs, and experiment history.

- How to distinguish between reduced usage, failed usage, hidden fallback behavior, migration to alternative tax workflows, and delayed reporting.

- What short-term mitigations, escalation paths, merchant communications, and rollback options may be appropriate if the issue is confirmed.

- What monitoring, alerting, ownership, and post-incident prevention steps should be established to prevent similar drops from going undetected.

The goal is to demonstrate a structured, evidence-led RCA approach that can separate signal from noise, narrow the affected surface area, protect enterprise merchants from tax and revenue disruption, and guide Stripe toward a confident diagnosis without jumping prematurely to a single cause.