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.

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

wants to merge 1 commit into from

Conversation

annikaschmid
Copy link
Contributor

Added Q1 product goals

Copy link

vercel bot commented Jan 15, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Jan 15, 2025 2:11pm

* 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 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants