Sprint - Jan 27 - Feb 7

[marandaneto]

Global Sprint Planning

3 things that might take us down

1. hot partitions
2. capture limits

Urgent incident follow-ups

https://github.com/orgs/PostHog/projects/103/views/2

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

# Team ___

**Support hero:** ___

## Retro

<!-- Grab the high and low priority items from last time and add whether that item was completed or not -->

- 

## Hang over items from previous sprint

<!-- For each item, decide to re-prioritise (and add below) or deprioritise -->

- Item 1. prioritised/deprioritise

## OKR

1. OKR, status (red/yellow/green) and action points if yellow/red


### High priority

-

### Low priority / side quests

-

[marandaneto]

Team Surveys

• Support hero @lucasheriques
• SDK Support hero @marandaneto
• In person Lucas onboarding - Seattle 27th-31st Jan.
• 1 day PTO each of us

Retro

• Support hero is tricky when you don't know the full stack @marandaneto
• Q1 planning worked well @marandaneto
• Having the freedom to take PTO @ioannisj
• Need to a better job remembering to follow up on stuff and closing issues @lucasheriques

Retro

High priority

🟢=finished 🟡=in progress 🔴=won't finish ⚪=not started

Surveys:

• 🟢 Q1 planning @marandaneto and team
• 🟢 Allow admins to configure font in the survey editor @lucasheriques
• 🟢 Define a plan for Mobile surveys @marandaneto
• 🟢 More product metrics @marandaneto
  • 🟢 top survey type created
  • 🟢 top survey question type created
  • 🟢 top survey templates clicked
  • 🟡 Surveys w/ specific features (added more, some missing)
  • ⚪ top churn customers
• 🟡 Lay the foundation for Mobile surveys on iOS and React Native @marandaneto @ioannisj
  • 🟡 RN - WIP
  • 🟢 iOS - WIP

Session replay:

• 🟢 Mobile SDKs do snapshot throttling (less repeated snapshots over the wire) @marandaneto @ioannisj
• 🟢 Mobile SDKs capture webp images instead of jpg (less data over the wire) @marandaneto @ioannisj
• 🟢 iOS SDK ability to manually start and stop session recordings @ioannisj
• 🟢 Flutter SDK Widget wrapper for masking Wigets manually @marandaneto

Low priority / Side quest

Surveys:

