• 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
  • Small teams
  • Experimentation

Experimentation Team

Last updated: Oct 31, 2022

On this page

  • People
  • Mission
  • Q4 2022 Goals
  • Values
  • Personas
  • Company Persona
  • User Persona
  • Jobs to be done
  • Feature flags
  • Experimentation
  • Feature ownership

People

  • @EDsCODE (Team lead)
  • @liyiy (Engineer)
  • @neilkakkar (Engineer)

Mission

Makers everywhere get better at building products because of PostHog

Q4 2022 Goals

Objective: Make feature flags incredible to use for customers with 3-15 engineers (currently we have 10 customers with 3+ engineers who have created a feature flag in the last 30 days)

  • Key Result: Launch remaining major platforms (with large marketing support to further drive adoption)
    • iOS
    • Android
    • Flutter
  • Key Result: 5 happy teams on permission and alerting features
    • alerting/notification hooks to slack
    • access control
    • prevent accidental rollouts - 100% rollout should be loud and clear
  • Key Result: 5 happy teams using feature flags based on cohorts
    • bulk add emails to cohorts
    • view cohorts by organization
    • edit static cohorts
    • cohort creation improvement, flexible user additions
    • cohorts by groups
  • Key Result: Release beta of developer integrated features with 5 users
    • connect codebase and show feature flag coverage by branch
    • reorient feature flag page to show flags that are active AND implemented
    • Opportunity: Allow debugging integrations to be added and do issue tracking related to possible active feature flags
    • (stretch goal) CI implementation that allows people to check flags in code deployment against what's active + exists
  • Rationale:
    • We want feature flags to be used across larger engineering teams. Currently we aren't solving their needs fully but we have a clear path to doing so.

Objective: Launch Direct SQL Querying Beta

  • Key Result:

    • Five beta users who retain for three weeks
  • Key Result:

    • Understand the possible product directions to extend direct sql querying
  • Rationale:

    • To fully support our technical users, we need to allow them to ask any sort of question about their data that might not be fit for an interface

Values

  • Fast, iterative and high output rather not slow and thoughtful - achieving this
  • Feedback-driven not spec-driven - we do a decent job at this
  • Missionary (we have a clear problem definition and are aligned on how impactful a solution would be) not mercenary - glimpses of this
  • Collaborative not lone wolf - glimpses of this

Personas

Company Persona

  • Primary
    • Size:
      • 20-75 employees
    • Stage:
      • Post-PMF
      • Series A-D
    • Customer type:
      • B2B/B2C/(B2B2C)
    • High expectation traits:
      • Use the modern data stack
      • Frontend uses typescript and react
      • High-growth
  • Not:
    • API companies
    • Shopify stores/no-code companies

User Persona

  • Primary
    • Role
      • Product-minded front-end engineer
      • Growth engineer
    • Seniority
      • Decision-making seat on product
      • Senior engineer
      • IC
    • High expectation traits
      • Reads HackerNews
      • Educated about the other feature flagging/experimentation tools in the space
      • Needs high-reliability and high-performance
      • Uses best-in-class tools such as Linear/Figma
  • Secondary:
    • Role:
      • Product Manager
  • Not:
    • Role:
      • Backend engineer
      • Marketing

Jobs to be done

Feature flags

  • Primary
    • Safely rollout frontend features with the least risk
  • Secondary
    • Persistent feature flags e.g. country/pay gate
    • Build/test in production
    • Enable beta users to try out experimental features ahead of time

Experimentation

  • Primary
    • Test whether a particular feature achieves the desired change in user behavior

Feature ownership

You can find out more about the features we own here

Questions?

Was this page useful?

Next article

Growth Team

People Emanuele Capparelli (Growth Engineer) Mission PostHog's company growth targets are met every quarter Q4 2022 Objective Start charging for session recordings resulting in a $100K increase in ARR from new customers (joint goal with Session Recording team ) What the Growth team does Each month, the Growth and Exec team carry on a Growth review session to accelerate growth work, as well as define tasks for the Growth team. The Growth team focuses on Activation metrics, namely: Signup…

Read next article

Authors

  • lharries
    lharries
  • Paul Hultgren
    Paul Hultgren
  • Cory Watilo
    Cory Watilo

Share

Jump to:

  • People
  • Mission
  • Q4 2022 Goals
  • Values
  • Personas
  • Company Persona
  • User Persona
  • Jobs to be done
  • Feature flags
  • Experimentation
  • Feature ownership
  • 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