@stipelelas@posthog disagree on master-of-none, our core products are world class. do agree we have a longer tail of products that don't get the same resources. which ones in particular have you noticed/you'd want us to invest more in?
Part of being as transparent as possible is sharing info about potentially awkward moments, like when people leave PostHog.
Just had a team member share their exit feedback, so I shared it with all employees (with permission!).
My main takeaways:
- we need to invest more in product design
- there's a missing layer of product thinking below James and me
- we need to start facilitating 360 feedback from people on different teams (right now it's all from immediate teammates)
The cost of coordination is often way larger than the cost of some duplicative work across an org.
This came up last week in our slack when someone cross checked our teams' Q4 goals.
- it costs a lot in overhead to silo tasks
- in most cases different teams' work will be better if it bleeds over anyways
- it's dumb to spend too much time directing people
@TomHacohen let me know if you figure this out! we’re doing a lot of defining boundaries in the codebase so it’s more deterministic but still huge amounts of tests
@j_becke@kylegawley appreciate the feedback! we are simplifying our website
have you tried using posthog ai or mcp to create charts? it’s a much better experience than the chart builder tbh