What do I do as a Product Manager?

Summary — What a Product Manager (PM) does

Source: Chloe (Product Manager at TikTok; formerly Boeing, Google, Caffeine, Facebook)

Core role and positioning

• PMs sit at the intersection of user experience, engineering/technology, and business (revenue, growth, safety, PR).
• Primary job: launch features that move business and user metrics, then iterate until the experience is right.
• PMs are staffed to specific product teams (not “PM of Company”); organizations are typically split by user experiences (creator, viewer, growth, monetization, insights) or by feature clusters (share button, go‑live, feed, notifications).

Frameworks, processes, and playbooks

Three-part product mandate (Todd Jackson framing):

1. Articulate what a winning product looks like (define north star / activation / aha).
2. Rally cross‑functional teams to build it.
3. Iterate until it succeeds.

Product decomposition and team scoping

• Organize teams by vertical experience or feature cluster.
• Expect product trade-offs and cross‑team impact; scope teams to limit ownership and responsibility.

Persona → problem → solutions → prioritize → roadmap

• Use design workshops and cross‑functional whiteboarding to define user personas and people‑problem statements.
• Brainstorm multiple feature solutions for each problem and ruthlessly prioritize those that move the north star.

North‑star / activation metric definition

• Use deep analysis to find the “aha” / activation thresholds that correlate with retention rather than relying on vanity metrics.

Product development lifecycle (playbook)

1. Understand and scope (UX mocks, copy/content strategy, success metrics).
2. Create the PRD (Product Requirements Document) — authored and owned by the PM.
3. Run cross‑functional reviews (product, design, data, legal/partnerships/ops).
4. Engineering technical review (client/server architecture, edge cases, effort estimates, tech debt).
5. QA and release testing; staged rollout (canary / small audience → global).
6. Ensure instrumentation/event logging; analyze results post‑launch.
7. Post‑launch: celebrate wins, report results, run postmortem and repeat.

Stakeholder alignment and communications

• Maintain group chats and frequent stakeholder updates explaining prioritization decisions and releases.
• Keep accessible docs that capture rationale, trade‑offs, and status.

Key metrics, KPIs, targets & examples

• North‑star / activation examples used as templates for PM thinking:
  • Slack: moved from raw “spaces created” to an activation milestone (space with ≥3 members and ≥3,000 messages) based on retention correlation.
  • Facebook: activation = “7 friends in 10 days” as the aha moment predictive of retention.
• Typical PM time allocation (meta KPI for role/time management):
  • Approximately 60% meetings, 30% documentation, 10% group/chat coordination (speaker’s estimate).
• Release and evaluation cadence:
  • Perform a staged rollout, analyze events/metrics after a few weeks, then produce a report and postmortem.

Concrete examples & case studies

• Org/team examples: creator experience, user growth, ads & monetization, creator insights, viewer experience.
• Feature cluster examples: share button, go‑live button, notifications, admin settings, feed, event creation flow.
• Trade‑off example: Instagram Stories launch likely reduced engagement/time for Instagram Posts — a demonstration of cross‑team/product trade‑offs.
• People‑problem → solution example (Facebook onboarding):
  • Problem: New users can’t find friends on the platform.
  • Solutions: suggested friends list; import contacts/emails during signup; browse profiles by network or school.
• Activation metric models: Slack and Facebook examples above serve as models for data‑driven north‑star selection.

Actionable recommendations for PMs and product teams

• Define an activation / north‑star metric grounded in retention analysis; avoid vanity metrics.
• Run cross‑functional design workshops to map personas → people‑problems → candidate features.
• Prioritize ruthlessly: focus on features that move the north star and have acceptable technical cost/ROI.
• Own and iterate on the PRD; expect many review cycles and understand cross‑team ecosystem effects.
• Coordinate early with engineering on technical cost, A/B test needs, and tech debt implications.
• Use staged rollouts and ensure instrumentation is in place before full launch.
• Post‑launch: measure, report, celebrate wins, and run a postmortem with documented learnings.
• Maintain active communication channels and accessible documentation for stakeholders.

Operational and organizational tactics

• Structure teams around experiences or feature clusters to limit scope and ensure clear ownership.
• Plan releases with cross‑team sign‑offs to avoid cannibalizing other metrics or features.
• Apply iterative development: v1 → test → learn → expand or pivot.
• Use data‑driven correlation analysis to set activation thresholds and determine feature success.

Presenter / source

• Chloe — host of “Colors of Chloe”; product manager working in the creator space; formerly at Boeing, Google, Caffeine, and Facebook; currently at TikTok.