PostHog

a new icon has appeared in our internal posthog project. ??

a little WIP

Who is more valuable? 1. Someone who occasionally does something very visible and noteworthy. 2. The person who does their job to a consistently high standard every day? It’s a false comparison, really. They’re both valuable, and they’re not mutually exclusive qualities, but which you praise most often says a lot about your company or team. Teams that praise highly visible contributions more than day-to-day excellence foster resentment, cynicism, and success theater. Why bother doing your job consistently when conspicuous one-off success is what gets noticed? Most people don’t nail their jobs every day. Make a habit of recognizing those who do and their success will compound throughout your team. What we’ve learned PostHog – We made “acknowledgments” a core part of our weekly company all-hands. It’s explicitly for thanking people for their work, rather than praising major milestones.

?? + ?? = ?? We had a chat with Octomind about how they've combined PostHog and HubSpot to improve their marketing strategy and get better web analytics insights. https://lnkd.in/eVSjWadP

Our newsletter, Product for Engineers, has just reached 20k subs! ?? These are the 5 most read issues we've published so far... 42k reads – The magic of small engineering teams by James Temperton: https://lnkd.in/g5pSpNyh 24.4k reads – A/B testing mistakes I learned the hard way by Lior Neu-ner: https://lnkd.in/eHBP69Em 17.8k reads – Beyond the 10x engineer by Ian Vanagashttps://lnkd.in/eZCy2yFd 17.8k reads – Hiring (and managing) cracked engineers by Charles Cook: https://lnkd.in/ey6kpp9U 17k reads – Defining our ICP was the most important thing we ever did by Andy Vandervell: https://lnkd.in/eQsWN-rN

?? If you use PostHog and your job title includes the word ‘Marketing’, I want to hear from you for some upcoming articles. DM, or email [email protected] to chat! Bonus points if you’ve never used any other analytics platform before.

What's the difference between a *software* engineer and a *growth* engineer? It's all in the mindset. ?? Hypothesis over requirements.? Software engineers work on features users clearly need. Growth engineers work on more unknowns and care more about exploration and discovery. To do this, they develop hypotheses and run experiments to validate their assumptions. ?? Iteration over stability.? While most engineers focus on developing stable, bug-free code, growth engineers would rather fail fast and iterate. For example, a software engineer might feel uncomfortable adding a dependency before evaluating it, while a growth engineer will ship it to help them test faster. ?? Pragmatism over perfection.? Growth engineers know their experiments might fail and get removed. This means they ship the "good enough" version over the maintainable and scalable one. They know they can always improve it later. Words by Ian Vanagas in 'How to think like a growth engineer' Read the full post: https://lnkd.in/eqZgAPUA

You can now sort your replays by: ?? Length (total duration, active time, or inactive time) ??? Activity (most clicks, key presses, or mouse movement) ?? Errors (showing replays with the most errors first) This makes it easier to find recordings that include the things you're looking for. Choosing 'most clicks', for example, will show you replays where the user completed lots of actions. Choosing errors will help you find areas of your app that have the most problems that need fixing.

One of our most requested features is now available as a beta: React Native session replay. It supports all the usual replay features, such as masking sensitive content, and is quick to setup too. React Native replays will remain in beta while we gather feedback and file off any rough edges. If you want to see it reach general release quickly then be sure to send us your feedback!