• Product
  • Pricing
  • Docs
  • Using PostHog
  • Community
  • Company
  • Login
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Handbook
  • People & Ops
  • Ramp up plans
  • Product Manager ramp up

Product Manager ramp up plan

Last updated: Oct 25, 2022

On this page

  • Timeline
  • Day 1
  • Week 1
  • Month 1
  • Quarter 1
  • Specialism
  • Analytics
  • Customer Research
  • Growth

This is a rough guide to ramping up as a product manager in PostHog.

Timeline

Day 1

Outcome: Get started

  • Get set up and follow your onboarding checklist
  • Do your first analysis in PostHog (e.g. Who are our biggest customers? what's the most used feature?)
  • Set up time to meet everyone in your team and understand their current strategy, motivations and risks
  • Read up about the OKRs of your team
  • Attend the Company All Hands

Week 1

Outcome: Get stuck into execution

  • Join your teams' standups
  • Learn about their current projects
  • Arrange and host 2+ calls (through customer success initially) and get feedback from customers about ongoing projects
  • Use PostHog to gather data to support with executing existing projects
  • Share an interesting finding from PostHog in the demo section of the company all hands

Month 1

Outcome: Your teams are hitting their goals faster

  • Finding opportunities to reduce scope and increase impact of big projects
  • Giving the team the context they need to design and build really amazing solutions to customer problems
  • Enabling the team move faster by finding and removing bottlenecks

Quarter 1

Outcome: Hit your goals and set the strategy for the next quarter

  • Pull out the stops to get your team across the line with their existing goals
  • Work with leadership and your team to define ambitious goals for next quarter
  • Use data and customer context to rationalize priorities

Specialism

As well as your day job with specific teams, its important we have PMs having company level impact across the following specialisms too.

Analytics

  • You're performing analyics on how customers use our products outside of your team's scope
  • This analysis defines how the company priorities what to build across product
  • You push the limits of what's possible in PostHog to help us build more advanced tools and you work with SQL to get answers to the most complex queries

Customer Research

  • You're always talking with our customers, and you intimately know how their frictions with our products
  • You're giving customer insights to every team (in and outside of product) to help them prioritize better
  • You're the first to hear about new opportunities and problems that our customers need solved and you capture this information

Growth

  • You work closely with growth engineering and leadership to understand how we can accelerate activation and revenue growth
  • You know inside-out our funnels for growth and provide the context for to make quick changes to validate hypothesis and grow faster

Questions?

Was this page useful?

Next article

Merch store

We have a merch store where our community can purchase high quality PostHog-branded merch. As we have a limited number of Shopify admins on our current plan, message Grace or Charles in the #team-people-and-ops channel if you need any help sending out merch or gift cards, as you probably won't be able to do it yourself. How do we think about merch? We care about: Quality - our merch must be something you would personally want to wear or use Sustainability - our merch shouldn't be…

Read next article

Authors

  • justinjones
    justinjones
  • Cory Watilo
    Cory Watilo

Share

Jump to:

  • Timeline
  • Day 1
  • Week 1
  • Month 1
  • Quarter 1
  • Specialism
  • Analytics
  • Customer Research
  • Growth
  • Questions?
  • Edit this page
  • Raise an issue
  • Toggle content width
  • Toggle dark mode
  • Product

  • Overview
  • Pricing
  • Product analytics
  • Session recording
  • A/B testing
  • Feature flags
  • Apps
  • Customer stories
  • PostHog vs...
  • Docs

  • Quickstart guide
  • Self-hosting
  • Installing PostHog
  • Building an app
  • API
  • Webhooks
  • How PostHog works
  • Data privacy
  • Using PostHog

  • Product manual
  • Apps manuals
  • Tutorials
  • Community

  • Questions?
  • Product roadmap
  • Contributors
  • Partners
  • Newsletter
  • Merch
  • PostHog FM
  • PostHog on GitHub
  • Handbook

  • Getting started
  • Company
  • Strategy
  • How we work
  • Small teams
  • People & Ops
  • Engineering
  • Product
  • Design
  • Marketing
  • Customer success
  • Company

  • About
  • Team
  • Investors
  • Press
  • Blog
  • FAQ
  • Support
  • Careers
© 2022 PostHog, Inc.
  • Code of conduct
  • Privacy policy
  • Terms