I aligned on scope: Facebook core app only. We’re investigating a ~10% drop in total sessions over ~6 months.
Metric sanity: “Active session” = logged-in user opens app and uses it until background/close. No definition or pipeline changes. Pattern: Western Europe-skewed, gradual (1–2%/mo), disproportionately <18 users. That timing + cohort screams policy-driven behavior vs. a single feature bug.
Quick externals pulse: similar session softness reported by other social apps in the region. In the same window, GDPR-derived youth safeguards tightened; countries pushed parental controls/limits. Treat as primary hypothesis.
I mapped likely impact vectors from parental controls:
Time caps: daily limits exhaust quickly → fewer sessions after the cap.
Content gating: stricter filters reduce engaging inventory → fewer voluntary opens.
Perceived surveillance: teens avoid app if they think parents can see activity.
Journey scan (for <18 in WEU):
Launch → feed loads fine.
Discovery → eligible content pool smaller; games/apps and certain Pages/Groups hidden.
Session end → hard stop when device/app time cap triggers.
Everything points to policy-induced ceiling on sessions, not breakage.
RCA (succinct): Sessions ↓ because youth sessions in Western Europe ↓; those declined due to GDPR/parental-control enforcement (time caps + content restrictions) that limit both time available and appeal of content. Not a measurement issue; not an isolated product bug.
Immediate actions (0–4 weeks):
Compliance-first, engagement-safe rails (no dark patterns):
– Build kid-safe high-retention bundles (edu mini-games, creativity prompts, moderated challenges) that fit within policy.
– Session pacing: pre-cap countdown + “resume later” save states so a cut-off doesn’t feel punitive.
– Smart notifications after caps reset (next day), opt-in and parent-approved.Parent UX: clearer granular controls (e.g., learning vs. social time buckets), one-tap temporary extensions for school tasks.
Inventory adaptation: expand family-safe Reels/shorts and curated creator lanes suitable for <18 to improve hit-rate within constraints.
Follow-ups (1–3 months):
Time budgeting: default daily schedule (e.g., 2× short windows after school) that spreads sessions vs. burning the cap at once (parents opt-in).
Content labeling & recs: finer age-suitability tags + recommender tuned to high-value, low-risk content types for teens.
Education partnerships: vetted educational creators/NGOs to enrich the teen-safe catalog.
Policy telemetry: per-country dashboards (cap set, cap used, blocks, content unavailability) to separate policy ceiling from product friction.
Longer-term (3–9 months):
Youth mode as a cohesive surface: distinct design, positive social mechanics (co-creation, clubs with tight moderation), and low-stimulation defaults.
Research-backed wellbeing guardrails: enforce session cooldowns and bedtime protection; publish transparency reports to regulators/parents.
Ad ecosystem shift: grow kid/parent-appropriate advertisers (education, hobbies, sports) with strict review → restores monetization without violating policy.
How I’d measure recovery:
North Star: Sessions per under-18 user in WEU stabilized, then +X% vs. post-regulation trough (within compliance).
Leading indicators:
– Cap utilization shape (more, shorter sessions vs. one long burn).
– Eligible content CTR/retention ↑ in teen-safe catalog.
– Parent control edits: adoption of granular buckets, temporary extensions.Quality/Compliance checks: Policy violations flat/↓; safety incidents ↓; regulator inquiries/tickets ↓.
One-liner summary I’d give in the room: This is a regulation-driven, teen-cohort session ceiling in Western Europe—not a bug; we’ll optimize within the new constraints by improving teen-safe content and pacing, giving parents better granularity, and reshaping recommendations so available time turns into more (and healthier) sessions.