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

replay q1 2025 objectives #10197

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

replay q1 2025 objectives #10197

wants to merge 5 commits into from

Conversation

pauldambra
Copy link
Member

first draft

Copy link

vercel bot commented Dec 20, 2024

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

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Jan 8, 2025 3:27pm

@annikaschmid
Copy link
Contributor

Should we have a "won't do for now" list as well, e.g. the rrweb stuff, heatmaps, page reports etc.?

My other feedback would be that objective 2 is quite vague, but I think that's the nature of the objective too. My main ask there would be that we divide and conquer, e.g. while I focus more on the revenue churn for example, Paul and Alex could start with a couple of user interviews.

We can also use the first growth review to make a more concrete list of research topics (as per the new focus of the first quarterly growth review).

Copy link
Member

@raquelmsmith raquelmsmith left a comment

Choose a reason for hiding this comment

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

Vague feedback.... this doesn't feel very ambitious. I feel like the magic playlists stuff probably won't take more than a few weeks? Should we do the commenting/sharing bit?

Also agree with Annika that Goal 2 seems vague - and vague things don't usually get done. We should specifically say what we are going to do. Eg "split churn into buckets and usage vs revenue; interview 10 usage churners and 15 usage-reduces to understand why their usage trends decline; make 3 improvements from those conversations"


# 📹 Goal 2: Replay playback 4000
# 👩‍🔬 Goal 2: Churn and retention exploration
Copy link
Member Author

@pauldambra pauldambra Jan 8, 2025

Choose a reason for hiding this comment

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

from @raquelmsmith

Also agree with @annikaschmid that Goal 2 seems vague - and vague things don't usually get done. We should specifically say what we are going to do. Eg "split churn into buckets and usage vs revenue; interview 10 usage churners and 15 usage-reduces to understand why their usage trends decline; make 3 improvements from those conversations"

I think it's vague by necessity because we're starting from a place of wanting to learn. i've tried to tighten it up... for sure if we hit Q2 with "maybe churn and retention" and not something specific or something finished there's a problem


follow along in our [q4 megaissue](https://github.com/PostHog/posthog/issues/25061)
# 🎤 Goal 3: Watch less and get more value
Copy link
Member Author

Choose a reason for hiding this comment

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

from @raquelmsmith

Vague feedback.... this doesn't feel very ambitious. I feel like the magic playlists stuff probably won't take more than a few weeks? Should we do the commenting/sharing bit?

interesting! so many interruptions this last quarter mean I put a brake on my self... i'm going to add something to cover that

but (without wanting to seem to ignore the feedback) this as well isn't a complete to-do list just the published goal. I'll add a mega-issue too


* queryable network data
* start replay on trigger e.g. event
* find the user groups (e.g. low recording count vs high recording count)
Copy link
Contributor

Choose a reason for hiding this comment

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

I've rephrased the bullet points for this objective so that it's clearer to know if we have achieved it or not. We mainly want to know why people churn, so that should appear in the objective (as opposed to high/low count necessarily). I also think we have a somewhat good grasp on metrics which tells us that churn is an area to focus on, so I don't think we need to improve metric definitions, instead we should focus on the "why".

Suggested change
* find the user groups (e.g. low recording count vs high recording count)
* Bucket users into "contracted, but still using the product", "churned (from paying), but still using the product" and "churned, and stopped using the product"
* Interview 5 customers in each bucket, try survey/email outreach if necessary to increase amount of feedback
* Run 5+ experiments based on learnings
* come out of this quarter either happy we can focus elsewhere or with a strong understanding of where to go next

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.

3 participants