I went straight to engagement metrics and kind of forgot to anchor on what 'success' even means for the product.
Start by clarifying the goal of Facebook Events: to help people create, discover, and participate in real-world gatherings. Then define success through a hierarchy of metrics: user engagement (e.g., event creation, RSVPs), event fulfillment (e.g., attendance, satisfaction), and long-term ecosystem health (e.g., repeat usage, network effects). Finally, tie metrics to business value like increased time spent and user retention.
Pro tip: Emphasize that success metrics should be segmented by user type (hosts vs. attendees) and event type (public vs. private), as a one-size-fits-all metric can mislead. Also, mention the importance of counter-metrics to guard against gaming, such as spammy event invites.
Define what Facebook Events is trying to achieve: connecting people through real-world experiences. Align on the core user value: easy creation, discovery, and coordination.
Segment users into hosts and attendees, and events into categories (e.g., personal, professional, public). Recognize that success metrics may vary by segment.
Map metrics to stages: creation (number of events created, host retention), discovery (event views, search), RSVP (conversion rate), attendance (check-ins, photo shares), and post-event (feedback, repeat attendance).
Link event metrics to broader Meta goals: increased engagement (DAU/MAU), time spent, and retention. Consider monetization potential through promoted events.
Select a North Star metric (e.g., weekly active event participants) and supporting metrics. Include guardrail metrics to prevent negative behaviors like spam.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.