Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add q1 product goals #10354

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

add q1 product goals #10354

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 10 additions & 12 deletions contents/handbook/product/product-team.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,20 +42,18 @@ Product managers primarily support their teams in reaching their goals. The top

As the PM team, we are pursuing a couple of side projects each quarter with the goal of leveling up how we do Product at PostHog.

In Q4 2024, those are:
In Q1 2025, those are:

**Goal 1: Improve how we coach product engineers "how to do product"** -> Anna & Annika
* Make sure the handbook is up to date for how to collect user feedback (surveys, interviews)
* Make sure the handbook is up to date for how we do product at PostHog
* Good structure for the “how to do product as an engineer” onboarding sessions, iterated based on feedback
* More engineers are confident to do user interviews on their own
**Goal 1: Bring growth and product thinking into teams** -> Raquel
* tbd, we should have some points here so that we know how to achieve this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raquelmsmith If you want to add more detail here, please do

**Goal 2: More teams have a PM** -> Annika
* Polish the hiring process (interview questions, superday)
**Goal 2: Hire a new PM** -> Annika, with support from Anna
* Update the superday task to make it more data analysis heavy
* Hire a third PM
* New PM is set up successfully with their first team
* Anna is set up successfully with one more team

**Goal 3: Improve product tooling** -> Anna
* Come up with a better way to organise user interview notes
* Move all remaining dashboards to PostHog from Metabase (only do this if data warehouse provides 90% of the missing features we need)
**Goal 3: Identify benchmarks for metrics we should care about to make them more actionable** -> Anna
* Define what per-product metrics we care about (e.g. activation, churn)
* Based on industry benchmarks, define what "good" looks like
* Define a standard how we track these metrics across products (e.g. for churn, do we want to use a rolling 3-month average?)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@annaszell This is something @raquelmsmith and I discussed in the session replay growth review, and is probably applicable for all products, hence why I added it to this goal. Happy to help / work on this too, once we agreed on the first two points.

Essentially once we have the benchmarks, given our volatile metrics, maybe comparing every month to the benchmark doesn't make the most sense. Instead we were thinking for the benchmark comparison, calculate a rolling three month average, and compare that to the benchmark. Apparently this is what Shopify does too (quote needed).

In the growth review, we would then report on monthly churn (to have a quicker feedback loop & to spot outliers) and rolling 3 month churn (to compare to the benchmark).

Either way what we agree on we should add to the handbook, so we have it tracked for future growth reviews and PMs, hence point 4.

* Update [Product Metrics](https://posthog.com/handbook/product/metrics) with agreed-upon definitions
Loading