Conversion in marketplace trust declined after a pricing or policy change. Diagnose it

Problem Statement Description

You are investigating a decline in conversion for an enterprise-facing marketplace trust experience after a recent pricing or policy change. The marketplace helps enterprise teams evaluate whether vendors, service providers, apps, or partners are credible enough to transact with, and conversion depends heavily on confidence, transparency, perceived fairness, and risk reduction.

The decline may be tied to how the change was introduced, how it affected buyer or seller behavior, how trust signals are displayed, or whether certain enterprise segments now face more friction before completing a transaction. Your task is to frame the anomaly clearly, identify where in the funnel the drop is occurring, and build a structured diagnostic approach that separates true user behavior changes from instrumentation, seasonality, mix shift, or rollout effects.

Focus on how you would investigate the issue as a product manager working with data, engineering, operations, sales, support, and policy stakeholders. You are not expected to jump to a fix immediately; the emphasis is on forming hypotheses, validating them with evidence, and deciding what actions or mitigations should be considered based on impact and confidence.

The experience should consider:

- The exact conversion metric that declined, including numerator, denominator, funnel step, time window, and affected user journey.

- Segmentation by enterprise account size, geography, buyer role, seller category, pricing tier, acquisition channel, and new versus returning users.

- Whether the pricing or policy change was rolled out globally, partially, or experimentally, and whether exposure was measured correctly.

- Instrumentation checks such as event firing, attribution changes, tracking gaps, funnel definition changes, or dashboard regressions.

- Hypotheses around trust perception, price sensitivity, policy comprehension, seller availability, compliance burden, approval workflows, or support escalation.

- Evidence sources including funnel analytics, cohort comparisons, qualitative feedback, sales/support tickets, cancellation reasons, and marketplace supply-side behavior.

- Short-term mitigation options, communication needs, and criteria for escalating, pausing, rolling back, or continuing the change.

- Prevention mechanisms such as monitoring, experiment design, alerting, pre-launch risk review, and post-launch trust-health tracking.

The goal is to demonstrate a clear RCA approach: define the anomaly, isolate the impacted cohorts, validate or eliminate likely causes, assess business and user risk, and recommend a disciplined path toward mitigation and longer-term prevention without assuming the pricing or policy change is the only cause.