Diagnose a sudden drop in team visibility for local services marketplace

Problem Statement Description

You are the product manager for a local services marketplace where customers discover, compare, and contact service providers such as cleaners, plumbers, tutors, repair specialists, and home professionals. A key paid offering allows premium subscribers to showcase their teams or crews more prominently across search results, category pages, profile pages, and lead-matching experiences.

Over the past day, the business has observed a sudden drop in “team visibility” for premium subscribers. This could mean fewer premium teams appearing to customers, lower impressions in marketplace surfaces, reduced ranking presence, missing team cards, or degraded exposure in lead-generation flows. The issue is important because premium subscribers pay for enhanced visibility, and a sustained drop could affect trust, renewals, lead volume, and marketplace supply quality.

Your task is to diagnose the issue before recommending fixes. Focus on how you would frame the anomaly, validate that it is real, isolate affected users and surfaces, inspect instrumentation, generate hypotheses, gather evidence, and decide what immediate mitigations or longer-term prevention mechanisms may be needed.

The experience should consider:

- How “team visibility” is defined, including numerator, denominator, marketplace surface, and expected baseline.

- Which premium subscribers are affected by geography, service category, subscription tier, device, app/web surface, ranking bucket, or traffic source.

- Whether the drop is real user impact or a measurement, logging, dashboard, or data pipeline issue.

- Recent changes that could affect visibility, such as ranking updates, eligibility rules, subscription enforcement, moderation filters, inventory changes, experiments, or release rollouts.

- Marketplace-side factors such as demand shifts, customer search behavior, provider availability, team capacity, profile completeness, or location matching.

- How to compare premium subscribers against non-premium providers, historical cohorts, control groups, and unaffected regions or categories.

- What evidence would be needed before escalating, rolling back, communicating with affected subscribers, or applying temporary mitigation.

- How to prevent recurrence through monitoring, alerting, ownership, QA checks, and clearer visibility health metrics.

The goal is to demonstrate a structured root-cause analysis approach for a hard marketplace incident: clarify the metric, determine blast radius, separate instrumentation from product reality, prioritize hypotheses, identify the most likely cause using evidence, and outline how the team should stabilize the experience without prematurely jumping to a fix.