Great tool, great company

I fell in love with PostHog (the tool AND the company) on one of my personal side projects. As technology leader responsible for Architecture and Engineering, I am now rolling this out into my enterprise globally. I love things that have been built well, with love. It is very friendly for developers (good documentation), but also for product management. PostHog enables us to track performance and UX much better than we have been able to do through other tools. Communication with team has been good (as far as I needed it) and I've been showing their Handbook and Careers site around internally as inspiration.

Nothing signification - it is a product that is continuously evolving so we'll jus t Few smaller items: - Would love to have access to more of the tracked/consumed data - the PostHog data that is made available in the SQL editor is still limited. Right now, we are still using Azure Application Insights in addition - On Session Replay, would be nice to be able to filter out console messages. Already implemented filter on events, but I find that the logs (which we use quite a bit) to be too polluted. - On Session Replay, the search box on network requests doesn't seem to work well. - We find that not all events are properly tracked (e.g., on Session Replay, the network traffic). This might be due to the client? - Being a client-side tool, we still need to correlate manually to server-side logs. There are some options around data pipelines, but this is not yet usable in our setup. From vision: would be interesting how far they will take things like feature flags / experiments. Can do a lot more there to for instance compete with LaunchDarkly

Poor performance / UX

Easy to adopt

Posthog has been easy to adopt and provided the team with significant visibility into our product usage

Difficult to come up with a dislike. It would be really nice to enter a few things about the software stack and for posthog to come up with best practices

A/B testing, visibility into product usage

A complex incredibly useful tool in our startup arsenal

Posthog's session replays were what originally got us to using it. It was incredibly helpful in understanding what our users were doing, and making sure that they were not facing any bugs. Bug reports became incredibly easy to resolve, because we could see almost everything that they would do, and once we can replicate it, we could solve for it. Since then, we've also started tracking various events in Posthog, our cohorts, grouping our users, and even making charts on product usage data. I'm honestly not sure how companies would do this before posthog, but it's been extremely useful to understanding our product usage and building a better product using this information. We use posthog every day, multiple times a day. The initial setup and integration was definitely very easy, but giving us the results we wanted, required it to be setup a specific way, which we has to figure out by trial and error. The customer support has been great though.

Since posthog offers so much, there's definitely a large learning curve before we were able to use it. Events needed to be tracked a specific way, such that we could get the insights we wanted. Creating charts was definitely not easy, because we knew what we wanted, but it was hard to figure out how to make that happen in posthog. I think we spent almost an entire month trying and failing on a lot of things. Even simple things, like when we identify a user, having that identification as a person property would have helped us quite a bit, but we had to add person properties separately while identifying the user (the same value as the distinct id). Things like this very were frustrating. There are also UI things, like in the cohort, you see a list of people, but clicking on delete, deletes that entire person, while intuitively, it should delete that person from the cohort

Understanding our users, gives us more insight into what they like, what they don't like, and shapes our product decisions