From fede47ae075a58a8a4a7a26832c3cdec8796786f Mon Sep 17 00:00:00 2001 From: Michael Matloka Date: Tue, 7 Apr 2026 13:34:27 +0200 Subject: [PATCH 1/3] Signals team Q2 2026 objectives Generated-By: PostHog Code Task-Id: 2f63c9ae-f5e3-42f9-8962-b4f07fa73163 --- contents/teams/signals/objectives.mdx | 50 ++++++++++++++++----------- 1 file changed, 30 insertions(+), 20 deletions(-) diff --git a/contents/teams/signals/objectives.mdx b/contents/teams/signals/objectives.mdx index 3277641e57c7..808f35647a4b 100644 --- a/contents/teams/signals/objectives.mdx +++ b/contents/teams/signals/objectives.mdx @@ -1,28 +1,38 @@ -## Q1 2026 +## Q2 2026 -### Objective 1: Signals & Tasks APIs (for app + Array consumption) +> **Note:** [Q2 planning doc](https://docs.google.com/document/d/1s8LQVo0UThfDx3VSEMBMp1_nmuENRBaiSDKLcTYuol4/edit?tab=t.0) +> +> Ownership will be assigned as we prioritize throughout the quarter. -What we’ll ship: -- Scheduled summarization creating signal groups, which are then turned into tasks (Alex) -- Way to schedule summarization: (Alex) - - let user provide golden paths - - let user provide features they care about +### Objective 1: 1-PR-merged-a-day -### Objective 2: Video-first session summarization +- Auto-create PRs +- Auto-creating PR autonomy slider +- Make PostHog Code Inbox UX spark joy -What we’ll ship: -- Re-architect session summarization to analyze full videos (Michael) -- Basic evals, and lots of prompt tuning for quality (Michael) -- Models iteration (Gemini 3/Claude instead of o3) (Alex) +### Objective 2: Getting users -### Objective 3: Correlating signals across products +- Make it work for PostHog team 2 +- Run user interviews with active PH Code users +- Set up Inbox usage/success/costs dashboard +- Bring back Traces hour for PH Code launch +- Reliability is non-optional -What we’ll ship: -- To experiment with: 1\. Matching signals based on relevant time ranges, 2\. Vector similarity search between signal types, 3\. Agent to run search tools to correlate signal types -- Vector search DB (Olly) +### Objective 3: Prioritization -### Objective 4: Video exports infra for exporting a double-digit % of sessions +- Making the agent run queries to determine if the problem is in a hot path +- Micro "analyze part of session visually" tool +- PostHog org member→GH user mapping needed for assignment +- Meta: Ability to reingest all signals in prod is key -What we’ll ship: -- Filter periods of inactivity from Replay and skip them when recording/analyzing (Olly) -- Replace Playwright with Puppeteer for better quality/FPS of the videos exported (Olly) +### Objective 5: Prioritized sources + +- Session Replay +- PostHog Support +- (Other teams integrating: on pause until we have confidence in core sources) + +### Objective 6: Experiments + +- "AI PM" - product autonomy → agent "owner" per product feature → run em on a cron to check feature status +- Memory +- Allow agent to schedule follow-up (esp. for LLMA + replay) From a6efc3ee6173ea497cd16e56e108c2f99d5154ed Mon Sep 17 00:00:00 2001 From: Michael Matloka Date: Tue, 7 Apr 2026 13:11:45 +0100 Subject: [PATCH 2/3] Tweak wording --- contents/teams/signals/objectives.mdx | 63 +++++++++++++++++---------- 1 file changed, 41 insertions(+), 22 deletions(-) diff --git a/contents/teams/signals/objectives.mdx b/contents/teams/signals/objectives.mdx index 808f35647a4b..d620c2fdb6e6 100644 --- a/contents/teams/signals/objectives.mdx +++ b/contents/teams/signals/objectives.mdx @@ -1,38 +1,57 @@ ## Q2 2026 -> **Note:** [Q2 planning doc](https://docs.google.com/document/d/1s8LQVo0UThfDx3VSEMBMp1_nmuENRBaiSDKLcTYuol4/edit?tab=t.0) -> -> Ownership will be assigned as we prioritize throughout the quarter. +For reference (internal-only): [Q2 planning doc](https://docs.google.com/document/d/1s8LQVo0UThfDx3VSEMBMp1_nmuENRBaiSDKLcTYuol4/edit?tab=t.0) -### Objective 1: 1-PR-merged-a-day +Going as far as it takes to make users feel Inbox is not just "cool" - but awesome. -- Auto-create PRs -- Auto-creating PR autonomy slider -- Make PostHog Code Inbox UX spark joy +Principles: +- We eat our own dog food - PostHog Inc. has to be a set of happy Inbox users, and we have a path to that +- Reliabiltity is non-optional - explicitly allocating time to reliability, including devex -### Objective 2: Getting users +_Ownership will be assigned as we prioritize throughout the quarter. Michael makes sure this happens as team lead._ -- Make it work for PostHog team 2 -- Run user interviews with active PH Code users -- Set up Inbox usage/success/costs dashboard -- Bring back Traces hour for PH Code launch -- Reliability is non-optional +### Objective 1: One PR merged a day -### Objective 3: Prioritization +Self-driving has to deliver concrete code to review and merge: +- Auto-create PRs +- Allow users to configure the level of confidence for PR creation +- Make PostHog Code Inbox UX must spark joy +- Run user interviews + - Annika will be running interviews with active PH Code users, we should take part +### Objective 2: Prioritization + +Serving "One PR merged a day": +Prioritization in the inbox has to always surfaces slam dunks above noise: - Making the agent run queries to determine if the problem is in a hot path -- Micro "analyze part of session visually" tool -- PostHog org member→GH user mapping needed for assignment -- Meta: Ability to reingest all signals in prod is key +- "Analyze part of session visually" tool for research +- Seamless PostHog org member→GH user mapping (for owner assignment) +- Ability to reingest all signals in prod + - Plus ability fo filter by pipeline version + +### Objective 3: Sources + +Specific sources have to result in salient inbox items: +- Error Tracking +- Linear +- GitHub Issues +- Zendesk +- PostHog Support +- Later in the quarter: Session Replay (much higher-effort w/ Replay team collab) + - Michael to write a spec for the person who'll help us ship here -### Objective 5: Prioritized sources +Other teams integrating: on pause until we have confidence in these core sources. -- Session Replay -- PostHog Support -- (Other teams integrating: on pause until we have confidence in core sources) +### Objective 4: Experiments -### Objective 6: Experiments +We're in delivery mode with PostHog Code launch, but when we have solid footing there. We should get back into some experimentation – we think we have some ideas that _may_ take the product to the next level, but they need to be actually tested: - "AI PM" - product autonomy → agent "owner" per product feature → run em on a cron to check feature status - Memory - Allow agent to schedule follow-up (esp. for LLMA + replay) + +### Non-objective: Pricing + +Pricing is not a priority before we feel that the Inbox is indeed _awesome_. We should just keep track of costs to keep an eye: + +- Set up Inbox usage/success/costs dashboard From fad9d4d19f59647abe88b7da013753f385f1de3d Mon Sep 17 00:00:00 2001 From: Michael Matloka Date: Wed, 8 Apr 2026 16:46:02 +0200 Subject: [PATCH 3/3] Apply Annika's cleanup --- contents/teams/signals/objectives.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/contents/teams/signals/objectives.mdx b/contents/teams/signals/objectives.mdx index d620c2fdb6e6..0453444ed747 100644 --- a/contents/teams/signals/objectives.mdx +++ b/contents/teams/signals/objectives.mdx @@ -15,14 +15,14 @@ _Ownership will be assigned as we prioritize throughout the quarter. Michael mak Self-driving has to deliver concrete code to review and merge: - Auto-create PRs - Allow users to configure the level of confidence for PR creation -- Make PostHog Code Inbox UX must spark joy +- Make PostHog Code Inbox UX spark joy - Run user interviews - Annika will be running interviews with active PH Code users, we should take part ### Objective 2: Prioritization Serving "One PR merged a day": -Prioritization in the inbox has to always surfaces slam dunks above noise: +Prioritization in the inbox has to always surface slam dunks above noise: - Making the agent run queries to determine if the problem is in a hot path - "Analyze part of session visually" tool for research - Seamless PostHog org member→GH user mapping (for owner assignment) @@ -32,7 +32,7 @@ Prioritization in the inbox has to always surfaces slam dunks above noise: ### Objective 3: Sources Specific sources have to result in salient inbox items: -- Error Tracking +- PostHog Error Tracking - Linear - GitHub Issues - Zendesk @@ -44,9 +44,9 @@ Other teams integrating: on pause until we have confidence in these core sources ### Objective 4: Experiments -We're in delivery mode with PostHog Code launch, but when we have solid footing there. We should get back into some experimentation – we think we have some ideas that _may_ take the product to the next level, but they need to be actually tested: +We're in delivery mode with PostHog Code launch, but when we have solid footing there, we should get back into some experimentation. We think we have some ideas that _may_ take the product to the next level, but they need to be actually tested: -- "AI PM" - product autonomy → agent "owner" per product feature → run em on a cron to check feature status +- AI PM: Agent as the "product owner" on a product/feature level: On a cron, the agent checks the feature status (metrics, errors etc.) & recommends actions - Memory - Allow agent to schedule follow-up (esp. for LLMA + replay)