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

replay q1 2025 objectives #10197

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
+35 −14
Open

replay q1 2025 objectives #10197

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0a45c95
first draft
pauldambra Dec 20, 2024
b167f78
text pass
pauldambra Jan 8, 2025
c5fe652
be honest about what will be happening
pauldambra Jan 8, 2025
65e454b
Fix typos
Jan 8, 2025
03118c1
more
pauldambra Jan 8, 2025
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
49 changes: 35 additions & 14 deletions contents/teams/replay/objectives.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,20 +1,41 @@
# 📱Goal 1: People think of PostHog as a mobile solution
# 🚀 Goal 1: Get Alex rocketing

* onboard Yiannis and get him rocketing
* mobile replay out of beta
* flutter replay
it's great to have Alex on the team... let's make it a success

# 📹 Goal 2: Replay playback 4000
# 👩‍🔬 Goal 2: Churn and retention exploration

Copy link
Member Author

@pauldambra pauldambra Jan 8, 2025 •
edited
Loading

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

* Replay UX Overview
* we've invited @corywatilo to our November offsite where we will decide what this means for the last eighth of the year...
* replay playback performance
* we believe that if we improve playback we will see waiting time decrease, watch time increase, and number of recordings watched increase
* we believe that those metrics are strong proxies for customer satisfaction in replay
We've had a lot of technology focus, let's have some product focus

# 🎤 Goal 3: Ship the things users keep asking for
This is a relatively vague goal, because we don't know enough to be specific. The goal is at a minimum to get to a place where we're operating from good knowledge

* queryable network data
* start replay on trigger e.g. event
* find the user groups (e.g. low recording count vs high recording count)
* talk to those users
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

* find good metrics
* run experiments to improve things
* come out of this quarter either happy we can focus elsewhere or with a strong understanding of where to go next

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

We've got good evidence that some customers need help finding which recordings to watch. We want to help people more quickly find the right recordings to watch.
And logically once you have more than ~1 hour of recordings a day you can't watch them all and need help finding the valuable ones

* HogBot
* part 1 was very simple but people liked it... let's grow HogBot
* bring people back into the product from email or slack by highlighting what they want to watch
* Magic playlists
* playlists are not used much but people who use them like them and have diverse reasons
* we can autogenerate useful playlists and prompt you when they have new recordings

# 💀 Goal 4: Squash distractions

1) Get our deployment of rrweb under control
2024 was interrupted by tech twiddling of rrweb. Ugrades, patching, contributing upstream.

It was unpredictable and disruptive. We've got a good relationship with the contributors and made some improvements but we need to get past this!

* incremental rollouts of rrweb and recorder changes
* no more patching of npm packages

2) Write optimised blob-ingestion

CDP are going to do this but will take at least @pauldambra's time in support
Loading