• 🟢 Use a bar chart instead of a trendline for the survey NPS insight @lucasheriques
• 🟢 🐛 Surveys is being showed multiple times @lucasheriques
• 🟢 🐛 [Submitting a survey in preview mode should redirect to the correct question] @lucasheriques (Submiting a survey in preview mode should redirect to the correct question #27552) @lucasheriques
• 🟢 Use a bar chart instead of a trendline for the survey NPS insight @lucasheriques
• 🟢 🐛 Reducer "flagPropertyErrors" returned undefined for action set flag property error @lucasheriques
• 🔴 🐛 Wrong graph series after changing question order @lucasheriques
  • Bandaid: remove drag button from not-draft surveys
  • Figure out if the originalQuestionIndex coming from the BE is persisted since the survey first iteration to fix the responses

Session replay:

• ⚪ Finish up the network instrumentation refactoring for iOS session replay @ioannisj
  • Dropped, @ioannisj had PTO
• ⚪ Stop and resume all integrations on opt-out/opt-in - session replay @ioannisj
  • Dropped, @ioannisj had PTO

OKR

• 🟢 Improve quality
• 🟢 Mobile Surveys
• 🟡 Talk to customers
• ⚪ Finish up WIP features

High priority

• In-person Lucas onboarding @marandaneto @lucasheriques
• Survey targetting platform, eg Mobile only, Web only, etc @marandaneto @lucasheriques
• Lay the foundation for Mobile surveys on iOS and React Native @marandaneto @ioannisj
  • The goal for this sprint is that surveys are loaded and cached with all conditions in React Native
  • In iOS, we'll be doing both branching and displaying logic
• 🐛 When filtering survey responses, the charts are not updated @lucasheriques
• 🐛 Wrong graph series after changing question order @lucasheriques
  • Figure out if the originalQuestionIndex coming from the BE is persisted since the survey first iteration to fix the responses
• 🐛 Surveys not capturing responses @lucasheriques
• 🐛 Unable to Save/Launch Survey @lucasheriques
• 🐛 Changes are lost on save when editing a survey that contains errors @lucasheriques
• Required answer on a survey @lucasheriques
• Reach out to AEs for customers actively using surveys, start building a closer relationship with them @lucasheriques

Low priority / Side quest

• 🐛 Survey was shown to only one user, but it says 3 unique users have seen it @lucasheriques
• 🐛 Surveys - Increase the number of allowed choices for single and multiple choices questions @marandaneto
• 🐛 Inconsistent Color Scheme for NPS Feedback Categories @lucasheriques
  • Follow up to see if it's still needed as implementation changed
• 🐛 Requested URL is incorrect when PostHog host includes a path @ioannisj
• Support multiple instances for iOS SDK @ioannisj

[dmarticus]

Team Finishing Large Assignments Gradually, Swiftly (Flags)

Retro

Onboarding, hackathon, support, incidents, and some actual feature work

• @haacked – .NET SDK shipped and Fixed a few bugs.
  • 32 downloads so far of the PostHog Nuget package!
• @havenbarnes hackathon remote configs
• @havenbarnes SDK support hero
• @dmarticus
  • handled some load incidents for feature flag pgbouncer-Read
  • fixed bugs that came up during support rotation
  • added a new feature regarding project-level flag defaults
  • finished local testing of new flags, now on to the production readiness stuff

This sprint

Themes: onboarding (Lucas will be onsite in Seattle for the second week), new flags production readiness (paying down feature gaps), feature management, Phil leveling up

Time off: @haacked 5 days (and then 5 more next sprint)

• @dmarticus

  • new flags
    • this week I'm focusing on the "necessary for release" issues from this ticket
    • prep for Lucas onboarding (need to book some events)

• @havenbarnes

  • Feature management re-prioritized
    • Shipping model changes, basic UX this week
  • Remote config flags
    • Plain remote config flags launching this week, encrypted payloads in review
  • Observability improvements
  • FF support hero

• @haacked

  • onboarding ticket
  • .NET SDK missing features
    • local evaluation
    • feature_flag_called events

Support

• 1/21-1/27 @havenbarnes
• 1/27-1/31 @dmarticus

Q1 2025 Objectives

(I'm going to turn these into sub-issues so I don't have to type so much)
✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

🟡 Performance & Reliability

• 🟡 Complete migration of feature flag evaluation traffic from the legacy /decide endpoint to the new /flags endpoint (@dmarticus)
• ⚪ Establish comprehensive monitoring and observability for the feature flag platform (@dmarticus, @havenbarnes)
• ⚪ Enhance Grafana metrics to differentiate between infrastructure failures and logical errors (@dmarticus)
• ⚪ Collaborate with infrastructure team to create infrastructure cost analysis and dependency mapping with Michi (@dmarticus)
• ⚪ Improve observability of the feature flag evaluation process by tying flag evaluation results to the original request context (@havenbarnes)
• ⚪ Experiment with sampling request parameters for high-value customers to have better observability for support requests (@havenbarnes)
• ⚪ Implement actionable Sentry alerts in #alerts-feature-flags channel (@havenbarnes)
• ⚪ Integrate PostHog error tracking with new flags endpoint (@dmarticus)
• 🟡 Implement read-only flags (specifics to be defined, see the following RFC) (@havenbarnes)

🟡 Customer-Driven Innovation

• ⚪ Behavioral cohort targeting for flags (RFC here) (@dmarticus)
• 🟡 Feature management (@havenbarnes)
• ⚪ Automatically manage flag staleness (@haacked)
• ⚪ Customer research-driven features (TBD based on the findings of the market research and customer interviews)

⚪ Strategic Research

• Identify and analyze key user segments:

1. Current active users
2. Competitor users
3. Custom solution implementers
4. Potential users unaware of feature flagging

• Conduct customer interviews to identify gaps and growth opportunities
• Document findings and recommendations for product roadmap.
• More context here

🟡 SDK Spike

• ⚪ Evaluate feasibility and tradeoffs around adding feature flags to the Java SDK
• ⚪ Investigate improving the Rust SDK (add feature flag evaluation, implement the suggestions from the open issues etc.)
• 🟡 Research .NET SDK demand + feasibility @haacked
• ⚪ Fix open issues in the Python and Node SDKs: (Python, Node)

🟡 User Experience Improvements

Low-hanging, medium-impact, and largely context-free fruit that can be picked up by any team member during available capacity:

• ⚪ Consolidate boolean and multivariate flag interfaces
• ⚪ Show flag evaluation results more clearly in the flag editor UI
• ⚪ Improve the experience of syncing flags between environments
• 🟡 Anything else from the current feature flag backlog

[MichaelKutsch-ph]

Team Infra

Support: @bciaraldi

Retro

• 🟢 observability for internal-cluster deployed
• 🟢 RDS follow ups: First added indexes with switching apps to writer-instance and clean up afterwards were successfull
• 🟢 VPC CIDRs on dev: new CIDRs are active - discussing next steps for prod envs
• 🟢 Argo runbooks -> runbooks exist, inline comments...
• 🟡 infra costs - talks with Google and AWS have been happening, we're digging deeper into negotiations. Made a strong point towards AWS that we need a good deal, working on quote from GCP.
• 🟡 ArgoCD alerts: argo CD alerts are not as great as we thought, switching to prometheus metrics instead and customize alerts instead to make it usable for us
• 🟡 Incident Follow-up: Stabilizing posthog-web by splitting out local evaluation and surveys: new standard chart for django apps in the making, local eval will be rolled out very soon, surveys and other parts will follow
• 🟡 yearly SOC2 checks - three more things missing, then we're done for '25
• 🟡 Migration to Argo: migrated loads of apps to argo, mostly django is missing (see other item) -> stay tuned for the allhands (demo time)
• 🟡 Argocd workflow - started with a better argo Diff, but this takes a while to get it right
• 🟡 Move to Warpstream: mirroring 100% traffic for a week, costs are looking great, latency looks good. Taking this to the next level next sprint
• ⚪ Kafka failover - no progress due to other topics

OKR

1. 🏃 Next level ArgoCD - Continuous Delivery
2. ☁️ 🕸️ Scalable networking
3. 💰 Mr. Bezos, bring down those costs!
4. 🎮 A stable pre-prod environment

High priority

• continue argoCD alerts with prometheus alerts instead @bciaraldi
• AWS PPA @MichaelKutsch-ph
• Move Django apps to new chart version / split out local evaluation and surveys @MichaelKutsch-ph
• Get a argoCD workflow going for great DX for teams @danielxnj
• Prep Warpstream for go-live @frankh
• Kafka failover to s3 @frankh

Low priority / side quests

• move old capture to new capture @MichaelKutsch-ph
• Evaluation of Robusta.dev (better alerts, AI and fancy things...)

✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

[jurajmajerik]

Team Experiments

Retro

Anders

• 🟢 Support
  • Spent quite a bit of time on support, also answering non-escalated tickets. Learned a lot about our product and customer pain points. Biggest pain points have been no-code experiments, caching/refresh behaviour (fixed here) and confusion around how experiment exposure works (will follow this up with an RFC)
• 🟢 Correct experiment results
  Identified some issues in how we calculate things that give wrong experiment results and resolved a couple of these
  Only show supported math functions
  Apply new count stats method and fix continuous method
• 🟡 Stop throwing errors when there is no experiment data - postponed as issues with experiment results got higher priority

Daniel

• 🟢 Filtering for experiment results
  • Added a “Create dashboard” button to experiments and “Add breakdown” button to dashboards to satisfy a user at [priority customer]
• 🟢 Graduate data warehouse integration out of beta
  • Researched current usage to discover low adoption rate (~2 customers)
  • Started work on support for remaining internal and user filters, as well as funnel experiment support
  • (by @mariusandra) Fixed "Filter internal and test users" when personsOnEventsMode = PersonsOnEventsMode.PERSON_ID_NO_OVERRIDE_PROPERTIES_ON_EVENTS
  • (mostly @ivanagas) Experiments documentation polish pass
  • Customer interviews: 1, 2

Juraj

• Catching up after vacation
• SDK support this week
• Working on better diagnostics for experiment results
• UI improvements, docs updates, events instrumentation
• Refactors, clean ups of tech debt from the last quarter

Sprint goals

Support hero: @jurajmajerik

Anders

• Correct experiment results
  • Trends: only include events that are preceded by a “$feature_flag_called” event when that is the exposure criteria
• Improve "no results" handling (stop throwing errors when there is no experiment data)

Daniel

• Continue with Graduate data warehouse integration out of beta
• Change how we evaluate win probability (only against control, not other variants)

Juraj

• No-code experiment UI bugs
• Start on credible interval timeseries chart (Trends)

[pauldambra]

Team Retain-you

Support hero: @pauldambra

Retro

• support still pretty high, a lot is wrapped up in one safari bug @pauldambra
  • going to work with Haynes to try and get a faster turnaround and better set of first responses
• pretty painful local dev experience @pauldambra
• being stubborn to figure things out but enjoying that @veryayskiy

## what we shipped

Replay

• 🟡 update to rrweb 18 including getting dialog element support into front end @pauldambra
  • out in the recorder
  • PR open for player but fighing CI
• 🟡 get support back under control after xmas @pauldambra
  • local dev environment really fighting me, lovely customer helping test safari bug fixes
  • shipped a lot of UI snags
• 🟡 user interviews around "how to get value out of recording" @veryayskiy
  • first interviews done, 2 confirmed reactivations 😊
  • and more booked
• ✅ default playlists - HogBot creates playlists for everyone like templates/insights @veryayskiy
  • this is out and we're figuring out next steps
  • navbar navigation to playlists
  • and updated player to be responsive and use less space for filters
  • extra credit adding cross sell from web analytics

OKRs 🟡

1. OKR, status (red/yellow/green) and action points if yellow/red

• ✅ 🚀 Goal 1: Get Alex rocketing
• 🟡 👩‍🔬 Goal 2: Churn and retention exploration
  • talking to users and picking metrics
• 🟡 🎤 Goal 3: Watch less and get more value
  • in the short term, looking at playlists and filters to see what we can get
• 🟡 💀 Goal 4: Squash distractions
  • need support to be less tricky things heavy

High priority

• 💀 Goal 4: Squash distractions
  • ship our own rrweb https://github.com/PostHog/posthog-rrweb @pauldambra
  • ✅ fix the safari bug @pauldambra
• 👩‍🔬 Goal 2: Churn and retention exploration
  • more cross selling into replay (probably from experiments) @veryayskiy
  • measure that cross selling @veryayskiy
  • propose first version of replay churn metrics @veryayskiy

Side quests and lower priority

• 🎤 Goal 3: Watch less and get more value
  • internal and test account filtering in a personless world @pauldambra
    • we've had opposite requests from customers on how this should work
    • right now replay does not show anonymous sessions if you have a person filter present

[mariusandra]

Team DevExter's Laboratory

Retro

• Adam: keep working on components in the shadows, design system work. First components: top nav, dropdown menus, tabs and other generic layout features.
  • 🎨 Worked a lot on the new layout, learned Kea. Focusing on the design system. Got color upgrades out.
• Marius: project folders - reorganize our codebase to support the next 50+ products
  • 🟢 Product Folders PR - merged
  • 🟢 First steps done:
    • products/{early_access_features, llm_observability, messaging}/
    • common/{hogql_parser, hogvm, plugin_transpiler}/
  • 🟡 Still this week: frontend split followup, and manifest-driven backends (e.g. automatic installed apps, routes, ...). Then: migration guides.

OKR

• Build a framework where we can have 50+ products? @mariusandra
  • Defining and splitting the common layer from the rest of the apps
  • Defining and implementing boundaries between apps
  • UX changes to support the new structure
  • Every product is able to export operations (backend) and widgets (components) => AI, notebooks etc.
  • Testing independently - if you change things on one product, we only run tests for that product
• Levelling up our product quality. @adamleithp
  • Design system that is self documenting
  • Mobile support
  • Finally figure out (explain) modals vs drawers
  • More standardised components
• Anti-goal for Q1: @corywatilo
  • Fixing CI when it randomly breaks (each team owns their tests)
  • Rewrite everything
  • Implement everything ourselves

High priority

See megaissue: Team DevEx Big List Of Stuff

• Adam:
  • Keep working on the design system.
  • Project "look mom, no mouse"
  • Standardize UX for highly used interactive elements
• Marius: Gotta build fast
  • Integrate nx for build dependency management and caching. Seriously consider nx cloud (watch this 10min video).
  • Split lemon-ui from the frontend and bundle it as a single workspace package
  • Map the boundaries between projects - for all languages
• Cory:
  • Keep iterating on the designs.

Low priority / side quests

• Adam: do some design work for the new layout
• Marius: new frontend abstractions (e.g. cached loaders)

[robbie-c]

Team Web Analytics

Support hero: @robbie-c + @rafaeelaudibert

Retro

Main quest

Robbie
🟡 Finish cookieless prototype (was blocked on a review from CDP, done now, should be done this week)
🟢 Mask personal data properties (e.g. Ad IDs) in posthog-js PostHog/posthog-js#1654
⚪ Started on revenue tracking in web analytics while cookieless was blocked

Rafael
🟡 Core web vitals in beta (internal only, waiting for materialisation)

Side quests & support:

Robbie
🟢 Use fbclid in channel type calculation #27686
🟢 A tiny bit of work for query perf (#27768 and #27778)
🟢 Bugfix the session attribution explorer #27700

Rafa
🟢 Added visual regression tests for web analytics and web vitals
🟢 P75 added as a metric globally

OKR

• Finish cookieless mode
• Build marketing analytics
  • Add revenue data to web analytics
  • Get ad spend data into data warehouse and use it for per-channel analytics
• Build per-page reports
  • Core web vitals

Sprint goals

High priority

Rafael

• Actual Core Web Vitals release
• SDK performance
• Basic Web Vitals on Toolbar

Robbie

• Add revenue tracking from event properties to web analytics

[daibhin]

Team Error Tracking

@oliverb123 off one week
@daibhin off two days

Retro

🟢 Beta launched (205 users enabled). Monitoring dashboard & alerts in place. Feedback mostly positive
🟢 User group assignment shipped. Many papercuts & teething issues fixed
🟢 Good progress on performance (column materialization, Tim's HogQL improvements, sparklines rewrite)
🛑 Dropped some ongoing work (alerting & billing capture)

OKR

🟢 Migrate PostHog off Sentry
🟢 Ship the damn thing

High priority

Migrate PostHog off Sentry

• Node exception capture (js lite support) feat: error tracking posthog-js-lite#366
• Django manual exception capture (currently only sending to Sentry) chore: posthog and sentry exception capture #27836

Ship the damn thing

• Issue overview loading
  • Clamp query time ranges feat: split issue loading and redesign issue page #28083
  • "Open issue" button from Activity (redirecting to an issue from a fingerprint)
  • Issue exception loading ("latest", "earliest" or uuid)
• Stack trace improvements (issue name selection, clientside ordering, in-app toggles for ordering & full / in-app view)

Low priority / Side quests

• Add source maps to docs chore: stack trace & symbol set docs posthog.com#10527

[benjackwhite]

Team Can’t Delete Plugins (CDP)

• Support: @MarconLP

Retro

Details

• ✅ Get mappings work released @MarconLP @benjackwhite
  • Released albeit flagged until we sort out some final bits
• 🔴 Finish the error issue alerts work @benjackwhite
• 🔴 Rollout RemoteConfig @benjackwhite
• 🟡 Migrate intercom plugins with confidence @MarconLP @meikelmosby
  • We have a better plan here we will pivot to
• 🟢 Roadmap and scaffolding in place for next version of Blobby @pl (w support @benjackwhite)
• 🟢 Migrate all action webhooks to Hog functions @meikelmosby
• 🟢 Got PostHog team using Zapier hog functions instead
• 🟡 Batch imports for the customers it is focused on @oliverb123
  • Its there! We just don't want to run it till he's back from vacation
• ✅ Capture mirror for Warpstream
  • Tests went great and it's working as hoped

Other work that came in

• Big refactor - Incident on the weekend forced the hand to focus on this as it is painfully obvious that we can improve this now and is our biggest pain point
• Plan to inline plugin destinations so we can finally move off of Plugins
• Plan to get Hog Transformations started (all part of removing plugins)
• Supporting WA get cookieless tracking working
• also a bunch of mini cleanups and refactors
• Added event list viewer for the destination filters

Other thoughts

• Easy to get side tracked as there are so many things going on but hoping can be more focused next sprint
• Keen to get more involved in other work going on so we have better cross-project context and knowledge

OKRs

• 😍 People choose us for their CDP first 🟡
• 🖕 Plugins be gone 🟢
• 🚀 Warpstream for events 🟢
• 🎈 Write-optimized session replay ingestion 🟢
• 💪 We make changes and improvements to the Node services with confidence 🟢

High priority

• Inline plugin destinations @MarconLP and @benjackwhite
• Rollout new Ingestion services and remove old code @benjackwhite
• Get Team 2 using Hog transformations and get all existing transformations translated to hog functions @meikelmosby
• Google Ads and LinkedIn ads destinations finally out! @MarconLP
• Get proper production metrics for Blobby V2 on production
  • Specifically things like write costs and batch efficiency so we know how complex a solution we actually need
  • Play with the various settings to get a feeling for what the right balance is
  • Ideally get to the point where we are writing actual S3 files (albeit to a test bucket)

Low priority

• Migrate Zapier stuff to Hog Functions (this allows us to finally kill webhooks services)
• Come up with a plan to test capture Warpstream for real (even if it is just for a few hours)

[timgl]

Team Batch Export

Support hero: ___

Retro

High priority

• Batch exports: Add key-pair for snowflake exports #26692
  • Hoping to get this out this week, halfway through this
• Property filters for batch exports Property filters for Batch Exports #26415 (use hogql in the backend to do this)
  • Confident it'll be out this week - doing hogql in the backend to make it more flexible
    Low priority / side quests
• use events_recent for all batch exports github.com/orgs/PostHog/projects/114/views/7?pane=issue&itemId=92837228
  • Rolled out to 10% of teams, all seems good
• encrypt
  • completed

Hang over items from previous sprint

• Item 1. prioritised/deprioritise

OKR

• 🟢 Reliability/stability
  • Canary deployments
  • Have alerting + runbooks set up for most failure modes

• alerting for specific exports

• 🍊 UI/UX (haven't started yet)
  • Backfill UI
  • Split up logs into “user reporting + user actionable” and “internal logs”, only show the first group in the UI.
  • Make it obvious you need teams plan for 5 min exports
• Notifications (slack/email)
  • Tim to figure out what CDP is doing, come up with a plan
  • 🟢 Exports using HogQL
  • 🟢 Allow any model to be exported

High priority

• Property filters for batch exports Property filters for Batch Exports #26415 (use hogql in the backend to do this) @tomasfarias
• Export sessions table Feature request: allow sessions table to be exported via batch exports #25387 @tomasfarias
• Use distributed events table for short term backfills @rossgray
• Backfill UI Batch export: Backfill UI #27788 @rossgray

Low priority / side quests

[aspicer]

Team Product Analytics

🪓 Losing @k11kirky to the AI gods 🪓
Sad to see him go. His contributions to product analytics will not be forgotten.

Q1 2025 objectives

1. Main Goal: Make it a no-brainer for customers to use our insights

   • Research and improve insights
     • [Sandy] Funnels
       • Filters in exclusion steps
       • Optional Steps
       • Time to convert trends
     • [Thomas] User Paths
     • [Anirudh] Retention
       • Revenue Retention - connect to data warehouse
     • Data management / Non-existing tools
   • [Thomas] Better path cleaning support
   • Taxonomic Filter Improvements
     • Better organized, easier to use
     • Information about properties (schema and statistics)
   • [Anirudh] Make other non-event sources a first-class citizen of the insight ecosystem
   • Metric to track - Reduce usage of HogQL as a workaround/crutch for missing UI features

2. [Anirudh] Small Goal: Alerts v2

   • Alerts on funnels
   • Notifications through Slack

3. [Sandy] Small Goal: Shared dashboards with passwords

4. [Sandy & Anna] Research Goal: Understand activation and contraction

Retro

Support hero: @thmsobrmlr @anirudhpillai @aspicer

• Finish open topics
  • 🟢 Legacy API conversion to HogQL [Thomas]
  • 🛑 Personless events actors modal fixes [Thomas]
  • 🟢 Customizable colors in insights follow ups [Thomas]
  • 🟢 Run migration of insights from filters to query [Thomas]
  • 🟢 Dashboard creation / edit experience improvements [Peter]
  • 🛑 Dashboard Filters and Variables in URL [Peter]
  • 🟡 Deploy and monitor issues with hogql cohort calculation [Sandy]
• Insight Research and Planning
  • 🟢 Funnels & Stickiness [ Sandy ]
  • 🟢 Retention Research & Some Changes [Anirudh]
  • 🟢 User Paths [ Thomas ]

Sprint Plan

Support hero: @thmsobrmlr @anirudhpillai

• [Anirudh] Retention
  • Insight UX
  • Retention on event properties
• [Thomas] Start on paths insights changes
  • UI / UX Wins
• [Sandy] Start on funnels changes
  • Time to convert trends
• [Sandy] Fixing issues with hogql cohort calculation

[zlwaterfield]

Team Growth

Gathering data from Metabase's store
Restructuring how insights pour
Organizing each metric's flight
Watching PostHog shine more bright
Testing trust in this new place
Helping teams adapt with grace

Retro

Retro items

• @zlwaterfield
  • RBAC
    • ✅ client side checks
    • ❌ internal/external documentation
    • 🏗️ first attempt at a migration
    • ✅ talk to each product team about implementation details
    • ✅ organization member permission changes
  • ✅ Onboarding @joshsny
  • 🏗️ Customer.io transactional emails in posthog (if time) and 2FA emails (if time)
  • ✅ Billing pg-bouncer (w/ infra)
  • ✅ Backfill all usage reports and investigate drop in revenue
  • ✅ Research + play around with Dagster to improve usage reports
  • ✅ Prep metabase -> Posthog move + play around with views in DW
• @patricio-posthog
  • Keep on the analysis for January forecasting
  • Continue with the Mobile replay new pricing
• @joshsny
  • ✅ First week - onboarding and next week in SF
  • ✅ Improving some styling through onboarding process
  • ✅ Using fresh eyes to ideate on improvements for onboarding/activation and cross sell opportunities
  • ✅ Extra: Deduplicate client side identify events, cs & sales mentioned this was an onboarding issue for some clients
  • 🟡 Extra: Cross-sells for data warehouse and experiments
  • 🔴 Extra: Self serve account deletion

Q1 2025 Objectives

✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

• 🟡 Usage dashboard (Pato)
• Pricing changes(Pato)
  • 🟡 Finish Mobile Replay pricing
  • ⚪ Query API pricing
  • ⚪ Clean up billing for identified / unidentified events
• 🟡 RBAC (Zach)
• ⚪ Enterprise add-on (Zach)
• ⚪ Improve SAML (Zach)
• 🟡 Use intent data to onboard users into multiple products (Josh)
• ⚪ Surface intent data later in the users journey (Josh)
• ⚪ Move core RevOps flows off of Zapier into the billing system (tbd)

Extras (nice to haves if we have time or feel inspired)

1. 🟡 Postgres (pgbouncer + read replica) - infrastructure handling this
2. 🟡 Self serve account deletion
3. ⚪ Case insensitive emails
4. 🟡 Move all transactional emails to Customer.io
5. ⚪ 3D Secure improvements - email flows
6. 🟡 Move revenue dashboards from Metabase into PostHog
7. ⚪ Get credit cart input experiment over the line
8. ⚪ Billing endpoint performance improvements (split up)
9. ⚪ Proper callbacks for time-sensitive checks

This sprint

Time off:

• @zlwaterfield
  • RBAC
    • last client side PR
    • migrations - write + run for team 2
    • get team 2 live
  • customer.io emails set up for posthog (if time, get 2fa emails flowing)
  • metabase -> posthog move complete, this includes the DW view for invoice with annual
  • explore dagster more for usage reports
• @patricio-posthog
  • Mobile session replay pricing
  • Change period_start for annual invoices, to count them on the month the contract was signed
• @joshsny
  • ✅ Run experiment to push session replay to more users in onboarding (with the aim to make it default on)
  • 🟡 Go through competitors onboarding (Mixpanel & Amplitude, June.so & Statsig)
  • 🟡 Add cross selling instrumentation across the repo and add stats to growth dashboard
  • 🟡 Finish off experiment to product analytics cross sell
  • Resurrect the quick start section: open it by default
  • Split quick start into Product Analytics, Feature Flags & Session Replay, so we are ready for adding other products
  • RFC for paid plan by default + credits for quick start (nice to have)
  • Pet project: Eager query loading for top N queries that are grouped by interval day/week/month (unlikely to have time for). Turns out this is being actively worked on by @anirudhpillai so I am chatting with him