Creator Payouts | Meta
Context: Creators and businesses on Facebook and Instagram require a payout account to receive earnings. While the core onboarding rules are identical, the supporting help documentation was scattered across three separate platforms.
The Challenge: Out of a 57-article matrix, 22 articles contained duplicate, repetitive data. This fragmented setup misaligned contextual help tools and heavily strained resources, leading to a massive Q4 backlog of 279,000+ customer support cases.
The Goal: Restructure the entire documentation ecosystem to reduce user confusion, automate data updates, and alleviate downstream support workloads
Project overview
I owned the data auditing, structural logic, and cross-functional program management from discovery to deployment:
Ecosystem Audit & Content Pruning: Audited payout documentation across three Help Centers, designing a massive content lifecycle strategy that migrated 27 articles and deprecated 37 redundant pages.
Single-Source Knowledge Architecture: Operationalized ref-ID content logic to dynamically reuse text snippets across properties, ensuring universal accuracy across surfaces without manual maintenance.
Centralized Hub Design: Engineered a centralized payouts home in the Meta Business Help Center and embedded targeted support snippets to resolve secondary user questions inline.
Cross-Functional Program Alignment: Secured critical alignment across PayOps, Product Management, and Engineering to programmatically sync automated help features with accurate product realities.
My Role
Product Manager
Content Designer
Product Engineer
Payment Operations Support Specialist
Key Collaborators
37 Redundant Pages Deprecated
Streamlined the system lifecycle by overhauling 5 articles, creating 9 new nodes, migrating 27 articles, and retiring 37 repetitive pages.
20 Support Hubs Synchronized
Established a single source of truth that stabilized the exact documentation infrastructure relied upon by 20 separate PayOps support hubs.