• 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
      • Breaking glass to debug PostHog Cloud
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
    • 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
      • Breaking glass to debug PostHog Cloud
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
    • 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

Product announcements

Last updated: Oct 31, 2022

On this page

  • Tier 3: Service features
  • Tier 2: Core features
  • Tier 1: Major features

Marketing takes responsibility for coordinating and publicizing news about PostHog, including product announcements.

However, not all announcements require the same level of marketing support. We therefore group them into tiers which help us decide what level of investment is required from the Marketing team. Which tier applies is agreed upon by the Marketing and Product teams and agreement should be sought as early as possible if Marketing support is expected.

The steps outlined below are a general checklist and the Marketing team will cater the level of support on a case-by-case basis.

Tier 3: Service features

Service features are those which introduce changes which we do not expect to have a noticeable impact for a majority of users.

An example of a service feature would include bug fixes or minor performance improvements.

Marketing support for a service feature would typically include:

  • Including the news in the PostHog newsletter.

Tier 2: Core features

Core features are those which introduce changes which we expect to have a noticeable impact for a larger subset of users, but not a majority.

An example of a core feature would include a new plugin which integrates PostHog with a third-party platform, or a cosmetic refresh of an existing feature.

Marketing support for a core feature would typically include:

  • Creating a blog announcement about the feature within one week of launch.
  • Sharing the blog announcement with the Slack community via the #editorial channel.
  • Sharing the blog announcement on PostHog's social media channels.
  • Sharing links to the social media announcement internally via Slack, so colleagues can amplify them.
  • If relevant, sharing the blog announcement with other external parties, such as integration partners or PPC agencies.
  • Updating any required assets on PostHog.com.
  • Including the news in the PostHog newsletter.

Tier 1: Major features

Major features are those which introduce changes which we expect to have noticeable impact for a majority of users or which would represent reasons why prospective users would choose PostHog.

An example of a major feature would include the creation of a new tool, such as session recordings, or a fundamental overhaul of an existing feature.

Marketing support for a major feature would typically include:

  • Creating a blog announcement about the feature within 24 hours of launch.
  • Sharing the blog announcement with the Slack community via the #general channel.
  • Sharing the blog announcement on PostHog's social media channels and scheduling further posts in the first week.
  • Sharing links to the social media announcement internally via Slack, so colleagues can amplify them.
  • If relevant, sharing the blog announcement with other external parties, such as an integration partner or PPC agencies.
  • Creating a follow-on blog article about the feature within three weeks of launch.
  • Updating any third-party sites or listings, such as G2.com or StackShare.
  • Coordinating PR and external communications if required.
  • Updating any required assets on PostHog.com.
  • Including the news in the PostHog newsletter.

Questions?

Was this page useful?

Author

  • Joe Martin
    Joe Martin

Share

Jump to:

  • Tier 3: Service features
  • Tier 2: Core features
  • Tier 1: Major features
  • 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?
  • 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