Pineapple on pizza

No data available

Members

Goals

Q4 2026 goals

  • PostHog Desktop: determine what the world looks like a year from now, have a point of view, and work towards it (Tim and James)
  • Better understand our costs, growth levers, and pricing on our core products
    • Built a growth model for the company (Matt)
    • Have a good handle on margins (Matt)
    • Improve our pricing and packaging (Ben B)
    • Hit the hundy (Everyone)
    • Anti-goal: do this for early stage/growing products
  • Put the engine in engineering (Paul)
    • Improve code and software quality
    • Improve CI and developer productivity
    • Make doing the boring work fun
  • Improve our positioning based on customer feedback (Charles)
  • Make observability and warehouse feel like first class data sources
    • Launch observability (logs/traces/metrics with alerts) in GA (Ben W)
    • Use observability for our own stack (Ben W)
    • Launch the warehouse in GA (Tim)
    • Auto instrument observability (Ben)
  • Rethink and simplify the core PostHog experience (sign up -> onboarding -> using) (Raquel)

Working together

The Blitzscale mini crestBlitzscale Team meets once a week to check in on immediate changes and unblock anything that needs to move fast. These meetings work best when the group stays lean, though sometimes we'll invite people outside the core team to contribute if they are working more closely on a specific area. This is particularly useful for deeper context or a new perspective on an ad-hoc basis.

A smaller meeting helps us move quickly and prevents us from overcollaborating. We've learnt that once the meeting gets too big, people become less likely to raise issues in their area and decision making slows down as a bigger group pushes for consensus instead of quick decisions.

To keep the group focused:

  • Blitzscale should be a small team, just like any other team at PostHog. We aim to keep it to fewer than six people.
  • As PostHog grows, we will add more director-level leaders but they will not necessarily join all meetings. If everyone joins the weekly meetings, the group will quickly become too large to be effective.
  • We will review who is in the weekly meeting every three months and adjust as needed.
  • Not being in the meeting does not mean your work is not important. It usually means you are doing a great job communicating everything the team might need to be aware about, so staying focused on your area is more important.

Blitzscale team members often post a weekly update in #team-blitzscale for the things they are working on that everyone should be aware of.

Handbook