Feature ownership

Last updated:

|Edit this page

Each feature at PostHog has an Engineering owner. This owner is responsible for maintaining the feature (keep the lights on) and championing any efforts to improve it (e.g. by bringing up improvements in sprint planning).

When a bug or feature request comes in, we tag it with the relevant label (see labels below). The owner is responsible for then prioritizing any bug/request that comes in for each feature. This does not mean working on every bug/request, an owner can make the deliberate decision that working on something is not the best thing to work on, but every request should be looked at.

💡 The Team Platform works a bit differently. Each subteam owns certain parts of PostHog. Among other things, this helps reduce any lead time when critical fixes are needed. Please review the Team Platform page for further details.

Feature list

You can also view the list directly in GitHub and filter issues there.

AppsTeam Pipelinefeature/pipelines
ActionsTeam Product Analyticsfeature/actions
Actors ModalTeam Product Analyticsfeature/actors-modal
AnnotationsTeam Product Analyticsfeature/annotations
API StructureSecurity + core updates owned by Team Pipeline. Features owned by the relevant small teamfeature/api-structure
Async migrationsTeam Pipelinefeature/async-migrations
BITeam Product Analyticsfeature/dashboards
BillingTeam Growthfeature/billing
Client librariesCore updates owned by Team Pipeline. Features owned by the relevant small teamfeature/pipeline
CohortsTeam Product Analyticsfeature/cohorts
Correlation AnalysisTeam Product Analyticsfeature/correlation-analysis
DashboardsTeam Product Analyticsfeature/dashboards
Data ManagementTeam Product Analyticsfeature/data-management
EventsTeam Product Analyticsfeature/events
ExperimentationTeam Feature Successfeature/experimentation
Feature FlagsTeam Feature Successfeature/feature-flags
FunnelsTeam Product Analyticsfeature/funnels
Group AnalyticsTeam Product Analyticsfeature/group-analytics
HogQLTeam Product Analyticsfeature/dashboards
IngestionTeam Pipelinefeature/pipeline
LifecycleTeam Product Analyticsfeature/lifecycle
Messaging (Email, Notifications)Team Growthfeature/messaging
NotebooksTeam Replayfeature/notebooks
OnboardingTeam Growthfeature/onboarding
PathsTeam Product Analyticsfeature/paths
PersonsTeam Pipelinefeature/persons
Platform (US + EU)Team Infrastructurefeature/platform
Project Home PageTeam Product Analyticsfeature/home
Property FiltersTeam Product Analyticsfeature/filters
ReplayTeam Replayfeature/replay
RetentionTeam Product Analyticsfeature/retention
Saved InsightsTeam Product Analyticsfeature/saved-insights
Security@benjackwhite is a good reference person but it is every teams job to consider and react to security issuesfeature/security
Self-hostingTeam Infrastructurefeature/self-hosting
Session AnalyticsTeam Product Analyticsfeature/sessions
Settings (personal & project)@liyiyfeature/settings
StickinessTeam Product Analyticsfeature/stickiness
ToolbarTeam Replayfeature/toolbar
TrendsTeam Product Analyticsfeature/trends
Web AnalyticsTeam Web Analyticsfeature/web-analytics

Why did we establish feature owners?

At our Engineering Offsite in February 2022 we realized the issue that some bugs and maintenance tasks may have been falling through the cracks because there were no clear owners.

Don't just copy other products

Some of the features we are building may exist in other products already. It is fine for us to be inspired by them - there's no need to reinvent the wheel when there is already a standard way our users expect things to work. However, it is not ok for us to say 'let's copy how X does it', or to ship something with the exact same look and feel as another product. This is bad for two reasons:

  • We're highly unlikely to overtake everyone else if we just build the open source version of everything that is already out there.
  • We may expose ourselves to legal risk/challenges from those companies, especially if they can point to a public issue where we have said 'let's copy X'.


Was this page useful?

Next article

Handling an incident

Incidents are going to happen. When to raise an incident When in doubt, raise an incident. We'd much rather have declared an incident which turned out not to be an incident. Many incidents take too long to get called, or are missed completely because someone didn't ring the alarm when they had a suspicion something was wrong. To declare an incident, type /incident anywhere in Slack. This will create a new channel and send updates. Anyone can declare an incident, including non-engineers. If in…

Read next article