PMMockr

QuestionsRoot Cause AnalysisMeta

Creator Studio engagement dropped 20% in two weeks among advertisers. Diagnose the issue

Problem Statement Description

Product context: Meta is a social technology company; its products include Facebook, Instagram, WhatsApp, Messenger, Threads, Quest, creator tools, and ads.

Meta’s Creator Studio is used by advertisers and their teams to manage content, publishing, monetization, insights, and campaign-related creative workflows across Meta surfaces. Over the last two weeks, engagement among advertiser users has dropped by 20%, raising concern that advertisers may be encountering workflow friction, measurement issues, product regressions, or shifting behavior to other tools or platforms.

You are asked to diagnose the issue as a product manager. Treat this as a live root-cause analysis problem: clarify what “engagement” means, determine whether the decline is real, isolate where and for whom it is happening, and identify the most likely causes without jumping directly to a fix.

Your investigation should account for Meta’s ecosystem dynamics, including advertiser dependence on reliable publishing, creative management, performance insights, team workflows, and ads efficiency. Consider both internal causes such as product changes, instrumentation, access, latency, policy enforcement, or UX regressions, and external factors such as seasonality, competitor behavior, privacy/platform changes, or shifts in advertiser budgets.

The experience should consider:

- How to define the engagement metric, including numerator, denominator, frequency, and whether it reflects meaningful advertiser value.

- How to validate the anomaly through instrumentation checks, logging changes, data pipeline issues, bot filtering, account eligibility, or dashboard changes.

- How to segment the drop by advertiser type, geography, platform, device, account size, objective, surface, workflow step, and new versus returning users.

- How to distinguish between fewer advertisers using Creator Studio and existing advertisers using it less deeply.

- What recent launches, experiments, policy changes, permission changes, API updates, outages, latency issues, or notification changes may have affected usage.

- What user journey evidence, funnel analysis, support tickets, qualitative feedback, and behavioral data would help confirm or reject hypotheses.

- How to assess business impact across advertiser retention, content publishing, campaign performance, creator monetization, and ads revenue risk.

- How to prioritize mitigation, communicate findings, monitor recovery, and prevent similar drops from recurring.

The goal is to demonstrate a structured RCA approach that moves from metric validation to segmentation, hypothesis generation, evidence gathering, impact assessment, mitigation, and prevention in a Meta-scale advertiser product environment.

What this question tests

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.

Start a timed mock interview

Related Root Cause Analysis questions

All Root Cause Analysis questions · Product manager interview questions by skill area