Goals

Q2 2026 objectives

Query performance Improvements Robbie CoomberRobbie Coomber

Query performance across the app needs to improve to support our largest customers.

• Finish backfilling sessions v3 on the new cluster
• Fix the gaps in our query tagging
• Ensure that new teams are created with an internal/test user cohort and help big customers migrate onto this
• Explore person ID sharding and help other teams use preaggregation
• Improve custom query performance with DMAT columns / and EAV table Sandy SpicerSandy Spicer
• Improve the query codebase Sandy SpicerSandy Spicer

Event schema Sandy SpicerSandy Spicer

Continue improving this feature

• Add support for blocking events that don't match the schema

Event schema Andy ZhaoAndy Zhao

The taxonomy filter contributes to posthog feeling slow, and we can also help out posthog-ai by keeping the taxonomy recent, accurate, and fast

• Expand properties-rs to capture property values as well as property names
• Ensure that posthog-ai has access to a good quality taxonomy

Handbook

Who are we building for?

Personas

• Primary Personas:
  • Product engineer
    • These are the engineers building the product. Normally full-stack engineers skewing frontend or frontend engineers.
    • Product engineers have more limited time. Need to quickly get high-quality insights to inform what they are building and assess what they've shipped.
  • Product manager (ex-engineer type)
    • Supports the product teams (engineers, PMs, designers) to build the best products. They guide the product roadmap by speaking to customers and diving into the data.
    • Product managers are the power-users of analytics (further evidence in the data analysis of paying users). They have desire and the time to go significantly deeper into the data.
• Limited focus:
  • Growth engineer
• Not a focus but should be usable by:
  • Everyone in the product team (less technical PMs, designers)
  • Marketing
  • Leadership team